How to Name and Code Your Job Levels (L1, L2, L3 and Beyond)

Why Your Level Names Are Quietly Causing Problems

Picture this: your payroll file has a "Senior Account Manager," a "Senior Account Executive," and an "Account Manager II" — three people doing nearly identical work at nearly identical tenure. When a new pay-transparency posting requirement lands, you need to know immediately which pay range applies to each title. You open your spreadsheet and find three different tabs built at three different times, none of them connected.

That's not a salary problem. It's a naming problem.

A job level naming convention is the skeleton your entire compensation architecture hangs on. Without one, every new hire negotiation, every promotion conversation, and every compliance audit becomes a translation exercise. With one, HR, managers, and employees all speak the same language — and your pay ranges attach to levels that actually mean something.

This article shows you how to name and code your job levels so the system is clear today and still holds together when you double in size.

---

The Three Elements Every Level Needs

Before you choose a naming style, understand what a job level actually has to convey. A complete level definition carries three things:

1. A code or shorthand — the fast-reference identifier used in your HRIS, your comp tool, and your org chart. Examples: L1, G3, IC4, M2.
2. A title descriptor — the human-readable career stage attached to that code. Examples: Associate, Senior, Staff, Principal, Director.
3. A scope statement — one or two sentences describing the autonomy, complexity, and accountability expected at that level, independent of job family.

Most small-company leveling systems have title descriptors but are missing the code and the scope statement. That gap is why two people with identical codes end up on wildly different pay ranges, and why managers use promotions as retention tools without a consistent threshold.

A level code without a scope statement is just a number. The scope statement is what makes the number defensible in a compensation review — or an audit.

---

Four Naming Conventions (With Honest Trade-Offs)

There is no universal right answer, but there are four patterns that appear consistently across structured organizations. Here's how they work and where each one breaks down.

1. Numeric L-Codes (L1, L2, L3…)

How it works: Each level gets a sequential number prefixed with "L." Individual contributor levels and management levels share the same scale, or you run two parallel tracks (IC: L1–L5; Management: M1–M3).

Example scale:

Code	Career stage	Typical scope
L1	Entry / Associate	Follows established processes; close supervision
L2	Developing / Mid	Applies skills independently; limited scope
L3	Experienced / Senior	Owns outcomes within a function; some mentorship
L4	Lead / Staff	Cross-functional influence; sets standards for others
L5	Principal / Expert	Org-wide impact; defines best practices

Strengths: Simple to explain to employees; easy to reference in HRIS fields; scales cleanly by adding L6, L7 if you grow.

Watch out for: Numbers can feel clinical or create status anxiety ("Why am I an L2 when my peer is L3?"). You'll need to pair codes with title descriptors in every employee-facing document — the code alone doesn't communicate career meaning.

---

2. Grade Letters or Alphanumeric Codes (G1–G8, or Band A–E)

How it works: Grades are labeled with a letter (Band A, Band B…) or an alphanumeric (G1, G2…). Often used when the organization already has a "pay band" vocabulary and wants the level code to map directly to a salary band.

Strengths: Familiar to anyone who has worked in government, healthcare, or large manufacturing; maps naturally to a pay band structure.

Watch out for: Letters run out faster than numbers if you expand, and employees may confuse grade labels with performance ratings. This convention works best when paired with a clear band-structure document — see how pay bands are structured in a complete guide before committing to a grade letter system.

---

3. Dual-Track IC / Management Codes

How it works: Individual contributors and people managers run on separate numbered tracks that branch at a defined seniority point.

Example:

IC Track	Management Track
IC1 — Associate	—
IC2 — Mid	—
IC3 — Senior	M1 — Manager
IC4 — Staff / Lead	M2 — Senior Manager
IC5 — Principal	M3 — Director

Strengths: Eliminates the classic "must go into management to advance" problem; keeps senior individual contributors on a credible, well-compensated path. Particularly useful for technical functions (engineering, data, finance) in professional-services or manufacturing firms.

Watch out for: You need explicit guidance on where the tracks branch and what the compensation parity is between, say, IC4 and M1. Without that, managers will assume management always pays more, which undermines the IC track.

---

4. Title-Only (No Codes)

How it works: Associate → Analyst → Senior Analyst → Manager → Senior Manager → Director. No numeric or letter code; the title is the level.

Strengths: Human-friendly; no translation needed for employees or external offers.

Watch out for: This is the most common system at sub-100-person companies and the one most likely to break. Title inflation ("we'll just call them Senior to keep them") is invisible because there's no code to enforce a gate. The moment you have two people with "Senior" in their title earning $30,000 apart, you have a defensibility problem. Title-only systems need especially rigorous scope statements to compensate.

---

How to Write a Scope Statement That Actually Holds

A scope statement answers three questions for a single level, in roughly two sentences:

1. What complexity of work does this level handle? (routine, varied, novel, ambiguous)
2. What is the supervision model? (receives close direction, works independently, directs others, sets direction for a function)
3. What does impact look like? (task, project, team, department, organization)

Example for L3 / Senior: Works independently on moderately complex problems within their function, drawing on established methods and occasionally adapting them. Decisions affect project outcomes; work is reviewed at milestones rather than step by step.

Example for L5 / Principal: Independently defines approaches to novel, high-complexity problems with limited precedent. Decisions and methodologies shape practices across multiple teams or functions; work is reviewed against outcomes rather than process.

Write scope statements before you assign anyone to a level. If you write them after, they will unconsciously describe the people currently in the role rather than the role itself — a common calibration error that surfaces immediately during pay-equity reviews.

For a detailed walkthrough of how scope statements fit into a full leveling framework, see how to build a job leveling framework for a small company.

---

How Many Levels Is the Right Number?

A useful rule of thumb for companies under 250 employees: four to six levels cover the vast majority of roles. More than six levels at this size creates more problems than it solves — managers start haggling over whether someone is truly L4 versus L5, and pay ranges become so narrow they're administratively useless.

Start with fewer levels than you think you need. You can always add a level later. Collapsing two levels you created prematurely is much more disruptive — it requires reclassifying people, adjusting pay ranges, and managing the optics of a demotion-adjacent conversation even when no one's pay goes down.

If a single job family genuinely needs more granularity (engineering depth ladders are a common example), create sub-levels within that family rather than expanding the org-wide level count. The difference between a job family and a job level is important here — if you haven't drawn that line yet, understanding job families vs. job levels is worth reading first.

---

Attaching Level Codes to Pay Bands

A level naming convention is most valuable when each level code maps directly to one pay band. That means:

• Level L3 → Band 3 (or Grade C, or whatever your band labels are)
• Band 3 has a defined minimum, midpoint, and maximum
• Every employee at L3 sits somewhere inside Band 3's range

This one-to-one mapping is what allows you to run a compa-ratio analysis (an employee's actual salary divided by the band midpoint, expressed as a percentage) and immediately see who is being paid below the range minimum or above the maximum. Without level codes attached to bands, that analysis requires manual lookup for every person.

To understand what those band minimums, midpoints, and maximums should be and how band widths are set, what are job bands covers the fundamentals.

---

A Practical Starting Point for a 25–150-Person Company

If you're building a level structure from scratch, here is a workable starting skeleton. Adjust the title descriptors to match your culture — the codes and scope logic are what matter.

Code	Title descriptor	Scope in one phrase
L1	Associate	Directed work, routine complexity
L2	Mid-Level	Independent within defined scope
L3	Senior	Owns outcomes; advises others
L4	Lead / Staff	Cross-team influence; sets standards
M1	Manager	Accountable for a team's output
M2	Senior Manager / Director	Accountable for a function

Six levels — four IC, two management — covers most roles at companies in this size range. You can expand the IC track to L5 (Principal) if you have deep technical functions; you can add M3 (VP / Head of) when the business requires it.

If you'd rather start with a structured template that includes scope statement language, level descriptors, and a format ready to map to pay ranges, the Job Leveling Framework Template gives you a pre-built version you can fill in rather than draft from scratch.

---

The Test of a Good Level Naming System

Before you lock in your convention, run it through three questions:

1. Can a hiring manager explain this level to a candidate in one sentence? If not, the scope statement needs work.
2. Can you assign any role in the company to a level without ambiguity? If two roles generate real disagreement about their level, either the scope statements aren't distinct enough or you're missing a level.
3. Does each level map cleanly to exactly one pay band? If a level spans two bands, or two levels share a band, the architecture has a gap that will show up immediately in a pay-transparency posting.

A naming convention that passes all three tests is one you can defend to an auditor, explain to a new hire, and build salary ranges on with confidence. ```