# System design interviews: a structure that holds when you are nervous

> A system design interview has no right answer, but it has a right order. Six steps and how to split forty-five minutes between them.

Source: https://hintvo.com/blog/system-design-interview-structure | Last updated: November 20, 2026 | Reviewed: 2026-11-20

A system design interview has no single right answer, but it does have a right order. If you follow the order, you always know what to say next: what it must do, how big it is, what the interface and the data look like, the simple design, one part in depth, and what breaks.

## The six steps

1. **Requirements.** What must it do, and what can it skip? Then the qualities: how fast, how available, how consistent.
2. **Scale.** Rough numbers only: users, requests per second, size of the data. Enough to choose between designs.
3. **Interface and data.** The two or three calls the system offers, and the main records it stores.
4. **The simple design.** A few boxes that would work for a small version. Draw it before you improve it.
5. **One part in depth.** Pick the hardest part, or let the interviewer pick, and design it properly.
6. **What breaks.** Where it fails, what you gave up, and what you would watch.

## Splitting forty-five minutes

| Step | Minutes |
| --- | --- |
| Requirements and scale | About 8 |
| Interface and data | About 7 |
| The simple design | About 10 |
| One part in depth | About 15 |
| What breaks | About 5 |

## Say the trade-off every time you choose

"I will use a queue here" is half an answer. "I will use a queue here, so a slow payment provider does not block checkout. The cost is that the customer hears about a failure later, not at once" is the whole one. Interviewers are grading the second sentence.

## Common mistakes

- Drawing boxes before asking what the system is for.
- Spending fifteen minutes on arithmetic that changes no decision.
- Naming technologies instead of saying what they are for.
- Defending the first design. Changing your mind out loud is a strength.

## When you do not know a part

Say so and reason from what you do know. Nobody has built every kind of system. What the interviewer wants to see is how you think about a part you have not built yet.

> **Where Hintvo fits:** for coding and system design questions, Hintvo answers with the approach, the trade-off and the code itself, and it can read a question that is shared on screen. Use Hintvo only where AI help is allowed. Check the rules of your company, school or interviewer first, and respect a no. See [the interview copilot](https://hintvo.com/interview-copilot).

## Related

- [AI interview copilot that answers from your CV](https://hintvo.com/interview-copilot.md): How does Hintvo AI help in a job interview, and how do I practice with it?
- [Coding interviews: what to do in the first five minutes](https://hintvo.com/blog/coding-interview-first-five-minutes.md): What should I do in the first five minutes of a coding interview?
- [Design reviews: ten questions worth asking](https://hintvo.com/blog/design-review-questions-worth-asking.md): What questions should I ask in a design review?
