Do Experienced Hires Take McKinsey Solve? A Working Professional’s Plan

McKinsey does not publish a Solve invitation rule for experienced hires. Learn what your invitation settles, how to practise rusty data skills, and how to balance Solve with case and PEI preparation across two working weeks.

Updated Oct 11, 2026By Esteban Ronsin
On this page

Do experienced hires take McKinsey Solve?

McKinsey does not publish a rule saying every experienced hire takes Solve or that experience exempts you; your invitation and recruiter determine what applies to your application. Its July 2025 account of Solve describes the game as given to early-career consultant candidates. That is an official description of one audience, not a complete invitation policy. Experienced applicants report receiving different instructions, but those accounts do not establish a firm-wide rule; what a Solve invitation does and does not signal covers the invitation itself.

Try a data task now, then use the worked exhibit below to repair whatever it exposes. This is Road to Offer's independent practice, not a McKinsey assessment or an official score.

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.

Fit Solve prep around your job

Enter your Solve test date and what your invitation says. You get a plan for each day until the test.

Build my Solve plan
QuestionWhat the checked evidence saysStatus
Who gets Solve?No published rule by experience, role, or officeNot published
Who does McKinsey describe?Early-career consultant candidates in its July 2025 accountOfficial
Where is your length?In your invitation emailOfficial
Is the game mix fixed?Applicants describe different versionsReported
Does Solve decide alone?It is considered with the application and other assessmentsOfficial

If you are still choosing an application route, the McKinsey resume guide helps you present your experience and the experienced-hire case interview guide covers the broader interview decision. Neither page can decide whether Solve is required for your vacancy.

Is Solve easier or shorter for a candidate with years of experience?

McKinsey publishes no easier, shorter, or separately scored Solve route for experienced applicants in the sources checked, so equal treatment across entry routes is unconfirmed too. The official Solve page and the Solve FAQ give general preparation and integrity rules. Neither sets out a lateral version or proves identical tasks for every applicant.

What is known about Solve for experienced applicants

McKinsey states
Solve is a gamified assessment in consultant recruiting.
No preparation, business knowledge or gaming experience is needed.
Scenarios vary in their parameters and data combinations.
Reported by candidates
Experienced applicants describe receiving different instructions.
Red Rock, Sea Wolf and sometimes Sustainable Futures Lab, in different combinations.
Not published
A Solve exemption or separate version by seniority.
A scoring curve or comparison group for experienced hires.
A pass mark, score scale or per-game minutes.

Your experience may help you define an objective or check a recommendation against a constraint. It will not make an unfamiliar screen familiar by itself. A manager who reads dashboards every morning may spot a trend quickly but still need to practise computing a rate from the correct baseline. A specialist who knows a market deeply may need to pause before importing an assumption the assessment has not supplied.

Transfer your work habits without importing your assumptions

1
Read the objective
Name the exact decision the screen asks for before inspecting every figure.
2
Select evidence
Keep the unit, date, and denominator beside each value you use.
3
Check constraints
Test the tempting answer against every stated rule.
It meets every stated ruleKeep it
It breaks oneReject it, however strong the number looks
4
Explain the conclusion
Separate what the data shows from a story about why it happened.

The main Solve guide owns the wider reported module picture. For other recruiting contexts, see the Solve guide for MBA candidates and the McKinsey internship guide. None of these routes is a basis for assuming your own task list or score comparison group.

What should you confirm before planning around your invitation?

McKinsey officially says your assessment length is in the invitation email, but it publishes no general deadline, extension, game-order, or per-game-minute rule, so plan from your actual message. Do not reverse-engineer your games from another applicant's duration.

Three sources settle your own sitting

Assessment length
Any deadline shown, with its timezone
Device and support instructions
Your invitationRead first
Copy the date into your calendar and plan from this message, not from a reported game map.
The objective and navigation of each task
The untimed tutorialOfficial
McKinsey says each live task begins with one, for the version you receive.
Whether this role includes Solve
Moving a slot around travel
Anything the message leaves unclear
Your recruiterAsk before committing
Ask before you book travel or meetings against the window.
The invitation and tutorial routes follow McKinsey's August 2025 Solve FAQ. Any deadline is whatever your own message shows; McKinsey publishes no general one.

Candidates report Red Rock, Sea Wolf, and sometimes Sustainable Futures Lab in different combinations. McKinsey's July 2025 article names only Sea Wolf; the other two names and their mechanics are candidate-reported. The Red Rock guide explains the reported data format, Red Rock versus Sea Wolf compares the two, and the Sea Wolf and Sustainable Futures Lab practice pages are separate Road to Offer exercises. The online assessments hub lists those practice options; it is not a forecast of your invitation.

Three related questions have their own pages: asking for a Solve deadline extension, the device check and system requirements, and a Solve retake, for which the checked official sources publish no waiting period or carryover rule.

How can you rebuild rusty exhibit reading and mental math?

An experienced applicant can use a short fictional data exercise to refresh baseline selection and interpretation; McKinsey does not prescribe this practice or publish a Red Rock question set. Suppose two service teams changed their intake process, and the question asks which team changed faster relative to its own start. These values are invented for teaching, not candidate data or an official Solve task.

Illustrative completed requests per week. The bars show absolute change; the question asks for change relative to each team's own start.

Each team's starting count is its own denominator:

Setup
Team A, 48 to 60 requests
Team B, 30 to 33 requests
Invented values. Team A changed faster in relative terms. The exhibit does not say why either count moved.

Team A: which count goes underneath?

Divides by the new count
60 is where Team A ended. The question asks about change from where it started.
Divides by the starting count
48 is Team A's own start, so the rate answers the question asked.

More completed requests may reflect capacity, demand, or a changed definition; the exhibit does not establish the cause or desirability of the increase. If the question instead asked which team handled more requests after the change, read the final counts, not the growth rates. The case interview math guide takes the denominator skill further.

Quiz

In the fictional exhibit, which team's requests changed faster relative to its own starting count?

Pick the right baseline in a free Red Rock run

Use Road to Offer's independent Red Rock practice to select evidence, calculate, and review worked answers. It is not a McKinsey task.

Practise Red Rock

How do you practise a constraint task without memorising a game?

The officially named Sea Wolf task involves selecting and evaluating microbes, while its detailed range and trait rules are candidate-reported rather than a published McKinsey specification. Practise the decision pattern with an invented example: a site requires a treatment's average strength to sit from 7 to 9 and at least one microbe to tolerate cold. Your proposed set has strengths of 6, 8 and 10, and only the second microbe tolerates cold.

Fictional set, strength range 7 to 9
Invented values. The site rule applies to the set average, so two members outside the range do not sink the set.

The trait rule is a separate check. The second microbe tolerates cold, so this set passes both invented conditions. Change one word in the rule and the same average no longer settles it:

Same set, stricter rule: every microbe must tolerate cold

Stops at the average

Accept the set

An average of 8 sits inside 7 to 9, so the set looks finished.
Reads the trait rule too

Reject the set

Only one of the three tolerates cold. A strong number never excuses a failed hard condition.

The Ocean Treatment and Sea Wolf guide works a complete fictional site with three ranges and two trait rules. The older Ecosystem Building guide is useful only for understanding why older game names still appear online; it is not a current game list.

Check every condition before you confirm a Sea Wolf set

Try Road to Offer's independent microbe-selection practice free and see your practice score at the end.

Try Sea Wolf free

What does a two-week weekday preparation plan look like?

This two-week weekday plan is an optional Road to Offer allocation for a working applicant, not a McKinsey requirement or a measured route to a pass. McKinsey says no preparation is needed and that each task starts with an untimed tutorial. Use the plan only if you want to reduce format surprise and refresh skills you have not used recently, and move it around the dates in your own invitation.

Week one: discover the gaps

1
Monday: read the invitation15 min
Mark its timezone and stated length, write one question for the recruiter if needed, and check that the planned device is a PC or Mac.
2
Tuesday: one data exhibit, no timer20 min
Label every value with a unit and a starting point.
3
Wednesday: two kinds of change25 min
One absolute, one relative. Write the denominator before calculating.
4
Thursday: a short constraint exercise20 min
List every required condition before selecting, then test the rejected option as carefully as the chosen one.
5
Friday: review your error log15 min
Choose one skill to repeat next week. Do not convert an invented practice score into an estimated McKinsey outcome.

Week two: keep Solve beside the rest of recruiting

1
Monday: repeat the weaker task type25 min
Use new numbers or conditions, then compare your decision method with last week's log.
2
Tuesday: one case exhibit or synthesis25 min
State what the data proves and what remains an assumption.
3
Wednesday: rehearse a PEI story20 min
Take it from your actual work: your decision, the resistance, the result and the lesson. Seniority alone is not the story.
4
Thursday: device, room and rules20 min
Check the exact device and quiet room you will use, read McKinsey's integrity rules, and remove any outside aid you would normally open at work.
5
Friday: final check15 min
Re-read the invitation, resolve any recruiter question, and stop adding new strategies. Move this earlier if the real deadline is sooner.
Optional weekday practice
Coaching time, not McKinsey test time. Move or shorten blocks to fit the deadline shown in your own invitation.

The reading for each block: the Red Rock format for Tuesday if that game is relevant to you, the case math guide to repair a missed operation on Wednesday, then the McKinsey case interview guide, the PEI guide and McKinsey's assessment integrity expectations in week two. If a case interview is imminent, shift a block toward the experienced-hire case guide. If the recruiter has not confirmed whether Solve applies, use the first block to resolve that before spending the rest on game mechanics. How much Solve matters goes further on splitting time between Solve and interviews, and how to get into MBB covers the broader route.

Run Thursday's and next Monday's blocks in whichever game your invitation points to. Each card opens Road to Offer's independent practice page for that game.

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.

What should you do on test day and after submitting?

McKinsey officially requires Solve candidates to work alone without outside applications, websites, AI tools, pre-prepared notes, recording, or screenshots, except for an accommodation it has approved in writing; it publishes no separate senior-applicant exception. The Solve FAQ says to choose an uninterrupted slot, use a PC or Mac, and complete the link's technical check. Sound is unnecessary and a mouse is optional.

Before opening the live task

  • Use the invitation. Confirm the actual deadline, timezone, length, and link rather than a reported game map.

  • Use the checked device. Take the technical check on the PC or Mac you will use for the assessment.

  • Protect an uninterrupted slot. Close work calls and outside tools; do not use saved notes or ask a colleague for help.

  • Keep support information available. Have the Solve support route from your invitation to hand before you start.

If this happensContactSource
Graphics or the technical check failSolve support, by email or live chat, when it happensOfficial, Solve FAQ
A non-technical questionYour recruiterOfficial, Solve FAQ
A disability, health or learning needYour recruiter, before the sittingOfficial, Solve FAQ
Work travel clashes with your windowYour recruiter, before the date shownNo public policy

The FAQ says support can diagnose the link and may give extra time or reset it, depending on the issue, and that no reset exception is made if you never contact support. McKinsey's disability guidance covers accommodations.

After submission, McKinsey says Solve is considered with your application and any other assessment results. It does not publish a pass mark, scoring weight, result timetable, or retake rule in the checked sources, so a difficult-feeling task cannot tell you whether your application has ended. Keep the submission record and any support case, ask your recruiter for an update against any timetable they gave you, and continue preparing the parts you can control, especially case interviews and PEI. The Solve impact guide explains why an assessment result is one recruiting data point rather than a public pass-or-fail formula.

Sources and evidence boundaries

  • Official, checked October 11, 2026: McKinsey's Solve page, the August 2025 Solve FAQ, the July 2025 game lab article, assessment integrity expectations, and disability accommodations guidance. The early-career description is not a rule for all experienced applicants.
  • Candidate-reported, unverified: experienced-hire invitation experiences and the names and mechanics of Red Rock and Sustainable Futures Lab. McKinsey names Sea Wolf, but does not publish a complete current game map. The fictional service and microbe exercises and the weekday allocation are original coaching illustrations, not McKinsey tasks or measured candidate outcomes.
  • Not published in these checked sources: who is invited by seniority, whether experienced hires have a distinct version or scoring group, deadlines and extensions, per-game times, a pass mark or pass rate, result timing, retakes, and any old-result carryover. Your invitation and recruiter answer individual process questions.

Frequently asked questions