McKinsey Problem Solving Test (PST) & Solve Assessment: Complete 2026 Guide

McKinsey & Company is the world's most selective management consulting firm. The firm hires fewer than 1% of applicants globally, and its recruitment process is deliberately designed to identify candidates who think analytically, communicate with precision, and demonstrate structured problem-solving under pressure. For both undergraduate analyst and MBA associate roles, the process is multi-layered and demanding at every stage.

What distinguishes McKinsey from other top consulting firms — including Bain and BCG — is the combination of a rigorous cognitive screen (either the Problem Solving Test or the Solve digital assessment), highly structured candidate-led case interviews, and the Personal Experience Interview (PEI), which evaluates leadership impact and entrepreneurial drive in depth.

The hiring process has evolved significantly. McKinsey originally administered the Problem Solving Test (PST) — a paper-based psychometric assessment — as its primary screening tool worldwide. From 2020 onwards, McKinsey progressively rolled out Solve, a game-based digital assessment, as a replacement for the PST in most markets. As of 2026, Solve is the standard screening tool for most global markets, with the PST retained in select regions. Candidates must confirm which format applies to their specific location and programme type at the point of application.

Across both formats, McKinsey is screening for the same core trait: structured, data-driven problem-solving ability. The case interviews that follow require candidates to drive the analysis themselves — unlike some firms where the interviewer leads. This candidate-led format is a hallmark of McKinsey's process and a key differentiator in preparation requirements.

McKinsey's full recruitment process runs across four primary stages. Each stage is a meaningful filter — roughly half of candidates are eliminated at each step. Progression requires consistent performance, not a single strong showing.

The McKinsey Problem Solving Test (PST) is a 72-question paper-based assessment completed in 60 minutes. It is — or was — McKinsey's most widely used initial screening tool, and despite the global rollout of Solve, it remains in active use in several markets. The PST is not an SHL aptitude test and is not a general psychometric battery. It is McKinsey's proprietary instrument, designed to mirror the analytical demands of actual consulting work.

The test presents business scenarios — typically based on client case material — and asks candidates to identify relevant data, draw sound inferences, and solve quantitative problems within a strict time limit. The emphasis is on speed and accuracy simultaneously. At 72 questions in 60 minutes, you have less than 50 seconds per question on average, which means learned pattern recognition and efficient data extraction are essential.

PST Question Types

• Data sufficiency: Given a set of data or constraints, determine whether the information provided is sufficient to answer a specific question. These questions test logical rigour — many candidates over- or under-read the data.
• Logic analysis: Business scenario-based reasoning questions. You must identify the most logical conclusion, find the assumption underlying an argument, or evaluate the strength of a given reasoning chain. Similar in spirit to verbal reasoning but grounded in business contexts.
• Chart and table interpretation: Multi-source quantitative questions — bar charts, scatter plots, tables, financial summaries. Faster to answer if you practise data extraction speed. Similar to advanced numerical reasoning but applied to consulting-style business data.

PST Scoring and Cut Score

McKinsey does not publish its PST cut score. Based on candidate reports and McKinsey's own published guidance, the test is scored on raw marks, and the pass threshold is estimated at approximately 70–75% correct (roughly 50–54 of 72 questions). However, the difficulty level and norm group mean that scoring well requires both accurate reasoning and consistent pacing — not just knowledge.

PST vs Solve: Comparison

McKinsey Solve is a game-based digital assessment developed specifically by McKinsey to replace the PST in most global markets. Launched from 2020 onwards and now the standard screening tool across North America, Europe, and most Asia-Pacific offices, Solve is fundamentally different from any aptitude test you may have taken before. It does not look like a test. It looks like a game — by design.

Solve typically comprises two game modules, though McKinsey has piloted additional modules in some markets. The two core games are Ecosystem Management and the Redrock Study. Together they run for approximately 70 minutes. The assessment is completed on a desktop or laptop browser, and McKinsey advises candidates to use a mouse rather than a trackpad for precision in the ecosystem game.

What Solve Measures

Solve Preparation Tips

• Use McKinsey's official practice module — McKinsey provides a sample game at the start of the Solve session. Take it seriously; it is a genuine orientation to the mechanics, not a throwaway tutorial.
• Practise inductive and abstract reasoning — The pattern recognition and rule-inference skills tested in inductive reasoning tests directly underpin performance in Solve's ecosystem game.
• Think out loud (even silently) in structured terms — Narrate your hypothesis: "If I reduce species X, I expect Y to increase because..." This structured reasoning approach mirrors what Solve is measuring.
• Manage time across both games — Solve is not time-pressured in the same way as the PST, but the ecosystem game has round limits. Avoid spending too long optimising a single round at the expense of learning from subsequent rounds.

After passing the digital assessment, McKinsey invites candidates to first-round case interviews — typically two interviews on the same day or across consecutive days. Each interview lasts approximately 45–60 minutes and is split between a case component (30–40 minutes) and a Personal Experience Interview component (15–20 minutes). Interviews are conducted by McKinsey consultants at the engagement manager or associate principal level.

McKinsey's case interview format is candidate-led — a critical distinction from the interviewer-led format used by some other consulting firms. In a candidate-led case, you are expected to structure the problem, propose the analytical approach, drive the analysis, synthesise findings, and deliver a recommendation — all under the interviewer's guidance but fundamentally at your own direction. The interviewer will respond to your questions and provide data when you request it, but they will not tell you what to analyse next.

The McKinsey Problem-Solving Approach

• Clarify the problem statement — Before structuring, ask 1–2 clarifying questions to confirm the business context, the client's specific goal, and any constraints. This demonstrates you understand that consultants scope problems before solving them.
• State your structure — Lay out the MECE (Mutually Exclusive, Collectively Exhaustive) framework you will use to approach the case. Say it aloud and confirm alignment with the interviewer before proceeding. Avoid applying off-the-shelf frameworks (Porter's Five Forces, 4Ps) without tailoring them to the case.
• Lead with a hypothesis — McKinsey's approach is hypothesis-driven, not exhaustive. State your initial hypothesis ("My hypothesis is that the profitability decline is driven by cost increases rather than revenue loss") and design your analysis to test it efficiently.
• Drive the analysis — Request specific data to test your hypothesis. When data is provided, interpret it accurately and update your hypothesis if the data requires it. Narrate your reasoning — show the interviewer your thinking, not just your conclusions.
• Synthesise and recommend — End with a clear, structured recommendation: "In summary, the client should [action] because [top 3 reasons]. The key risk is [X], and I would recommend addressing it by [Y]." Avoid wishy-washy "it depends" conclusions without direction.

Key Frameworks Used in McKinsey Cases

Rather than memorising frameworks, build a toolkit of analytical approaches you can adapt. The most commonly relevant structures in McKinsey cases include profitability trees (revenue vs cost decomposition), market entry analyses (market size, competitive dynamics, capability fit), merger and acquisition synergy analyses, and operational improvement frameworks. For a comprehensive approach to structuring cases, see our Case Study Interview Guide.

The Personal Experience Interview (PEI) is McKinsey's distinctive approach to behavioural and competency interviewing. Unlike general competency-based interviews that cover a wide range of soft skills, the PEI is tightly focused on three core themes that McKinsey believes predict consultant effectiveness. Each PEI typically explores one theme in a single interview — so across two first-round interviews and two final-round interviews, all three themes will be covered, sometimes revisited.

The Three PEI Themes

How to Prepare PEI Stories

Each PEI answer should follow a structured narrative — McKinsey interviewers are trained to probe deeply. A surface-level STAR answer is not sufficient. The interviewer will follow up with probing questions: "What would you have done differently?", "Why did you make that specific decision?", "What was your personal contribution versus the team's?". Your story must be real, rich in specific detail, and consistent under scrutiny.

• Prepare 3 anchor stories — one for each theme — drawn from the most impactful experiences in your CV. These should be real, specific, and demonstrably significant in scale or difficulty.
• Lead with your personal role — McKinsey is explicitly assessing your individual contribution, not the team or organisation. Use "I" not "we" when describing decisions and actions. Acknowledge team contributions without hiding your personal impact.
• Quantify outcomes wherever possible — "The project delivered a 23% reduction in processing time" is more compelling than "we improved efficiency significantly."
• Practise probing follow-up questions — Rehearse with a partner who asks "why did you do that?", "what was the alternative?", and "what was your greatest learning?" after each story segment.

For a broader framework on behavioural interview preparation, see our guide on the STAR interview technique. For strength-based variations that some McKinsey interviewers also use, see our strengths-based interview guide.

Candidates who pass the first round are invited to McKinsey's final round — two further interviews, both conducted by partners (senior partners or directors). The final round typically takes place at a McKinsey office, though virtual formats are available in some regions. Unlike assessment centres at other firms, McKinsey's final round is purely interview-based — there are no group exercises, written case studies, or presentations to prepare separately.

The format mirrors the first round: each interview contains a candidate-led case and a PEI component. However, final-round cases tend to be more ambiguous, more strategic in nature, and more likely to involve a situation where data is sparse or contradictory. Partners are testing not just whether you can solve a well-defined problem, but whether you can navigate genuine uncertainty and still deliver a well-reasoned recommendation.

What Changes at the Final Round

• Greater ambiguity — Partner cases are frequently less structured at the outset. The problem statement may be intentionally vague, or the "right" answer may be genuinely debatable. McKinsey is testing whether you can impose structure on an ill-defined problem without being paralysed by it.
• More strategic, less operational — First-round cases often test analytical mechanics (profitability trees, market sizing). Partner cases are more likely to involve strategic trade-offs — entering or exiting a market, responding to a competitive threat, advising on an acquisition. These require broader judgement in addition to quantitative rigour.
• Partner interruptions and challenges — Partners are more likely to push back on your structure, challenge your recommendations, or introduce new information mid-case to test how you adapt. Stay calm, acknowledge the challenge, and update your reasoning explicitly.
• PEI at partner level — Partners probe PEI stories more deeply and are more sceptical of polish. Overly rehearsed answers that lack authentic detail will not land as well with partners as they might with junior interviewers. Genuine reflection on challenges and failures is valued.
• Cultural and values fit — Final-round partners are also assessing whether you would thrive in McKinsey's culture — its high standards, its pace, and its collaborative but demanding environment. Authentic curiosity about consulting and a genuine understanding of what the job involves matters here.

After the Final Round

Decisions are made at the partner level following all final-round interviews, usually within 1–2 weeks. McKinsey will typically provide a verbal offer via phone before written confirmation. If unsuccessful, McKinsey may indicate whether you are encouraged to reapply in a future cycle — this is taken seriously and many successful McKinsey hires applied more than once.

If you are preparing for a video-format final round, our HireVue interview guide covers techniques for performing well in recorded and live video interview formats.

A structured 6-week preparation plan aligned to McKinsey's process. Adjust the timeline based on when your assessment invitation arrives — but allow at minimum 4 weeks of active preparation before your first case interview.

Weeks 1–2: Cognitive Assessment Preparation

• PST candidates: Download McKinsey's official PST practice materials (available on the McKinsey careers website). Complete full timed mock PSTs. Target 100% completion within the 60-minute window — leaving questions unanswered is costly. Drill numerical reasoning for data speed, and verbal reasoning for logical precision in business contexts.
• Solve candidates: Use McKinsey's provided practice module. Build cognitive flexibility through inductive reasoning practice. Familiarise yourself with systems dynamics thinking — read about feedback loops and second-order effects in complex systems.
• All candidates: Complete several timed practice tests under realistic conditions. Review every error analytically — what reasoning error led to the wrong answer?

Weeks 3–4: Case Interview Fundamentals

• Learn the candidate-led case format — Practice cases from McKinsey's official case library (available free on the McKinsey careers site). Work through at least 10 cases before your first mock with a partner. Focus on structuring, hypothesis formation, and synthesis first; quantitative execution second.
• Practise with a case partner — Solo case preparation has limits. Partner practice that simulates the real interview format — with follow-up questions, data requests, and probing — is significantly more effective. Use consulting prep communities (PrepLounge, RocketBlocks) if you do not have access to McKinsey alumni.
• Build your PEI story bank — Draft your three core PEI stories. For each story, write out the full context, your specific actions, the outcome, and your retrospective reflections. Then practise narrating them aloud until they feel natural rather than rehearsed. See our STAR technique guide for story structuring.
• Develop commercial awareness — Read the Economist, FT, or HBR regularly. Build a view on 2–3 industries. McKinsey cases span sectors — the broader your business knowledge, the more quickly you can orient in unfamiliar case contexts. Our commercial awareness guide provides a structured framework.

Weeks 5–6: Advanced Practice and Simulation

• Simulate full interview sessions — Practice 45–60 minute mock interviews that include both a case and a PEI component, back to back. Build the cognitive endurance to perform well across two full interviews in a single day.
• Stress-test your PEI stories — Have a partner probe deeply: "What would you have done if the stakeholder had still refused?", "What was the single biggest thing you personally contributed?", "What did you learn from this that you applied later?" Your stories should hold up under 15 minutes of follow-up.
• McKinsey-specific research — Read McKinsey Global Institute reports and the McKinsey Quarterly. Know McKinsey's major practice areas and understand the difference in culture and approach between McKinsey, Bain, and BCG. Be able to articulate specifically why McKinsey over its peers.
• Situational judgement readiness — Final-round partner cases involve genuine situational judgment. Our situational judgement test guide covers the underlying reasoning frameworks that inform sound professional judgment under ambiguity.