What MBB interviewers are really scoring
The question behind every case is simple: could this person sit in front of a client tomorrow without embarrassing the firm? Everything an interviewer probes feeds that one judgment. They are not grading you on whether you reach the "right" number. They are watching how you think when a problem is ambiguous, the data is incomplete, and someone keeps interrupting.
That has a few practical consequences for MBB case interview prep:
- A clean process beats a lucky answer. Two candidates can reach the same conclusion; the one with a clear, defensible path passes.
- Out-loud reasoning is the product. The interviewer cannot score what you do in your head. Go silent for thirty seconds and you have handed them nothing to evaluate.
- Recovery counts. Everyone makes a math slip or picks a weak branch. Catching it and adjusting is itself a strong signal.
Read the case as a simulation of real client work, not a puzzle with a hidden solution. That framing alone changes how you behave in the room.
How McKinsey (interviewer-led) vs BCG/Bain (candidate-led) cases differ
The single most useful thing to know before you walk in is who is driving the case.
McKinsey: interviewer-led
In a McKinsey case interview, the interviewer holds the wheel. They present a situation, then walk you through a planned sequence: structure the problem, work a specific calculation, interpret an exhibit, brainstorm drivers, deliver a recommendation. Each question is somewhat self-contained, and the interviewer steers you to the next one. Your job is to answer each prompt sharply and completely rather than to decide what the case should explore next.
McKinsey also tends to lean on more abstract, "what would drive this?" prompts and pairs the case with the Personal Experience Interview (PEI), where you tell structured stories about leadership, impact, and resolving conflict. Prepare those stories as seriously as you prepare the math.
BCG and Bain: candidate-led
A BCG case interview or Bain case interview usually hands you a prompt and expects you to drive. You build the structure, then say what you want to look at first and why, ask for the data you need, and decide when you have enough to conclude. The interviewer reacts rather than leads. This rewards candidates who can hold a thread, prioritize on the fly, and narrate a coherent path through the problem.
The underlying skills are identical, so do not over-index on the difference. But you should practice both modes: answering crisply when led, and steering confidently when not. If you only ever practice one, the other format will feel foreign on the day it counts.
The five dimensions you are evaluated on
Across all three firms, the scoring collapses into five areas. We built our five-dimension scorecard (Structure, Quantitative, Business Insight, Communication, Recommendation) around exactly these, because they are what interviewers actually write down.
- Structure. Can you break an open problem into a logical, MECE-ish set of pieces that actually fits this case, not a memorized template stamped on top of it?
- Quantitative. Can you set up the math, estimate sensibly, do arithmetic under pressure without a calculator, and read the so-what out of the number?
- Business insight. Do your hypotheses and interpretations show commercial judgment, or are they generic? This is where strong candidates separate from competent ones.
- Communication. Are you concise, top-down, and easy to follow? Do you signpost where you are going before you go there?
- Recommendation. Can you land a clear, decisive answer, backed by your analysis, with the main risks and next steps named?
When you review your own practice, score yourself on each separately. "That felt okay" is useless feedback. "My structure was strong but I buried the recommendation and my math was slow" tells you exactly what to drill next.
A realistic prep timeline
Most candidates underestimate how much of this is reps, not reading. Here is a timeline for someone starting from scratch. Compress it if you have less time, but do not skip the out-loud practice.
Weeks 1–2: build the method
- Learn how a case flows end to end and watch or read two or three full worked examples.
- Drill mental math daily in short bursts: percentages, growth rates, breakeven, market sizing.
- Learn a few flexible structures so you are not starting from a blank page, then practice adapting them.
Weeks 3–5: volume and out-loud reps
- Do full cases out loud, several per week. This is where most of the improvement happens.
- Alternate interviewer-led and candidate-led formats so both feel natural.
- After each case, score yourself on all five dimensions and pick one thing to fix in the next one.
Weeks 6–8: pressure and polish
- Practice under realistic conditions: a timer, interruptions, curveballs, and no second takes.
- Tighten your recommendations so they are decisive and top-down.
- If you are interviewing with McKinsey, rehearse your PEI stories until they are sharp and structured.
A rough target: 20 to 40 full cases before your first real interview. Fewer if you are improving fast; more if your math or communication is still shaky. Quality of feedback matters more than raw count.
Practicing under real interview pressure
The most common reason strong candidates underperform is that they prepared by reading cases quietly and then met an interviewer who interrupted, pushed back, and sat in silence waiting for them to keep going. Solving a case at your desk and solving it while being challenged are different skills. The interview tests the second one.
To close that gap, your practice has to feel like the real thing:
- Out loud, always. Verbalize your structure, your math, and your reasoning. Silent practice trains the wrong muscle.
- On a timer. Real cases run roughly 30 to 45 minutes. Practice in that window so pacing becomes instinct.
- With pushback. Find a partner or a tool that interrupts, questions your assumptions, and drops curveballs. Comfort with being challenged is what carries you through the real room.
- With honest feedback. You cannot grade your own blind spots. Get a structured read on each of the five dimensions so you know precisely what to work on.
This is the gap AI Mock Case is built to close. You run a live voice interview with an AI interviewer that interrupts and pushes back like the real thing, then minutes later your five-dimension scorecard is emailed to you, each score tied to what you actually said. The case library and interviewer behavior were calibrated by two ex-MBB interviewers with 5+ years coaching across 100+ cases. It is currently in private beta.
Keep going
Use the rest of the guide library to go deeper on each piece of your prep:
See how the live voice case and scorecard work on the AI Mock Case homepage, or create your account to run your first one.
Frequently asked questions
How long does MBB case interview prep take?
Most candidates need six to eight weeks. You can build a working method in two to three weeks, but fluency comes from repetition. Aim for 20 to 40 full cases out loud before your first real interview.
Do I need to memorize frameworks?
No. Memorized frameworks are obvious to interviewers and often fit the case badly. Learn a handful of flexible structures, then practice adapting them to the specific problem in front of you.
How do I practice under real interview pressure?
Do full cases out loud, on a timer, with something or someone that interrupts and pushes back. Reading cases is not the same as performing under challenge, which is what the real interview exposes.