CASE INTERVIEW
You may be doing everything that normally makes you successful.
You collect the information. You analyze carefully. You avoid jumping to conclusions. You try to give a complete answer.
Then the case interviewer asks, “So what do you think?”
And suddenly those habits feel much less helpful.
A case interview rewards judgment before completeness.
That is where many strong Master’s candidates get surprised.
You were trained to gather evidence first... the case may ask for a view first
In coursework, the safest sequence often looks like this:
research, analyze, validate, conclude.
A consulting case can reverse that rhythm.
You may need to form an initial hypothesis with incomplete information, identify what would prove or disprove it, and then update your view as the case develops.
That can feel uncomfortable.
Especially if your degree rewarded careful qualification.
But the interviewer is not asking you to pretend certainty.
They are watching whether you can move forward intelligently without having every answer.
That is a different skill.
Your framework can look perfect... and still do nothing
Three neat buckets. Mutually exclusive categories. Plenty of sub-bullets.
It looks structured.
But what decision is it helping you make?
That is the question that exposes a common case mistake.
A framework is not there to prove that you know business vocabulary. It should tell the interviewer what you need to investigate and why.
Compare:
“Revenue, costs, competition.”
with:
“If profits fell because revenue declined, I would first determine whether the problem is lower volume or lower price. If revenue is stable, I would shift to the major cost drivers.”
The second structure starts moving.
Boxes are not a hypothesis.
For more Master’s-specific failure patterns, read Common Case Interview Mistakes Master’s Students Make.
Then comes the number most candidates calculate correctly...
Suppose you find that a new product could generate $40 million in annual revenue.
You state the answer.
The interviewer waits.
That silence is the test.
Is $40 million large enough? Relative to what? Does it close the client’s growth gap? Is it worth the investment? Does it change your recommendation?
The arithmetic may be finished.
The analysis is not.
A case interviewer usually cares less about the isolated number than what the number does to your thinking.
This is where academically strong candidates sometimes leave value on the table. They treat the calculation as the destination instead of evidence.
The case can be lost before the difficult part even starts
The opening minutes feel harmless.
Clarify the objective. Take a moment. Build the structure.
Yet this is where you set the direction of everything that follows.
If you misunderstand the client’s objective, create generic buckets, or never state what you want to investigate first, the rest of the case becomes reactive.
You are answering questions.
The interviewer is driving the case.
For a closer look at those early moments, read What NOT To Do in the First 5 Minutes of a Case Interview.
Fixing cases starts somewhere surprisingly small...
Do not finish your next practice case and ask, “Was that good?”
Ask:
- Where did I stop leading?
- Where did I give information without an implication?
- Where did my structure fail to prioritize?
- Where did I wait for certainty?
- Where did I answer the calculation but not the client?
One recurring weakness is enough.
Fix that.
Then case again.
Because most Master’s students do not fail cases because they cannot think.
They fail because the interview asks them to make their thinking visible in a very particular way.
And once you can see that difference, practice changes completely.