Clarifying Questions to Ask in Case Interview
Twenty clarifying questions for the opening minutes of a consulting case interview: confirming the objective, pinning down scope and timeframe, finding out what the client has already tried, and establishing constraints before you commit to a structure.
The questions
Open any question for the note
Before I start, can I check that I have the objective right? The client wants to work out whether to enter this market, is that correct?
Why ask it
Restating the prompt in your own words is the one clarifying question worth asking in every case. It catches the misread that would otherwise cost you the whole interview, and interviewers correct you here far more often than candidates expect.
Is the goal profit specifically, or revenue, or something else?
Why ask it
Growth, share and profit lead to different structures, and a prompt about improving performance rarely says which. If the interviewer says profit, you have effectively been handed the top of your tree.
Is there a target number or a deadline attached to it?
Why ask it
A stated target turns the case quantitative and tells you what your recommendation has to clear. When there is no target, say you will treat it as directional rather than inventing a threshold later and getting attached to it.
Could you tell me a little about what the client does and how it makes money?
Why ask it
Ask this when the industry is unfamiliar, and ask it plainly rather than bluffing. Interviewers expect it for niche businesses, and a wrong assumption about the revenue model will misdirect every branch of your analysis.
Which geographies are we looking at?
Why ask it
Assuming one country when the client is regional, or the reverse, changes market sizing and competitive dynamics entirely. It is a one-word answer, which makes it cheap to ask and expensive to skip.
Which products or business lines are in scope?
Why ask it
Multi-line businesses often have the problem sitting in one line. If the answer narrows it, you have avoided a market-wide analysis of something the client does not care about.
Are we looking at the whole market or a particular segment?
Why ask it
This decides whether segmentation belongs in your framework or has already been done for you. An answer of the whole market is a hint that segmenting will be where the insight comes from.
When did this start, and how has it moved since?
Why ask it
A sudden change points at one event: a competitor entering, a contract lost, an input price. A slow drift points at structural causes. Getting this early stops you building a framework for the wrong shape of problem.
Is this affecting the whole business, or is it concentrated in one part?
Why ask it
Concentration is the single most useful thing you can learn in the first two minutes, because it tells you where to look before you have spent any structure on it. Interviewers usually have the answer ready.
Is this happening to competitors as well?
Why ask it
An industry-wide decline and a client-specific decline call for completely different recommendations. Candidates who skip this often spend twenty minutes on internal costs when the answer was a market shift.
Has the client already tried anything?
Why ask it
Whatever has been tried and failed is the most valuable fact in the case, and it is often withheld until asked. It also protects you from recommending something the client abandoned last year.
What is prompting this now?
Why ask it
The trigger reveals what the client actually wants, which may differ from the stated question: a board demand, a new competitor, an expiring contract. It also tells you the timeframe your answer has to work within.
Are there constraints I should know about, such as capacity, capital or regulation?
Why ask it
Constraints eliminate branches of your tree before you waste time in them. Ask once, broadly, rather than checking each one individually as you go.
Is anything off the table, for example an acquisition or a price increase?
Why ask it
Interviewers frequently have one path fenced off. Finding it out early is far better than presenting a recommendation and being told the client would never do that, which leaves you rebuilding under time pressure.
How will the client judge whether this worked?
Why ask it
The measure shapes your recommendation and your risks section. If the answer is vague, propose a measure yourself later, since candidates who define success explicitly tend to close much more cleanly.
Who is making this decision, and what do they care about most?
Why ask it
Useful in organizational and change cases in particular. A founder, a private equity owner and a divisional head weight cash, growth and risk differently, and your recommendation should be addressed to whoever is deciding.
Can I check one term? When you say attachment rate, do you mean the share of customers buying the add-on?
Why ask it
Always ask rather than guess. Confirming a definition takes five seconds and reads as precision, while a misunderstood metric produces a confident answer to the wrong question and is usually caught in the math.
Should I ask you for data as I go, or work from estimates?
Why ask it
This establishes how the case will run and saves you asking for numbers that do not exist. In a candidate-led case you will be told to ask; in an interviewer-led one the data will be handed to you at set points.
Could I take a minute to think this through and come back with a structure?
Why ask it
Nearly always granted, and taking the pause is treated as composure rather than hesitation. Use it to write the objective at the top of the page, then your structure; talking while you think is what produces the meandering framework.
Before I move on: we know the market is growing, margins are down and the client has not changed price. Have I missed anything important?
Why ask it
A short recap at the end of scoping catches the fact you noted wrongly and invites the interviewer to hand you anything they were waiting to give. It also demonstrates that you were listening rather than transcribing.
Using the first three minutes well
Practical guidance for the conversation itself
How many to ask, and when
Two to four questions, then stop
Clarifying is scoping, not discovery. Confirm the objective, then ask the two or three questions that would change your structure. A candidate working through ten questions before proposing anything reads as someone stalling rather than someone thorough.
Do not ask what the prompt already told you
It is the most common unforced error, and it signals that you were not listening. Write the prompt down as it is read, and only ask about what is genuinely absent from your notes.
Ask, then say what you will do with the answer
I would like to know whether competitors are also declining, because if they are I would focus on the market rather than the client's costs. The reasoning is what gets credit; the answer alone is just information.
Separate scoping from testing a hypothesis
Clarifying questions come before your structure and are about what the problem is. Questions that test an idea come after, and asking them too early looks like guessing at the answer before you have framed it.
What to clarify by case type
- Profitability: whether the decline is in revenue or cost, over what period, and whether it is industry-wide.
- Market entry: the definition of the market, the geography, and what the client already owns that is relevant.
- Pricing: what is being priced, against what alternative, and whether the client has pricing power or is a follower.
- Growth: whether growth means revenue, volume or share, and whether it must come from existing customers.
- Operations: which step of the process is the constraint, and what the current performance actually is.
- Mergers and acquisitions: what the client is trying to gain, and whether the decision is whether to buy or how much to pay.
What loses marks
- Asking for numbers you are expected to estimate. Population, market size and average price are usually yours to build, not to request.
- A stream of yes or no questions with no reasoning attached to any of them.
- Not writing down the objective, then drifting away from it twenty minutes later.
- Asking about industry background at length when the interviewer clearly wants you to structure the problem.
- Accepting a vague objective. Improve performance is not something you can solve or measure against.
- Restating the prompt word for word rather than in your own words. It shows recall, not comprehension.
If the interviewer turns a question back on you
Being asked what do you think, or told to make an assumption, is normal and is usually a test rather than an obstruction. Give a specific assumption, say why it is reasonable, and flag that you will revisit it if the data disagree. If a question you consider central is refused outright, treat that as information: the case is probably meant to run without it, and continuing to push for it costs you time you will want later for the numbers.