Mock: system design round
60 minutes on one worked-prompt shape, scored against the Staff column of the design rubric.
Use a prompt from the system design track's practice lists, or one of these (written for this site): a notification service for 100M users; a feature-flag platform; an LLM evaluation service that runs nightly for 50 teams; a document ingestion pipeline with per-document permissions.
This rubric is ours, built from published signals (for example OpenAI's "well-designed solutions, high-quality code, optimal performance, and good test coverage"). It is not any company's scoresheet. See Sources.
System design round
60:00
- Requirements and scope (8 min)
- Estimates (5 min)
- API and data model (7 min)
- High-level design (12 min)
- Deep dives (22 min)
- Wrap-up (6 min)
Score yourself (or have a partner score you)
Past attempts
Practice
Written for this site to drill the lesson. Not reported interview questions.
- Write a one-paragraph summary of your design and its top two risks right after the timer ends.
Check yourself
Which rubric row most separates Staff from Senior?
Trade-offs: naming each decision's cost and when it would flip.
Saved in this browser.