Red Rock vs Sea Wolf: Which McKinsey Solve Game Is Harder?

Which is harder, Red Rock or Sea Wolf, and which should you practise first?

Neither Red Rock nor Sea Wolf is officially the harder McKinsey Solve game: McKinsey publishes no comparative difficulty, per-game weights or pass mark. Practise whichever produces the clearest repeatable error in your own independent run first. McKinsey's Solve page says the result is considered with the rest of the application, not by a published game-by-game formula; how much Solve matters follows that point through.

You do not need a guess about which game feels tougher. Try both, record where a decision failed, and spend the next practice block fixing a behavior you can name. The wider Solve guide covers the overall assessment, and what a Solve invitation signals covers the invitation; this page makes the narrower practice choice. The Red Rock run below is independent Road to Offer practice, not an official McKinsey assessment. One free simulation per game is available; the Red Rock page explains that practice route.

What is actually known about the two games?

McKinsey officially names Sea Wolf and describes selecting and evaluating microbes, while the Red Rock name, detailed tasks and individual game times are candidate-reported. Its July 2025 game lab article establishes the Sea Wolf premise, and its Solve FAQ covers the invitation and tutorials.

This table is a source map, not a difficulty ranking, and the reported details may differ from your screen. A longer reported clock can reflect a different task structure, not a higher score weight. For the full reported Red Rock sequence, use the Red Rock study guide; for the microbe task and its older reported names, the Ocean Treatment game guide. If your invitation mentions a further task, the Sustainable Futures Lab page covers that separate practice path, and the online assessments overview puts the games side by side.

How do Red Rock and Sea Wolf demand different decisions?

Red Rock practice calls for choosing relevant evidence and expressing a calculated finding, while Sea Wolf practice calls for testing a proposed treatment against several conditions; these are coaching descriptions based on reported formats, not McKinsey's scoring rubric. The figure sorts the errors you can observe in a practice run by the check that fixes them.

Repeating a full run without naming the failure tends to repeat the habit. If exhibit arithmetic is the problem, the case interview math practice guide is a separate place to review the underlying skill. If the microbe task is unfamiliar, start from the official Sea Wolf premise above, then use the tutorial in your actual sitting. McKinsey says no prior business knowledge or gaming experience is required.

How should you compare one run of each game?

Compare one complete independent Red Rock run with one complete independent Sea Wolf run by logging observable errors, not by treating practice scores as official probabilities. A low practice result without that review does not tell you whether the problem was evidence, arithmetic, a trait rule or the clock.

Here is a fictional coaching example, not a recorded Road to Offer user or product output. Noor runs each game, reviews, then runs each again.

The repeated Sea Wolf rule is now the better next target, even though the first Red Rock run had more issues. A permanent split based on the first scores would have been a poor plan. The fictional counts do not map to McKinsey scoring.

The Red Rock simulation sits at the top of this page. The Sea Wolf simulation is here, so you can fill the second half of the log without leaving the article.

What should you do if Red Rock was the weaker practice run?

If Red Rock exposed a repeatable evidence or arithmetic error, practise that exact step before taking another full run; this is a coaching recommendation, not an official McKinsey priority. Take a fictional practice exhibit, invented for this page and not a Red Rock question. It asks for the growth in completed inspections from Period 1 to Period 2.

A growth question uses the earlier count as its base. Two lines answer it:

A correct percentage from the wrong periods would still be a poor explanation. If your actual problem was selecting the exhibit, rehearse identifying the period and unit before any math. If it was running out of time on later Cases, practise the handoff between tasks and review what you left unfinished. The dedicated Red Rock guide has fuller phase examples.

What should you do if Sea Wolf was the weaker practice run?

If Sea Wolf exposed a repeated missed condition, turn the site's rules into a check you apply to every proposed treatment before running it again. McKinsey's official description says Sea Wolf involves selecting and evaluating microbes for contaminated sites; the detailed site constraints are candidate-reported. Noor's repeated error was an overlooked exclusion rule, so here is a fictional Tidal Flat site to audit. It asks for average uptake from 3 to 6 and average stability from 5 to 7, both inclusive, and it excludes every drifting microbe.

Test K, L and M first:

Then swap M for N:

The order of this audit is a coaching device, not a claim about the assessment's scoring, and passing a practice rule set does not establish an official result. If the real tutorial describes a different interface or rule, follow it. The Ocean Treatment game guide works a second fictional site in full, and the Sea Wolf page explains the independent simulation.

How should your practice plan change with the time left?

With little time left, correct the clearest repeatable error and protect an uninterrupted sitting; with more time, rerun both games and change the priority when the error pattern changes. This is optional coaching advice. McKinsey's FAQ says no preparation is needed and puts your overall assessment length in the invitation. It does not publish a deadline or extension policy, so ask your recruiter about the timing of your own invitation; the Solve deadline extension guide separates the dates involved, and the system requirements guide covers the device check before you start.

If your invitation is close, use one focused correction and one brief check of the other game. With several days, alternate targeted review with a complete run of each game, and stop prioritizing a weakness that no longer appears. A changing error log beats a fixed fraction of study time. Each card opens Road to Offer's independent practice page for that game.

If you are fitting this around a job or a recruiting calendar, the experienced-hire Solve plan and the Solve guide for MBA candidates deal with that scheduling. The interview prep timeline can help reserve space for the case interview guide, McKinsey practice cases and PEI guide alongside Solve.

Can a strong result in one game make up for a weak result in the other?

McKinsey has not published whether strength in one game offsets weakness in the other, because its public Solve guidance gives no game weights, pass mark or score scale. Its Solve page says it considers Solve alongside the rest of the application and other assessments. That broad statement does not tell you how two game results combine. A practice percentage or an anecdote about receiving an interview cannot establish a compensation rule, and McKinsey publishes no retake rule either; the Solve retake guide covers what to ask after a rejection.

Use the two-run comparison only to allocate your own practice. If both runs seem strong, check whether you can explain the choices and complete the tasks without guessing. If both are weak, start with the error you can clearly reproduce, then retest the other. Beyond the assessment, the resume guide, internship guide and MBB application guide answer separate application questions; they do not supply a hidden Solve scoring formula. For older game names, the Ecosystem Building guide explains that distinct context.

Sources and evidence boundaries

• Official, checked October 11, 2026: McKinsey's Solve page describes the assessment and says the result is considered with the wider application. The August 2025 Solve FAQ states that the overall length is in your invitation, tutorials are untimed, no prior business or gaming knowledge is needed, and technical problems should be reported promptly. The July 2025 game lab article names Sea Wolf and describes microbe selection. The assessment integrity expectations state the wider conduct rules.
• Reported, unverified: Red Rock's name and Study/Cases format, Sea Wolf's detailed site rules, the approximate individual clocks and the possible additional game come from candidate descriptions. They can vary. The inspections exhibit, the Tidal Flat site and Noor's error log are invented teaching material, not candidate results or McKinsey content.
• Unknown in the checked official sources: comparative difficulty, individual game weights and minutes, score scale, pass mark, retake rules, deadline and extension policy, and who receives which games. Use your invitation and recruiter for your personal instructions.