The Setting
What a system design interview actually measures.
An hour of whiteboarding is rarely about the whiteboard. It is a rehearsal for the conversations you will have on the job, run at half the time and twice the stakes.
The Premise
We are not auditing your knowledge of databases. We are watching how you lead a hard, fuzzy, ten-direction conversation, and where you choose to spend the room's attention.
Technical depth is the floor, not the ceiling. The candidates who get offers are the ones who think out loud with structure, decide deliberately, and bring the interviewer along for the ride.
The Rubric
Four signals the interviewer is grading.
Articulation
Translating complex technical concepts into language any stakeholder can follow.
Structure
Leading a long, open-ended discussion with a clear narrative spine.
Trade-offs
Naming the cost of every choice, defending it, and revisiting it under pressure.
Ownership
Signaling that you could land in a team and drive a project end to end.
The Traps
Two ways smart engineers lose the room.
Unfocused discussion
Hopping between scope, storage, and APIs without anchoring the conversation. The interviewer loses the thread, and so do you.
Drowning in detail
Reaching for the row-level schema before the system has a shape. Depth means nothing if the surface area is undefined.