Your McKinsey Solve Crashed. Here's What to Do Right Now.

If you're reading this mid-assessment with a frozen screen or a disconnection error, skip straight to the immediate fixes section below. Everything will be okay.

McKinsey Solve technical issues are more common than most candidates realize. The assessment platform — whether you're in the Sea Wolf game or the Red Rock Study — runs entirely in your browser, which means your local setup matters. A lot.

The good news: most technical problems are preventable, and McKinsey has a documented process for handling disruptions that aren't your fault. This guide covers every scenario, what to do in the moment, and how to make sure tech issues never cost you a McKinsey offer.

Common McKinsey Solve Technical Issues

Here are the problems candidates report most frequently, ranked by how often they occur:

Browser Compatibility Errors

The most common McKinsey Solve glitch is the assessment refusing to load or displaying a blank white screen. This almost always comes down to browser choice. The platform is optimized for Google Chrome. Firefox, Safari, Edge, and Brave all have documented compatibility issues — from rendering bugs to JavaScript errors that silently break game mechanics.

Symptoms: Blank screen on load, missing UI elements, buttons that don't respond, error messages about unsupported browsers.

Lag and Slow Response Times

Candidates in the Sea Wolf game sometimes report a 2–5 second delay between clicking a microbe and seeing the ecosystem update. In a 35-minute timed assessment, that kind of lag can burn through 10–15% of your available time.

Common causes: Weak Wi-Fi signal, background applications consuming bandwidth (Dropbox syncing, cloud backups, streaming), browser tabs competing for memory, or an underpowered device.

Disconnection Mid-Test

A dropped internet connection during the Solve is the scenario candidates fear most. The platform does have some auto-save functionality, but a prolonged disconnection (more than 30–60 seconds) can trigger a session timeout.

Symptoms: Spinning loader that doesn't resolve, "connection lost" banner, or a redirect to the login screen.

Screen Freeze

The game interface stops responding entirely. Your cursor moves, but clicks do nothing. This typically happens when the browser runs out of available memory — especially on machines with 4GB RAM or less, or when dozens of tabs are open alongside the assessment.

Audio or Visual Rendering Issues

Less common but still reported: missing icons, overlapping text, or audio cues that don't play. These are typically caused by aggressive ad-blockers, privacy extensions, or custom browser settings that block JavaScript execution.

What to Do During the Test if Something Goes Wrong

Take a breath. You have options.

Step 1: Don't close the browser tab. Your session data is tied to that tab. Closing it can make recovery harder.

Step 2: Wait 10–15 seconds. Many "freezes" are actually the platform processing a complex calculation. The Sea Wolf ecosystem simulation and Red Rock data visualizations are computationally heavy. Give it a moment.

Step 3: If still frozen, try these in order:

1. Click somewhere neutral on the screen (not on a game element) to check if the browser itself is responsive

2. Open your browser's task manager (Shift + Esc in Chrome) and check if the tab shows "Not Responding"

3. If the tab is unresponsive, wait another 30 seconds before doing anything else

4. As a last resort, refresh the page (F5 or Cmd+R). The platform should reconnect you to your active session

Step 4: If you're fully disconnected:

1. Check your internet connection immediately — try loading any other website

2. If your Wi-Fi is down, switch to a mobile hotspot as backup

3. Return to the assessment URL and log back in

4. The platform should restore your session from the last auto-save point

Step 5: Document everything. Take a screenshot or note the exact time, error message, and what you were doing when the issue occurred. You'll need this if you contact McKinsey.

How to Contact McKinsey Support (And What to Say)

If a technical issue cost you significant time or prevented you from completing the assessment, contact McKinsey's recruiting team. Here's how to do it effectively.

Who to contact: Reply directly to the email that contained your Solve invitation link. This goes to the recruiting coordinator assigned to your application. If you can't find that email, reach out to the office you applied to through McKinsey's website.

When to contact them: Within 24 hours of the incident. The sooner the better — McKinsey's platform logs session data, and earlier reports are easier to verify.

What to include in your message:

• Your full name and application ID

• The exact date and time the issue occurred (include your timezone)

• Which game you were in (Sea Wolf or Red Rock Study)

• A specific description of the problem ("The screen froze for approximately 3 minutes at 2:14 PM EST while I was in the Sea Wolf game")

• Any screenshots or error messages

• Your browser version and operating system

What typically happens: McKinsey reviews the server-side session logs. If the logs confirm a platform-side issue, they'll usually offer you a chance to retake the assessment. If the issue was on your end (poor internet, unsupported browser), outcomes vary — but a professional, specific report always helps your case.

Browser and Device Requirements

Meeting these requirements eliminates about 80% of McKinsey Solve technical problems before they start.

A few critical details most guides skip:

• Disable all browser extensions before starting. Ad-blockers, VPNs, privacy extensions, and password managers can all interfere with the assessment platform's JavaScript.

• Use a laptop or desktop, not a tablet. The Solve interface requires precise clicking and hover interactions that don't translate well to touchscreens.

• Close every other application. Slack, Spotify, Zoom — all of it. You want 100% of your system resources dedicated to the assessment.

Pre-Test Technical Checklist

Run through this list 24 hours before your scheduled assessment, then again 30 minutes before you start.

24 hours before:

1. Update Chrome to the latest version (Settings → About Chrome)

2. Restart your computer to clear memory

3. Run a speed test at speedtest.net — confirm you're above 10 Mbps download

4. Test your setup on the McKinsey Solve simulation to verify everything runs smoothly in your browser

5. Identify a backup internet source (mobile hotspot, nearby café with Wi-Fi)

30 minutes before:

1. Close all applications except Chrome

2. Close all Chrome tabs except the assessment

3. Disable all browser extensions (chrome://extensions → toggle everything off)

4. Plug in your laptop charger — battery-saving modes throttle CPU performance

5. Put your phone on Do Not Disturb

6. Disable system notifications (Focus mode on Mac, Focus Assist on Windows)

7. If on Wi-Fi, sit as close to your router as possible — or connect via Ethernet cable

This checklist sounds excessive. It isn't. A 2-second lag spike during a critical Sea Wolf decision or Red Rock data interpretation can shift your percentile score. The candidates who score in the top 25% don't leave anything to chance.

Will Technical Issues Affect Your Score?

This depends entirely on whether the issue was on McKinsey's end or yours.

Platform-side issues (server errors, bugs in the assessment software): McKinsey can identify these in their logs. If confirmed, you'll almost always get a retake opportunity. Your original score is typically discarded.

Client-side issues (your internet dropped, your browser crashed, your laptop died): These are harder to resolve. McKinsey may still offer a retake if you report the issue promptly with documentation, but it's not guaranteed.

The uncomfortable truth: Even if you get a retake, you've now lost time and added stress to an already high-pressure process. Prevention is dramatically better than cure here.

That's exactly why practicing on a McKinsey Solve simulator before test day matters beyond just strategy prep. Running through the Sea Wolf simulation or a full Solve practice session on your actual test device, in your actual test environment, using your actual internet connection, surfaces technical issues while the stakes are zero.

Frequently Asked Questions

What browser should I use for the McKinsey Solve?

Google Chrome, updated to the latest version. McKinsey's assessment platform is built and tested primarily on Chrome, and the vast majority of McKinsey Solve technical issues candidates report involve non-Chrome browsers. Disable all extensions before starting the test.

Can I retake the McKinsey Solve if I experience technical problems?

Yes, but only if you report the issue to McKinsey's recruiting team promptly (within 24 hours) with specific details — exact time, error description, and screenshots if possible. McKinsey reviews their server logs to verify platform-side issues and typically grants a retake when confirmed. For client-side problems like internet outages, outcomes depend on the specific situation.

Will McKinsey know if I had technical issues during the test?

McKinsey's platform logs session activity, including disconnections, page refreshes, and response time anomalies. If something went wrong on their servers, they can often see it without you reporting it. However, always report issues proactively — don't assume they'll catch it on their end.

How much internet bandwidth do I need for the McKinsey Solve?

A minimum of 10 Mbps download speed is recommended, though 25+ Mbps provides a comfortable buffer. More important than raw speed is connection stability. A consistent 15 Mbps connection on Ethernet is far better than a 100 Mbps Wi-Fi signal that drops intermittently. Run a speed test at speedtest.net before your assessment.

Should I practice on the same device I'll use for the real test?

Absolutely. Running through a McKinsey Solve simulation on your actual test device is the single best way to catch technical issues in advance. You'll verify browser compatibility, test your internet stability under load, and get comfortable with how the interface performs on your specific screen size and resolution. Think of it as a technical dress rehearsal.