Your goal: explain a denial-of-service attack precisely, then respond to one in the right
order, with controls that stop the attack without turning real customers away.
How this works (about 30 minutes)
- You're interviewing for a security engineer role at Google. Marcus asks one technical
question and goes deep on it with a made-up incident.
- Ask him for what you'd look at: traffic, sources, endpoints, latency, the edge setup. He
gives one fact 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 controls.
- 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
- The kinds of denial of service, and which resource each one exhausts
- Facts before actions: confirm, size and classify before you block
- Containment at the edge, keyed to spare real users, with the cost of each limit
- Watching what real customers see, not just the attack volume
- Fixing the expensive thing the attacker leans on
- A clear call when your control hurts someone, and the number that would change it
Tips
- Take Security Coach · Networks first.
- Ask before you block: "Which endpoint, and from where?"