Your goal: run a whole security engineer loop the way a strong candidate does: four different rounds, each answered at the right depth, with your energy and structure intact at minute forty.
How this works (about 45 minutes)
- Part one, technical (about eleven minutes): how a firewall works and how you would configure one for a made-up company's cloud setup.
- Part two, design (about nineteen minutes): secure sign-in for that company's millions of members, with a twist near the end.
- Part three, story (about eight minutes): a time you asked for help early and avoided an outage. Pick a real one.
- Part four, leadership (about five minutes): Marcus becomes the VP of Product. Your own design has a cost; make the call in plain words.
- Ask Marcus for any fact you need; he hands them over one at a time. Everything about the company is made up. Anything else, assume and say so.
- A shared notepad is there if you want it: just ask.
- No hints and no scores during the call. One written report covers the loop.
What scores well
- How it works underneath, not product names
- Who attacks, what they want, and the path, before any control
- Controls in layers: prevent, detect and respond, each with its cost
- An order you would actually ship, and what waits
- A story with your own action and a real result
- A recommendation in the VP's words, with the trade-off and what would change your mind
Tips
- Take the module mocks first; this is all of them in one sitting.
- Reset at each switch: one breath, restate the new question, then start.