Job leveling: How to build your framework in 2026

Job leveling assigns every role in your organization a defined level based on scope, responsibility, and decision-making authority. Job classification then groups those roles into families and grades, so titles, pay bands, and promotion criteria stay consistent across the business.

This stopped being a back-office exercise. Pay transparency laws now cover more than a dozen US states, and every salary range you publish has to trace back to a defensible level. If your levels do not hold up, your pay ranges will not either.

This guide covers what job leveling does, how many levels you actually need, and how to map existing titles onto a structure your people and your auditors can both follow.

A job leveling framework answers one question for every role: how much scope does this job carry, and what does the organization pay for that scope?

Without defined levels, three problems compound quietly:

• Titles inflate. Two people doing identical work sit at different grades because one manager negotiated harder.
• Pay drifts. Ranges get set case by case, and unexplained gaps open between people doing the same work.
• Progression stalls. Employees cannot see what the next level requires, so they go looking for it somewhere else.

That last one carries a direct cost. Careerminds research found that 43% of HR managers are focusing on upskilling their current workforce to promote staff internally. Internal promotion only works when employees can see exactly what the next level demands of them. See the full career frameworks report for the underlying data.

These three terms get used interchangeably, and they should not be. Each does a different job.

Term	What it does	What it produces
Job leveling	Sets how much scope, autonomy, and impact each role carries	A ladder of levels that applies across the whole organization
Job classification	Groups roles into families and grades based on shared work content	Job families, grades, and a consistent titling system
Job evaluation	Measures the relative worth of one role against another	A ranking or points score used to set pay
Job architecture	Combines all three into one connected system	A full map of roles, levels, families, and pay bands

Most organizations need all four working together. That combined system is your job architecture, and job leveling is the spine that holds it upright.

Pay transparency legislation has spread quickly across the US. Illinois and Minnesota requirements took effect in January 2025, New Jersey in June 2025, Vermont in July 2025, and Massachusetts in October 2025. Maine follows in July 2026. Virginia’s law applies to every employer with no headcount threshold at all.

Each of these laws forces the same thing: publish a good-faith pay range. You cannot publish a defensible range without a defensible level behind it.

Employers with European operations face a second deadline. The EU Pay Transparency Directive set a transposition deadline of 7 June 2026, and its standard is equal pay for work of equal value. That means justifying pay differences using objective job content rather than tenure or negotiation. That is a job leveling exercise by another name.

The gap these laws target is widening rather than closing. The US Census Bureau reported that the female-to-male earnings ratio for full-time, year-round workers fell to 80.9% in 2024, down from 82.7% in 2023. That is a second consecutive annual decline.

There is no standard number. Search demand for “the 7 levels of employment” suggests a fixed hierarchy exists somewhere, but no standards body defines one. The real systems all use different counts:

• The US federal General Schedule runs 15 grades, each with 10 steps.
• The International Labour Organization’s ISCO-08 classification uses four skill levels across 10 major occupational groups.
• The University of California’s Career Tracks system uses roughly five professional levels and six management levels.

Pick your number from the work itself. Count the genuine breaks in scope, the points where decision-making authority actually changes hands. Most mid-sized organizations settle between six and nine levels. Fewer than five flattens distinctions that matter to people. More than ten creates promotions that carry no real change in responsibility.

Whatever number you land on, these five bands give you a starting structure. For each one, the question is not what the title says but what the role decides.

Executives set direction and own outcomes across business units or the whole organization. They control budget allocation, they answer to the board, and their decisions play out over years rather than quarters. Document the scope of accountability here, not the reporting line.

Typical roles: chief technology officer, chief financial officer, chief medical officer, plant vice president.

These leaders translate strategy into operating plans and manage other managers. They own departmental budgets, headcount decisions, and cross-functional delivery. The distinction from executive level is scope of authority: they optimize within a strategy rather than setting it.

Typical roles: IT director, nursing director, regional operations manager, dean of students.

First-level managers run daily operations and directly supervise individual contributors. They assign work, manage schedules, and handle the first line of performance conversations. This is the band where frameworks most often break down, because people get promoted into it on technical merit alone.

Careerminds research found that 82% of managers step into leadership positions without receiving any formal training. Defining this level properly, with explicit people-management criteria, is what stops that gap from forming.

Typical roles: software development team lead, charge nurse, site supervisor, warehouse supervisor.

Senior specialists carry deep expertise without managing people. A functioning framework pays them on a par with managers at equivalent scope, which is the only way to stop technical experts from moving into management purely for the money. If your structure has no senior individual contributor track, you are pushing your best specialists toward the wrong ladder.

Typical roles: senior data scientist, senior counsel, principal engineer, senior clinician.

Early-career employees work under direction and build core skills. The level criteria here should be explicit about what “ready for the next level” looks like, with a realistic time-in-level expectation. Vagueness at this band produces the highest attrition.

Typical roles: analyst, junior QA tester, medical assistant, associate.

This is the part most teams get wrong, because they start with titles. Start with work content instead.

1. Write the level criteria first. Define scope, autonomy, decision rights, and required capability for each level before you place a single person. If you build criteria around existing people, you will simply encode the current inconsistencies.
2. Audit actual job content. Collect what each role genuinely does, not what the job description said three years ago. Ask managers what decisions the role makes without approval.
3. Benchmark against the external market. Match your roles to market data by content, not title. Two companies use “senior manager” to mean completely different things.
4. Slot roles and hunt for outliers. Place every role, then look hard at anyone who lands unexpectedly high or low. Those cases are where pay equity risk sits.
5. Attach pay bands to levels. Each job grade gets a range with a defined midpoint and overlap. This is what makes your posted ranges defensible under transparency law.
6. Publish the criteria. A job leveling framework nobody can read delivers none of the retention benefit. Employees need to see what the next level requires.

A job leveling matrix is the usual output: levels down one axis, competencies across the other, with the expected behaviour at each intersection. Our guide to building career frameworks walks through how to construct that matrix in practice.

Four failure patterns account for most of the damage:

• Building levels around people. Design the structure for the roles you need, then place people into it.
• Too many levels. If a promotion does not change what someone decides, it is a title change, not a promotion.
• No individual contributor track. Forcing specialists into management to progress loses you the specialist and gains you a reluctant manager.
• Publishing levels without pay bands. Employees read a level structure with no pay attached as an empty exercise.

Development equity is the quiet one. Careerminds research found that 48% of remote workers report feeling overlooked for promotions, projects, or skill development. Clear, published level criteria are the most direct fix, because they replace manager discretion with a documented standard.

A framework built in 2020 does not contain the roles a 2028 organization needs. The US Bureau of Labor Statistics projects total US employment growing 3.1% between 2024 and 2034, while computer and mathematical occupations grow 10.1% over the same period. Whole categories of work are shifting shape underneath your existing structure.

Review your framework at least every 18 to 24 months, and immediately after any restructure or major technology change. A practical trigger: if more than a fifth of your roles have materially changed scope since the last review, you need a redesign rather than an update.

AI is accelerating this. Tools that analyze job descriptions at scale can now build a skills taxonomy and flag roles that have drifted from their defined level, which turns an annual manual audit into something continuous. Our piece on AI career frameworks covers where that helps and where human judgement still decides. If you are unsure whether your current structure is holding, these five warning signs are a useful starting check.

Job leveling is the process of assigning every role a defined level based on scope, responsibility, and decision-making authority. It creates a consistent hierarchy that pay bands, titles, and promotion criteria all connect to.

No. Job evaluation measures the relative worth of individual roles against each other, usually producing a ranking or points score. Job leveling uses that output to build the organization-wide ladder of levels.

No standards body defines a fixed seven-level hierarchy. Real systems vary widely: the US General Schedule uses 15 grades, ISCO-08 uses four skill levels, and most mid-sized employers use between six and nine. Choose your count based on where scope genuinely changes.

A grid that maps levels against competencies, showing the expected behaviour and scope at each intersection. It is the working document managers use to place roles and explain progression to employees.

A job grade is a specific step in the structure, usually tied to one pay range. Job bands are wider groupings that contain several grades, used when an organization wants fewer, broader pay ranges with more movement inside each one.

At least every 18 to 24 months, and straight after any restructure, acquisition, or significant change in how work gets done.

Job level classification is not an administrative tidy-up. It decides who gets paid what, who gets promoted, and whether your pay ranges survive scrutiny. Done well, it gives employees a visible path and gives you a defensible answer to any question about pay.

With 20M people supported across 100+ countries, Careerminds helps HR leaders design job levels and career frameworks that hold up under real-world pressure. Contact us to talk through your framework.