I would make the interview prep the bigger block once you are comfortable with the Solve format.
Search across courses, cases, drills, coaches and more.
My Mckinsey interviews within 2 weeks. The Solve assessment and the preparation of the case interviews.
I would make the interview prep the bigger block once you are comfortable with the Solve format.
With 2 weeks I'd separate Solve prep from case prep instead of mixing both every session.
There are a lot of Solve game types and I don't have unlimited prep time. I'm wondering if it's better to get very comfortable with the main formats or try to touch every possible game once. How broad does prep need to be before test day?
Mayank G.CoachYou do not need to become equally expert in every possible Solve task. The priority is understanding the mechanics and decision logic of the game types you are most likely to encounter, then building enough flexibility for unfamiliar variations.
In practice I second-guess myself a lot. Sometimes checking again catches a mistake, other times I waste time and change an answer that was right. For McK Solve, is it better to move once the logic feels solid, or should I leave time to verify most decisions?
Mayank G.CoachYou generally want a balance between decisiveness and verification. Rechecking every step can destroy your pacing, but blindly trusting every first answer can turn small mistakes into avoidable losses.
I'm getting decent accuracy in practice but some tasks take me forever. I can usually reach the right answer if I keep working, but I'm not sure how much pace matters in the scoring. Should I be optimizing mainly for correct decisions or also aggressively cutting time per task?
Mayank G.CoachCorrectness matters, but very slow execution can still become a problem because Solve is time-constrained. The right target is accurate decisions at a sustainable pace, not perfect certainty on every task.