Part 6 of 9 · 1 min read
What an interviewer looks for
What a system design interview is, and the habits that help or hurt.
A system design interview is a conversation. The interviewer gives a big, vague task, such as "design a photo-sharing app". Nobody expects a full design of a real product in under an hour, because real products took many engineers many years.
The interview checks how the candidate thinks. There is no single right answer. The route to the answer matters more than the final picture.
Good candidates usually show these habits:
- They ask questions first. They find out what the system must do before they draw anything.
- They think out loud. The interviewer can follow the reasoning and step in.
- They state trade-offs. Each choice comes with what it gains and loses.
- They start simple. They draw a small design first and add parts only when a reason appears.
- They accept feedback. If the interviewer points at a weak spot, they improve the design instead of defending it.
Over-engineering
Over-engineering means building more than the problem needs: extra parts, extra copies, extra layers. The extra parts cost money and time, and make the system harder to understand and to fix.
Example: adding ten servers and a waiting line for a shop that gets two orders an hour.
Interview angle
Answer in your head first, then open it.
How should a candidate use the first minutes of a design interview?
Starting to draw within the first minute is a common warning sign. Spend the first few minutes asking what the system must do and for how many users. Then say the plan out loud before drawing.
Check yourself:
- Why might an interviewer prefer a simple design with reasons over a complex design without them?
- Which of the five habits would you find hardest to practise?