Why McKinsey in 2026: An Answer Built From Its Own Pages

Where “Why McKinsey” sits, and the ninety-second budget

McKinsey states the shape of its process in one sentence. Its interviewing page, checked 29 September 2026, reads: "For most client-facing roles, you will participate in a personal experience interview, followed by a problem-solving interview." Your motivation question lives in that first half, before any case starts.

That placement matters for two reasons. The first is time. The personal experience half also has to carry your stories, so a motivation answer that runs four minutes eats the part of the conversation you control best. Ninety seconds is the working budget.

The second reason is evidence. The firm asks its candidates to arrive with examples: "We suggest coming prepared with two personal examples that demonstrate how you've made an impact in each of the four areas below." The habit that sentence describes is the habit your motivation answer needs. A reason with an example attached behaves like the rest of the interview. A reason without one behaves like a cover letter.

So the question is doing something narrower than testing enthusiasm. It asks whether you can name a thing about this firm that is true, that you can show you engaged with, and that you would lose if you joined somewhere else. Everything below is about producing that, from documents the firm publishes itself.

Four checkable pages, and a mission with two sides

Four McKinsey pages give you material a recruiter can verify while you speak. All four were read on 29 September 2026, the first two through Wayback snapshots because the domain refuses our connections.

Two details are worth carrying. On the industries page, Public Sector and Social Sector point to the same destination, so 25 labels cover 24 pages. And the mission sentence is explicitly double: "We are equally committed to both sides of our mission: attracting and developing a talented and diverse group of colleagues and helping our clients create meaningful and lasting change." A candidate who talks only about client impact has engaged with half of a sentence the firm chose to write.

The same overview page describes an alumni network of "over 50,000 former colleagues in nearly 140 countries". Read plainly, that is the firm publicizing how many people leave. Saying you want the exit options is still a weak answer, and the reason is in the next section.

Three angles, and the swap test they have to survive

Every strong answer in this format does the same job. It names something specific, then proves you met it somewhere other than a careers page. Three sources of specificity work.

1. A practice, taken from the published list and tied to work you have done. "Your Operations capability inside healthcare" is checkable in two clicks. Follow it with the six months you spent rebuilding a clinic's appointment flow, and the reason stops being a preference.
2. A piece of the firm's published work you actually read. McKinsey publishes constantly, which makes this the cheapest angle and the easiest to fake. The test an interviewer applies is whether you can say what you disagreed with or what you would test next.
3. A conversation with a named person in a named office. The two accounts the firm publishes on its own careers blog both start here, which is the strongest evidence available that the firm reads this as a real reason.

The three are not equal in cost. The first needs nothing but honesty about your own history. The second needs an hour of reading. The third needs a month of outreach, which is why it should be started before you need it.

A useful rehearsal test: read your reason aloud, then ask whether it would still be true with BCG or Bain in the sentence. If it survives the swap, you have described consulting rather than this firm, and the interviewer will make that swap in their head whether or not they say it.

One Why McKinsey answer, delivered in full

The candidate below is invented, and her details are examples of the kind you would replace with your own. She is a final-year engineering student who spent eight months on a hospital logistics project, and she is interviewing for Business Analyst, which is the title the firm's undergraduate page names.

"Two things pulled me toward McKinsey specifically. The first is where your Operations capability meets your Healthcare practice. I spent eight months on the loading dock of a 400-bed hospital, remapping how sterile supplies reach the operating theaters. We cut the average retrieval walk from eleven minutes to four. What I could not do was change how the hospital bought those supplies, because that decision sat two levels above anyone in the room. Your operations work reaches that level, and the healthcare pages describe exactly the kind of engagement I kept wanting to be part of.

The second thing is narrower. I spoke to an engagement manager in the Chicago office in July, and I asked her what she would remove from the job. She said the travel is heavier than the recruiting material implies, and that she would keep it anyway because of who is on the team. I trusted the firm more after that answer than after anything I read. I want to work where someone answers a question like that straight.

I also read the two sides of the mission statement literally. I am applying at the point in my career where being developed matters as much as delivering, and the firm writes that down as an equal commitment. If it holds, that is where I want my first three years."

That runs about 220 words, which lands near ninety seconds when spoken at an interview pace. It names two verifiable things, carries one number from her own history, and includes something unflattering that she chose to keep in.

What two McKinsey consultants said pulled them in

McKinsey publishes first-hand accounts on its careers blog. They are chosen by the employer, so treat them as evidence of what the firm is happy to show rather than a survey of its people. On the question of motivation they are still useful, because both authors answer it without being asked.

Jo joined as an associate in the Houston office in January 2020, recruited during her applied physics PhD. Her account, dated 11 May 2020, opens with the trigger: "I first learned about the work McKinsey is doing in digital and analytics through a connection of mine who works out of the Houston office." She names the practices that followed, then adds what made her apply: "I'm very interested in that type of work as well as sustainability and energy, which are also growing areas of focus for McKinsey."

That is a named capability, a named office, a named conversation, and an interest she can trace. It is the structure of the three angles above, written by someone who got the offer.

Alvaro, in a post dated 10 August 2020, credits the recruiting process itself: "McKinsey recruiters and their campus recruiting program stood out from the crowd for three reasons: program structure, student attention and individualized treatment." His route ran through a consulting club and a case competition in Brazil. Neither account mentions prestige, rankings or exit options, and both were published by the firm that hired them.

Where a weak reason breaks, and the question that breaks it

Three failure modes account for most of the damage, and each one has a standard follow-up that exposes it.

A fourth failure is quieter. Candidates sometimes describe the firm in words it does not use about itself, picked up from third-party summaries. The firm's own sentence on who it hires is broad: "We seek smart, driven problem-solvers from a wide range of disciplines." Narrowing that to a type in your answer tells the interviewer where you did your reading.

The repair is the same in every case. Attach one fact from your own history to one thing the firm publishes, and stop there.

Lines to keep out of a Why McKinsey answer

Five things cost more than they return.

1. The wrong entry title. After an undergraduate degree the role is Business Analyst, per the firm's undergraduate page. Associate is the post-MBA entry. Getting this wrong in the first minute is cheap to avoid.
2. A claim about preparing for Solve. The firm writes "There's no need to prepare" about its assessment. Announcing weeks of preparation for it argues with a published sentence.
3. A ranking. No firm publishes one, and an interviewer knows where they come from.
4. A number you cannot source. Compensation figures from aggregators invite a question you cannot answer. Our McKinsey salary page shows what is actually filed and by whom.
5. The single-firm story. Claiming this is the only firm you applied to is rarely true, and the comparison question is standard. Naming the others and saying what separates them scores better than loyalty theater.

What remains after those cuts is short, which is the point. A ninety-second answer with two verifiable anchors beats three minutes of adjectives, and it leaves the rest of the interview for the stories the firm asked you to bring.

Rehearsing the delivery against a scored answer

The content above is the easy half. Saying it once, cleanly, under a clock is the part that slips. Our synthesis rubric weights a spoken answer Answer first 35, Evidence 25, Risk 20, Next step 20, and those numbers come out of src/lib/grading/rubrics.ts. We wrote them. No firm publishes a marking scheme for a motivation answer, McKinsey included, and anyone who shows you one is showing you their own.

Read against a motivation answer, two of those weights do real work. Answer first means the reason arrives in sentence one, before the story that supports it. Evidence means the story carries something checkable, like a number or a named conversation. Our drills and the weights themselves sit on the method page, free to open without an account.

Two things the tool does not do. It cannot tell you whether your reason is true, because only you know that. And none of our six assessment simulators are live: the assessments page says 0 of 6 are running, on its own face. For the case half of the same interview, our McKinsey case interview guide covers what the firm publishes, and answering why consulting handles the question that usually arrives right before this one.