The high-level design interview: a step-by-step answer framework
A repeatable order of steps for answering any 'Design X' question in about 45 minutes.
Why it matters
Under pressure, most people either freeze or start drawing boxes before they understand the question. Both lose marks. A fixed method gives you something to do in every minute, and shows the interviewer how you think.
The idea
Interviewers judge how you think, not whether you reach one 'right' design. A framework stops you jumping straight to boxes and arrows. The usual order: clarify requirements, estimate the scale, define the API, sketch the data model, draw a simple design that works, then go deep on the hardest parts and discuss trade-offs.
An architect meeting a client. They ask how many people will live in the house and what it is for before they draw anything.
A client answers once. In an interview you keep checking in ('does this match what you had in mind?'), and the interviewer may change the requirements halfway on purpose to see how you adapt.
How it works
- Requirements: ask who uses the system and what the 3–4 core features are. For a URL shortener: 'Do we need custom aliases? Expiry? Click analytics?' Then the non-functional side: 'How many users? Is a slightly stale read acceptable?' Write the answers in a corner of the board.
- Estimates: turn the numbers into requests per second and storage. Say each assumption out loud, for example 'I'll assume 100 reads for every write'.
- API: write 2–4 endpoints with their inputs and outputs. This fixes exactly what the system must do.
- Data model: list the main tables or objects and their keys. Ask yourself: what is the main query, and which key does it use?
- High-level design: draw client → load balancer → service → database, and walk one request through it. Make it work before you make it big.
- Deep dives: find the bottleneck from your estimates (reads, writes or storage) and fix it with caching, replicas, sharding or queues. Explain each choice and what it costs.
- Wrap-up: summarise the design in three sentences, name its weak spots, and say what you would monitor.
Example
For 'Design a URL shortener': 3 minutes on requirements (shorten, redirect, custom alias? expiry?), 3 on estimates (100 million new links a month), 3 on the API (POST /urls, GET /{code}), then the simple design, then a deep dive on generating unique short codes.
Key points
- 1. Requirements (about 5 min): functional (what it does) and non-functional (scale, latency, availability, consistency). Write them down.
- 2. Estimates (about 3 min): users, requests per second, storage, bandwidth. Only as much as changes a decision.
- 3. API (about 3 min): the main endpoints with inputs and outputs.
- 4. Data model (about 3 min): the main entities, and which kind of database fits.
- 5. High-level design (about 10 min): the simplest design that works end to end.
- 6. Deep dives (10–15 min): fix the bottlenecks — caching, sharding, queues, failure handling.
- 7. Wrap-up: the trade-offs you made, what you'd do with more time, how you'd monitor it.
Trade-offs
- Don't over-design early: start simple, then scale only the parts the numbers say need it.
- Think out loud. If you are silent, the interviewer can't give you credit for good reasoning.
Common mistakes
- Designing before asking a single question.
- Adding Kafka, microservices and sharding to a system that gets 10 requests a second.
- Long silences. The interviewer can only give credit for what you say.
- Never stating trade-offs. Every choice has a cost, and naming it is what earns the strongest marks.
Not true: A stronger answer: add Kafka, microservices and sharding, even at 10 requests a second.
In fact: A system that gets 10 requests a second needs none of them. Match the design to the numbers: every extra part costs complexity.
Not true: First minute: start drawing boxes; questions about requirements can wait.
In fact: The first five minutes are for requirements: what the system must do, and at what scale. A design built on wrong assumptions answers the wrong question.
In the interview
Before I design anything, I'd like to clarify the requirements and the scale. Then I'll propose a simple design that works end to end, and we can go deep on the parts you care about most, discussing the trade-offs as we go.
Part of Unit 0: How system design interviews work in the free System Design course.