All articles

Job levelling explained,
and what L1 to L5 means.

ArticleBy Sunandan BanerjeeUpdated September 20268 minute read

Colleagues reviewing a role framework on screen

Job levelling is the process of placing every role in an organisation on a common scale, so that a marketing manager and an engineering manager at the same level carry comparable scope, autonomy and impact. It is the frame that lets pay ranges, promotion criteria and career paths stay consistent across functions.

What levelling is for

Lacking a levelling framework, every function invents its own hierarchy and the titles lose meaning across boundaries. Three problems follow, and they arrive in this order.

  • Pay stops being defensible. Two people doing equivalent work in different teams end up materially apart, and the explanation is historical rather than reasoned.
  • Promotion becomes a negotiation. Where the bar is undefined, the people who advance are the ones who ask most persistently, which is a different population from the ones performing best.
  • Hiring drifts. A role advertised as senior in one team draws candidates who find the actual scope junior, and the offer falls over late.

A framework fixes the scale rather than the salary. Pay ranges hang off the levels afterwards, which is why levelling has to be settled before benchmarking is worth commissioning.

The dimensions a level is built from

Most frameworks score a role on four or five dimensions and place it by the combination rather than by any single one.

  1. Scope. How much of the business the role affects. A task, a project, a team, a function, the company.
  2. Autonomy. How much direction the person needs. From work assigned and reviewed, through work set against objectives, to setting the objectives.
  3. Complexity. Whether problems arrive defined, ambiguous, or undefined and contested.
  4. Impact. What is at stake when the person is wrong, and how long the consequence lasts.
  5. Influence. Whether the person persuades their team, their function, the executive, or the market.

Years of experience is deliberately absent. It correlates with level and predicts it poorly, and a framework that uses it rewards tenure rather than contribution.

What L1 to L5 typically means

Labels vary between organisations, and the shape rarely does. A five-level individual contributor scale usually runs something like this.

LevelScopeAutonomyTypical title
L1Own tasks, clearly definedWork assigned and reviewedAnalyst, Associate
L2Own projects end to endObjectives set, method chosenSenior Analyst
L3Own an area, guides othersSets own objectives within a planLead, Principal
L4Owns a function or programmeShapes the planHead of, Director
L5Owns an outcome for the businessSets the agendaVP, Chief

Management usually runs as a parallel ladder from roughly L3 upwards rather than as a continuation of it, so that a principal engineer and an engineering manager sit at the same level on different tracks. That parallel structure is what lets someone advance as a specialist rather than a manager, which retains specialists who would otherwise leave for a title.

Building a framework while keeping it lean

Levelling projects go wrong more often through excess than through neglect. A framework with twelve levels and six dimensions produces debates nobody can settle, and it goes unused within a year.

  1. Start with the roles you actually have. Write the levels that describe your current organisation, then extend upward for where it is going.
  2. Use five levels, or six. Fewer forces unlike roles together; more creates distinctions people argue about and managers exploit.
  3. Write each level as a paragraph rather than a matrix. A paragraph someone recognises themselves in beats a grid of adjectives.
  4. Calibrate on real people. Place thirty known roles before publishing. Where two people obviously equivalent land in different levels, the framework is wrong rather than they are.
  5. Publish it. A framework people are unable to read is a framework that exists only to justify decisions after they are made.

Levels and promotion

The single most useful thing a framework does is separate two questions that get conflated: is this person performing well, and is this person operating at the next level.

Strong performance at L2 argues for a rise within the L2 range. It argues for promotion to L3 only where the person is already demonstrating L3 scope and autonomy. Framing it that way converts an uncomfortable conversation about worth into a legible one about evidence.

The uncomfortable corollary is that some people will sit at a level for years and perform excellently there. A framework that reads that as a step down pushes good specialists into management against their inclination, which is how organisations lose their best practitioners and gain mediocre managers.

Levels and titles are different things

A level is internal and describes scope. A title is external and describes standing. Organisations that fuse the two end up letting the market set their internal hierarchy.

Keeping them separate buys real flexibility. A candidate who needs Director on a business card to make the move can have it while sitting at the level their scope actually warrants, with pay set from the level rather than the title. Sales functions have worked this way for decades for exactly that reason.

  • Levels drive pay range, promotion criteria and internal comparison.
  • Titles drive external credibility, and they can be generous where that costs nothing.
  • The pairing should be published, so that a Director at L3 and a Director at L4 is a visible distinction rather than a discovered one.

Where an organisation refuses to separate them, every offer negotiation becomes a negotiation about the framework itself, and the framework loses.

Why frameworks drift, and how to hold them

Most frameworks are accurate on the day they launch and misleading within two years. Three forces cause it.

  • Title inflation at offer stage. A candidate asks for Director and gets it, and the level beneath them becomes incoherent.
  • Promotion as retention. A level granted to keep someone rather than because the scope changed, which prices every peer out of line.
  • Scope creep that goes unlevelled. A role grows steadily and stays on its original level until the person leaves and the replacement is hired at the level the job has actually become.

Holding it takes two habits: a calibration session once a year where a group reviews placements together rather than manager by manager, and a rule that any offer above the agreed level for a role needs the same approval as an exceptional salary. Both are cheap. Both survive only when someone owns them.

Frequently asked questions

Placing every role on a common scale so that equivalent roles in different functions carry comparable scope, autonomy and impact. It is the frame that keeps pay ranges, promotion criteria and career paths consistent across an organisation rather than varying by team.

A five-point scale running from owning defined tasks to owning a business outcome. L1 works on assigned tasks under review; L3 owns an area and guides others; L5 sets the agenda for a part of the business. Labels vary between organisations and the shape rarely does.

Five or six for most organisations. Fewer forces genuinely different roles together. More creates distinctions people argue about and managers exploit, and the framework falls into disuse.

Largely terminology, with grading tending to imply a points-scored method. Grading systems score roles against weighted factors and total them. Levelling frameworks more often describe each level in prose and place roles by judgement against that description.

Yes. An unpublished framework exists only to justify decisions after they are made. Publishing the level descriptions, with individual placements kept optional, is the usual middle ground and removes most of the suspicion around promotion.

Annually, in a session where a group reviews placements together. Manager-by-manager review preserves each manager’s bias. A shared session is the mechanism that keeps a marketing L3 and an engineering L3 genuinely comparable.

It sets the range rather than the number. Exceptions remain possible and should be visible. A framework that has an exception for a quarter of the organisation has stopped describing it, and the honest response is to fix the framework rather than the exceptions.

Related reading

Article

What is salary benchmarking?

Levels set the frame. Benchmarking prices it against the market.

Read more

Article

What is organisational design?

Where roles sit, who decides what, and how the structure holds the strategy.

Read more

Article

A pay structure that survives negotiation

Ranges hold or collapse at the offer. What to settle before the conversation.

Read more

Tell us about the mandate.

Fill in the form and our team will get back to you within 24 hours.