Case interview mistakes: what I actually see as an MBB interviewer

I have evaluated over 300 case interviews at Bain & Company across 13 years. If there is one thing I can say with certainty, it is that most candidates who fail do not fail because they lack intelligence. They fail because of avoidable mistakes. Mistakes that repeat themselves over and over, across candidates from all kinds of universities, MBA programs and professional backgrounds.

The most frustrating part is that many of these case interview mistakes are invisible to the candidate: they walk out of the interview thinking they did reasonably well, only to receive a rejection without understanding what went wrong.

In this guide I will walk you through the mistakes that actually eliminate candidates, ranked by severity, from the perspective of someone who has been on the other side of the table.

The memorized framework: the number one mistake

If I had to pick a single mistake that eliminates the most candidates, this is it: using a memorized framework that does not fit the case. And I am not saying this as an opinion. I am saying it as a pattern after hundreds of interviews.

A memorized framework is detected immediately. The branches do not align with the reality of the case or with the hypothesis the candidate just proposed. When you double-click on a branch, the candidate cannot go deeper. They cannot explain why they chose those specific categories and not others. The level of detail is shallow and sounds rehearsed.

Interestingly, what does not give it away is the terminology. A candidate can say "I will analyze revenues and costs" without that being a red flag for memorization. What gives it away is the disconnect between the structure and the actual problem. If a candidate proposes a framework that could serve any profitability case without changing a single branch, that is exactly what an interviewer sees: a generic structure, not a way of thinking.

In my book Crack The Frameworks I say it directly: memorizing frameworks is a trap. Consulting cases are too varied for a "fixed template" approach to work. What you need is to understand how to build a framework from scratch: start from a hypothesis and, from there, think logically about what would have to be true for that hypothesis to hold. That is what good candidates do. They do not repeat. They build.

And if you learn better by practicing, download our full cases to practice with for free and come back to this article with the method fresh.

Math errors: where the strongest profiles collapse

It may seem surprising that math errors rank this high on the list, but the reality is harsh: I have seen candidates with excellent grades, from top universities and elite MBA programs, who froze under pressure and could not calculate a weighted average during the interview. This happens more often than people think.

The problem is not the difficulty of the calculation. The math in a case interview is not complex. The problem is doing it under pressure, with someone watching you, in a context where every second counts. When a candidate gets stuck on a simple calculation, the signal it sends is devastating: if they cannot handle this here, how will they do it in front of a client?

Preparing for math in case interviews is not just about knowing the operations. It is about training speed and accuracy under stress conditions. Your normal performance might be 100, but under pressure it can drop to 80. Practice does not eliminate nerves, but it raises your baseline so that your 80 is still good enough.

Making up answers without validating them

This mistake is less well known but heavily penalized. The candidate puts forward an assertion, a number or a conclusion without checking it against the data in the case. They do not ask the interviewer for information, they do not validate their assumptions, they simply press forward as if what they just said were fact.

In real consulting, everything is validated. Every number has a source, every conclusion has analysis behind it. When a candidate invents an answer and presents it confidently but without foundation, they are showing exactly the kind of behavior an MBB firm does not want in a consultant. It is not about always having the right answer. It is about knowing the difference between what you know, what you estimate, and what you need to ask.

The closing that ruins a good case

A candidate can deliver an excellent framing, analyze correctly, solve the math cleanly, and still sink at the end. This happens when the case closing is poor or unstructured.

The most common pattern: the candidate talks for five minutes giving too much detail of little added value and dilutes the conclusion. They believe that because it is long, the conclusion must be solid. It is exactly the opposite. A good closing is short, structured and goes straight to the point: what is the recommendation, why, and what are the next steps. Top-down communication, the way consultants do it.

Solving the case well is just as important as communicating the conclusion correctly. If you do the first but not the second, it counts for very little. Because the question an interviewer asks at the end is not "did they reach the answer?" but "could this person present this to a client?"

No hypothesis: reacting instead of leading

This is the fourth most eliminatory mistake, and it is deeply connected to the first. A candidate who does not generate a hypothesis when opening the case jumps from topic to topic without direction. From the outside, it looks like they are reacting rather than leading. And in a consulting interview, that is a serious problem.

The hypothesis does not have to be perfect. It is not about guessing the solution in the first minute. It is about establishing a logical starting point that guides your analysis and gives structure to everything that follows. Without a hypothesis, the framework loses its purpose, the analysis scatters, and the closing has no clear thread.

Communication errors that complicate the interview

There is a set of mistakes that are not eliminatory on their own but make the interview significantly harder. The first is not thinking out loud. You can ask for time to organize your thoughts, and that is perfectly fine. But what you cannot do is not share your reasoning during the case. If the interviewer does not understand where you are or how you are thinking, they cannot evaluate you properly and they cannot guide you either.

The second is not listening to the interviewer's hints. In many case formats, especially interviewer-led, the interviewer is giving you signals about where to focus your analysis. When a candidate ignores those signals because they are too deep in their own framework, they end up making the case harder than it needs to be.

The third is needing too much help. The phrases that come up most often when interviewers reject a candidate are: "they could not structure the case", "they were clearly lost", "I had to guide them too much." That "I had to guide them too much" is a clear signal that the candidate lacks the autonomy the firm is looking for.

What makes the exceptional candidate different

The exceptional candidate also makes mistakes. The difference is how they handle them. When they slip up mid-case, they identify what went wrong, communicate it openly, and move on, this time aiming to do it flawlessly. That shows self-awareness, the ability to recover under pressure, and resilience. Exactly what we look for.

What separates the candidate who passes from the one who receives an offer is not the absence of mistakes. It is the ability to recover from them with clarity and determination.

How online prep and AI are changing the mistakes

The core mistakes remain the same: poor structure, failed calculations, weak closings. But there are new nuances. Massive online preparation and tools like ChatGPT have created a type of candidate who sounds polished on the surface but is fragile when challenged. Perfectly formulated frameworks that fall apart at the first double-click. FIT answers that sound flawless but memorized.

The irony is that AI tools are designed to be agreeable and validate the user. A real interviewer does exactly the opposite: they challenge your assumptions, pressure your recommendations and look for holes in your logic. If your preparation has been mainly with AI and not with real practice with other people, you are likely to arrive at the interview without having experienced that level of pressure.

Frequently asked questions about case interview mistakes

How many mistakes can I make and still pass?

There is no magic number. What matters is the severity of the mistake and how you handle it. A minor math error you recover from quickly will not eliminate you. A framework that does not fit the case probably will. The interview is a holistic assessment of your performance, not a test where you lose points for every slip.

Are mistakes in the first round more forgivable than in the final round?

Not necessarily. The evaluation criteria are consistent. What changes is that in final rounds the cases tend to be more elaborate and the interviewers are more senior. But a structural mistake eliminates you just as easily in round one as in round three.

Do interviewers focus more on technical mistakes or communication mistakes?

Both, but technical ones carry more weight. If your structure is poor, it does not matter how well you communicate. That said, if your structure is solid but your communication is confusing, that is still a problem. Consulting is well-communicated analysis. Both matter.

Are there differences between McKinsey, BCG and Bain in which mistakes they penalize?

For the case portion, practically none. It is quite common for candidates who receive an offer from one MBB firm to also receive offers from the others. The standards and evaluation criteria are very similar. Where there may be more nuance is in the FIT evaluation, but in case-solving the three firms look for the same things.

What should I do if I realize mid-case that my framework is not working?

Communicate it. Say something like "the data is indicating that my initial structure does not cover this dimension well, I would like to adjust it." That is not a weakness. It is exactly what a good consultant would do when faced with new information. What does penalize you is continuing to push a broken framework as if nothing is wrong.

Is practicing alone enough or do I need to practice with other people?

Practicing alone is essential for building the foundation: internalizing frameworks, training mental math, preparing your case closing. But it is not enough. Solving a case alone is very different from doing it with an interviewer: the time pressure is more intense, communication changes, and there is no real stress. Combine both forms of practice.

Want to prepare to avoid these mistakes with real methodology? Crack The Frameworks teaches you how to build frameworks from scratch without memorizing. Crack The Case Interview gives you full cases to practice from start to finish. And Crack The Math trains your mental math so that nerves do not trip you up. All available in digital format on the Prep Platform.