McKinsey Hierarchy 2026: Five Named Rungs, Two More

Five levels of the McKinsey hierarchy, named on its careers site

The firm's consulting roles page, checked 29 September 2026, lists five levels in order and writes a scope for each. The wording below is the firm's, quoted.

Read the four verbs in sequence and the shape of the ladder appears. A BA analyzes and presents. An Associate owns a piece. An Engagement Manager directs a project. An Associate Partner carries several projects and starts finding new ones. A Partner holds the relationship. The unit of responsibility grows from a slide to a workstream to a project to a portfolio to a client. The firm's live posting puts a size on the middle rung, naming a team of three to five consultants on one client project.

The page also states where people come in: "Most consultants join McKinsey as business analysts or associates and grow from there". Two doors, and the rest of the ladder is internal.

Two rungs of the McKinsey hierarchy only the filings name

McKinsey filed 453 certified Labor Condition Applications with the US Department of Labor in the first three quarters of fiscal 2026, each naming a job title and a wage. The disclosure file, checked 29 September 2026, carries seven distinct consulting titles. Two of them never appear on the careers site.

Senior Business Analyst appeared on 51 filings, so it is a real rung with real volume. Senior Partner appeared once, which makes it a filed title rather than a documented level. Neither name is anywhere on the careers site. If you are told you have been promoted to Senior Business Analyst, you will not find a page describing the job. The full band table and the city detail sit on our McKinsey salary page, which is where the pay question belongs.

Where two rungs overlap, and what that does to a promotion

The filed bands do not stack like stairs. Two boundaries are worth doing the arithmetic on.

The Senior Business Analyst ceiling is $192,000. The Associate floor is $192,000. The same number, which means the pre-MBA ladder tops out exactly where the post-MBA ladder starts. Moving from one to the other adds responsibility before it adds salary.

The Associate ceiling is $212,000 and the Engagement Manager floor is $200,000. Subtract: $212,000 minus $200,000 leaves $12,000 of overlap. A well paid Associate can be earning more than a newly promoted Engagement Manager. The promotion is a change of job rather than a raise, at least in the month it happens.

That matters if you are choosing between an internal promotion and an outside offer. The step from Associate to Engagement Manager swaps analysis for team and client management, and the filed bands say the money follows later. The two rungs with clean separation are Associate Partner, whose floor of $243,000 sits $1,000 above the Engagement Manager ceiling of $242,000, and Partner.

How long each level lasts, according to the only page that says

McKinsey publishes one tenure figure anywhere we could find. Its Denmark careers page, read 29 September 2026 from an archived copy because the role bodies are not in the served HTML, says: "you can apply to our 2-year apprenticeship as a business analyst". The same page gives the exit route: "High performing business analysts can be presented with the opportunity to return to McKinsey as associates after completion of their master's degree or MBA."

That is a program length and a re-entry path. It is not a promotion window, and no McKinsey page we read carries one. The global roles page says only that people grow "some for a few years, others for an entire career". The firm's position is that advancement follows readiness: "You will have every opportunity to advance as soon as you are ready".

So any figure you have read that puts a fixed number of years on each McKinsey rung did not come from McKinsey. We do not publish one either. What is verifiable is the shape of the ladder, the scope of each level, and the pay boundary between them.

Denmark proves the McKinsey hierarchy changes by country

Take the global page as universal and you will misread a job posting. The Denmark page places new joiners into "one of three groups" and names them business analyst, consultant, and associate. Consultant is the middle group there, described as the entry for someone applying "shortly after finishing your master's or PhD degree". The global roles page has no Consultant level at all.

Denmark also labels that rung "Consultant (Junior Associate)", which is a title in parentheses precisely because it does not travel. And the page adds a detail worth knowing before you apply: "The recruitment process for all roles is the same." The interview does not get easier at the lower rung.

Two consequences. Read the posting for the office you want. A global summary will not carry the local title, and the title in the posting is the title you would hold. And when you compare an offer across firms, compare the scope rather than the word, because the word moves. Our BCG levels page shows the sharpest version of that problem: Associate at BCG is a pre-MBA rung, and Associate at McKinsey requires "an advanced graduate degree (e.g., MBA, PhD, etc.) or equivalent work experience".

What a week on the ladder looked like, in three logs

McKinsey states that "There is no typical week at McKinsey Denmark" and that "Projects typically last 2 to 4 months". Beyond that the firm describes the job and leaves the calendar alone. Three of its own associates published hour by hour logs on the McKinsey careers blog, and those are first hand accounts of specific days rather than a description of the role.

Brooke, an associate in Dallas writing on 17 March 2015, opens at 6:30am in a hotel. She notes the travel rhythm plainly: "My team travels in on Monday evening or Tuesday morning to match the client's schedule." Her day holds an 8:00am team check-in on priorities, a two hour problem solving workshop with the client, an afternoon client meeting, two hours building a deployment plan, and a 5:30pm check-in. Amy, an associate in New York writing on 7 April 2016, uses the word workstream as a personal unit: she reviews CFO comments on workstream A, then prepares an internal session on workstream B.

Three points converge across the logs, which makes them a pattern rather than an anecdote: hotel nights during the week, one block of client meetings and one block of internal problem solving, and deck work pushed to the late afternoon or the evening. All three posts are a decade old and all three sit on a recruiting page, so read them as what those people did on those days. Brooke's line about dinner for "our engagement manager's promotion to associate partner tonight" is also the only promotion event described by anyone at the firm in public.

What McKinsey will not put a number on

Four things a reader reasonably wants that no primary source we read provides.

1. A promotion rate at any rung. Not published, by the firm or by anyone with access to its data. Every percentage in circulation on this query traces back to a private survey or to nothing at all.
2. Whether the firm operates up or out. The phrase is everywhere on this query and on none of the pages McKinsey publishes. What the firm does write is that people grow "some for a few years, others for an entire career", which is compatible with several very different internal policies. We do not assert one.
3. How many people sit at each level. Filing counts are sponsorship cases. They say nothing about headcount. Seventy-three Associate filings are not seventy-three associates, because only roles filed for sponsorship appear in the record at all.
4. How many analysts an Associate supervises. The Associate posting describes owning a workstream and says nothing about line management. The Denmark page says an associate takes "an active role in all aspects of an engagement" and also stops short of naming supervision.
5. What the evaluation actually measures at each review. The firm publishes the scope of the next level, so you can read what the job demands. What the review looks at is internal, and nobody outside it has seen the form.

Who holds each of those five: McKinsey's own people function, and only McKinsey. There is no regulator, no filing, and no school report that carries any of them, which is why this page stops here rather than estimating.

For the rung itself, the live posting is the authoritative document, and it is public. For the pay, the filings and the firm's own posted ranges are public and dated, and they are both on our salary page.

Preparing for the rung you are actually applying to

Which rung you enter changes what the interview asks. A BA candidate is assessed on whether the reasoning can be built. An Associate candidate has an advanced degree behind them and gets less credit for promise. Both sit the same case, and the Associate seat page sets out what the post-MBA bar adds.

Our free synthesis drill is the one that maps onto the rung difference, because a recommendation is what an owner of a workstream produces. It scores four dimensions, and the numbers are ours rather than the firm's: we wrote the scale, and the weights sit in our code and on our method page as Answer first 35, Evidence 25, Risk 20, Next step 20. No firm publishes a rubric, McKinsey included.

Two limits, stated plainly. The drill teaches no business content, and it does not simulate the Solve assessment: our /assessments page says 0 of 6 simulators are live, in those words, on the page itself. What runs today is the drills and the graded scorecard, open without an account.

The drill is also a cheap way to test whether the rung question is even the live question. Someone who cannot deliver a recommendation with a number and a risk inside ninety seconds is being screened out before any ladder applies. Someone who can is in the population these filings describe, and the better next question becomes which office and which practice, both of which shape the work more than the title does.