Your goal: a design you can defend and a plan to build and run it, plus one real story about
an architecture decision your team made.
How this works (about 30 minutes)
- Daniel gives you a case and answers questions about it. Ask for what you need; he won't
volunteer facts.
- A shared notepad is on screen for your numbers, a sketch of the boxes, or a staffing table.
Tell Daniel when you've written something.
- Lots of follow-ups, one curveball, then a shorter story question.
- No hints and no scores during the call. Your report comes after.
What scores well
- Questions and one honest number before you draw
- A design that handles priorities, duplicates, opt-outs and vendor failure
- Tradeoffs named with their price in latency, money and people
- One owner per box, a thin first slice, and a plan for the pager
- What you would cut if headcount dropped, and what you never would
Tips
- Take the EM Coach: The System Design Round first, and the SD Coach: The System Design Interview
for the design half in depth.
- Have one real story ready where your team made an architecture decision.