McKinsey Business Analyst Interview — PEI Personal Impact Story
Take this on a laptop or desktop — not your phone. The live interview needs a full screen and keyboard (including a sketch whiteboard on coding rounds). You can buy now, but start it from a computer.
- Field
- Consulting
- Company
- McKinsey & Company
- Role
- Business Analyst
- Duration
- 20 min
- Difficulty
- Easy
- Completions
- New
- Updated
- 2026-05-23
How to prepare
What this round tests, what strong and weak answers sound like, and the traps to sidestep.
What this round is about
- Topic focus. One real story where you personally led people or changed the mind of someone who did not want to be moved, told from the last two years.
- Conversation dynamic. The interviewer stays on that single story for the entire round and asks ten to twenty-five follow-up questions on it rather than moving to new prompts.
- What gets tested. Whether you can isolate what you personally did from what the team did, with the specific person, the specific words, and a real outcome.
- Round format. This is the McKinsey Personal Experience Interview, judged on its own and treated as just as decisive as the case.
What strong answers look like
- First-person ownership. You say I decided, I went to that person, I owned this part, and you can separate your contribution from the group even when pushed.
- Concrete influence mechanics. You name the specific person who resisted, what they wanted, and the actual words and actions you used, for example I learned he was worried about on-call load, so I proposed a phased plan and took the first week myself.
- Quantified result with a baseline. You give an observable change with a before and after, for example adoption went from two teams to nine in six weeks, not it went well.
- Honest reflection. You name one specific thing you misjudged and what you changed, without being asked twice.
What weak answers look like (and how to avoid them)
- Hiding in the team. If every answer is we, decide in advance which decisions were yours and say so in first person from the start.
- Vague outcome. Replace it went well with one number or observable change and the baseline it moved from.
- Endless backstory. Keep the setup near ninety seconds and get to your first decision fast.
- Low-stakes story. Pick a situation with real conflict or personal risk so the what did you do probes have something to hit.
Pre-interview checklist (2 minutes before you start)
- Pick one driven story. Choose a situation from the last two years you personally drove, not a group project you participated in.
- Identify the person. Name the one human being you led or influenced and what exactly they resisted.
- Pull up one number. Have a quantified or observable result with its baseline ready before the first question.
- Recall the hardest moment. Know what you were feeling at the lowest point and how that changed your next move.
- Have a real reflection. Decide the one thing you would do differently before you are asked, because you will be asked.
How the AI behaves
- Stays on one story. It will not jump to a new question when one gets uncomfortable, it goes deeper into the same one.
- Interrupts on we. The moment your individual role goes unclear it stops you and asks what you personally did.
- Verifies every number. If you claim an outcome it asks for the baseline and how you separated your effect from everything else happening.
- No mid-round praise. It will not say great answer or validate you, it acknowledges one specific detail and pushes.
Common traps in this type of round
- The we narration. Describing a team accomplishment and never surfacing your individual decision.
- Participant not driver. Choosing a story where you were one of many, so every personal probe returns a team answer.
- Outcome without baseline. Quoting a result with no before state, so it cannot be verified.
- Story drift under probing. Contradicting an earlier detail when the same story is approached from a new angle.
- Reflection skipped. Showing no self-awareness about what you misjudged or would change.
- Process without result. Describing what was done step by step but never the measurable or observable change it produced.
The full breakdown
How you're scored, the questions candidates ask most, and the research this interview is built on. Skim it — or just start the interview.
Interview framework
You will be scored on these 5 dimensions. The full rubric with definitions is below.
What we evaluate
Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.
- Personal Ownership Isolation20%
- Influence And Conflict Mechanics18%
- Quantified Impact With Baseline18%
- Story Consistency Under Probing16%
- Situation Scoping Discipline14%
- Reflective Self-Awareness14%
Common questions
Sources this interview is built on
Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.
- McKinsey PEI: Questions, Examples, and Prep (2026)hackingthecaseinterview.com
- McKinsey PEI Questions (examples, tips, framework) - IGotAnOfferigotanoffer.com
- McKinsey PEI Connection 2026: What It Is and How to Answerstrategycase.com
- McKinsey PEI Leadership 2026: What It Is and How to Answerstrategycase.com
- Failed McKinsey Interview? What to Do Next (2026)hackingthecaseinterview.com
- McKinsey & Company Business Analyst Interview Experience & Questions | Glassdoorglassdoor.com