McKinsey Resume: Structure, Examples, and Bullet Checklist

A McKinsey resume should make your most relevant evidence easy to verify: what you owned, how you approached the work, what changed, and what you can explain under interview follow-up. Students and recent graduates will often use an education-first one-page format. Experienced candidates may lead with recent work when that makes the role fit clearer. Treat those as document defaults, not McKinsey rules. The current role description and application portal decide what you must submit. Your tailoring job is to move the most relevant proof higher without changing the underlying facts.

What makes a resume work for McKinsey?

A McKinsey resume works when a recruiter can see leadership, personal impact, and entrepreneurial drive in a 30-second scan, with each claim tied to what you actually owned. Use one page as a reported early-career default, 3-5 bullets per role, and quantified results when supported by your records. These are reported application-writing rules and a tailoring lens, not an official McKinsey scoring formula; the current role description and application portal control.

Reported practice rules, not official McKinsey requirements:

• One page: Use one page for student and early-career applications unless the current instructions say otherwise; experienced candidates should use the shortest format that preserves material evidence.
• 3-5 bullets per role: Keep the bullets that show leadership, personal action, and the result, and cut duty lists.
• Quantified results: Add a metric when you can verify it; otherwise use an observable result such as adoption, a decision, or a process reused by the team.
• 30-second recruiter scan: Put the clearest leadership signal, personal impact, and result in the first half of the page.

Reported McKinsey emphasis in this article: leadership, personal impact, and entrepreneurial drive. Use that as a tailoring lens, not as a claim about an official McKinsey scorecard.

Leadership-to-Impact Method, a Road to Offer method:

1. Action: I led or initiated [initiative, team, or workstream] and owned [decision or change].
2. Method: Using [stakeholder coordination, analysis, experiment, or implementation], I [specific action that moved the work forward].
3. Quantified result: This moved [metric] from [before] to [after], a [change]; if no number is verifiable, state [adoption, decision, or implementation result].

Next action: use the free consulting resume grader for one free complete AI review per account.

The first screen should answer four questions without forcing the reviewer to decode the page: what stage you are at, what you have owned, what changed because of your work, and which claim deserves a follow-up question. Road to Offer uses those questions as an application-writing method, not as an official McKinsey rubric.

Read the page from the top until the end of the first role. If the strongest evidence appears lower, move it. If a heading, activity, or older bullet consumes space without changing the reader's view of you, cut it.

How should you order the sections?

Choose the order that makes your candidate type legible.

The consulting resume guide owns generic template choice and formatting mechanics. Use it to settle the base document. This page owns the McKinsey application question: which evidence should be visible now, and which evidence can become a story later?

How do you write a bullet that survives follow-up?

Use four parts: action, scope, result, and proof. Start with what you personally did. Name the problem or decision. Add a number only when it is already supported. Finish with the observable change or the audience that used the work.

1. Action: replace "supported" with the decision, analysis, coordination, or implementation you owned.
2. Scope: name the customer segment, workstream, team, or operating question without disclosing confidential details.
3. Result: state a measured result or a safe observable proxy, such as adoption by a sponsor or a process reused by the team.
4. Proof: ask what document, calculation, stakeholder, or sequence would support the line if an interviewer probed it.

The result is a bullet that can become a structured interview answer. It does not need a firm label. It needs a clear chain from your action to the outcome.

Three before-and-after bullet examples

These examples come from Road to Offer's owned generic resume example set. They illustrate the writing move. Replace every detail with your own approved evidence.

None of these lines is "McKinsey language." That is intentional. The firm-specific step is selecting the examples that best support the target role and the stories you can defend. Polishing a weak fact does not make it relevant.

What should your evidence checklist contain?

Use a candidate-owned checklist instead of asserting a current firm competency list that has not been live-verified:

• One example where you defined or reframed a difficult problem.
• One example where your own action changed a decision or result.
• One example where you led, influenced, or coordinated people through ambiguity.
• One example where analysis became a concise recommendation.
• One example you can explain without revealing restricted or confidential information.

The checklist is complete only when each example is visible on the resume and consistent with the story you would tell. If two bullets prove the same thing, keep the clearer one and use the space for a different signal.

How should the resume connect to the cover letter and PEI prep?

Recruiters read the documents as one application story. The resume proves the facts. The McKinsey cover letter can explain why those facts point to the role, office, or transition when the current application flow accepts a letter. It should not introduce a result that the resume cannot support.

The same boundary applies to interview preparation. A resume bullet can seed a personal story, but it is not the full story. The McKinsey PEI guide helps you expand one line into context, tension, action, and reflection. The McKinsey case interview guide covers the separate problem-solving preparation job.

What should you check before submitting?

1. Confirm the current portal requirements for the exact role and market.
2. Read only the first screen and verify that stage, ownership, and best result are visible.
3. Check every metric and proper noun against your records.
4. Remove any firm-specific interpretation you cannot support.
5. Compare the resume with the cover letter so the facts, role, and office story agree.
6. Rehearse the follow-up question behind the first bullet in each section.

Finish by reading the document as a skeptical interviewer. If a line sounds more senior than the story behind it, narrow the claim. If the evidence is real but buried, move it. If the line cannot produce a clear explanation, rewrite or cut it.

Source notes

• Consulting resume guide, generic section order, template selection, and owned bullet examples, repository version reviewed July 18, 2026.
• McKinsey cover letter, document-pair boundary, repository version reviewed July 18, 2026.
• McKinsey PEI guide, interview-story continuation, repository version reviewed July 18, 2026.
• Current McKinsey role description and application portal: verify for the role, office, and market before submission.