How is the McKinsey Solve assessment scored?

The core of the McKinsey Solve assessment lies in its shift away from traditional multiple-choice psychometric testing. Instead of merely recording whether your final answer is right or wrong, the algorithmic scoring engine tracks everything you do. This approach is divided into two distinct dimensions: the product dimension and the process dimension. The product dimension evaluates the final output of your choices, such as whether your constructed food chain survives or whether your defensive layout succeeds. It is the structural validity of your answer.

Conversely, the process dimension focuses entirely on how you reached that final output. Every click, drag, pause, and reversal is logged as a distinct data point. This telemetry tracking maps your problem-solving style against pre-defined competency models. McKinsey uses this dual-scoring method to build a comprehensive profile of your cognitive abilities. This helps them determine if your natural analytical approach aligns with the expectations of management consulting, before you ever step into an assessment centre or superday.

The product dimension resembles traditional grading but operates in a dynamic, simulation-based environment. In exercises like the ecosystem creation game, the scoring engine checks if you satisfied all explicit and hidden constraints. For example, did the species you selected achieve a caloric balance, or did the predators deplete the prey population within the simulation timeline? Your final submission must meet the structural criteria of the task to earn full product points.

Failing to achieve the primary objective significantly harms your product score, but it may not completely disqualify you if your process data shows strong logic. The scoring software calculates how close your final solution came to the optimal configuration. Because these scenarios are complex, multiple viable solutions often exist. The algorithm does not look for a single correct answer key; instead, it evaluates whether your final product satisfies the mathematical rules governing the simulation environment.

The process dimension is where many candidates inadvertently lose points by trying to game the system. Telemetry tracking measures your efficiency, adaptability, and critical thinking speed. If an applicant blindly clicks through options without a clear strategy, the algorithm flags this as low-planning behavior. Conversely, time spent reading instructions, followed by deliberate, structured movements, indicates a methodical mindset. The software creates a behavioral timeline of your entire assessment session.

This telemetry data also serves as a robust defense against cheating and answer memorization. If a candidate inputs a highly optimized solution with zero exploration or planning time, the algorithm flags this behavior as irregular. This suggests the user may have bought leaked solutions or patterns online. McKinsey values a structured process over a rushed, perfect answer. Working on structured platform practice, like the interactive modules provided by Intervyo, can help you build the authentic pacing and deliberate decision-making habits that the process algorithm rewards.

The Solve suite spans several distinct game formats, and each one applies the same dual-scoring logic in a slightly different way. The way product correctness and process telemetry are weighted shifts with the demands of the specific scenario in front of you.

One of the most frequent questions from candidates preparing for a graduate scheme or summer-analyst position is the exact pass mark. McKinsey does not publish a universal passing score, and no fixed percentage guarantees advancement. Instead, your raw product and process scores are normalized against a cohort benchmark. This benchmark can vary based on the specific office you apply to, the role type, and the overall strength of the applicant pool during that recruitment cycle.

Because the firm uses norm-referenced scoring, your performance is compared directly to other high-achieving applicants. A score that secures an invite to a superday in one region might fall short in a more competitive or oversubscribed office. Furthermore, McKinsey views the Solve score as one component of a holistic review process. It is considered alongside your CV or resume, academic background, and any initial screening results, meaning the required threshold is never entirely static.

Understanding how your score travels through McKinsey's internal systems is crucial if you plan to apply to multiple roles or offices. Generally, your Solve assessment result is tied directly to the specific application pipeline for which it was triggered. If you are rejected after the assessment, a strict retake window applies. This window is commonly reported as around one year, meaning you cannot bypass a low score by applying to a different office the following month.

If you apply for a summer-analyst program and later apply for a full-time graduate scheme within the same year, McKinsey will typically reuse your existing Solve data. You cannot choose to retake the test to improve your score unless explicitly instructed by human resources. This data permanence means your first attempt must be fully prepared. Treat the assessment with the same level of discipline as a final university exam or a live case interview.