McKinsey Solve Retake: What to Do After a Rejection

McKinsey publishes no general Solve retake wait. Learn what to ask your recruiter, when to pursue other firms, and how to use a 12-week preparation window.

Updated Oct 11, 2026By Esteban Ronsin
On this page

McKinsey does not publish a general rule for retaking Solve after a rejection, or a fixed wait before reapplying, in the official sources checked October 11, 2026. Ask the recruiter handling your application for your actual eligibility date and whether another Solve invitation would be part of a new process. McKinsey says it considers Solve with the rest of your application, so the next decision is larger than whether you can replay a game.

Can I retake McKinsey Solve after being rejected?

McKinsey has not published a general post-rejection Solve retake right or waiting period in its Solve page or August 2025 FAQ, checked October 11, 2026; ask your recruiting contact to clarify the next step for your role and office. The familiar 12- or 24-month figures circulate on prep sites, unverified. Do not put one in a calendar without confirmation.

ClaimEvidence statusWhat you can do
A fixed wait applies after SolveNot publishedAsk for the date tied to your application.
Your old score disappears on reapplicationNot publishedAsk whether an earlier result affects the next process.
A rejection identifies a failed gameNot publishedAsk if any feedback can be shared; keep your own recollection separate.
A technical link may be resetOfficial, conditionalContact Solve support when the fault occurs.
Solve is considered with the applicationOfficialReview the wider application as well as assessment practice.

The FAQ directs nontechnical questions to your recruiter. A new job posting, another office or a different email address does not answer whether you are eligible. If your decision email gives a date or instruction, keep it and ask only about what is unresolved. Our reapplying after consulting rejection guide covers the wider firm question, though its reported waiting periods are not a McKinsey Solve rule. An invitation that is still open is a different problem, covered in the Solve deadlines and extensions guide.

Try a focused reasoning check: The Red Rock practice below is a Road to Offer simulation, independent of McKinsey. It can expose an error in your own work; it cannot reveal how McKinsey scored your previous sitting or whether you may retake Solve.

Live free simulator from Road to Offer for the McKinsey Solve Red Rock study. Practise this style of assessment in the browser, no account needed to start.

Plan the next attempt by date

Enter your next Solve test date, or none yet, and get a plan for each day until then. Free to build.

Build my Solve plan

Does rejection after Solve mean I failed the assessment?

No: a rejection after Solve does not establish that Solve alone caused it, because McKinsey officially considers the result alongside the application and other assessments. The decision tells you the application did not progress, and nothing more specific.

What a rejection after Solve can and cannot tell you

McKinsey states
Solve is considered with the rest of the application and any other assessment results.
The recruiter decides on multiple factors, not on Solve alone.
Solve is an additional data point in recruiting.
Circulates on prep sites, unverified
Pass-rate percentages and score cutoffs.
A penalty for each missed condition.
Waits of 12 or 24 months.
Not published
A pass mark, score scale or game weights.
Whether a score or breakdown is shared.
When results arrive.

Suppose you remember losing time on a chart, then receive a rejection. That memory can guide practice. It cannot explain the email.

One memory of a slow chart, two ways to use it

Reads a cause into the email

The chart cost me the interview

The email discloses no score and no failed game, so this claim cannot be verified.
Keeps a practice hypothesis

Check how I extract the denominator

A habit you can test on an independent question while you improve the rest of the application.

Note the task and your suspected error without reconstructing confidential game content, and keep it apart from anything a recruiter tells you: the recruiter message can set an application decision, the memory only guides practice. If feedback is offered, use it. Our Solve overview owns the changing format and scoring evidence, whether Solve matters covers its place beside other recruiting evidence, and who receives a Solve invitation is a separate unpublished question.

Apply the denominator check in a free Red Rock simulation

Use an independent chart question to check which population your answer describes.

Open Red Rock practice

Should I wait for McKinsey or apply to other firms now?

Apply to suitable other firms now if their own application windows and your readiness permit; McKinsey has not published a general Solve reapplication date, and waiting for an unconfirmed one need not pause your whole search. This is a recruiting strategy, not a claim that another firm will invite or accept you.

SituationMcKinsey actionOther-firm actionDecision trigger
Recruiter gives an eligible dateSet a reminder and build a stronger application.Pursue relevant live roles in parallel.Your own deadlines and readiness.
Recruiter has not answeredFollow up once with role and office details.Keep preparing and applying where eligible.A verified application opening, not a rumored wait.
New McKinsey invitation arrivesRead its instructions and confirm the required assessment.Keep existing applications moving.The invitation and your available preparation time.
Your profile has not changedImprove the CV and evidence of impact before reapplying.Consider roles that fit your current evidence.A credible new accomplishment, not just time elapsed.

One McKinsey application can be a priority without being your only route. The MBB recruiting roadmap covers the broader sequence; do not borrow its unsourced pass-rate or deadline figures for this decision. Each firm runs its own assessment, so see the McKinsey assessments hub for this one and follow each actual invitation elsewhere.

What should I ask my McKinsey recruiter before reapplying?

Ask your McKinsey recruiter for the eligible application date, whether the new role requires another Solve sitting, and whether any previous result or feedback affects that process; the official FAQ sends nontechnical questions to the recruiter and does not publish these retake answers. Include your role, office and application reference if you have one.

For example: “Thank you for the update on my application for [role] in [office]. I remain interested in future openings. Could you confirm when I may apply again, whether another Solve assessment would be required, and whether you can share any feedback I should use before reapplying?” If the message already names a date, ask only the remaining questions, and do not imply that a recruiter owes a score breakdown. The experienced-hire Solve guide and MBA Solve guide address those application contexts, but neither replaces a role-specific recruiter answer.

What if a technical issue disrupted my Solve sitting?

McKinsey officially says to contact Solve support by email or live chat when a technical issue arises; support may add time or reset the link depending on the problem, but a reset is not automatic. The FAQ also says that without contact at the time of the issue, McKinsey makes no reset exception for it. This route concerns a disrupted sitting, not a new attempt after a recruiting decision.

A fault during the sitting and a retake after a decision go to different people

A technical fault while your link is still active
Solve supportOfficial route
Email [email protected] or use live chat when it happens. Support may add time or reset the link.
A retake after a recruiting decision
The date you may apply again
Your recruiterOfficial route
The FAQ sends nontechnical questions here. It publishes no retake answer.
Contact routes as given in McKinsey's August 2025 Solve FAQ.

When you write to support, give the time, the type of fault and your application reference. Do not send screenshots or recordings of assessment content: McKinsey's integrity rules prohibit capture. If the sitting has ended, tell your recruiter what happened and whether you contacted support at the time, without promising yourself a late reset. Running out of time is a practice issue, not the technical exception the FAQ describes.

How can I use 12 weeks without assuming a 12-week retake rule?

Use a 12-week sample plan as a self-chosen preparation window, not as a McKinsey waiting period: the official sources checked October 11, 2026 give no reapplication interval. Start it when you receive a decision and change its length when a recruiter answers.

Illustrative candidate: Maya is a fictional analyst rejected after a Solve sitting. She has two possible consulting applications opening in the next three months, an older CV with one measurable project result, and a habit of rushing percentage calculations in practice. None of this describes a real applicant or a McKinsey scoring pattern. Her window is her own choice of four blocks:

Clarify + build evidence + rehearse + submit, in weeks (fictional)
These are planning blocks chosen for the example, not McKinsey eligibility periods or assessment timings.

What Maya does in each block

1
Clarify and chooseWeeks 1 to 2
Send the recruiter note, check live openings and build a one-page tracker of role, deadline source, contact and next action. Rewrite one CV bullet as an outcome she can document. Run one independent Red Rock attempt and record one calculation she can explain on a fresh problem.
2
Build evidenceWeeks 3 to 6
Pick a work project with a real deliverable and have a manager check the wording before it goes on the CV. Talk to people in the roles she is considering. Each week, review one case interview and one assessment attempt and carry one correction forward.
3
RehearseWeeks 7 to 10
Use fresh chart questions to test whether she still confuses percentage change with percentage points, then move to a different habit, such as a missed condition in Sea Wolf practice. Practise a full case and an interview story with a partner.
4
Submit and adjustWeeks 11 to 12
Submit only where she has checked the opening and her eligibility, then prepare for the next real step each firm sends.
The recruiter gave a later dateKeep McKinsey on the tracker and pursue the other two roles
The recruiter gave an earlier dateCompress the rehearsal block
A fictional plan. Other firms are in it from week one; her actual Solve result stays unknown throughout.

Each block has its own guide. For the application: the consulting resume guide, McKinsey resume guide and networking guide. For the data method: the Red Rock study guide and case math practice guide. For interviews: the case interview prep timeline, McKinsey case guide and PEI guide. If another assessment is invited, Maya reallocates practice to that invitation, not to a remembered game list.

Her weekly hours move as the plan does. Once the CV and role decision is made, time shifts toward interviews while one Solve reasoning session stays.

A fictional schedule, not a measured candidate outcome or recommended universal dose.
Week 1 hours: CV and roles + cases + Solve (fictional)
Week 10 hours: CV and roles + cases + Solve (fictional)
Case share of week 1
Case share of week 10

The weekly total is unchanged and the case share is larger. That is all the numbers show: an allocation, not an outcome. A recruiter reply or a near deadline would change it again.

Quiz

What can Maya conclude from her fictional weekly chart?

Find the condition you skipped in a Sea Wolf run

Three sites and a practice score at the end, free. Log the one condition you missed, as Maya does in weeks 7 to 10.

Try Sea Wolf free

How should I prepare if I am invited to Solve again?

If McKinsey sends a new Solve invitation, its stated length and each task's untimed tutorial are the official guides for that sitting; McKinsey does not publish that your earlier score is erased or that the game mix will repeat. Its July 2025 article names Sea Wolf; Red Rock and Sustainable Futures Lab are candidate-reported, and no complete current game list is published.

Before a new sitting

1
Read the invitation
Take the role, length and instructions from the actual McKinsey message. No general deadline or game map is published.
2
Pick an uninterrupted slot
The FAQ says to choose a time when you can finish without being disturbed.
3
Run the technology check on a PC or Mac
The link checks your device before Solve begins.
It passesStart when you are ready
It fails, or a fault appears mid-sittingContact Solve support at that moment
4
Read each untimed tutorial
It explains the objective and navigation for that task, whatever an outside guide says.
5
Put outside aids away
Websites, applications, AI tools, prepared notes, recording and help from others are barred unless an accommodation is approved in writing.
Based on McKinsey's August 2025 Solve FAQ.

Until an invitation names the games, practise the reasoning each one asks for. Every card opens an independent Road to Offer simulation; none is McKinsey's assessment.

Build a Solve plan for the days you have

Enter your Solve test date and get a plan for each day until then. No date yet? The plan still builds, and you can set the date later.

Use Red Rock practice for data reasoning, Sea Wolf practice for constraint checks, and Sustainable Futures Lab practice only if it is relevant to your invitation. The Red Rock versus Sea Wolf guide explains how those decisions differ, the Ocean Treatment guide works one fictional microbe site in full, and the system requirements guide covers the device check. The older Ecosystem Building name belongs to the game history guide.

Sources and evidence boundaries

Official sources checked October 11, 2026: McKinsey's Solve page and August 2025 Solve FAQ establish the use of Solve with the wider application, invitation length, tutorials, device and support route. McKinsey's assessment integrity expectations cover recording and outside help. McKinsey's July 2025 game lab article names Sea Wolf and calls Solve an additional recruiting data point.

Reported, unverified context: candidate descriptions of Red Rock and Sustainable Futures Lab and circulating 12- or 24-month waits. The 12-week plan, Maya and the chart numbers are expressly fictional teaching choices. Not published in the reviewed official sources: a general retake or reapplication rule, score carry-over, a guaranteed breakdown, per-game weights, a cutoff, who receives an invitation, and a universal result date. Your recruiter and any new invitation govern your case.

Frequently asked questions