Your goal: think like an attacker in a structured way, then finish like a defender: the
cheapest path in, and the two controls that break it.
How this works (about 30 minutes)
- You're interviewing for a security engineering role at Google. Marcus asks one question about
a fictional company and goes deep on it.
- Ask him what you want to know about the company: its systems, its people, its defenses. He
hands it over one line at a time and won't volunteer. The details are made up.
- Stay at the level of stages: how they get in, how they stay, how they reach the goal. No tools,
no payloads, no exact steps.
- Then the flip: as the defender, which two controls first?
- One curveball, then a trade-off turn built from your controls.
- Say "can I use the notepad?" if you want to sketch the path.
- No hints and no scores during the call. Your report comes after.
What scores well
- A goal and an attacker chosen on purpose, with a reason
- Paths by stage, the cheapest one named, and how each step works underneath
- Two defender controls that break the cheapest path early and late, plus detection and response
- 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 · Threat Modeling first.
- Ask what the company cares about most before you choose the goal.