Your goal: answer a screen question like a working security engineer: a precise definition,
a mechanism, a ranked decision and a fix with its cost.
How this works (about 30 minutes)
- You're interviewing for a security engineer role at Google. Marcus opens with a short
motivation question, then one technical question he takes deep.
- He makes it concrete with a made-up bug report. Ask him for any facts you need; he gives them
one at a time and won't volunteer. The details are invented for the exercise.
- Lots of follow-ups, one curveball, then a trade-off turn built from your own fix.
- If you want to jot or sketch, say "can I use the notepad?" and Marcus puts it up.
- No hints and no scores during the call. Your report comes after.
What scores well
- A real moment behind "why security", not a slogan
- Vulnerability, threat and risk kept apart
- The mechanism underneath, in plain words, and where teams slip
- A decision on when to fix, from exposure, ease, asset and evidence
- A layered fix (prevent, detect, respond) with its cost, and a call when the fix hurts someone
- Saying what you don't know, and how you'd find out
Tips
- Take Security Coach · The Security Loop first.
- Ask before you assume: "Do we have access logs?"