System design interview prep · method

The System Design Interview

How the hour runs, what the interviewer writes down, and a step-by-step method to fill it: scope, numbers, an end-to-end design, two or three deep dives, a failure walk and a clean finish. The other labs are the depth; this one is how to deliver it under a clock.

01 · What it is

What the hour is, and what gets graded

You get a deliberately vague prompt ("design a metrics store") and 45 or 60 minutes with an engineer who plays a mix of product owner and skeptical colleague. There is no right answer to find. The interviewer is sampling how you work: how you turn an unclear ask into a scoped problem, whether your design works end to end, how deep you go where it matters, and how you reason about the trade-offs you make on the way.

The one-line modelDrive the conversation, design something that works first, then spend most of the time where the hardest requirement bites, and say why at every fork.

The usual shape

PartOf 60 minWhat happens
Introductions0–5Two sentences about you. Don't spend it; the design clock is what counts.
Design5–50You drive. The interviewer answers questions, adds constraints, and steers toward the areas they want to probe.
Your questions50–60Ask about the real system and team. Good questions are a final signal of how you think.

Many companies run 45 minutes with roughly 35 of design. The pacing section has plans for 35, 45 and 60 minutes of design time.

Variants, and how to adapt

VariantExample promptShift your time toward
Product designNews feed, ride matching, chat, ticket bookingAPI, data model, read path, caching, fan-out. More boxes, each one shallower.
Infrastructure designRate limiter, distributed log, metrics store, job scheduler, multi-tenant query serviceMechanism: partitioning, replication, the ack point, consistency, failure handling. Fewer boxes, much deeper.
Your own system"Walk me through something you built"Decisions you owned, the alternatives, what broke. See section 10.
Design critique"Here's our design. What's wrong with it?"The failure walk and the numbers. Find where it breaks first, then fix the worst one.
Component deep dive"How does replication work in X? What does a SELECT see?"Pure depth. This is where the other labs pay off.

At a database or infrastructure company, expect the infrastructure variant and expect the interviewer to push on storage, replication, consistency and multi-tenancy. Lab 06 is a full worked answer in that shape.

What the interviewer scores

Rubrics differ by company but nearly all reduce to these six. Each is graded on evidence: something you said or drew. A strong signal you never voiced doesn't count.

DimensionStrong signalWeak signal
Problem navigationScopes in minutes. Asks questions whose answers change the design. Finds the hard part and says so.A checklist of questions it never uses again. Or no questions, straight to boxes.
Solution designA working end-to-end design early. Each component has one job and a reason to exist. The data flow is traced.Box soup. A component nobody can explain. A design that misses a requirement it agreed to.
Technical depthGoes two or three levels down where it matters. Knows mechanisms and rough numbers."Use Kafka", "add a cache", "shard it" with no how, no why and no cost.
Trade-offsNames the alternative, picks one with a reason tied to a requirement, says what would change the choice.One option as if it were the only one. "It depends" without resolving it.
Operational maturityFailure modes, detection, rollout, migration, cost. Would you trust this person on call?Happy path only. "We'll add redundancy."
CommunicationSignposts, checks in, uses hints, keeps the board readable.Monologue or long silence. Treats hints as attacks.