Technique

The 10 most common case interview mistakes (and what to do instead)

The same ten mistakes cost candidates offers every season, and interviewers are trained to watch for them. Each one with how it sounds in the room and the habit that replaces it.

On this page

• 1. Naming a framework out loud
• 2. Calculating before explaining
• 3. Ignoring the interviewer's hints
• 4. Delivering numbers without a so-what
• 5. Reacting to an exhibit before reading it
• 6. Presenting a number with the wrong magnitude and not catching it
• 7. Monologuing
• 8. Losing the actual question
• 9. Panicking at silence
• 10. Ending without a recommendation
• Drill this
• Frequently asked questions

Most rejected candidates do not fail on intelligence. They fail on a short list of habits that experienced interviewers flag over and over, and the list barely changes from season to season.

Here are the ten that come up most. Each one comes with how it sounds in the room and what to do instead. If you fix only the first three, you are ahead of most of the field.

1. Naming a framework out loud

Announcing a framework by name reads as borrowed thinking, and the strictest interviewers start discounting you before the sentence ends. Use the ideas, hide the labels: three or four buckets in your own words, built for this client. The full argument is its own guide, see why memorizing case frameworks fails.

2. Calculating before explaining

If the interviewer has to ask how you got a number, the number has already lost most of its value. Silent math also means a wrong approach gets caught two minutes too late, after a wrong number that cannot be unsaid.

Instead: state the equation and get buy-in before computing. "Revenue per store times stores, minus the two cost lines, so three multiplications. Shall I run it?" Then compute out loud. This habit is big enough to have its own guide, see explain before you calculate.

3. Ignoring the interviewer's hints

Interviewer comments are almost never small talk. A question that points somewhere is a steer, and driving past it costs you twice, once for the miss and once for the coachability signal.

Instead: treat every interviewer question as data. Go where they point, and say the transition out loud so they know you caught it. One distinction: a redirect is not the same as a challenge. If they push back on a conclusion you believe is right, defend the logic before you fold.

4. Delivering numbers without a so-what

A number is not an answer. Interviewers wait to see whether you extract the insight or just stop, and stopping is one of the most common ways strong quant candidates lose points.

Instead: attach a consequence to every number. "About 200 million, and since the client needs 40 million to break even, they would need a fifth of the market. That feels aggressive for a new entrant, which already tells us something."

5. Reacting to an exhibit before reading it

Except the axis was indexed, the units sat in a footnote, and the two best regions were divested last year. Jumping to interpretation before description is where otherwise strong candidates quietly lose cases, because misreading a chart poisons every conclusion built on it.

Instead: narrate the exhibit before you interpret it. Title, axes, units, time period, footnotes, then the trend, then the so-what. Ten seconds of description buys you the right conclusion and shows the interviewer you will not misread a client's data.

6. Presenting a number with the wrong magnitude and not catching it

The candidate had 80 stores at 5 million each and lost a factor of ten somewhere in the zeros. Everyone slips a zero occasionally. What kills credibility is not noticing, because a confident wrong magnitude destroys interviewer trust faster than almost any other error.

Instead: sanity-check before you say it. Eighty stores at 5 million is 400 million, and a one-second per-store gut check catches the extra zero. Track zeros in one system, thousand, million, billion, and never mix them mid-calculation.

7. Monologuing

A case is a dialogue with a colleague, not a presentation to an audience. Long monologues force the interviewer to cut you off, and every cut-off costs momentum.

Instead: hand the turn back regularly. After the structure: "does that work for you?" After a finding: "given that, I'd look at pricing next, sound good?" Checking in is not weakness. It is what working with a client sounds like.

8. Losing the actual question

Sounds like: a tidy cost analysis that ends with a recommendation about costs, when the client asked whether to enter a new market.

Cases drift. Twenty minutes in, many candidates answer the question they have been analyzing instead of the question the client asked at the start.

Instead: anchor to the objective out loud. Write the client question at the top of your page, and tie findings back to it as you go: "so on the entry question, this margin data says the market can support us."

9. Panicking at silence

The answer started half a second after the question, built from whatever was nearest. Candidates fear the pause and trade thinking time for a weaker answer, and to the person sitting inside it, a pause always feels longer than it is.

Instead: buy the silence explicitly. "Let me take twenty seconds to lay this out." Announced pauses read as composure. Unannounced rambling reads as panic.

10. Ending without a recommendation

The close is the last thing the interviewer hears, and a summary is not a recommendation. Hedging at the end undoes twenty good minutes.

Instead: answer first, then support. "I recommend entering, for two reasons, with one risk to manage and one next step." A clear recommendation you can defend, with the main risk named, beats a hedge. The question behind the whole interview is whether a partner could put you in front of a client, and clients do not buy "several interesting angles."

Drill this

Run a self-audit on your next practice case.

1. Record a full practice case, start to finish. The recording is the point, because you cannot catch these habits while you are busy having them. A study partner or an AI interviewer both work. Without either, run a casebook case solo with the solution covered and say every move out loud.
2. Listen back with this list open and tick every mistake you catch yourself making. Most people find three to five on the first pass.
3. Pick your top two, write them on a sticky note, and make them the only focus of your next case.
4. Re-audit every third case. The list should shrink by one or two per week.

Fixing habits one or two at a time beats trying to hold all ten in your head during a live case.

Frequently asked questions

Interviewing somewhere specific?

Read next