Your goal: show you know the OAuth flow well enough to see where it breaks, and turn every
weak step into a control, a signal and a priority.
How this works (about 30 minutes)
- You're interviewing for a security engineering role at Zoom. Marcus asks one question and
goes deep on it.
- Ask him what you want to know about the product's flows, tokens and logging. He hands it over
one line at a time and won't volunteer. The details are made up for the exercise.
- Stay at the level of steps and defenses: which step, what an attacker gets, what stops it.
- One curveball, then a trade-off turn: your control works, and something else gets worse.
Keep, change or scope it?
- Say "can I use the notepad?" if you want to sketch the flow.
- No hints and no scores during the call. Your report comes after.
What scores well
- The flow walked in order, with what each parameter (state, PKCE, redirect URI, audience) stops
- For each weak step: prevent, detect and respond, and what the control costs
- Fixes ranked for this product, not a generic list
- A call in the trade-off turn, with the number that would make you reverse it
- Answers that say where they're going and land in a minute or two
Tips
- Take Security Coach · Identity and Access first.
- Ask which clients exist (web, mobile, third-party apps) before you rank anything.