What does the candidate-drives expectation mean in a system-design round when the interviewer stays quiet?
answer
- Silence is note-taking, not disapproval
- The agenda belongs to you
- Announce transitions, do not request them
- Direction with a default, never approval
- Reclaim the wheel by naming the time left
basics
~20 sIt means you own the agenda for the whole round. Silence from the interviewer is note-taking and evaluation, not disapproval, so you announce each transition, keep the shared canvas moving, and ask for direction rather than for permission.
solid answer
~50 sDriving means the round has a plan and the plan is mine. I state what I am doing next rather than asking whether I may - *the requirements list is settled, so I am going to sketch the high level now* - and I keep the canvas moving through the beats without waiting to be prompted. Silence is the normal state: the interviewer is taking notes, and a quiet stretch usually means nothing is wrong. When I do want input, I ask a directional question with a default attached, like *I am planning to open up the delivery path next unless there is something you would rather see*, which is different from asking whether my design is good. If I stall waiting for approval, the round stops producing evidence, and an empty stretch of canvas is the thing that gets scored.
go deeper
Know that you are expected to keep the round moving yourself and that a quiet interviewer is not a bad sign. Be ready to say what you would do next rather than waiting to be asked.
Explain the difference between an approval question and a directional one, and give an example of each. Expect to describe how you would announce a transition between beats without stopping for permission.
Demonstrate live agenda ownership: checkpoint under silence, follow a steer without losing the thread, and resurface to your own plan after a run of probes. Naming the remaining time and how you will spend it is the strongest single signal here.
Own the balance between driving and listening. Be ready to argue when you would abandon your plan entirely because the interviewer's questions have revealed what they actually care about, and how you avoid mistaking heavy probing for a redirect.
## What "you drive" is actually testing In most system-design rounds the interviewer deliberately says less than feels comfortable. This is not coldness and it is rarely disapproval - it is the measurement. The round is trying to find out whether you can take an ambiguous problem and make forward progress without supervision, which is a large part of what the job is. If the interviewer had to prompt every step, the round would have measured their prompting rather than your judgment. So the expectation has a concrete shape: **the agenda is yours, the canvas keeps moving, and the interviewer's silence is the default state rather than a signal.** ### Announce transitions; do not request them The single most visible marker of driving is how you cross between beats. Compare two candidates at the same point in an invented round - a Series C scale-up, a senior backend role, the requirements list agreed at minute nine: - *Um, is that enough requirements? Should I start drawing now, or do you want more?* - *That is the scope I am going to work to. I will sketch the high level next and leave the last stretch for whichever part you want opened up.* Both are polite. Only the second leaves the interviewer free to redirect without having to run the round. Announcing gives them a cheap intervention point - a single word stops you - while asking transfers the work to them and reads as needing to be led. ### Ask for direction, not for approval There is a real difference between these two and interviewers hear it immediately: - **Approval-seeking:** *Is this design okay? Is that what you were looking for? Am I on the right track?* These invite a yes that means nothing and put the interviewer in the position of grading you mid-round. - **Directional:** *I can go deeper on the retry behaviour or on how status gets reported back - which is more useful to you?* This is a real question with a real answer, and it is what the deep-dive beat is designed for. A directional question with a proposed default is strongest, because it costs nothing if the interviewer has no preference: *I am planning to open up the delivery path unless you would rather see something else.* ### Reading silence correctly A quiet interviewer is usually writing. Candidates who misread this do one of two damaging things: they abandon a perfectly good design and start over, or they fill the silence by talking without adding anything, which eats the clock and buries the signal. Neither is recoverable in a 45-minute round. The useful reflex when silence stretches and you genuinely are unsure is a **checkpoint**, not a retreat: state where you are on the shared canvas, state what you are doing next, and continue. *So that covers the first four requirement lines; I am going to spend the next few minutes on how sends get retried.* If the interviewer wanted you elsewhere, that sentence gives them the opening, and if they did not, you have lost eight seconds. ### When the interviewer takes the wheel Sometimes they interrupt heavily, and that is a different situation from silence. Follow the steer - their questions are usually the rubric surfacing - but keep ownership of the parts they are not steering. After answering a probe, return to the plan out loud: *that is how the retries behave; coming back up, I still owe you the reporting path, and then I would go deeper wherever you like.* Answering probes without ever resurfacing turns the round into an interrogation, and interrogated candidates get scored on the interviewer's agenda rather than showing their own. ### The failure this guards against Driving is not the same as speed, and the fastest way to look like you are driving while failing the round is to **start drawing boxes and arrows before requirements or scale are agreed**. That is motion without an agenda. Genuine drive shows in the ordering - scope, sizing, structure, depth - held without being told, with the shared canvas showing the trail. A candidate who moves fast through beats in the wrong order looks decisive and scores badly. ### Recovering the drive when you have lost it If you notice you have been passive for several minutes - answering questions, waiting for cues, adding nothing to the canvas - the recovery is a single sentence that reclaims the agenda: *let me lay out where I think we are and what I would do with the time left.* Say the remaining minutes out loud and how you propose to spend them. Interviewers score the recovery, not the lapse.
- I have said nothing for six minutes - what do you make of that?That you are taking notes and I should keep going. I read a long silence as the normal state of this round rather than as a verdict. If I am genuinely unsure I will checkpoint - say where I am on the canvas and what I am doing next - and carry on, because that gives you a cheap moment to redirect me without me stopping the round to ask.
- Would you rather I told you what to design next, or chose yourself?I will choose and say so, and you can override me in a word. Right now I would open up the delivery path, because it is where the requirement about acceptable delay actually bites. If you would rather see the reporting side, that is a better use of the time and I will switch - but I do not want to hand you the agenda by default.
- You have been answering my questions for ten minutes without adding anything - what now?I take the wheel back explicitly. I would say where we are against the requirements list, name what I still owe - the reporting path, in this case - and propose how to spend the minutes left. Naming the remaining time out loud is the fastest way to turn an interrogation back into a designed round.
saying these in an interview costs you the question
- Stopping to ask permission before every transition between beats
- Reading a quiet interviewer as disapproval and abandoning a sound design
- Filling silence with talk that adds nothing to the shared canvas
- Asking whether the design is good instead of where to go deeper
- Answering probes for ten minutes without resurfacing to the plan