Failed McKinsey Solve? Retake and Reapply Rules

Can you retake McKinsey Solve after a rejection?

McKinsey does not publish a general right to retake Solve after a rejection or a fixed wait before another attempt; the recruiter handling your application must confirm whether and when a new sitting is possible. The official Solve page and August 2025 Solve FAQ explain how the assessment is used and how to obtain technical help. Neither gives an ordinary retake policy.

That matters if a rejection follows a sitting that felt poor. Your feeling is useful for deciding what to practise, but it does not establish your score or the reason for the decision. McKinsey officially says the Solve result is considered alongside the rest of your application and any other assessment results. The guide to how the Solve result is used sets out that official wording, the scores and results guide covers what a candidate message can and cannot tell you, and the pass rate guide checks the unsupported cutoff and pass rate figures.

For example, suppose you lost track of a Sea Wolf constraint and later received a rejection. You can log the constraint error as a practice target. You cannot conclude that Sea Wolf alone caused the rejection or that an automatic retake becomes available on a particular date. Keep those as separate questions for the recruiter. A strong feeling about one game does not prove that another game compensated for it either: McKinsey publishes no per-game weights.

When can you reapply to McKinsey after Solve?

McKinsey does not publish a general reapplication waiting period after Solve in the reviewed public sources, so only your recruiter can give a usable date for your role and office. Figures of 12 or 24 months circulate on prep sites and forums, but they are unverified. Do not turn either figure into a deadline, a guarantee that an application will be accepted, or advice to apply through another office.

The next useful step is a short message tied to your actual application: “Thank you for the update on my application for [role and office]. I would like to be considered again when eligible. Could you tell me when I may reapply, whether a new application would include Solve, and whether my earlier Solve result affects the next process?” This asks for a decision you can act on without claiming there is a universal rule. If the rejection message already states a date or next step, use that instruction and ask only about what remains unclear.

If you applied to more than one role or office, name each application separately. McKinsey's reviewed sources do not explain whether a result transfers across offices, whether a second invitation is issued for a different role, or whether your application history changes eligibility. A different email address or office is not a reliable workaround. Wait for a recruiter answer before treating a new posting as permission to sit Solve again. The invitation guide explains what to read when you do receive a new link, and who receives a Solve invitation covers why a new application does not guarantee one. If you come back later through a different route, see what is known about Solve for experienced hires and for MBA candidates. While you wait for a decision, the timeline guide separates official timing from candidate reports.

What if a technical problem disrupted your Solve attempt?

McKinsey officially says to contact [email protected] or the Solve live chat when a technical issue arises; support may give extra time or reset your link depending on the issue, but a reset is not promised. The August 2025 FAQ says support can run diagnostics on your link and help with problems such as failed technology checks or graphics not working. It also says that if you do not contact support when the issue occurs, McKinsey cannot make a reset exception for that technical problem.

If the assessment is still open, use the support route shown in your invitation or link. Give the time and type of failure and the stage where it happened, without sending screenshots or recorded assessment content. McKinsey's integrity rules prohibit recording or capturing the assessment. If you have already finished and did not contact support at the time, tell your recruiter what happened, but do not present a late reset as an official entitlement. A pacing mistake or an answer you regret is not the technical issue described in the FAQ.

For a future sitting, the official FAQ says the link runs a technology check before Solve starts, the assessment requires a PC or Mac rather than a phone or iPad, and each task starts with an untimed tutorial. The system requirements guide covers the technology check and the common faults, and the test day checklist explains the setup and support path in more detail. If you need an accommodation for a disability, a health condition or a specific learning difficulty, McKinsey's official direction is to speak to your recruiter; raise it before you open the link. McKinsey's disability accommodations page has more.

Does a rejection prove you failed Solve?

A McKinsey rejection after Solve does not prove that Solve alone caused the outcome: McKinsey officially says its recruiters consider the result with the rest of your application and other assessments. A rejection establishes the decision on that application. It does not, by itself, reveal a pass mark, a game score, the weight of Solve or which part of your profile mattered most.

Suppose your Red Rock analysis felt strong but your Sea Wolf treatment felt rushed. The useful observation is that you may want a better rule check under time pressure. The unsupported leap is “I failed Sea Wolf, so that must have been the reason.” Conversely, a confident sitting followed by rejection does not show that your answers were scored highly. If a recruiter shares feedback, use it. If no feedback is available, keep an uncertainty label on your self-review. For the question of whether a particular score predicts an interview, see how to read Solve results; for the skills McKinsey says the assessment looks at, see what Solve measures.

It is also possible to spend the whole gap practising an old format. Candidate reports in 2026 describe Red Rock, Sea Wolf and versions of Sustainable Futures Lab, while McKinsey's July 2025 blog officially names Sea Wolf only. McKinsey does not publish the current game list. Check the dated format update when a new invitation arrives and let the actual invitation and tutorial take priority over any old prep page.

How do you decide what to practise without a score breakdown?

McKinsey publishes no guaranteed game-by-game feedback, so use a labelled self-review to choose practice rather than pretending you know your assessment score. Write down the task where you lost time, the rule you may have missed, and the action you would take next time. Label each note “remembered from my sitting” or “confirmed in independent practice.” Those are training clues, not McKinsey grading evidence.

Choose the first drill by the error, not the game you enjoyed most. If you misread a denominator or forgot a unit, go to the Red Rock practice method and explain the unit before calculating. If you kept changing microbes without a full constraint check, use the Sea Wolf method and verify the whole treatment before committing. If your later decisions drifted from your priorities, use the Sustainable Futures Lab guide to write a decision rule and test it against new information.

Independent practice on the practice chooser can show whether you repeat an error, but its feedback is not a McKinsey score. After each run, record the question type, your reasoning, what the feedback showed, and one correction to try. When an error stops repeating, move to the next one. If you cannot remember what happened in the real sitting, start with one untimed run per relevant game rather than inventing a diagnosis. The difficulty guide groups the common reasoning traps without turning them into a claimed official scoring formula, and Red Rock versus Sea Wolf helps you pick which game to practise first when both feel weak.

What should you do in the months before another application?

Use the time before a possible McKinsey reapplication to strengthen both Solve reasoning and the rest of your candidacy; the plan below is our practice plan, keyed to events instead of dates, because McKinsey publishes no official waiting period or eligibility date. Start it when you receive a decision and let your recruiter's answer set how long the middle stretch lasts. McKinsey officially considers Solve together with the rest of your application, so game practice is only part of the work.

The gap is where the work happens. Do it in this order, compress it if your recruiter gives a short window, and repeat the middle steps if the window is long.

If a technical issue was reported during the sitting, keep the support reply and follow its instructions alongside this plan. When a new invitation arrives, stop the long plan and switch to the short preparation plan and the habits that protect a sitting.

What should you check if McKinsey invites you to Solve again?

If McKinsey sends you a new Solve invitation, the official FAQ says its stated length and the task tutorials govern that sitting; McKinsey does not publish that your old score is erased or that the games will match your last attempt. Confirm the role, deadline and support contact in the new message. Do not assume a different office, role or email means a fresh scoring policy.

Use the invitation length guide to see which games candidates report for different lengths, while keeping the reported status visible, and the deadline and extension guide if the new date is tight. Read the untimed tutorial before each task even if you recognise the theme. McKinsey says scenarios vary so candidates do not get identical parameters and data combinations. Practising a method transfers better than memorising an answer. For a tight window, the seven day, three day or final 48 hour plans help you select a manageable schedule.

Keep the final sitting clean: McKinsey officially forbids outside applications, websites, AI tools, prepared notes, recording and help from another person, except for accommodations approved in writing. Breaking those rules can bring exclusion, a rescinded offer or restrictions on future applications, which matters more than usual if you are counting on another attempt. Independent practice is for before test day. When Solve is live, use only the resources its instructions permit and contact support at once if a technical issue appears. The test day checklist lists the setup checks, and the short-answer FAQ covers the remaining rule questions.

Sources and evidence boundaries

• Official, checked October 11, 2026: McKinsey's Solve page says Solve is considered with the rest of the application and gives the Solve technical support route. The August 2025 Solve FAQ specifies technical support, possible extra time or a link reset depending on the issue, contact at the time of the problem, untimed tutorials and the recruiter's role in nontechnical questions.
• Official, checked October 11, 2026: McKinsey's assessment integrity expectations and the Solve FAQ prohibit outside help and recording. The July 2025 McKinsey blog names Sea Wolf and describes Solve as an additional recruiting data point.
• Reported, unverified: Prep sites and candidate discussions circulate 12 or 24 month waits and describe particular game formats. Neither figure is a published McKinsey rule. This guide does not infer an eligibility date, a score reset or a hiring outcome from them.
• Not published in the reviewed official sources: a general retake policy after a result, a reapplication interval, score carry-over across applications, a limit on attempts, per-game weights, and a universal result timeline. Your recruiter is the source for your particular application.