ResumeAdapter

Updated 2026-06-06

The McKinsey interview, round by round.

Why this mattersMcKinsey publishes the spine of its process: a CV screen, the Solve assessment, and interviews in which most client-facing roles take a personal experience interview followed by a problem-solving case. The part candidates underrate is the PEI: the personal interview is half the loop, scored against named areas, not warm-up small talk. This page walks the process round by round, marks what McKinsey states versus what candidates report, and shows how to pre-load your resume for the case and the PEI together.

Every interview
Case + PEI

Paired in most client-facing loops, official

Assessment
Solve

Game-based, given to roughly 300k a year

Rounds
First + final

Roughly 2 to 3 each, community-reported

Decision
Interviewers

Consultants and partners decide

Sequence5 stagesCV screen to offerSolve to the final round

The quick answer

How does the McKinsey interview process work?

McKinsey publishes the spine of its process. You apply at jobs.mckinsey.com with a CV in English and no cover letter, and a recruiter reviews it; there is no third-party applicant tracking system in the flow. Most consulting applicants then take Solve, McKinsey's game-based problem-solving assessment. Interviews come next, and McKinsey states that for most client-facing roles you take a personal experience interview followed by a problem-solving case, so the two run together. Candidates commonly report two rounds, a first round and a final round of roughly two to three interviews each, with partners weighted into the final round, after which the interviewers decide and extend the offer. The PEI is not small talk: it probes named areas, personal impact, entrepreneurial drive, and inclusive leadership, with deep follow-up on one story per area. Treat the round counts, the seniority mix, and the timing as community-reported. Scan your resume to pre-load the specific, quantified craft the case and the PEI will both probe. Scan your McKinsey resume.

McKinsey's careers interviewing page states that for most client-facing roles candidates take a personal experience interview followed by a problem-solving interview, and asks candidates to prepare personal examples against personal impact, entrepreneurial drive, and inclusive leadership. Its application FAQ says each CV is reviewed by a recruiter and the firm reviews every application, and it describes the Solve assessment as a step for most consulting roles. The number of interviews per round, the seniority mix, and the timing to an offer are not specified by McKinsey, so that detail here is community-reported.

McKinsey is clear about the outline. Its careers pages state the spine: a CV screen, the Solve assessment, and interviews in which most client-facing roles take a personal experience interview followed by a problem-solving case. So on this page that spine is marked official, while the number of interviews per round, the seniority mix, the Solve scenario names and timing, and the time to an offer are marked community-reported: detail consistent across practitioner guides and aggregated candidate accounts, but not McKinsey's stated process. Treat it as the typical case, not a guarantee.

The single most useful correction is the PEI myth. The personal experience interview is not a warm-up chat; it is half of every client-facing interview, and McKinsey publishes the areas it probes, personal impact, entrepreneurial drive, and inclusive leadership. An interviewer typically takes one story per area and drills it for many minutes, so prepare it with the same rigor as the case.

The second correction is the case itself. The problem-solving interview rewards structured thinking and clean quantitative reasoning out loud, not a recited framework. Memorizing a list of frameworks and forcing one onto every problem reads as exactly that.

The practical takeaway runs through every round: because the CV is read by a human and the interview pulls from the stories your resume implies, the resume work is to make problem solving, drive, and leadership legible and to pre-load specific, quantified craft the case and the PEI can both probe.

Read the stages in order. Each row carries what happens and a tag for provenance, official where McKinsey states it on its careers pages and community-reported where it does not. Composition shifts with office and role, so treat the community detail as typical, not guaranteed.

  1. 01

    CV screen via the McKinsey careers portal

    You apply at jobs.mckinsey.com and submit a CV in English; no cover letter is required. McKinsey's application FAQ states the CV is reviewed by a recruiter and that the firm reviews every application, so there is no keyword parser to beat. Make problem solving, drive, and leadership legible to a human on a fast skim.

    Official (mckinsey.com/careers)
  2. 02

    Solve, the online problem-solving assessment

    Most consulting applicants take Solve, McKinsey's game-based problem-solving assessment, after applying. McKinsey says it is given to roughly 300,000 early-career candidates a year and that no preparation is needed. The specific scenario names and timings reported online are community sources, not the official page.

    Official: exists, no prep / Community: scenarios, timing
  3. 03

    First-round interviews: the case plus the PEI

    McKinsey states that for most client-facing roles you take a personal experience interview followed by a problem-solving case, so each first-round interview pairs the two. Candidates commonly report two to three interviews in the round. The number of interviews and who conducts them are community-reported and vary by office and role.

    Official: case + PEI / Community: round count
  4. 04

    Final-round interviews with partners

    The final round repeats the case-plus-PEI structure, commonly with more senior interviewers and partners, and goes deeper on both the problem solving and the personal stories. The composition, the count, and the seniority mix are community-reported, not McKinsey-stated.

    Official: case + PEI / Community: round mix
  5. 05

    Offer

    After the final round, the interviewing consultants and partners decide and extend the offer. The decision mechanics and the timing to an offer are community-reported and vary by office and cycle, so treat any specific turnaround you read as typical rather than guaranteed.

    Official sequence / Community timing
The two halves of every interviewCase + PEI, official structure

McKinsey pairs two interviews in most client-facing loops. Both are scored, and a strong showing in one does not carry a weak showing in the other.

The problem-solving case
A business problem you structure, work through with quantitative reasoning out loud, and close with a recommendation. Rewards structured thinking, not a recited framework. Make sure the analytical scope on your resume is something you can defend live.
The Personal Experience Interview
One story per area, personal impact, entrepreneurial drive, and inclusive leadership, with deep follow-up on what you did and why. Pre-load two strong, quantified stories per area, each one you, not the team, drove.

Community reports often describe two to three interviews per round and partners weighted into the final round. Hold those specifics loosely: the official anchor is the case-plus-PEI structure of each interview.

For campus and early-career hires, typically Business Analyst and Associate roles entered through programs and internships, the full sequence applies: the CV screen, Solve, and the case-plus-PEI rounds. This is the path McKinsey's student-facing material describes most directly.

Experienced and advanced-degree hires go through the same portal and the same case-plus-PEI core, but McKinsey notes some roles add expertise interviews, and candidates commonly report more weight on track record and the specific practice or team. This added detail is community-reported, so treat the experienced path as the typical pattern rather than a single stated process.

The resume implication splits cleanly. For the campus path, pre-load the structured, quantified stories the case and the PEI will pull from. For the experienced path, lead with track record and practice-relevant scope, because the people you talk to are reading for a direct fit to the team you would join.

The consultants and partners who interview you make the call, comparing signal across the back-to-back interviews and the two rounds. The decision weighs the problem-solving case and the personal experience interview together, which is why a brilliant case cannot rescue a thin PEI, and vice versa. McKinsey does not publish an internal scoring rubric, so this decision model is community-reported, not a stated mechanic.

This is where the framing differs from a single-interviewer screen. No one room owns the outcome; the interviewers compare notes, so a consistent signal across all of them, on both the case and the PEI, is what moves the decision. The people you meet are potential colleagues, and they are reading for whether you would be credible in front of a client.

The implication for you is direct. Because the decision pulls from both halves and from the stories your resume implies, a resume with specific, quantified craft, problems solved, initiatives driven, teams led, gives the interviewers concrete, owned results to probe and agree on rather than a generic profile with nothing for the PEI to grab.

The interview evaluates three things, and your resume should carry the raw material for all three before you walk in.

Structured problem solving
The case: can you break an unfamiliar problem into a clean structure and reason through the numbers. Show analytical scope on the resume you can actually defend live, not a tool you only listed.
Personal experience
The PEI: personal impact, entrepreneurial drive, and inclusive leadership, drawn from real stories. The round reuses what your resume implies, so every owned, quantified bullet is an answer in waiting.
Client-ready communication
Whether you are clear, concise, and credible enough to sit in front of a client. A tight, results-led resume signals the same clarity the interviewers are listening for.

The resume implication is the part most candidates miss. The PEI does not invent new material; it pulls from what your resume references, and a resume full of specific, quantified, owned craft gives the interviewers concrete stories to probe rather than a generic profile with nothing for this loop to grab.

FAQ

McKinsey interview FAQ

The questions most candidates surface when they map McKinsey's CV screen, the Solve assessment, and the case-and-PEI rounds to their resume. Answers are byte-identical to the FAQPage JSON-LD, because AI engines that extract HTML and AI engines that extract JSON-LD should not see different text.

How many interview rounds does McKinsey have?

McKinsey's published structure is a CV screen, the Solve assessment, then interviews in which most client-facing roles take a personal experience interview followed by a problem-solving case. Candidates commonly report two rounds of interviews, a first round and a final round, with roughly two to three interviews in each and partners weighted into the final round. Treat the CV screen, Solve, and the case-plus-PEI structure as McKinsey's stated sequence, and the exact number of interviews as community-reported, since it varies by office and role.

What is the McKinsey case interview?

The case interview is McKinsey's problem-solving interview: the interviewer presents a business problem and you structure it, work through the analysis out loud, do the quantitative reasoning, and reach a recommendation. McKinsey runs it alongside the personal experience interview in most client-facing loops and offers practice cases on its careers site. The detailed interviewer-led format is well documented by prep sources; the takeaway is to think structurally under pressure, not to recite memorized frameworks.

How long does the McKinsey interview process take?

End to end it commonly runs from a few weeks to a couple of months, from application and Solve through the first and final rounds to an offer, with campus timelines more structured than experienced-hire timelines. The specific turnaround is community-reported and varies by office, role, and recruiting cycle, so treat any single timeline you read as typical rather than guaranteed.

Is the McKinsey interview hard?

It is demanding. You face a problem-solving case that tests structured thinking and quantitative reasoning under time pressure, and a personal experience interview that drills one story per area with deep follow-up, across two rounds. This is the community read of difficulty rather than an official statement, so calibrate to your target office and role, and pre-load the quantified stories your resume already implies.

Do you have to pass Solve before interviewing at McKinsey?

McKinsey describes Solve as one step in the process for most consulting roles, considered after you apply and alongside the rest of your application. Candidates commonly report it as a gate before interviews, but McKinsey frames it as an additional data point rather than a published pass-fail cutoff, so treat the exact weighting as community-reported. The safe approach is to take it seriously as a test of how you analyze an unfamiliar problem.

Who makes the hiring decision at McKinsey?

The consultants and partners who interview you decide, weighing the problem-solving case and the personal experience interview together across the first and final rounds. McKinsey does not publish an internal scoring rubric, so the exact decision mechanics are community-reported. What is consistent is that a strong, consistent signal across both the case and the PEI, in both rounds, is what moves the decision, which is why a resume that pre-loads specific, quantified stories helps.

Pre-load your resume for the case and the PEI

Run your resume against a McKinsey job description.

Get your score, the problem-solving and personal-experience craft your resume is missing, the quantified stories the PEI will probe, and a line-by-line rewrite plan. Free to scan; no signup to see the score.