system-design

Part 11 — The Interview

Everything you’ve learned in Parts 0–10 is the material. This part is the performance — how to actually run a 35-minute design round so the knowledge turns into an offer.

Time for this part: Weeks 3–4 on the Standard track, in parallel with case-study practice (Part 12). Read The Framework early — it’s the scaffold you’ll hang every mock interview on — then return to the deep-dive chapters as you practise.

The unifying idea: the interview grades judgment and process, not a list of facts. The candidate who clarifies, estimates with purpose, justifies each choice with a trade-off, and drives the conversation beats the candidate who knows more but structures nothing. This part teaches that process.

Chapters

The scaffold

#	Chapter	Time	The problem it solves
1	The Framework ⭐	20 min	The minute-by-minute structure so you never freeze

The stages, in order

#	Chapter	Time	The problem it solves
2	Requirements Gathering	16 min	Clarify before you solution; functional vs non-functional
3	Estimation in Interviews	16 min	Numbers with a purpose — each one drives a decision
4	Drawing Diagrams	14 min	A clean high-level picture, both paths, the right altitude
5	Deep Dives	16 min	Going deep on the component that matters, with options

The soft skills that score

#	Chapter	Time	The problem it solves
6	Trade-off Vocabulary	16 min	The phrases that make your reasoning legible
7	Rubrics	16 min	What the interviewer is actually scoring
8	Common Mistakes	18 min	The moves that lose points, catalogued
9	Handling Uncertainty	16 min	Reasoning calmly when you don’t know

The other rounds, and putting it together

#	Chapter	Time	The problem it solves
10	Low-Level Design	18 min	The object-oriented round: SOLID, patterns, extensibility
11	Mock Interview Scripts ⭐	22 min	Two annotated transcripts — the good and the bad, move by move

The things to remember

Clarify before you solution. Never draw a box before you know the functional requirements and the NFRs. Solutioning first is the #1 way candidates lose the round.
Estimate with purpose. Every number should lead to a design implication (“40 writes/sec is easy; 20K reads/sec needs a cache”). Numbers you don’t use are wasted time.
Justify every choice with a trade-off. “I’ll use X because Y, accepting Z” beats “I’ll use X” every time. The trade-off is the signal.
Drive the conversation. Name edge cases (hot keys, failure) unprompted; propose the next step. The interviewer wants a colleague, not an interrogation subject.
Connect decisions back to requirements. “That aligns with favouring availability, which we established up front” — the callback proves your design is derived, not memorised.
Under uncertainty, reason from principles calmly. Never bluff a confident falsehood; acknowledging, reasoning openly, and making progress is more impressive than recall.
The LLD round is a separate skill. If you target India/Pakistan, Amazon, or product companies, prepare object-oriented design (SOLID, patterns, the “now add X” extension test) distinctly.

Before moving on

You should be able to do these without notes:

Recite the minute-by-minute framework for a 35-minute round.
Distinguish functional from non-functional requirements and interpret NFRs into design directions.
Do a back-of-envelope estimate and tie each number to a decision.
Name the trade-off phrasing for three common decisions (SQL vs NoSQL, sync vs async, CP vs AP).
State what a rubric rewards and the top five point-losing mistakes.
Handle “I don’t know” by reasoning from principles instead of bluffing.
Explain how the LLD round differs and run the entity → relationship → pattern framework.
Watch a mock (or your own recording) and mark each move 🟢 or 🔴.

Next: Part 12 — Case Studies — 36 full designs, from a URL shortener to a multiplayer game, each run through the framework you just learned.

This site is open source. Improve this page.