3 min read

The question you should ask before you answer

A clarifying question is not a weakness. It changes what a good answer looks like, and it tells the interviewer how you think.

  • interviews
  • preparation

The worst answer in a rehearsal is rarely the least knowledgeable one. It is the person who answers a different question confidently for three minutes.

When the candidate hears "design a rate limiter", the candidate begins sketching a token bucket. The interviewer referred to a rate limiter for a single internal service with a known caller, not a public API with abusive users. The answer is coherent. It is also about a system nobody asked for.

A clarifying question could have altered the answer. It would also have shown the interviewer something the answer cannot: that you know which assumptions matter.

What a question buys you

An interview question is usually underspecified on purpose. The missing details are the decision space:

  • Scale. A thousand requests a day and a million a second are different problems.
  • The constraint that wins. Cost, latency, consistency, and operational simplicity. You cannot optimise all four at the same time, and the interviewer typically has one in mind.
  • The boundary. What is already built, what you are permitted to assume, and what is out of bounds.
  • What "done" means. A working prototype, a design that can withstand an audit, or a migration with no downtime.

You're not asking for an answer. You're asking which answer is being graded.

The question is part of the signal

Interviewers are instructed to evaluate communication, not just knowledge. A candidate who makes an assumption and double-checks it is easier to work with than someone who disappears into a whiteboard for ten minutes. The question reflects the same judgement that the rest of the interview is attempting to assess.

The failure mode is not asking too much. It's asking nothing but defending a design based on a guess.

How to ask without stalling

One question, one assumption, and one answer.

"Before I start: is this public-facing, or internal? I will assume public and design for abusive clients unless you tell me otherwise."

That sentence does three things. It names the fork, states the default you will use, and gives the interviewer a chance to correct it. You're not awaiting permission. You're making your reasoning visible.

If the interviewer says "you decide", decide out loud and keep going. The goal is not to extract a spec. It is to show that you know a spec is missing.

What not to ask

Avoid questions whose answer is in the posting, the prompt, or the last sentence the interviewer said. Avoid a list of five questions before you have thought for ten seconds. Avoid using the question to delay the part where you have to commit to something.

The useful question is narrow, relevant to the decision you're about to make, and can be answered in one breath.

Practise the move, not the hint

Most rehearsal tools grade answers. That is the visible part, but the move before the answer is the one that can be used in a real room.

During a rehearsal, you can ask the interviewer for constraints before responding. The answer stays beside the question for the rest of the session, it is not written into the transcript, and it does not change your grade. The goal is to practise asking, not to gather hints.

The next time you rehearse, pick one question you would normally guess at. Ask it first. Then answer with the assumption stated. The answer will be shorter, more specific, and easier to defend.

That is usually the difference between a correct answer and a good one.