McKinsey Solve System Requirements: Complete Setup Guide

If you’re preparing for the McKinsey Solve, also known as the McKinsey Problem Solving Game (PSG), understanding the system requirements is essential. Many candidates underestimate how technical issues, browser settings, or weak devices can affect test performance. Whether you’re using a Mac, Windows, or low-spec laptop, ensuring your setup meets McKinsey Solve system requirements can make the difference between a smooth experience and a disrupted test. This guide walks you through the technical requirements, browser and internet setup, and expert tips to help you perform your best on test day.

TL;DR - What You Need to Know

• McKinsey Solve system requirements include updated browsers, stable internet, and a modern Mac or Windows computer to ensure smooth gameplay.
• The mandatory technical check verifies your hardware, browser, and network setup before starting the McKinsey Problem Solving Game (PSG).
• Both Mac and Windows devices work well, but low-spec laptops risk lag during 3D simulations like Ecosystem or Seawolf.
• Use Chrome, Edge, or Firefox with wired internet and a single Full HD screen for best performance.
• Optimize your system by closing background apps, enabling high performance mode, and running the McKinsey Solve test check 24 hours in advance.

How does the Solve technical check work before testing?

Before starting the McKinsey Solve test, every candidate must complete a system check to confirm that their computer and browser meet the technical requirements. This pre-test verification ensures your setup can handle the McKinsey PSG’s 3D visuals, audio, and interactive elements without performance issues.

The Solve technical check automatically tests several key components:

• Browser compatibility: Confirms you are using an updated and supported browser (Chrome, Edge, or Firefox).
• Internet connection: Evaluates your network stability, speed, and latency to prevent lags during gameplay.
• Hardware readiness: Assesses CPU, memory, and graphics capability to ensure smooth 3D rendering.
• Display and resolution: Verifies that your screen size and resolution allow all interface elements to display correctly.
• Input devices: Confirms your mouse and keyboard are functioning, as both are required throughout the test.

Once the system check runs, you’ll see a series of green check marks when all requirements are met. If any component fails, the test portal will prompt you with troubleshooting steps or configuration updates (such as switching browsers or closing background programs).

Example: If your browser cache is full or outdated, the test may flag compatibility issues. Clearing cache, updating the browser, or restarting the computer usually resolves this.

Completing the check at least one day before your test window opens is highly recommended. This gives you enough time to fix any hardware or internet problems and ensures the McKinsey digital assessment runs seamlessly when it counts.

Can I use Mac, Windows, or a low-spec laptop for Solve?

Yes, the McKinsey Solve game works on both Mac and Windows computers, as long as they meet the minimum system and browser requirements. However, using a low-spec laptop may cause lag, slow rendering, or crashes due to the game’s 3D and data-heavy nature.

Platform compatibility:

• Windows: Works best on Windows 10 or 11 with Chrome or Edge. Older Windows versions may fail the system check.
• Mac: Fully supported on macOS Big Sur (11) or later when using Chrome or Firefox. Safari is not always compatible with all features.
• Linux or tablets: Not officially supported and may result in display or control errors.

Performance on low-spec devices:
 While the test can technically run on entry-level laptops, weaker CPUs or integrated graphics often struggle with real-time animations. Candidates using such devices should:

• Close all background programs before starting the test.
• Use a wired internet connection to minimize lag.
• Avoid screen-sharing or streaming software that consumes memory.
• Test the device using the McKinsey system check at least a day early.

Example: A 2018 MacBook Air with 8 GB RAM and Chrome typically passes the technical check but may display minor frame drops in complex tasks like Ecosystem or Seawolf. If possible, borrow or use a more powerful desktop to ensure smooth performance.

Pro Tip: Always prioritize stability over portability. Running McKinsey Solve on a device that exceeds minimum specs will help you focus on problem-solving instead of troubleshooting.

What are the browser, network, and display requirements?

McKinsey Solve runs entirely in your web browser, so maintaining the right browser version, internet stability, and display settings is critical. Using outdated browsers or slow Wi-Fi can lead to freezing, delayed responses, or even test submission errors during the McKinsey Problem Solving Game.

Browser requirements:

• Use the latest version of Google Chrome, Microsoft Edge, or Mozilla Firefox.
• Enable hardware acceleration in browser settings for smoother 3D visuals.
• Avoid private browsing or extensions that block scripts or cookies.
• Disable automatic updates or notifications that might interrupt gameplay.

Internet and network setup:

• A stable wired connection (Ethernet) is preferred over Wi-Fi to prevent lag.
• Minimum download speed: 10 Mbps; recommended: 25 Mbps or higher.
• Keep latency below 100 milliseconds for responsive in-game interactions.
• Avoid VPNs or firewalls that can block the McKinsey assessment portal.

Display settings:

• Recommended resolution: 1920x1080 (Full HD) for clear visuals and full interface visibility.
• Use one primary monitor only; the test may flag multiple screens as irregular activity.
• Ensure adequate brightness and color contrast for reading charts and visuals in games like Redrock or Seawolf.

Example: Candidates using an older browser version or weak Wi-Fi frequently report delayed responses when switching between mini-games. Refreshing the browser or switching to a wired network usually resolves these issues.

Pro Tip: Before the test, perform a full browser restart, clear cache, and disable unnecessary tabs or apps that consume bandwidth. A clean, stable connection greatly improves your Solve experience.

What happens if your setup fails or errors occur?

If your system fails the McKinsey Solve technical check or experiences errors during the test, you should immediately contact the support team through the test portal. McKinsey allows candidates to report technical issues and may reschedule your session if the problem is verified.

When the system check fails:

• Double-check that your browser and operating system are up to date.
• Restart your computer and re-run the test link in a supported browser.
• Disable any VPNs, antivirus pop-ups, or background programs that interfere with connectivity.
• If the test still fails, reach out through the official McKinsey support contact provided in your invitation email.

During the test:
  If the test freezes, the screen turns blank, or a mini-game fails to load:

• Take a quick screenshot of the issue for documentation.
• Exit the test safely and email McKinsey support immediately.
• Do not attempt to restart the test unless instructed. McKinsey can verify your session and reopen it if necessary.

Example: A candidate reported a mid-test crash due to a Wi-Fi drop. After contacting support within minutes, they were granted a retake window the following day. Timely reporting is key to preserving eligibility.

Pro Tip: Always test your setup at least 24 hours before your Solve deadline. Most issues like slow rendering or browser freezes are easily resolved through early troubleshooting.

How hard is maintaining performance during the Solve test?

Maintaining smooth performance during the McKinsey Solve test can be challenging on slower computers or unstable networks. The game’s interactive, 3D-based environment demands consistent processing power and stable internet speed throughout all modules, including Ecosystem, Redrock, and Seawolf.

Performance factors to monitor:

• CPU and memory usage: High resource use from background apps can cause lag. Close video calls, downloads, or antivirus scans before testing.
• Graphics performance: The Solve environment relies on moderate GPU rendering. Integrated graphics can work but may slow down scene transitions or animations.
• Internet stability: Temporary drops in bandwidth can disconnect you from the game server, forcing restarts or freezing progress.
• Browser responsiveness: Tabs with heavy extensions or cached data increase latency. Clear cache and use a single tab for testing.

Example: Candidates with high browser memory use or multiple open apps often experience noticeable delays when switching between Solve modules. Running a clean system with minimal active programs helps maintain full responsiveness.

Pro Tip: During the test, avoid multitasking entirely. Even background tools like cloud sync apps or streaming services can interfere with memory allocation and CPU performance, affecting real-time problem-solving accuracy.

Tips for optimizing your system for Solve

Optimizing your setup before the McKinsey Solve test helps prevent slow performance, browser errors, or disconnections. Small technical adjustments, like improving your network connection or adjusting device settings, can make the McKinsey Problem Solving Game run noticeably smoother and more stable.

Practical setup tips:

• Update your browser and system: Always use the latest Chrome, Edge, or Firefox versions to ensure compatibility with McKinsey’s test environment.
• Use a wired internet connection: Ethernet minimizes lag and packet loss compared to Wi-Fi.
• Close background applications: Shut down file sync tools, notifications, and downloads that consume bandwidth or CPU resources.
• Clear cache and restart before starting: Reduces memory strain and ensures a clean browser session.
• Adjust power settings: On laptops, enable “High Performance” mode to prevent CPU throttling during gameplay.
• Test external hardware: Verify your mouse, keyboard, and power adapter are functioning properly; input lag or battery drain can interrupt gameplay.

Environmental setup tips:

• Choose a quiet, well-lit room with minimal distractions.
• Avoid taking the test on battery power; plug in your laptop throughout the session.
• Keep a notepad nearby for quick calculations or observations in modules like Redrock or Ecosystem.

Example: Candidates who switched from Wi-Fi to Ethernet or disabled auto-updates reported smoother gameplay and faster load times across all modules.

Pro Tip: Run the McKinsey Solve system check 24 hours before the test and once again on test day. This double check ensures last-minute software or browser updates do not affect performance.

Frequently Asked Questions

Q: Can I use Excel during McKinsey's Solve?
A: You cannot use Excel during McKinsey's Solve. The McKinsey Problem Solving Game (PSG) is a browser-based digital assessment that runs in a secure environment, so no external programs, spreadsheets, or calculators are allowed during the test. 

Q: How long does McKinsey take to respond after PSG?
A: McKinsey typically responds within one to two weeks after you complete the Solve game. The timeline can vary based on application volume and region, but your PSG results are reviewed before interview invitations are sent. 

Q: What if I fail McKinsey Solve?
A: If you fail McKinsey Solve, you usually cannot retake the test for the same recruiting cycle. The firm uses PSG scores to filter candidates before interviews, so ensure your system setup and performance meet McKinsey Solve system requirements before starting.

Q: How long does it take to prepare for McKinsey Solve?
A: Preparing for McKinsey Solve typically takes one to two weeks of focused practice. Use that time to review the test format, run a technical check to confirm your PC meets McKinsey Solve system requirements, and practice time management under pressure. 

Q: What is the passing rate for the McKinsey Solve game?
A: The McKinsey Solve game pass rate is estimated to be around 20 to 30%. This means most applicants do not advance past this digital assessment, making it essential to ensure your technical setup and readiness meet all McKinsey Solve test requirements.