McKinsey PEI: how to prepare your stories
What the McKinsey Personal Experience Interview is, what each of its four dimensions (Connection, Leadership, Drive and Growth) looks for, and how to prepare stories that hold up to 15 minutes of questions.
Practice case math
If you passed the Solve, interviews come next. At McKinsey each one lasts about an hour and has two parts: a case (the Problem Solving Interview) and the Personal Experience Interview, or PEI. This guide covers the second one: what it looks for, how to choose your stories and how to tell them so they hold up to the follow-up questions.
This guide combines what McKinsey publishes on its careers site with what prep guides and candidates describe. Your recruiter gives you the instructions for your own process: if anything differs, go with what they tell you.
What the PEI is
The PEI is a behavioral interview with a twist: instead of asking you lots of short questions, your interviewer picks a single experience of yours and goes through it in depth for about 15 to 20 minutes.
- At the start they tell you which topic they’re interested in (one of the four dimensions below) and ask for a concrete example from your life.
- Then come the follow-up questions: what exactly you did, why, what you were thinking, how others reacted and what happened next.
- The story can come from anywhere: work, an internship, university, sports, volunteering or your personal life. It doesn’t have to be a spectacular achievement. It has to be real, hard for you and with a clear role for you.
- According to prep guides, it carries as much weight as the case: a strong case doesn’t make up for a weak PEI.
That’s why a good anecdote isn’t enough. What’s assessed is how you thought and acted at each moment, and that only comes through when the story survives fifteen minutes of questions.
The four dimensions
McKinsey renamed its dimensions in mid-2025. There are now four, and each interview usually assesses just one.
| Dimension | What it looks for | A typical question | Former name |
|---|---|---|---|
| Connection | That you can influence people and build trust: listen, understand why someone sees things differently and reach agreement. | “Tell me about a time you convinced someone who disagreed with you.” | Personal Impact |
| Leadership | That you can guide a group toward a goal, getting the best out of different people even when there’s friction. | “Tell me about a time you led a team through a difficult moment.” | Inclusive Leadership |
| Drive | That you set demanding goals and keep going when obstacles appear, without waiting for someone to push you. | “Tell me about something you set out to do that seemed very hard to achieve.” | Entrepreneurial Drive |
| Growth | That you learn something new quickly, apply it under pressure and know what changed in you. | “Tell me about a time you had to learn something from scratch to solve a problem.” | Courageous Change |
Since you’ll have several interviews, it pays to arrive with stories for all four. Note that no dimension measures results on their own: a project that went well without any obstacle leaves nothing to assess.
How to choose your stories
1. Take inventory. Write down 10 to 15 moments from the last three or four years when something was hard: a conflict, a goal that seemed impossible, a team that wasn’t working, something you had to learn in a hurry.
2. Filter with four questions.
- Was there a real obstacle? Someone who pushed back, a deadline, something you didn’t know how to do.
- Was your role decisive? If the outcome would have been the same without you, it won’t work.
- Do you remember the details? What you said, what you were thinking, dates and numbers.
- Does it clearly show one dimension? A story that works “a bit for everything” tends to be weak for all of them.
3. Assign two stories per dimension. Eight in total. That way you don’t have to repeat a story in the same round, and you have a backup if the first one doesn’t fit the question you’re asked.
4. Aim for variety. If all your stories come from university, mix in an internship, a sport or volunteering. It shows more of you.
How to tell it
Your first answer should take about two or three minutes. The questions will ask for the rest. A structure that works:
- A headline. One sentence that sums up the story before you tell it: “I’ll tell you how I convinced the warehouse manager at a distributor to change how he tracked inventory during my internship.” It tells your interviewer where you’re heading.
- Context, in 20 to 30 seconds. Where, when and what was at stake. Only what’s needed to follow the rest.
- The challenge. What made the situation hard and why it mattered to you to solve it.
- What you did. This is the core. Walk through it step by step, with your decisions and the reason for each one. Say “I”, not “we”: the team matters, but what’s being assessed is what you did.
- Result and lesson. With a number if possible, and what you’d do differently today.
Prepare each story as bullet points, not as a script to memorize. The PEI is a conversation, and a memorized script falls apart by the second question.
The follow-up questions
This is where the PEI is won or lost. The questions tend to go in these directions:
- Your decisions: Why did you choose that approach? What other options did you see and why did you rule them out?
- The other people: What was the other person thinking? How did you know? What exactly did you say? How did they react?
- You: What was the hardest part for you? How did you feel at that moment?
- The result: How did you know it worked? What happened afterwards?
- The lesson: What would you do differently? Have you applied it again?
Some tips for answering them:
- Keep answers short and concrete, and let them ask for more. Don’t jump ahead to the end of the story.
- If you don’t remember a detail, say so. Making it up shows, because the next question exposes it.
- Talk about what you were thinking at the time, not just what you did. That’s where your judgment shows.
- It’s fine to admit mistakes. A story where something went wrong and you fixed it often shows more than a flawless one.
A Connection example
This story is made up, to show what a good answer looks like.
- Headline: “I’ll tell you how I convinced the warehouse manager at a food distributor to use an inventory spreadsheet during my summer internship.”
- Context: the company was losing sales to stockouts, and my job was to set up a spreadsheet to see them coming.
- Challenge: the warehouse manager, with twenty years at the company, refused. He said his notebook worked and the spreadsheet was extra work. Without him there was no data, because he was the one who logged everything.
- What I did:
- Instead of insisting, I spent two mornings in the warehouse to understand how he worked. That’s how I learned that years earlier the company had tried a system that failed and cost a big order, and he had taken the blame.
- I redesigned the spreadsheet so it used the same data as his notebook and took five minutes at the end of his shift, and I suggested trying it for a week alongside the notebook, without giving it up.
- At the end of the week I showed him two stockouts the spreadsheet would have flagged, and asked for his input to improve it.
- Result: he kept using it and suggested adding a column himself. For the rest of the internship, stockouts dropped from about six to two a month.
- Lesson: before trying to convince someone, understand why they think what they think.
And the follow-up questions could go like this:
- “Why didn’t you ask your boss to just tell him to use it?” A good answer explains the reasoning: an order would have made him fill it in to comply, not for real, and the spreadsheet depended on him every day.
- “What did you say the first time he said no?” This is where the actual words help, not a summary.
- “What would you have done if he still said no after the week?” It shows you had alternatives and weren’t relying on a single move.
Common mistakes
- A team story where your part isn’t visible. If you keep saying “we”, your interviewer has nothing to assess.
- Too much context. If you haven’t reached the challenge after two minutes, you’re running out of time.
- A story with no real tension. Without difficulty there are no decisions, and without decisions there’s nothing to show.
- A memorized script. It sounds rehearsed and falls apart under questioning.
- Exaggerating. Fifteen minutes of detailed questions expose anything that didn’t happen that way.
- One story for everything. Each dimension needs its own example.
A one-week prep plan
| Day | What to do |
|---|---|
| 1 | Take inventory: 10 to 15 hard moments from recent years. |
| 2 | Filter with the four questions and assign two stories to each dimension. |
| 3 | Write each story as bullet points: headline, context, challenge, three or four actions with their reason, result and lesson. |
| 4 | Tell them out loud and record yourself. Cut the extra context. |
| 5 | Ask someone to grill you with follow-up questions for 15 minutes per story. |
| 6 | Add details wherever you went blank: what you said, numbers, dates. |
| 7 | Light review. Also prepare a couple of questions to ask your interviewer. |
The other half of every interview is the case. The case guide explains its question types with a solved example, and you can practice its math, done without a calculator, with the mental math trainer.
Frequently asked questions
Can I use a story from my personal life? Yes. What matters is a real challenge and a clear role for you, not where it comes from.
How recent does it need to be? Ideally from the last three or four years. An older story can work if it’s very strong, but recent ones better show who you are today.
Can I reuse a story across interviews? The safest approach is to have different stories for each interview in the same round. That’s why it pays to prepare two per dimension.
How long does it last? According to most guides, 15 to 20 minutes of an interview that lasts about an hour, with the case making up the rest.
Where can I find the real questions? McKinsey asks candidates not to share the content of their interviews, and this guide doesn’t include any. The questions and the example on this page are our own.