Your goal: design a secrets service that teams will actually use, with every control tied to
an asset and a path, audit and response when something leaks, a cost, and an order.
How this works (about 30 minutes)
- You're interviewing for a security engineering role at Snap. Marcus asks one design question
and goes deep on it. Ask him what you want to know about the workloads, the secrets and what
exists today. He answers one line at a time and won't volunteer. The details are made up for
the exercise.
- Lots of follow-ups on how it works underneath, one curveball, then a trade-off turn: one of
your controls worked and cost something. Keep it, change it, or scope it?
- If you want to sketch or jot, 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
- Scope first: who consumes secrets, what kinds, what exists today
- The first request solved: how a workload proves who it is without a copied secret
- The root of trust, the policies and the audit log treated as assets
- Leases, rotation and revocation; detection and a plan for the hour after a leak
- Availability taken seriously: the service is in everyone's path
- An order you can defend, and a call when a control hurts the teams
Tips
- Take Security Coach · Design: Identity and Data first.
- Ask Marcus what exists today; it changes your first step.