The interview framework
A repeatable path through a system design interview: requirements, estimates, API, data model, high-level design, deep dives, trade-offs and wrap-up, with a time budget.
20 min7 steps
By the end you can
- Order the stages of a system design interview and say what each one produces
- Make quick estimates that decide the design, such as total storage over years
- Choose deep dives that target the riskiest part of the design
- Budget interview time across the stages and protect time for deep dives
A path you can follow under pressure
1
Requirements
2
Estimates
3
API
4
Data model
5
High-level design
6
Deep dives
7
Trade-offs
8
Wrap-up
Put the interview stages in order.
- 1Clarify functional and non-functional requirements
- 2Deep-dive into the riskiest components
- 3Define the API
- 4State trade-offs and wrap up
- 5Define the data model and access patterns
- 6Draw the high-level design
- 7Estimate load, storage and bandwidth
Start with requirements, not boxes
Ask
- Core use cases
- Users
- Scale
- Qualities that matter most
Not yet
- Drawing boxes
Estimates that decide something
Fits one machine?
storage
Cache it?
read / write
One DB enough?
write rate
Conclusion
4 TB/yr: one DB, shard later
Loading question…
Simple first, then evolve
Dive where it could break
Pick
- Highest load
- Hardest consistency
- Most likely failure
For each, say
- How it fails
- What users see
Budget the clock
- Requirements and estimates8 min
- API, data, high-level12 min
- Deep dives15 min
- Trade-offs and wrap-up10 min
Loading question…
Check your mastery, then rehearse
Interview mode
checklist, calculator, canvas, rubric
Score 80% or more. Rehearse in interview mode.
Mastery check
4 questions on fresh variants. One attempt each, no time limit. Score 80% or more to master the lesson.
Answer this step to continue.