Skip to content
All resources

Interview Strategy

Common Mistakes to Avoid

8 min read

Most case interview failures are not caused by lack of intelligence, they are caused by a small set of predictable, avoidable mistakes. Knowing what they are and having a concrete fix for each one is one of the highest-leverage things you can do in your preparation.

The 8 Most Common Mistakes

  • 1. Speaking before thinking. Launching into a framework before fully processing the question is the root cause in approximately 80% of failed case interviews. Fix: always pause 30–60 seconds to structure before speaking. It is perfectly acceptable to say 'Give me a moment to organise my thoughts.'
  • 2. Skipping clarifying questions. Without clarifying the objective, the benchmark, and the scope, you risk building a beautiful framework for the wrong problem. Fix: ask 1–3 targeted clarifying questions upfront. Not ten, just the ones that materially change your approach.
  • 3. Memorising and reciting frameworks. Rote frameworks produce generic, surface-level analyses that experienced interviewers can spot immediately. Fix: understand the logic behind each framework so you can adapt it to the specific case context. Tailor every structure to the prompt.
  • 4. Poor time management. Getting lost in one branch and running out of time for the recommendation is a common trap. Fix: track time mentally, prioritise the branches most likely to contain the answer, and synthesise even if your analysis is incomplete, 'Based on what we've found so far, my preliminary recommendation is...'
  • 5. Not connecting the recommendation to the objective. Delivering a recommendation that does not tie back to what the client originally asked is a final-minute killer. Fix: before your recommendation, re-read (in your head) the original question. Open with: 'Returning to our objective of X, my recommendation is...'
  • 6. Answering each question in isolation. Treating each interviewer question as a standalone puzzle without integrating the findings into a running hypothesis wastes time and confuses your narrative. Fix: maintain a live hypothesis and update it explicitly as new information arrives: 'This data points me away from the cost hypothesis and toward a pricing issue, let me explore that next.'
  • 7. Avoiding or rabbit-holing on math. Candidates either skip calculations entirely (raising doubts about quantitative ability) or become so absorbed in arithmetic that they lose the case's strategic thread. Fix: estimate confidently with round numbers, narrate your approach, and sanity-check your answer before moving on.
  • 8. Robotic delivery and no rapport. A technically correct case performed without human engagement, no eye contact, no humour, no checking in, leaves interviewers cold. Fix: treat the interview as a collaborative client conversation. Smile, check in, be curious. The interviewer is evaluating whether they would want to work with you.

The Preparation Mistake That Compounds Everything

Successful MBB candidates typically complete 30–50 full practice cases before their interviews. Many unsuccessful candidates complete fewer than 15. More critically, most candidates spend approximately 95% of their preparation time on cases and only 5% on behavioral prep. At McKinsey, BCG, and Bain in final rounds, behavioral performance carries as much weight as case performance. The split should be closer to 75/25.

After every practice case, identify the single biggest mistake you made and write a one-sentence fix. Over 30 cases, you will accumulate a personalised list of 10–15 failure patterns, which is far more valuable than generic advice.

Practising with a partner who does not give you honest, critical feedback is nearly as bad as not practising. Find at least one partner who will interrupt you when your structure is unclear, push back on your recommendation, and ask follow-up questions you have not prepared for.

One-Page Pre-Interview Checklist

  • Did I clarify the objective before building my framework?
  • Is my framework MECE with no overlapping or missing branches?
  • Did I quantify the key metrics before proposing solutions?
  • Is my final recommendation directly tied to the client's original objective?
  • Did I quantify the impact of my recommendation?
  • Did I address the primary risk?
  • Did I propose a concrete next step?

Reading only gets you halfway

Try a live case with an AI interviewer that pushes back on weak reasoning. Free, no signup required.

Practice this live