Ultimate Guide to the McKinsey Case Interview

The first thing I learned about case interviews at McKinsey wasn't a framework. It was that the partners across the table weren't testing whether I could recite Porter's Five Forces. They were testing whether I could think, out loud, under pressure, about a problem I'd never seen.

That distinction decides who gets offers. This guide covers the McKinsey case interview as someone who sat on the candidate side of it: the interviewer-led format, the five skills actually being scored, the PEI half most candidates neglect, and a prep sequence that doesn't waste your hours. The case round is one of three hurdles in McKinsey's process, see how to handle the Solve game here & how to prep for the Personal Experience Interview here.

How is the McKinsey case interview different from BCG and Bain?

McKinsey runs interviewer-led cases. The case is centrally developed with a set script, and the interviewer steers you through pre-planned questions: structure this problem, interpret this exhibit, compute this number, recommend. BCG and Bain lean candidate-led, where you drive the structure yourself. The McKinsey format feels more controlled and punishes candidates who try to wrestle the wheel away.

How many rounds is the McKinsey case interview?

After the Solve assessment, expect two interviews in the first round and two to four with partners in the final round, each running 45 to 60 minutes, though the exact count shifts by office and role, so confirm with your recruiter once you're invited. Every session pairs a Personal Experience Interview with a case. That pairing matters: half your scored time has nothing to do with market sizing.

1. The interviewer-led format changes what good looks like

In a candidate-led case, rambling can survive if the destination is right. In a McKinsey case it can't, because the interviewer controls the route and scores you inside each stop. When they ask for a structure, they want a complete, organized answer in about 90 seconds. When they hand you an exhibit, they want the insight, then the implication.

The skill to build is structured response on command. Take a moment of silence, even 20 seconds, to organize before speaking. Nobody at McKinsey penalizes the pause. I watched candidates hurt themselves far more often by answering instantly with a shapeless list than by thinking briefly and answering in labeled parts.

McKinsey's script isn't a constraint on great candidates. It's a spotlight that makes disorganized thinking impossible to hide.

2. Five skills are being scored, and framework recitation isn't one

Strip away the mystique and each case scores the same five things: structure, quantitative reasoning, insight, communication, and composure when the interviewer pushes back. That last one is deliberate. Interviewers are trained to challenge answers they agree with, just to watch what you do.

Notice what's absent. Nobody is grading which named framework you invoked. The firm's own preparation advice keeps saying versions of this and candidates keep not believing it, because memorizing 20 frameworks feels like progress. It isn't. One of my Harvard classmates showed up with a binder of frameworks and no reps thinking without them. No offer. The signal was fluency, and fluency doesn't come from binders.

3. Build custom structures instead of reciting templates

Every McKinsey case I've seen maps to a handful of underlying types: profitability, market entry, M&A, operations, and market sizing. Learn the drivers behind each type, then build a structure specific to the prompt in front of you.

The difference shows immediately. A template answer to a declining-profits case says "I'd look at revenue and costs." A custom structure says "This is a regional airline, so I'd split revenue into load factor, pricing, and route mix, and costs into fuel, labor, and fleet, because fuel moved 30 percent last year and that's probably our lead suspect." Same skeleton. Completely different signal.

MECE still matters: categories that don't overlap and don't leave gaps. Use it as a check on your structure, not as vocabulary to say out loud. And keep Porter's Five Forces in its lane. It earns its place on genuine industry-structure questions and nowhere else.

Interviewers can tell within two minutes whether you're thinking about their case or reciting someone else's, and only one of those gets scored well.

4. The math fails more candidates than the structure does

McKinsey cases embed arithmetic at pressure points: market sizes, breakevens, percentage changes across an exhibit. The computations are rarely hard. Doing them while talking, with a partner watching, after 40 minutes of cognitive load, is what breaks people.

Train it separately. Two weeks of daily mental math, 15 minutes a day, changes your interview more than five extra practice cases. Drill percentages, large multiplication, and quick sanity checks. Then build the case habit that protects you: state your approach before computing. "I'll multiply stores by daily customers by average ticket, then annualize" gives the interviewer a map, buys your brain a beat, and lets them redirect you before you burn three minutes on the wrong calculation.

Round aggressively and say you're doing it. 297 times 41 is 300 times 40 in this room. Precision theater wastes clock.

5. The PEI is half the interview and most candidates prep it last

Every McKinsey session opens with the Personal Experience Interview: roughly 10 to 15 minutes on a single story from your life, probed deeply. The dimensions were renamed in 2025 to Leadership, Connection, Growth, and Drive, with one dimension per interview. Across a full round, all of them get covered.

The format is what surprises people. This isn't rapid-fire behavioral questioning. It's one story, excavated. What did you say in that meeting. What was the other person's objection. What did you do the next morning. A story with real texture survives that. A resume bullet inflated into a narrative collapses by the third follow-up.

Build two stories per dimension, each with named people, a specific conflict, and a measurable outcome. Then practice with a partner whose only job is to interrupt and dig. A student I coached through WSG rebuilt her leadership story three times before it held up. The version that worked was smaller and truer than the version she started with. She signed her BA offer in October.

A PEI story survives follow-ups in direct proportion to how true it is, and interviewers dig precisely because polish is easy to fake.

6. Start with McKinsey's official cases, then buy reps with partners

McKinsey publishes full practice cases on its interviewing page, currently including Beautify, Diconsa, Electro-Light, GlobaPharm, National Education, and Talbot Trucks, with the exact lineup shifting occasionally, so check the page directly before you start. Run all of them before touching anything third-party. They're written by the people who'll evaluate you, and the question style is the actual house style.

Then get live reps. Casing alone builds theory. Casing out loud with a partner builds the skill. PrepLounge has a deep case library and a partner-matching pool. Crafting Cases is worth your hours for structure drills. If you want one book, Case in Point gives vocabulary and worked examples, but treat it as a dictionary, not a bible, for the reasons in section 2.

Twenty to thirty full cases out loud is the realistic competitive floor, with McKinsey-style interviewer-led reps weighted heaviest. Keep a log: date, case type, what broke. When the same failure stops appearing for five straight cases, you're close.

7. Solve gates the case, so don't let a game end your cycle

Before any human interview, McKinsey sends Solve, its gamified assessment, currently built around Redrock plus companion modules like Sea Wolf and, for longer invitations, the Sustainable Futures Lab. The lineup has shifted before (an older Ecosystem Building game was phased out) and can still vary by role and region, so treat your specific invitation as the source of truth. The firm says no prep is needed. What the games measure, though, is trainable: extracting numbers from noise, managing a strict clock, deciding with incomplete information.

Give it the same two weeks of daily mental math you're already doing for cases, read the official Solve page and your invite email closely, and take it somewhere quiet on a real computer. Candidates with excellent case skills get cut at Solve every cycle for treating it as a formality.

8. Close every answer like a consultant, not a student

McKinsey interviewers weight the synthesis. When the case ends with "the CEO walks in, what do you tell her," the winning answer leads with the recommendation, gives two supporting reasons with numbers attached, and names the first next step. Fifteen seconds of structure beats ninety seconds of recap.

Practice this as its own drill: after every practice case, deliver the close in one breath. Answer first. Reasons second. Risk or next step third. The habit generalizes, because inside the case the same instinct, closing each segment with a so-what, is what makes an interviewer write "distinctive" instead of "solid."

9. Partners score judgment, and the final round is a different exam

First-round interviewers, usually engagement managers and senior associates, check whether your casing is sound. Partners check something else: would I put this person in front of my client next month. The case in a partner round can wander off script, chase a tangent from your own answer, or turn into a genuine discussion about the industry. That's not the interview breaking. That's the interview working.

Two adjustments for the final round. First, have a view. Partners ask what you'd actually do, and "it depends" with no follow-through reads as empty. Commit, then flex when new information arrives. Second, expect your own background to become case material. A partner who sees a healthcare research assistantship on your resume may build the discussion around hospital economics. The candidates who shine treat that as home turf instead of a curveball.

Some offices also run expertise interviews for specialized tracks, focused on a domain rather than a general case, so confirm with your recruiter whether yours does. The scoring logic doesn't change: structure, numbers, insight, a clear close.

Partners are buying a colleague, not grading a performance, and candidates who talk with them instead of at them convert at visibly higher rates.

On opening a case, and holding your ground

Right after the prompt, resist the instinct to name a framework. Saying "I'd use the profitability framework here" tells the interviewer you're pattern-matching, not thinking. Better to ask for a beat: "Give me 30 seconds to structure this," then deliver something specific to the business in front of you. "Profits fell, so I want to look at three things specific to this business: patient volume, reimbursement rates, and staffing costs. Volume first, because the exhibit hints admissions dropped."

The same discipline applies to "why McKinsey," a question asked in every round. A generic answer like "it's the best firm in the world for consulting" says nothing an interviewer hasn't heard a hundred times. A grounded one does more work: "I want the interviewer-led problem-solving culture. Every McKinsey person I've spoken with, including a BA in the Chicago office, described being pushed on their thinking in team sessions, and that's how I improve fastest."

And when the interviewer challenges your answer, don't cave immediately to whatever they seem to want. Check your work out loud instead: "Let me check that against the numbers. If churn is really 5 percent, my conclusion holds. If it's 15, you're right and the driver is retention, not acquisition." Composure plus evidence, not compliance, is what gets scored.

The six-week prep plan

One calendar note before the plan. For Summer 2028 Business Analyst internships, applications are expected to open in early 2027, with interviews following four to six weeks after the deadline, though exact dates won't be confirmed until McKinsey posts them. Count backward from that and six weeks of prep lands in late fall 2026. Starting in December is comfortable. Starting the week you're invited to Solve is not.

Weeks one and two: run McKinsey's official cases untimed, start daily mental math, and draft two stories per PEI dimension. Weeks three through five: three live cases per week with a partner, alternating interviewer-led and candidate-led, plus one PEI excavation session weekly. Week six: full mock interviews, PEI plus case back to back, with someone instructed to push back on everything.

The McKinsey case interview is the most scripted, most studied interview in professional services, which is exactly why it rewards preparation this specific. The candidates who win aren't smarter. They practiced the actual test.