Consulting Fit Interview & McKinsey PEI: Your Story Guide

Most people walk into the McKinsey Personal Experience Interview thinking it's a vibe check — tell them you're driven and collaborative and you're through. The firms have seen that play thousands of times. What they're running is a structured oral exam with a pre-loaded scoring rubric, and interviewers are trained to probe until your story holds or collapses.

The good news: the rubric is public. The bad news: most candidates prepare the wrong way.

What Is the Consulting Fit Interview, Exactly?

The consulting fit interview is a structured behavioral evaluation used by McKinsey, BCG, Bain, and comparable firms to confirm whether a candidate has demonstrated specific competencies their model demands — typically personal impact, leadership, entrepreneurial drive, and collaborative problem-solving. It is not a culture-fit conversation; it is a scored oral examination where interviewers start with a trigger question and probe six to eight levels deep until they either confirm a real behavior or find where the story was rehearsed rather than lived. McKinsey calls its version the Personal Experience Interview (PEI), testing four named pillars: Personal Impact, Leadership, Entrepreneurial Drive, and Problem Solving. BCG uses a similarly structured experience interview. Bain runs fit rounds with an equivalent probe depth. All three firms draw from at least three life contexts — professional, early career, and leadership outside work. A 2023 review of 400+ McKinsey first-round reports on Glassdoor found Personal Impact appeared in over 60% of sessions — making it the highest-priority story category to prepare first.

The PEI is not a test of your personality — it is a test of whether specific behaviors exist in your past.

McKinsey alone receives over 200,000 applications per year for roughly 2,000 entry-level positions globally, according to published recruiting figures. That math means every evaluation component carries weight — and the fit round is the one most candidates underweight because they assume it is softer than the case.

Which Stories Does McKinsey's PEI Actually Test?

Each PEI dimension maps to a specific story type. Knowing the definition before you pick a story is not optional — it's how you avoid bringing the wrong story to the wrong moment.

Personal Impact: A time you changed someone's mind or moved an organization in a direction it initially resisted. Not "I presented the analysis and they agreed" — interviewers want disagreement, a specific mechanism you used to shift the outcome, and evidence it was your effort that tipped the situation.

Leadership: A moment you took charge without formal authority. Most MBA students reach for team projects here, which almost always fail because the power dynamics were artificial. If anyone could have assigned you the role, it doesn't score.

Entrepreneurial Drive: A time you created something from zero, took a risk that was real to you, and worked through genuine ambiguity. If the worst-case outcome was a missed bonus, the risk wasn't real.

Problem Solving: A complex analytical challenge with an unclear path and multiple competing approaches. This dimension is where most technical candidates overclaim — interviewers are not scoring the elegance of your solution; they are scoring how you structured the thinking process when the right path wasn't obvious.

The biggest prep mistake is picking your best story and force-fitting it to whatever dimension gets asked. Stories need to be pre-matched to dimensions before you walk in.

Selecting the right story is half the battle. One practical filter: ask whether you could reconstruct this story in detail a month from now after only sleeping four hours. If the answer is no, it's not fully yours — it may be composite or borrowed. PEI interviewers are trained to notice the difference between a story that was lived and one that was assembled in preparation.

How to Build a Fit Story That Survives Follow-Ups

The PEI is not graded on your opener. It is graded on how your story survives six probes. Interviewers are trained to ask "Can you be more specific?" until you either name the exact words you said or you start hedging.

The most common story source mistake is going too senior too fast — candidates pick the most impressive project, which is usually one where they had the least individual visibility. A mid-stakes moment where you were the only person who did something specific is almost always a stronger story than a high-profile project where 30 people contributed.

Here is the six-step structure that holds:

1. Scene in two sentences. Firm name, your role, the specific constraint. Nothing else.
2. Name the obstacle precisely. Not "there was pushback" — what the resistance looked like and who it came from.
3. Name the decision point. What were the available options? Why was the obvious option not enough?
4. First-person action only. "I did X" — not "we decided" or "the team moved." Every "we" is an invitation for a probe you won't survive.
5. Quantify the outcome. Not "it worked" — what changed, measured.
6. Name the follow-on consequence. What happened six months after the outcome because of what you did?

The last step is what separates a story about execution from a story about impact — and impact is what the rubric scores.

Build six stories minimum. Distribute them across PEI dimensions and across three distinct life contexts. The variety matters because interviewers will ask follow-up questions that can only be answered if the moment was real. A story that doesn't survive "what exactly did you say?" isn't ready.

Three Worked Examples Across Different Contexts

Here is what the structure looks like applied across three different candidate backgrounds.

Example 1: Operations Manager, Personal Impact

Interviewer: "Tell me about a time you had significant personal impact on an organization."

Candidate: "In early 2024, I was running regional last-mile operations at a courier company in Riyadh. Our B2B on-time delivery rate had dropped from 91% to 84% over three months. The CEO wanted to let two fleet supervisors go. I disagreed — I believed the routing algorithm was the problem, not the people."

Interviewer: "What specifically did you do?"

Candidate: "I ran 60 days of delivery logs manually, overnight. I found that 70% of late deliveries occurred on three routes where the algorithm ignored live traffic data between noon and 4pm. I put together a one-pager showing the CEO that the supervisors' performance on other routes was above average."

Interviewer: "What was his reaction?"

Candidate: "He said the data looked too convenient. I offered a two-week controlled test: keep the supervisors, patch the routing on those three routes, report back. Delays on those routes dropped 65%. Both supervisors are still with the company."

Example 2: MBA Student, Entrepreneurial Drive

Interviewer: "Give me an example of your entrepreneurial drive."

Candidate: "In my second year at INSEAD, I built a student tutoring marketplace from scratch — not a class project, a real one. I launched in February 2024, charged €15 per session, and hit €4,000 in gross revenue by May."

Interviewer: "What was the hardest moment?"

Candidate: "March. A platform from another school entered at €8 per session. Twelve of my active tutors were deciding whether to switch. I couldn't compete on price."

Interviewer: "What did you do?"

Candidate: "I pivoted in 48 hours. I stopped operating as a marketplace and repositioned as a premium placement service — I tested every tutor personally, added a satisfaction guarantee, and repriced at €25. Eleven of my twelve tutors stayed. Revenue doubled by April."

Example 3: Software Engineer, Leadership

Interviewer: "Describe a time you led without formal authority."

Candidate: "In 2023, I was a mid-level engineer at a fintech startup, six weeks from a major product launch. Our QA lead was blocking releases over minor documentation gaps. The PM and tech lead had already argued with her and gotten nowhere."

Interviewer: "What did you do?"

Candidate: "I asked her for coffee — not to persuade her, but to understand the concern. She told me a previous launch had run into a compliance failure because documentation was incomplete. That was the real issue. I offered to write the documentation template myself and route it through the compliance team directly. She couldn't reject that without being seen as obstructive."

Interviewer: "What was the result?"

Candidate: "We launched on time. She cited my approach in a company-wide retrospective as an example of cross-team collaboration."

The pattern across all three: each candidate identified the specific form of resistance, engaged with its root cause, and took a first-person action with a measurable outcome.

Why Do Most Consulting Fit Stories Fall Apart?

The failure mode isn't nerves. It's the story construction.

Vague settings. "I was working on a project at my company" tells an interviewer nothing. They will ask for the firm name, your role, and the constraint in the first follow-up. If you don't have those details ready, the credibility gap opens immediately.

Plural agency. "We decided," "the team agreed," "we moved forward." PEI interviewers are trained to re-probe every "we" in the first person. If you can't restate the action as "I did X," the story collapses.

Unmeasured outcomes. "The client was happy," "the project launched on time," "the situation resolved itself." BCG interviewers in particular will ask you to quantify every outcome. No number means no score.

Borrowed stakes. Stories from situations where the real risk was on the company, not on you. If the worst-case outcome was a performance review, the stakes weren't real enough to score on Entrepreneurial Drive.

The lesson appended at the end. "And that's when I learned the importance of communication." Real stories don't need an editorial note at the close. The behavior speaks without commentary.

Over-polished delivery. Candidates who memorize a version too tightly stop being responsive. When an interviewer changes the direction of a follow-up, they loop back to the script. Interviewers notice. The answer to "what exactly did you say to her?" is never "as I mentioned."

IntervYou's mock PEI mode runs exactly this kind of probe sequence — six follow-up questions per story, scored against the PEI rubric dimensions. It's the fastest way to find which of your stories collapse before the actual interview does.

McKinsey PEI vs BCG vs Bain: What Actually Changes

All three firms run behavioral evaluations with the same underlying goal. The differences are structural.

One structural difference that matters for prep: at McKinsey, the PEI interviewer is a separate person from the case interviewer, specifically trained to run the behavioral round. At BCG and Bain, the same interviewer sometimes handles both the case and the fit portion — which can mean less structured probing but also less time for your story. Don't count on less rigor from the integrated format. BCG partners in particular are known for sharp behavioral follow-ups.

Prepare to McKinsey PEI standards and you are covered for all three firms.

The fit interview is the most controllable part of the consulting application process. The case round carries genuine variance — you might draw a hard market-sizing prompt or a straightforward operations case. The fit round is almost entirely about preparation: either your stories have been stress-tested to six levels of probing, or they haven't.

Build the six stories. Map them to dimensions. Use IntervYou to run the probes before the interview room does.

Start a free mock →

Related reading

• Behavioral Interview Questions and Answers: The Complete Guide
• How to Prepare for a Consulting Case Interview at MBB
• Common Interview Questions: Answer Them With Confidence