Here's what your interviewer would think: Strong structured thinking — your issue tree was MECE and hypothesis-driven from the first sentence, which is rare. Quantitative reasoning was sharp on the revenue side but you hesitated on cost decomposition. Your PEI story on Drive was compelling but needed a crisper 'so what' at the end. With tighter synthesis, this is a 'Strong Yes' packet.
152
WPM
Ideal range
2.1
Fillers/min
Good
48%
Talk Ratio
Aim: 50%
Competency Breakdown
Tap to see evidence
Structured Thinking91
Exceptional MECE issue tree with hypothesis-driven approach. You led the case from the first sentence — exactly what McKinsey's 4-5/5 looks like on this dimension. The revenue breakdown was textbook.
▼ See the moment
Quantitative Reasoning76
Sharp on the revenue side with clean math. Lost rigor on cost decomposition — shifted from structured estimation to guessing. Inconsistency within a case is a flag at McKinsey.
▼ See the moment
Business Judgment82
Strong commercial instinct — you naturally connected data to real-world business implications. The PEI story demonstrated genuine business impact ($12M retained, 40% expansion).
▼ See the moment
Synthesis And Communication74
Clear and collaborative during the structured portions. The PEI reflection was too generic — 'go beyond your job description' could be anyone's takeaway. McKinsey evaluates self-awareness and growth mindset in the synthesis.
▼ See the moment
What You Did Well
Built a MECE issue tree with a clear hypothesis in under 60 seconds
Interviewer asked
Your client is a European airline that has seen profits decline 20% over two years despite stable passenger numbers. Where would you start?
You said
Since passenger numbers are stable, I'd hypothesize this is cost-driven rather than revenue-driven. Let me break profit decline into two buckets: revenue per passenger and cost per passenger. On revenue: has the fare mix shifted toward economy? Are ancillary revenues down? On costs: the big three are fuel, labor, and maintenance — which moved most? I'd like to start with revenue per passenger to confirm or reject my hypothesis.
Why this was effective
This is exactly what a 4/5 looks like on Structured Thinking at McKinsey. You led with a hypothesis, built MECE buckets (revenue vs. cost), drilled into sub-components, and stated where you wanted to start and why. The interviewer noted you were 'leading the case, not being led.'
Structured Thinking
Demonstrated strong commercial instinct on the PEI Drive question
Interviewer asked
Tell me about a time you achieved something significant despite major obstacles.
You said
At my previous firm, I identified that our $12M logistics client was about to churn because their API integration was failing 15% of the time. My team said it wasn't our problem — it was a vendor issue. I disagreed. I spent three weekends reverse-engineering the vendor's API, found that they'd changed their rate-limiting without documentation, built a queueing system that brought failures to under 0.5%, and presented the solution to the client's CTO myself. They renewed for three years and expanded the contract by 40%.
Why this was effective
This PEI answer hits every Drive signal McKinsey looks for: you identified the opportunity yourself, persisted through internal pushback, went deep on a technical problem, and delivered measurable commercial impact ($12M retained + 40% expansion). The specificity of '15% → 0.5%' and '40% expansion' are exactly the data points that make PEI stories credible.
Drive
Focus Areas
Your top improvements
high
Cost decomposition lacked the same rigor as your revenue analysis
Interviewer asked
Okay, we've confirmed revenue per passenger is stable. Let's look at costs. What's driving the increase?
You said
Well, fuel is probably a big one... and labor costs tend to go up over time... and maybe maintenance if they have an aging fleet?
Why this hurts your score
After a razor-sharp revenue analysis, your cost decomposition dropped into guessing mode. You lost the hypothesis-driven structure that made your revenue analysis strong. At McKinsey, inconsistency within a case is a red flag — it signals that your structured approach might be rehearsed rather than instinctive.
A stronger response
Let me apply the same structure. Airline operating costs typically break down roughly 30% fuel, 25% labor, 20% aircraft ownership/leasing, 15% maintenance, and 10% other. Over two years, fuel prices rose ~18% in Europe. Let me size the fuel impact first: if fuel is 30% of costs and rose 18%, that's a 5.4% cost increase — which alone accounts for about a quarter of the 20% profit decline. Can I get the exact fuel cost data to validate this?
Your goal for next time
Apply the same level of structure to every part of the case — when you notice yourself guessing, pause and build a framework first.
medium
PEI synthesis needed a sharper 'so what' — McKinsey wants the takeaway
Interviewer asked
What did you learn from that experience?
You said
I learned that sometimes you have to go beyond your job description to solve the real problem.
Why this hurts your score
The story was excellent, but the reflection was too generic. McKinsey's PEI evaluates Growth and self-awareness. A 'so what' that could apply to anyone doesn't demonstrate either. They want to hear a specific, non-obvious insight about yourself.
A stronger response
What I took away is that I'm most effective when I treat 'not my problem' as a signal, not a boundary. That vendor issue wasn't technically our scope, but the churn risk was real. Since then, I've made it a habit to audit adjacent systems when a client relationship is at risk — I've caught three similar issues before they became churn events. It's become a pattern I actively look for.
Your goal for next time
End every PEI story with a specific, personal insight — not a generic lesson. 'I learned X about myself' beats 'I learned that Y is important.'
Speech Analytics
Words Per Minute
152wpm
Ideal range (130–160 ideal)
Pace Variation
Dynamic
Good variation keeps listeners engaged
Fastest moment
At 6:10 — "and maybe maintenance if they have an aging fleet?"
Filler Words
2.1/min
Target: under 5/min
Here's exactly what you said:
“well”×3“um”×2“basically”×1
Hedging Phrases
2.8/min
Too much hedging
Impact
Phrases like “I think maybe”, “sort of”, “kind of” weaken credibility. Replace with direct statements.
Vocal Confidence
76/100
Strong
HesitantModerateCommanding
Weak moment
At 6:15 — “Well, fuel is probably a big one... and labor costs tend to go up...”
Strong moment
At 0:45 — “I'd hypothesize this is cost-driven rather than revenue-driven”
How we measure this
Vocal confidence is scored from language patterns: direct statements score high (“I decided”, “We shipped”), deferential language scores low (“I would like to”, “Can you give me”).
Practice These Next
1.Your client is a global retailer considering entering the Indian market. They want to know: should they go online-only, physical stores, or both? Structure your approach.
2.A private equity firm is evaluating whether to acquire a mid-size hospital chain. What would you investigate to determine if this is a good investment?
3.Tell me about a time you had to persuade someone who fundamentally disagreed with your recommendation. (PEI: Connection)
How was your experience?
Rate the interview + report — your feedback shapes what we build next