What interviewers actually score in a case interview (it's not the answer)
Having sat on the interviewer side, I can tell you: we're not looking for the right answer.
Most candidates walk into a case convinced that the goal is to land on the correct recommendation. They spend the entire case hunting for it, and you can see the stress build when they're not sure they've found it. But when I was evaluating candidates, the recommendation itself was one of the smallest boxes on the scorecard.
What carried far more weight was how you structured the problem, how clearly you communicated your thinking, whether you formed and tested hypotheses along the way, and how you responded when I pushed back on something.
That last part, coachability, is the piece candidates underestimate the most.
The scorecard isn't what you think
Every major consulting firm uses some version of a structured evaluation. The exact format varies, but the dimensions are remarkably consistent. When I was scoring candidates, I was watching for roughly four things.
Problem structuring. Did you break the problem into logical parts? Did the structure actually fit the problem, or did you force a memorised framework onto it? I could always tell when someone was running a template versus actually thinking. The candidates who paused for 30 seconds to build something from scratch almost always did better than the ones who jumped straight into a four-box framework they'd drilled the night before.
Analytical reasoning. When you got data, did you know what to do with it? Could you pull out the insight that mattered and ignore the numbers that didn't? This one separates candidates fast. Some people calculate everything they're given because they're not sure what matters. Strong candidates ask themselves what they need to prove before they start running numbers.
Communication. Were you clear? Could I follow your logic without having to ask you to repeat yourself? Did you signal where you were going before you went there? The best candidates narrate their thinking in a way that makes it easy for the interviewer to stay with them. They say things like "I want to look at three areas" before they start, and they flag when they're shifting from one area to another.
Coachability. This is the one that matters more than most people realise, and the one that gets the least preparation time.
Why coachability changes everything
If I offered a hint or challenged an assumption during a case, I was running a test. I wanted to see whether you could absorb new information and adjust without falling apart.
The candidates who got defensive or rigid scored poorly even when their analysis was technically sound. If I said "What if the market is actually shrinking?" and you responded by doubling down on your growth assumption without engaging with the new information, that told me something. It told me you'd be difficult to work with on a real engagement, where client feedback and senior partner input come at you constantly and you need to adapt in the moment.
The candidates who treated the case as a conversation scored well. They'd say something like "That's a good point. If the market is shrinking, then my earlier assumption about volume growth doesn't hold. Let me rethink this part of the analysis." That response tells me you can think on your feet and you're comfortable being wrong in front of someone senior. Both of those things matter enormously in consulting.
I've seen candidates with average analytical skills get offers because they were exceptional at this. And I've seen technically brilliant candidates get rejected because they couldn't take a hint.
What this means for your preparation
If you're spending all your prep time memorising frameworks so you can arrive at the right answer, you're optimising for the wrong thing. The scorecards are designed to evaluate how you think, not what you conclude.
Here's what I'd focus on instead:
Practise structuring from scratch. Take a problem you've never seen and give yourself 60 seconds to build a structure. Don't reach for a template. Ask yourself: what are the two or three things I'd need to understand to answer this question? That's your structure.
Get comfortable with pushback. Have your practice partner challenge you mid-case. Not just "what if this number is wrong" but "I don't think that's the right approach." Practise responding to that without getting flustered. The response should acknowledge the pushback, engage with it, and then either adjust or explain why you're sticking with your original direction.
Narrate your thinking out loud. Record yourself doing a case and listen back. Are you signposting where you're going? Can you follow your own logic? If you lose yourself in the recording, the interviewer lost you too.
Stop chasing the right answer. In most cases there isn't one single correct recommendation. There are several defensible positions, and the interviewer knows this. They want to see you pick one, support it with evidence, and hold it with confidence. A well-defended wrong answer scores higher than a correct answer with no reasoning behind it.
The bottom line
The interviewer isn't sitting across from you with a correct answer in their head, waiting to see if you match it. They're watching how you think, how you communicate, and how you respond when things don't go as planned.
Those are the things that predict whether someone will be effective on a real project. And those are the things the scorecard is built to measure.
If you optimise your preparation around these dimensions instead of hunting for correct answers, you'll walk into your interviews with a very different kind of confidence.