Asking Clarifying Questions Well

Many interview questions are deliberately underspecified — a probability puzzle that doesn't say whether events are independent, a market-sizing question that doesn't say which city. Jumping straight into an answer without noticing the ambiguity is a common way to lose points before you've done any real work. But asking too many low-value questions, or asking one just to look thorough, reads just as poorly.

Ask questions that would change your approach

The test for a good clarifying question is simple: would a different answer to it send you down a materially different path? "Should I assume the dice are fair?" is worth asking if the problem hinges on it and isn't stated. "What city should I assume?" is worth asking before a market-sizing estimate, because Mumbai and a small town give very different numbers. A question like "is this a hard question?" or one whose answer wouldn't change anything you do next is filler, and interviewers notice the difference between someone probing genuine ambiguity and someone stalling for thinking time.

A good habit is to ask one or two sharp questions, then state any remaining ambiguity as an assumption rather than continuing to ask. "I'll assume the coin is fair unless you tell me otherwise" moves things forward even when you haven't resolved every possible unknown, and it demonstrates that you know how to make reasonable assumptions rather than depending on being spoon-fed every detail.

Example

Given "how many golf balls fit in a school bus," a strong candidate asks one thing — "should I assume a standard yellow school bus, empty of seats?" — gets a quick "yes, assume empty," and moves straight into estimating dimensions. A weaker candidate asks four or five questions about bus color, ball brand, and packing method before doing any estimation, which reads as avoidance rather than diligence.