Your goal: design security for a payments platform the way a strong candidate does: start from
what an attacker wants, tie every control to a path, and make calls with their costs to merchants.
How this works (about 45 minutes)
- One design question, taken deep for about thirty-five minutes. Marcus holds a made-up payments
platform and answers one line at a time when you ask.
- He presses on assets, how money leaves, how one mechanism works underneath, who inside can touch
what, and how you would see an attack in progress. One curveball.
- A trade-off at the end, built from the first control you chose.
- Say "can I use the notepad?" to sketch the system.
- No hints and no scores during the call. Your report comes after.
- This is practice built from a question people report for Meta. Real rounds vary, so check the
format you are given.
What scores well
- A scope in a few minutes: who uses it, what moves, what exists today
- Assets ranked with a reason, including the ones that reach everything
- Paths with an attacker, an entry and a route, ending in money or card data
- Controls that prevent, detect and respond, each tied to a path, each with its cost
- A call on the trade-off that keeps protection where the money is and removes friction elsewhere
Tips
- Take Security Coach · Secure Design (SALT) and Security Coach · Design: Identity and Data first.
- Before the round, say out loud how money leaves a payments platform. Then say how it shouldn't.