Clarifying questions in a case interview
The six kinds of clarifying question in a case interview, the one or two to ask before you structure, the ones that belong later, and what makes one weak.
Updated October 28, 2026
| Type | What it establishes | Example |
|---|---|---|
| Objective | What does success look like, in what measure, by when? | “Is the goal margin percent or profit dollars, and over what horizon?” |
| Scope | Which part of the business, geography or customer set is in play? | “Are we looking at all stores or the ones that opened in the last two years?” |
| Definition | What does a term in the prompt actually mean here? | “When you say shrink, is that theft and spoilage together, or spoilage only?” |
| Baseline | What changed, since when, compared with what? | “Did margins fall against last year, against plan, or against competitors?” |
| Constraint | What is off the table? | “Is closing stores an option, or is this about running the existing ones better?” |
| Data | What do we already know, so I do not guess at it? | “Do we have the split between revenue and cost, or do I need to work it out?” |
Why do clarifying questions matter so much?
Because a case is graded on how you think, and a question is thinking made audible. A good clarifying question tells the interviewer three things at once: you heard the prompt, you noticed what it did not say, and you know which missing fact changes the answer. A bad one tells them you are stalling.
The test for a clarifying question is simple. If the answer could change your structure or your recommendation, ask it. If it could not, you are asking to fill time.
Which questions should I ask before structuring?
One or two, from the top of the table: objective and scope, sometimes a definition. Ask them right after you play back the prompt and before you lay out the structure. The interviewer expects them and usually has an answer ready. Three or more at the start, and you have delayed the part they want to hear.
- Play back the prompt in one sentence. Client, situation, what they want.
- Ask the objective question. Measure and horizon. This is the one question almost every case rewards.
- Ask one scope or definition question only if the prompt is ambiguous. “Margins fell” is ambiguous; “operating margin fell three points in the last fiscal year” is not.
- Then structure. Say the buckets, and end the structure with the next question.
Which questions come later, and when?
The rest of the table belongs inside the case, each at the moment the interviewer gives you data that raises it. When a number arrives without a question attached, that is your cue: compute what you can, then ask the question that splits the number.
Two more patterns that earn their place:
- The constraint question before a recommendation. “Before I suggest closing the weakest stores, is that an option for the client?” It costs five seconds and prevents the recommendation the client cannot act on.
- The data question before a long calculation. “Do we have the category split, or should I estimate it?” Interviewers often have the number and are waiting to be asked.
What makes a clarifying question weak?
- It asks for the answer. “What do you think is causing it?” The interviewer will hand it back to you.
- It is a yes or no with no follow-up. “Is this a profitability case?” Ask what the measure is instead.
- It restates the prompt as a question. “So margins fell?” That is a play-back, not a clarification; do the play-back, then ask something new.
- It is a list. Four questions in one breath. The interviewer answers the last one and you lose the first three.
- It ignores the answer. You asked about horizon, they said “this year”, and your structure covers five. Use what you asked for.
How do I practice asking?
Take ten prompts from a public casebook. For each, write the one objective question and the one scope question you would ask, then check them against the case’s own clarifications. Most casebooks list what the interviewer should say if asked; if your question would have unlocked that line, it was a good one. Then run a recorded mock in a browser tab with Casepartner listening and compare: when it shows a next-question hint and you asked nothing, that is the gap to close.
Questions
How many clarifying questions should I ask in a case interview?
One or two before you structure, on the objective and the scope. The rest belong inside the case, each when the data the interviewer gives you raises it.
What is the best first clarifying question?
The objective: what measure, over what horizon. It changes the structure of almost every case and the interviewer expects it.
Is it bad to ask no clarifying questions?
Usually. A case prompt leaves something out on purpose. Structuring without asking what the measure is tells the interviewer you did not notice.
How does Casepartner help with questions?
When data arrives without a question, the window shows one clarifier as a next-question hint. In practice, the useful signal is the turns where it shows one and you asked nothing.