No McKinsey Solve pass rate or success rate is published. Online pages estimate that about 20% to 30% of candidates pass, or about 70% to 80% do not, without showing data or a method (unverified, checked October 3, 2026). The only official figures are that Solve is given to around 300,000 early-career candidates a year (McKinsey blog, July 2025) and that results are considered together with the rest of your application, so no single score guarantees, or rules out, an interview.
| Figure | Value | Source and status |
|---|---|---|
| Pass rate | About 20% to 30% | Online estimates; unverified |
| Fail rate | About 70% | Online estimates; unverified |
| Candidates taking Solve | Around 300,000 a year | Official: McKinsey blog, July 9, 2025 |
| Pass mark, cutoff, score scale | Not published | Official: McKinsey Solve page and August 2025 FAQ |
"What is the pass rate?" is a reasonable question. You want to know how hard the bar is and how much preparation is enough. The problem is that the question assumes a fixed bar that McKinsey has never described. This guide does three things: it lists the claims that circulate and shows what each one is based on, it explains what McKinsey's own sources say actually decides advancement, and it ends with the parts of the outcome you can control. For how to read a result you have already received, use the McKinsey Solve results guide; this page does not repeat it.
What does McKinsey officially say about passing Solve?
McKinsey says nothing about a pass rate. The current McKinsey Solve page and the August 2025 Solve FAQ (checked October 3, 2026) publish no pass rate or cutoff, and say only the following about how Solve works and counts:
- Solve is McKinsey's game-based assessment, and no business or gaming knowledge is needed.
- Your invitation states how long your assessment is, and each task begins with an untimed tutorial.
- You complete it alone, without outside tools, and you may not record it.
- Your Solve results are considered together with the rest of your application.
- McKinsey's July 2025 blog post adds that Solve is given to around 300,000 early-career consultant candidates a year.
Neither source gives a passing score, a percentile cutoff, the weight Solve carries, or a score scale shown to candidates. Every number you read about passing comes from somewhere else. That is the boundary for the rest of this page.

Opening your Red Rock run…
The Red Rock run did not open here.
Where do the McKinsey Solve pass rate numbers come from?
Every McKinsey Solve pass rate figure comes from third-party pages or anonymous online posts, not McKinsey: figures of about 20% pass, 20% to 30% pass and about 70% fail circulate, all without data. We checked the pages that most often surface for "McKinsey Solve pass rate" on October 3, 2026; the table is a map of claims, not a set of facts.
| Claim | Who says it | Stated basis | Why it is unverified |
|---|---|---|---|
| Pass rate around 20% | A pass-rate page | Labelled an estimate; no source or method given | No McKinsey data, survey or sample is cited |
| 60% to 70% of applicants receive Solve | The same page | No source given | No invitation rate is published; another prep page says 80% to 90% of those who pass the screen instead |
| Failure rate around 70% | A score guide | "Most estimates"; no citation | The page itself says no passing score is published |
| Pass rates of 20% to 30%; about the 80th percentile is usually enough | A passing-score guide | Self-described inference from anecdotes | The page asks readers to treat it as a range, not a target |
| About 70% do not pass; decile 8 or above to be confident | An assessment guide | "Unofficial statistics"; no source | No sample or method; sites like this sell courses |
| About 20% pass; filters 80% of roughly 200,000 applicants a year | Another page, undated | No source given | No date, no data. McKinsey's own July 2025 blog says Solve is given to around 300,000 candidates a year, more than this applicant figure |
| Usually about 20% invited to interview; recently closer to the top 10% | An online post, 2024 | Personal view of the hiring market | No data; other posters said details are confidential |
| Roughly 20% to 30% move on after Solve | An online post, 2026 | No basis stated | One answer, no sample |
Notice two patterns. First, several figures cluster around "one in five", and none of the sources shows its data, so agreement between them is not independent evidence. Second, several of them mix different things: the share of applicants invited to Solve, the share of Solve takers who reach interviews, and a percentile on the test. Those are three different numbers, and none is published.
Sites that run their own simulators sometimes publish statistics about their own users. Those can be honest about their method and still say nothing about McKinsey's decision, because their users, tasks and scoring differ from the real assessment.
Where does Solve sit in the McKinsey hiring funnel, and how many candidates take it?
McKinsey Solve sits after the application and CV screen and before the case and personal experience interviews, and McKinsey says the result is read together with the rest of your application. The only official volume figure is from McKinsey's July 2025 blog post: around 300,000 early-career candidates take Solve each year. Every other number below is a third-party claim, and the claims do not add up to McKinsey's figure.
- ApplicationClaim
"More than 200,000 applications" a year, per third-party pages (unverified).
- CV screen, then Solve invitationClaim
60% to 70% of applicants receive Solve after a resume screen, per one prep page; another page says 80% to 90% of those who pass the screen. Accounts say an invitation usually means the CV already passed. McKinsey's July 2025 blog says around 300,000 early-career candidates take Solve each year, which does not fit these applicant and invitation estimates (200,000 applicants at 60% to 70% would be 120,000 to 140,000 Solve takers); treat both as unreliable. Does everyone get Solve? looks at who is actually invited.
- Solve result read with your applicationOfficial
Around 300,000 early-career candidates a year take Solve (McKinsey blog, July 2025), and McKinsey says results are considered together with the rest of your application. The share who advance, about 20% to 30% in most estimates, is not published.
- Case and personal experience interviewsNot published
No source we found gives a credible share of interviewees who receive offers.
- OfferClaim
Overall acceptance "below 1%", per one page, without a source.
Compiled by Solve Game Prep from unverified third-party claims, McKinsey's Solve page and its July 2025 blog, checked October 3, 2026. Only step 3 is an official statement.
Some pages also say large offices such as New York and London have more competitive thresholds than smaller markets. That is plausible given the reports below that the bar moves with the candidate pool, but no source offers data for it.
How does the McKinsey Solve pass rate compare with the old PST?
Some pages say McKinsey Solve filters slightly more candidates than the paper Problem Solving Test (PST) it replaced, but McKinsey has published neither figure. Two pages compare the two: one says Solve eliminates about 80% of candidates against about 70% under the PST, and another puts the PST at around 70%. Neither cites McKinsey, and the PST was a different test taken by a different applicant pool, so the comparison says little about your odds today. The McKinsey Problem Solving Game history explains how the tests relate.
Why do candidates fail McKinsey Solve?
Candidates most often fail McKinsey Solve through an unfamiliar format, time pressure, too many interacting variables, inconsistent decisions and no realistic practice, according to online write-ups. McKinsey gives no failure reasons, so these are reported patterns, not McKinsey feedback; each is paired below with a fix.
- Unfamiliar format. Time goes on working out what the screen wants. Fix: learn the controls in the untimed tutorial, and run each game once before test day.
- Time pressure. Rushed decisions late in a game, or Red Rock Cases left unanswered. Fix: rehearse a time budget, as in the Red Rock method.
- Too many interacting variables. Sea Wolf ranges and trait rules, or SFL priorities, slip out of view. Fix: check every choice against the rules before committing, as in the Sea Wolf method.
- Inconsistent decisions. Later SFL choices contradict the priorities set at the start. Fix: write your ranking down and test each decision against it, as in the SFL guide.
- No realistic practice. Candidates who go in cold meet all of the above at once. Fix: one timed run per game, then review errors by type.
Reasons 1, 2, 3 and 5 are commonly listed online. Reason 4 is a common concern for the SFL. The fixes are ours.
Is there a McKinsey Solve passing score or cutoff?
No Solve passing score or cutoff is published, and McKinsey does not show candidates a score scale or a threshold (Solve page and August 2025 FAQ, checked October 3, 2026). Candidates posting online describe the bar as relative rather than fixed: some say no exact cutoff exists publicly and that invitations depend on the candidate pool and hiring needs, so the same result could lead to an interview in one market and not another. That is anecdotal, not a McKinsey statement, but it fits the official line that Solve is weighed with the rest of the application (see does McKinsey Solve matter?).
Some candidates do report receiving a score or decile, sometimes after asking a recruiter. The McKinsey Solve score guide explains percentiles and deciles and includes a polite request template. Knowing your decile tells you where you ranked in a comparison group; it still does not tell you the cutoff, because none is published.
Do you need decile 8 or above? One page says decile 8+ means you can be confident and decile 6 most likely does not advance, without citing data. The reported case below cuts against treating that as a safe line: a 75th percentile result is in the 8th decile, and that applicant described a rejection.
What is a good McKinsey Solve score?
A good McKinsey Solve score has no official definition, because no scale is published; "good" can only mean a relatively strong result that supports the rest of your application. Two reported cases show why a score alone is not the answer:
- In an April 2024 online post, an applicant in Australia and Oceania reported a 75th percentile result followed by a rejection.
- In a July 2026 online post, an applicant with a reported top-decile independent score was still waiting on a CV review before any invitation.
Both are single reports and unverified. Together they illustrate the official point: the result is one input, read alongside your CV, experience and the office's needs. If you are still deciding how much to prepare, is McKinsey Solve hard? shows where prepared candidates actually lose points. For score scales, deciles and how to read a number you receive, see the McKinsey Solve score guide.
What McKinsey says it considers
- Solve resultsRed Rock, Sea Wolf, and the SFL if your invitation includes it
- The rest of your applicationCV, experience, education and other application material
One decision
Interview invitation, or application closed
No published pass rate, cutoff or weighting
Original diagram by Solve Game Prep, based on McKinsey's statement that Solve results are considered with the rest of the application. The relative weight of each input is not published.
How do you know if you passed McKinsey Solve?
You know you passed McKinsey Solve when you receive an interview invitation; a message saying your application will not proceed means you did not. An automated score email, a decile shared on request or a long silence is not a decision. People describe four kinds of messages after Solve:
| Message | What it is, as reported | Is it a decision? |
|---|---|---|
| Automated score email soon after submitting | A system email about your Solve score, reported a day after Solve; candidates read it as automatic | No |
| Score or decile shared on request | Some reportedly receive it after asking a recruiter | No, it is information, not an outcome |
| Interview invitation | The application moves forward to case and personal experience interviews | Yes, you advanced |
| Application will not proceed | A message closing the application for this cycle | Yes, for this application |
Timing is not a signal either. Acceptances and rejections reportedly take the same time. The Solve timeline guide gives the reported waits for each stage and when to follow up, and the results guide explains how to tell if you passed.
How can you improve your chance of passing McKinsey Solve?
You improve your chance of passing McKinsey Solve by knowing which games your invitation includes, removing avoidable errors in each game and protecting the sitting itself; an unverified pass rate is not useful for planning. Each of the seven steps below is trainable.
- Know which games you face. Your invitation length is the best clue: candidates report that about 65 minutes means Red Rock and Sea Wolf, about 85 adds the standard Sustainable Futures Lab, and about 95, reported since August 24, 2026, includes a newer 30-minute SFL first described by a candidate on September 11, 2026. The 95-minute guide explains the difference.
- Remove avoidable errors in Red Rock. Units, denominators and irrelevant facts are the usual traps. The Red Rock practice method works through them.
- Check every Sea Wolf choice against the site ranges and trait rules before you commit. The Sea Wolf method shows how.
- Stay consistent across SFL decisions. The SFL guide covers both versions.
- Use the untimed tutorials. The FAQ says each task starts with one. Learn the controls there, not on the clock.
- Protect the sitting. A quiet room, a passed technical check and your support contact saved, as in the test-day checklist.
- Strengthen the rest of the application. Since Solve is read alongside it, a sharper CV is part of "passing" too.
Find your weakest game with a free practice run
We offer one free run each of Red Rock, Sea Wolf, SFL Classic and SFL Island. Red Rock includes the full Study and six Cases, with 12 scored decisions worth 35 points on a 35-minute practice clock; Sea Wolf includes Site 1 of Simulation 1, four scored decisions on a 10-minute Simulation clock. With no account you can play the Red Rock Study, all of Sea Wolf Site 1 with its score, the start of SFL Classic and the SFL Island tutorial and onboarding; a free account (no card) unlocks the rest of each free run, the other scores and the reviews. Visual explanations include highlighted Red Rock calculations and charts, Sea Wolf constraint and treatment visuals, Classic decision and dependency diagrams, and Island evidence chains, placement maps and team feedback. These practice scores are not McKinsey scores or pass predictions. Paid Learning mode adds step-by-step coaching and feedback across all four formats, untimed in the clocked games, with the matching game pack, Solve pack or qualifying Annual access. The separate free account-based Solve plan schedules practice from invitation length and test date, not your score, for up to 28 days.

A practical way to use practice: run each game once untimed, list every error by type, then run it timed and check whether the same error types return. A shorter error list is a better readiness signal than any circulated percentage. The guide on how to prepare for McKinsey Solve turns that into a seven-day, three-day or 48-hour schedule, and the tips guide lists fifteen habits that protect your score.
What should you do if you did not pass McKinsey Solve?
If you did not advance after McKinsey Solve, plan to reapply later and fix whatever practice shows you repeat; a rejection tells you the outcome of that application, not which input decided it, because McKinsey reads the result alongside everything else. McKinsey's September 2026 Solve FAQ says you may complete Solve only once every 12 months from your completion date; confirm with the recruiter when a new application will be considered. The Solve retake guide sets out what is and is not known. Use the time on whatever you can measurably improve: if practice shows the same Red Rock calculation slips or Sea Wolf range errors, fix those; if your games were clean, the CV and experience side may matter more. The timeline guide covers the reapplication reports in more detail.
Are older McKinsey Solve pass rate claims still reliable?
No. Older McKinsey Solve pass rate claims are weaker still than current estimates, because none of the sources says which version of Solve its figure describes, and early versions featured games such as Ecosystem Building that 2026 candidates no longer report. The PSG, Imbellus and Solve history explains how the names map and covers the earlier Ecosystem game. A figure from an older test, or a different game mix, says even less about the 2026 assessment.
For how Solve compares with other firms' screens, see McKinsey Solve vs BCG Casey vs Bain SOVA. For the whole assessment in one place, start with the McKinsey Solve guide, or the McKinsey Solve FAQ for short answers. The McKinsey Solve game prep home page sets out the format, timing and rules in one place.
Sources and evidence boundaries
- Official: McKinsey Solve (digital assessment) page and Solve FAQ (PDF, August 2025), checked October 3, 2026. No pass rate, cutoff, score scale or weighting is published. McKinsey's July 2025 blog post (July 9, 2025) gives the figure of around 300,000 Solve candidates a year.
- Third-party estimates (unverified), checked October 3, 2026: figures from several pages, including some that give different invitation rates. None cites McKinsey data or a disclosed method.
- Online reports (anecdotal): individual candidate posts dated between 2024 and 2026. They describe individual cases and cannot be verified.
- Not known: any official pass rate, cutoff, percentile threshold, score weighting or invitation rate.
- Our practice: we offer four practice formats: Red Rock, Sea Wolf, SFL Classic and SFL Island. Our scores describe original exercises only. Written and reviewed by Esteban Ronsin.

