20 McKinsey Interview Questions + Answers (2026) — PEI & Case Prep

Q1. “Tell me about a time you influenced someone senior to change their decision.”

Tests: Personal Impact. McKinsey wants evidence that you can persuade upward — that your influence is not limited to peers.

Situation: The VP of Operations at my company had decided to shut down a small regional logistics hub, citing cost overruns. The decision had been communicated to staff and a timeline was set.
Task: I believed the analysis underpinning the decision was flawed — it had not accounted for the hub’s role in serving our three largest accounts, which collectively represented 28% of revenue.
Action: I spent two evenings building a counter-analysis. I modelled the cost impact of the hub closure on the three key accounts, including delivery time increases, contract penalty clauses, and the realistic probability of account attrition based on the contract terms. I requested a 20-minute meeting with the VP, framed my request as “I want to share some data you may not have seen before making the final call,” and presented a single-page summary with the financial exposure clearly quantified at $4.2M over 24 months. I did not ask him to reverse the decision outright — I asked him to delay by two weeks to allow a fuller review.
Result: He agreed to the delay. The full review confirmed my analysis. The hub was retained with a redesigned cost structure. The VP later told me the analysis was the clearest cost-benefit framing he had received in years, and he recommended me for a stretch assignment six months later.

Pro tip: The follow-up McKinsey will ask is “How did you know the original analysis was flawed?” and “What was the hardest part of the conversation?” Prepare for both.

Q2. “Describe a situation where you had to persuade a large group with no formal authority.”

Tests: Personal Impact at scale. Changing one person’s mind is good; changing a group’s direction without authority is exceptional.

Situation: I was a junior member of a cross-functional working group designing a new client onboarding process. The group had been working for three months and had converged on a solution that the five most senior members supported but that I believed had a fundamental flaw — it required clients to provide data in a format that our actual client base could not easily produce.
Task: I needed to redirect a group of fifteen people, including four managers, without the standing to mandate anything.
Action: I did not raise the objection in the full group — that would have felt like an attack on the three months of work people had invested. Instead, I spent a week doing informal one-on-one conversations with the key decision-makers, starting with the person I thought would be most open to the concern. I framed it not as “this is wrong” but as “I want to sense-check something with you before the next meeting.” By the time we reached the formal session, three of the five senior members had already privately acknowledged the issue. I proposed a modification in the meeting that preserved 90% of the existing design and addressed the client data problem.
Result: The modification was adopted unanimously. The onboarding process went live and the client data submission rate was 94% on first attempt — 30 percentage points higher than our previous process. The working group lead cited the process as a model for future cross-functional design projects.

Q3. “Tell me about a time you delivered a difficult message — what happened?”

Tests: courage and communication under pressure. McKinsey consultants routinely deliver findings clients do not want to hear. Show that you are direct without being destructive.

Situation: Our analysis showed that a product line the client had invested $8M in developing over two years was structurally unprofitable and would never reach the margin targets set at launch. The product had been championed by the CEO.
Task: I was the analyst responsible for the financial model. The engagement manager asked me to present the findings directly to the CEO in our final steering committee.
Action: I prepared by thinking carefully about what the CEO needed to hear versus what she wanted to hear, and how to frame the gap. I led with the analysis rather than the conclusion — walking through the unit economics, the market constraints, and the competitive dynamics that combined to make the current model unworkable. Only then did I present the conclusion: the product would not reach profitability in the current configuration. Crucially, I also presented three restructuring options that could change the economics, with a clear assessment of each. I was direct but not clinical — I acknowledged the investment the team had made and the difficulty of the finding.
Result: The CEO did not dispute the analysis. She chose the second restructuring option. The product was repositioned, margin improved by 18 percentage points within 12 months, and the line reached profitability. She later called the analysis “the most useful thing the engagement produced.”

Q4. “Give an example of navigating significant ambiguity to achieve an outcome.”

Tests: Personal Impact under uncertainty. McKinsey wants people who move forward with imperfect information rather than waiting for clarity that never comes.

Situation: I was asked to “own” the launch of a new internal analytics platform. There was no launch plan, no defined success metrics, no dedicated budget, and no clarity on which teams were required to use it versus which were optional.
Task: Within six weeks, I needed to generate meaningful adoption from a group of 200 potential users across eight departments.
Action: Rather than waiting for clarity on the ambiguous constraints, I identified three decisions I could make immediately: which two departments to target first (the ones with the highest data maturity and the most visible problems the platform could solve), what “good adoption” looked like (I defined it as 40% of target users completing at least three sessions within 30 days), and what resources I had (I had my own time, access to the platform team, and informal influence with two department heads). I ran a four-week “champion programme,” recruiting two power users per department and supporting them intensively to generate visible wins that others could see. I tracked adoption weekly and shared results with leadership in a one-page update every Friday.
Result: After six weeks, adoption across the two pilot departments was 58% against my 40% target. Leadership approved a company-wide rollout and assigned a dedicated budget. The Friday update format was adopted by the product team for all future launches.

Q5. “Tell me about a time you created value that wasn’t expected of you.”

Tests: Personal Impact through initiative. McKinsey wants people who exceed what is asked because they see the larger opportunity, not because they want to be seen to work hard.

Situation: I was hired to build a monthly financial report for the leadership team. It was a well-defined task with a clear template.
Task: While building the report, I noticed that the data sources feeding it contained information that leadership was not using — specifically, customer-level revenue concentration data that showed that 11% of customers generated 67% of gross profit.
Action: I built the requested report, then spent two additional evenings building a customer profitability analysis that was not in scope. I presented both to the CFO: the standard report and a two-page annex showing the concentration risk and three potential actions. I framed it carefully — “This was not what you asked for, but the data suggested it was worth 10 minutes of your attention.”
Result: The CFO shared the annex with the sales team. Within a quarter, the company had introduced a customer tiering programme that increased retention among the top-tier segment by 15% and freed up sales effort from the lowest-margin accounts. The annex became a standing section of the monthly report. My role expanded significantly as a result.

Pro tip: The most powerful Personal Impact stories have three qualities: you took action that was not required, the action was based on insight rather than just hard work, and the outcome was measurable.

Q6. “Tell me about a time you built something from scratch.”

Tests: Entrepreneurial Drive. Show ownership, initiative, and what you built end-to-end — not just a contribution to an existing project.

Situation: My university had no formal mentorship programme connecting students to alumni in their target industries. Students were navigating career transitions entirely alone, and the placement rate in competitive fields like consulting and finance was well below peer universities.
Task: I decided to build one. I had no funding, no institutional support, and no experience running programmes.
Action: I started by mapping the problem: what specifically was failing? Through 20 conversations with students and alumni, I identified that the core gap was not information but relationships — students didn’t know how to reach alumni, and alumni didn’t have a structured way to help. I designed a matching system based on industry, role, and degree of career pivot, recruited 45 alumni mentors by personalising every outreach email, and partnered with the career services office to use their email list for student applications. I ran the first cohort with 30 mentor-mentee pairs and collected structured feedback after each milestone.
Result: In the first cohort, 18 of 30 students received offers in their target field within six months — a 60% conversion rate versus the department’s prior 22%. The programme was adopted by the university, scaled to 150 pairs in year two, and is still running. I received the Dean’s Award for student leadership.

Q7. “Describe your most significant achievement — why was it hard?”

Tests: Entrepreneurial Drive anchor question. This is the most common PEI opener. McKinsey interviewers will spend 15 minutes here. Choose your most difficult, most detailed, most genuinely impressive story — not the one that sounds best on one sentence.

Situation: During a post-merger integration, I was asked to lead the consolidation of two customer service organisations with different technology stacks, different process designs, and deep cultural friction between the legacy teams.
Task: The mandate was to reduce the combined cost base by 25% within 18 months without degrading customer satisfaction scores below 4.2 out of 5.
Action: The hardest part was not the technical consolidation but the people problem: the acquired company’s team believed — with some justification — that their processes were superior and that “integration” meant erasure of everything they had built. I dealt with this by structuring the process design work as a genuine competition between approaches rather than an assumption that the acquiring entity’s way would win. We ran parallel pilots, measured outcomes on the same metrics, and let the data decide. In three of five process areas, the acquired company’s approach won and was adopted. This changed the dynamic from resistance to ownership. On the technology side, I partnered with the IT team to build a migration sequence that maintained system uptime throughout, phasing the transition over 90-day sprints. I also held weekly all-hands sessions for both teams together, which was uncomfortable at first but built shared identity faster than any other single action.
Result: We achieved 27% cost reduction against the 25% target in 16 months against the 18-month timeline. Customer satisfaction improved from 4.1 to 4.4 across the combined organisation. Staff attrition during the integration was 8% against an industry benchmark of 22% for comparable integrations.

Pro tip: McKinsey will ask “what was the single hardest moment?” and “what would you do differently?” Your answers to these follow-ups matter as much as the opening story. Prepare them explicitly.

Q8. “Tell me about a time you failed and what you learned.”

Tests: Entrepreneurial Drive through resilience and self-awareness. McKinsey wants genuine failure, not a success dressed up as a failure. The learning must change your behaviour visibly.

Situation: I led a product launch that failed. I had been responsible for the go-to-market strategy for a new B2B software product. We launched on schedule and within budget, but adoption at six months was 12% of the target we had committed to the board.
Task: I had to account for the failure, understand its root causes, and determine what I would do differently.
Action: The honest post-mortem revealed two failures that were mine. First, I had validated the product with a small group of early adopters who were unusually sophisticated users — I had not tested with the median buyer, who turned out to have different needs and much lower technical tolerance. Second, I had prioritised launch timing over sales enablement; the sales team did not have adequate product knowledge or objection-handling tools for the first 90 days. I had treated the launch as a marketing problem when it was equally a sales readiness problem. After the post-mortem, I rebuilt the sales enablement materials myself and ran a two-day workshop with the sales team before we pushed for a second wave of outreach.
Result: The second wave achieved 71% of the original target within four months. The product ultimately reached profitability. I now treat validation breadth and sales readiness as non-negotiable launch criteria, not nice-to-haves.

Q9. “Give an example of pushing past setbacks to achieve a goal.”

Tests: persistence, a core Entrepreneurial Drive signal. The setback should be real and significant, not a minor obstacle overcome with extra effort.

Situation: I was leading a fundraising campaign for a community infrastructure project that required $500K in private donations. At the six-month mark we had raised $140K and the two largest potential donors had declined.
Task: The project was facing cancellation. I needed to either raise the remaining $360K in the next four months or find an alternative path to completion.
Action: Rather than redoubling the same approach, I analysed why the two large donors had declined. Both cited uncertainty about the project management credibility. The ask was large and the track record was thin. I pivoted the strategy: instead of targeting more large donors, I launched a “community funding round” targeting 100 donors at $2,000 each. I partnered with a local bank that co-branded the campaign, which provided the third-party credibility the large donors had flagged. I also brought in a project management firm on a deferred fee arrangement so I could show a credentialed delivery team. Over the next three months I ran 40 community information sessions, handled every objection personally, and converted 87 of the 100 targeted donors.
Result: We raised $174K from the community round, plus a $220K grant we unlocked because the community funding demonstrated public support — a grant criterion we had not previously met. Total raised: $534K. The project was completed on time.

Q10. “Tell me about a time you took a calculated risk.”

Tests: judgment and courage in driving outcomes. McKinsey wants people who are bold when the analysis supports boldness — not reckless, but not paralysed by risk either.

Situation: I was managing a supplier relationship that was central to our operations. Our primary supplier had 60-day delivery lead times that were causing us to hold excess inventory worth $2.4M. I identified a smaller, faster supplier that could deliver in 14 days but had never handled our order volume and had no prior relationship with us.
Task: The risk of switching was real: if the new supplier failed to perform, we would face production stoppages. The risk of staying was financial: $2.4M in tied-up capital with a 20% annual carrying cost.
Action: I structured the transition as a 90-day pilot at 15% of our volume. I negotiated a performance bond with the new supplier, maintained a 45-day buffer inventory during the trial, and defined clear go/no-go criteria at 30 and 60 days: on-time delivery rate above 95%, quality rejection rate below 0.5%. I also identified a secondary backup supplier in case the pilot failed, so we had a recovery path. The pilot ran without incident. I presented results to the procurement committee with the data and a recommendation to scale.
Result: We migrated 80% of volume to the new supplier over six months. Inventory carrying costs fell by $380K annually. The primary supplier responded to the competitive pressure by reducing their lead time from 60 to 32 days, improving our position further.

Pro tip: “Calculated risk” means you can articulate exactly what you stood to gain, what you stood to lose, what the probability of each outcome was, and what you did to mitigate the downside. Show the calculation, not just the courage.

Q11. “Tell me about a time you led a diverse team through a hard challenge.”

Tests: Inclusive Leadership anchor question. Show that you actively managed the diversity of perspectives and that it improved the outcome.

Situation: I led a nine-person project team working on a supply chain redesign for a global manufacturer. The team included engineers, finance analysts, and operations managers from four countries with very different working cultures — and a high-stakes deliverable due in ten weeks.
Task: The early weeks revealed a cultural pattern: the team members from more hierarchical cultures were not raising concerns in group settings even when they had critical information, while the members from more direct cultures were dominating discussions. The team was not actually using all of its knowledge.
Action: I restructured our working sessions. I moved from open discussions to structured rounds, where each person gave input in turn before any debate started. I also introduced a “pre-mortem” session two weeks before the final deliverable — asking everyone to identify the three most likely ways the recommendation could fail. The pre-mortem format, which requires individual written input before group discussion, surfaced concerns that had not come up in any prior meeting. Three of the issues raised changed the final recommendation materially.
Result: The deliverable was delivered on time and received the highest client satisfaction score of any engagement that quarter. Two team members who had been largely silent in weeks one to three became active contributors by week six. The pre-mortem format was adopted by the engagement director across the practice.

Q12. “Describe a time you helped someone on your team succeed who was struggling.”

Tests: Inclusive Leadership through individual development. McKinsey wants evidence that you invest in others’ success, not just your own performance.

Situation: A teammate was consistently the last to contribute in team discussions. His written analysis was strong but he visibly shut down in real-time discussions, which was affecting how the engagement manager perceived his contribution and his trajectory on the project.
Task: I was not his formal manager but I could see the dynamic and chose to address it.
Action: I had a private conversation and discovered that he processed information more slowly than others in real-time discussion — not because of a language barrier but because of a deeply ingrained habit of not speaking until he was certain. He had been interpreted as disengaged when he was actually working through the problem. I proposed a small change: before our next team session, I would message him the discussion agenda so he could prepare specific points in advance. I also, separately, asked the engagement manager to direct two specific questions to him in the session — not to put him on the spot but to create an entry point. The first time it worked, his answer was the clearest of the session.
Result: Over four weeks he went from the least visible to one of the most respected analytical voices on the team. The engagement manager changed his assessment and included him in the client-facing presentation. He told me it was the first project where he had felt his contribution was actually valued.

Q13. “Give an example of creating an environment where people felt safe to speak up.”

Tests: psychological safety as a leadership practice. Show concrete actions you took, not just a belief in openness.

Situation: I took over as lead of a team that had been through a difficult period — a prior project had gone badly and several team members had been publicly criticised by senior leadership for mistakes made under extreme time pressure. The team was risk-averse, over-validated every decision upward, and had stopped sharing concerns early.
Task: I needed to rebuild the team’s willingness to surface problems before they became crises, which required rebuilding psychological safety that had been damaged.
Action: I did three things. First, in my first team meeting I shared a time I had made a significant mistake and what I had learned — modelling that disclosure was safe. Second, I introduced a “concerns first” standing agenda item at our weekly meeting: the first five minutes were reserved for anyone to raise a risk, doubt, or concern with no commentary or immediate problem-solving — just acknowledgment and a parking lot. Third, when someone did raise a concern that turned out to be correct, I publicly credited them by name in the broader project update. This was not just fair — it signalled to the rest of the team that raising issues was rewarded, not punished.
Result: Within six weeks the “concerns first” segment was consistently surfacing three to five issues per meeting that would previously have gone unraised until they were urgent. We caught a data quality problem in week seven that would have required a full deliverable rewrite if it had been discovered in week ten. The team’s satisfaction score on the project pulse survey improved by 31 percentage points between my first and last weeks.

Q14. “Tell me about a time you resolved a conflict within a team you led.”

Tests: Inclusive Leadership under tension. McKinsey wants to see that you address conflict directly and constructively rather than avoiding it or forcing a resolution from authority.

Situation: Two senior team members had a genuine professional disagreement that had become personal. One believed the project should prioritise quantitative rigour; the other believed we were over-indexing on data at the expense of the client relationship. Both were partially right, and both were becoming less effective because of the tension between them.
Task: As team lead, I needed to resolve the conflict without losing either person’s expertise or damaging the working relationship further.
Action: I met with each of them separately first to understand not just their positions but the underlying concerns. The quantitative advocate was worried that the team would deliver an imprecise recommendation that would embarrass the firm. The relationship advocate was worried that the client was losing trust and that no recommendation, however rigorous, would be implemented if the relationship broke down. Both concerns were legitimate and compatible — they were not actually in opposition. I convened a joint conversation framing it not as “who is right” but as “how do we satisfy both constraints?” I asked each person to articulate what the other was genuinely right about before making their own case. That reframing changed the conversation from debate to design. We restructured the workplan: three weeks on rigorous analysis, followed by a dedicated client co-design session, with the quantitative work feeding the relationship building rather than competing with it.
Result: The conflict dissolved within two sessions. The final deliverable was both analytically rigorous and client co-owned. It was implemented within 90 days — unusually fast for a recommendation of its scale — precisely because the client had been part of developing it.

Q15. “Estimate the annual revenue of Starbucks in Canada.” (Market sizing)

How to structure your answer: State your approach before calculating. Break the problem into drivers. Show your arithmetic clearly and check your answer with a sanity test at the end.

Framework: Revenue = Number of Starbucks locations in Canada × Average revenue per location per year.

Worked answer: Canada has a population of approximately 40 million people. Starbucks typically has one location per 15,000 to 20,000 people in urban markets, with fewer in rural areas. Adjusting for Canada’s urban concentration (roughly 82% urban), I estimate approximately 1,800 locations. Average revenue per location: a typical Starbucks serves 400 to 500 customers per day, with an average transaction of approximately $8 Canadian. That gives $3,400 per day or $1.24M per year per location. Total: 1,800 locations × $1.24M = approximately $2.2B CAD annually.

Sanity check: Starbucks Canada has publicly reported approximately $2.2–2.4B in annual revenue. This estimate is reasonable.

Pro tip: In McKinsey market sizing, the quality of your decomposition matters as much as the accuracy of your final number. Show a logical, MECE breakdown and acknowledge the key assumptions you are making.

Q16. “A client’s profits are declining. Walk me through your diagnostic framework.”

How to structure your answer: State a top-level hypothesis, then break profits into revenue and costs. Explore each systematically. The interviewer will guide which branch to develop.

Framework: Profit = Revenue − Costs. Revenue = Volume × Price. Costs = Variable costs + Fixed costs. I would explore each branch in turn.

Worked answer: My initial hypothesis is that the decline is more likely to be revenue-driven than cost-driven, since costs tend to be more controllable. On the revenue side, I would ask: Is total market size declining, or is the client losing market share? If share is declining, is it across all products and geographies, or concentrated in a specific segment? I would look at price realization — has the client been discounting to maintain volume, compressing margin? On the cost side, I would examine whether fixed costs have grown faster than revenue (suggesting under-utilisation or over-hiring), and whether variable costs per unit have increased (input cost inflation, lower operational efficiency, or product mix shift toward lower-margin lines). I would also ask about external factors: new competitive entrants, regulatory changes, customer concentration risk.

After framing the full tree, I would prioritise the one branch most likely to contain the root cause based on any data the client has already shared, and request the data needed to confirm or reject that hypothesis before going further.

Q17. “Your client is considering entering the EV market. What would you analyse first?”

How to structure your answer: Market entry questions involve market attractiveness, competitive position, and capability fit. State these three lenses upfront, then explain which one you would prioritise and why.

Framework: I would structure the analysis across three areas: (1) Market attractiveness — is this a good market to enter? (2) Competitive position — can this client win? (3) Capability and financial feasibility — can the client execute the entry?

Worked answer: I would start with market attractiveness, because if the market is structurally unattractive, the analysis ends there. For EV specifically, I would examine: total addressable market size and growth trajectory (EV penetration is rapidly increasing, particularly in developed markets), margin structure (EV margins have historically been compressed by battery costs, but that is changing as scale increases), and whether the market is winner-take-most or has room for multiple profitable players. The EV market is not monolithic — I would ask which segment: passenger vehicles, commercial fleets, charging infrastructure, or EV components? Each has very different economics. Once I understood market attractiveness, I would move to competitive position: what capabilities does this client have that would differentiate them? Do they have manufacturing expertise, a distribution network, a brand in an adjacent category? The hardest part of EV market entry is not the technology — it is scale manufacturing and battery supply chain. I would want to understand whether the client has a path to those, or whether a partnership or acquisition is a more realistic entry route than organic build.

Q18. “How would you structure a cost-reduction study for a hospital?”

How to structure your answer: This combines a cost-reduction framework with healthcare sector knowledge. Show that you can adapt a generic framework to a specific sector context.

Framework: Hospital costs break into: clinical operations (staffing, supplies, pharmaceuticals), support services (facilities, food, laundry, IT), administrative overhead, and capital costs (equipment, debt service). I would examine each for reduction opportunities, with a constraint: clinical quality and patient safety are non-negotiable.

Worked answer: I would start with staffing, which typically represents 50–65% of a hospital’s cost base. The key questions are: What is the staffing model relative to peer hospitals on a per-patient or per-procedure basis? Is there a high reliance on agency or locum staff, which carries a significant cost premium? Are there scheduling inefficiencies that create overtime costs that could be redesigned? Second, I would examine supply chain — pharmaceuticals and clinical supplies are major cost centres where group purchasing, formulary standardisation, and vendor consolidation can yield 10–20% savings without clinical impact. Third, I would look at support services, where outsourcing benchmarks are readily available and there is often a significant gap between in-house costs and best practice. Finally, I would examine administrative overhead: billing efficiency, denial management, and revenue cycle optimisation (which, counterintuitively, reduces cost by reducing the administrative burden of rejected claims). Throughout the study I would track any recommendation against its clinical risk — a cost saving that increases readmission rates is not a saving in the full-system view.

Q19. “Why McKinsey over BCG or Bain?”

Tests: genuine motivation and research. This is a trap for candidates who have not done the work. Generic answers fail. Show that you understand what is actually different about McKinsey.

Situation: I have seriously considered all three firms.
Task: I need to articulate a differentiated reason that is grounded in my specific background and goals, not in McKinsey marketing copy.
Action: There are three things that have led me to McKinsey specifically. First, the global network: McKinsey’s scale and the genuine movement of people and knowledge across offices means that expertise assembled in one context is available everywhere. Given that I want to work across industries and geographies, that matters more to me than a more specialised practice. Second, the PEI itself signalled something about the culture — the fact that McKinsey has formalised leadership assessment to the point of testing it in a structured, standalone interview format tells me something about how seriously the firm takes developing leaders, not just technical analysts. Third, and most specifically, McKinsey’s [specific practice, e.g. Healthcare or Operations] practice is the deepest in the market, and my background in [relevant area] makes me want to be where that expertise is concentrated.
Result: BCG and Bain are excellent firms and I would be glad to work at either. But the combination of global knowledge mobility, cultural focus on leadership, and depth in the specific practice area I care about most makes McKinsey the right choice for where I want to go.

Pro tip: Research McKinsey’s specific practice areas, recent published reports, and any notable alumni or partners who have built the kind of career you want. Name-check specifics. Vague answers about “prestige” and “impact” are immediately disqualifying.

Q20. “What are 3 words your team would use to describe you, and why?”

Tests: self-awareness and fit. McKinsey wants people who know themselves clearly and can substantiate self-assessments with evidence, not just adjectives.

Situation: I have explicitly asked former teammates and managers this question to calibrate my self-perception against external observation.
Task: I need to choose three words that are both true and relevant to McKinsey’s expectations.
Action: The three words that come up consistently are: rigorous, clarifying, and dependable. Rigorous — I have a reputation for checking the numbers more than once and flagging assumptions that others take for granted. A former manager told me I was the only person on the team she did not re-check. Clarifying — I have a tendency to distil complex situations into their essential structure, which teammates have told me is helpful when they are overwhelmed. I think this comes from a discomfort with working on something I do not fully understand. Dependable — when I say I will do something, it happens. Teammates have come to rely on that, which I am proud of, though I have also had to learn when to push back on requests that would compromise quality rather than just absorbing them.
Result: These are not the most glamorous adjectives, but I think they are accurate, substantiated, and genuinely relevant to the work McKinsey does. I would rather be accurately humble than inaccurately impressive.