← Back to Tiny Team

Job Leveling (2026): How to Build a Framework for Small Teams

Job leveling is the practice of sorting every role in your company into a consistent set of levels based on scope, impact, and responsibility, not job title. It gives a 15-person startup the same clear ladder a 500-person company uses to answer questions like "what does 'senior' actually mean here?" and "is this person ready for a promotion?" Done well, a job leveling framework becomes the backbone for pay, promotions, hiring, and career growth.

Most guides on this topic are written for HR teams at companies with 200-plus employees. This one is built for the messy middle: teams of 5 to 100 where a founder or the first HR hire is setting up structure for the first time. You will get a step-by-step method, department-specific examples, a copy-and-paste template, and the mistakes that trip up small teams.

What is job leveling?

Job leveling (sometimes called job level classification or job architecture) is a framework that groups roles into a hierarchy of levels. Each level carries a shared set of expectations: how much scope a person owns, how independently they work, and how much impact their decisions have on the business.

The key idea is that a level is separate from a title. A "Senior Engineer" and a "Senior Account Executive" can sit at the same level even though their day-to-day work looks nothing alike, because they own comparable scope and operate with comparable autonomy. That shared meaning is what makes the framework useful.

A basic small-team structure usually has two tracks:

  • Individual contributor (IC) track: people who deliver work directly. Levels often run IC1 (entry) through IC5 (staff/principal).
  • Management (M) track: people who lead others. Levels often run M1 (team lead) through M3 (director or VP).

The two tracks matter because they let a great engineer or designer keep growing in title, pay, and influence without being forced into management to get there. According to SHRM, job leveling helps grade a position's value to the organization in a consistent, defensible way, which is exactly what you want when someone asks why two roles are paid differently.

Why small teams need a job leveling framework

It is tempting to think leveling is an enterprise problem. It is not. The pain shows up earlier than most founders expect, usually around the 15-to-30 person mark, when informal "everyone knows what everyone does" stops working.

Here is what a framework fixes:

Title inflation. Without levels, titles get handed out to close a hire or calm a nervous employee. Six months later you have four "Senior" people doing wildly different work and no way to explain the difference.

Vague promotions. When there is no ladder, promotions become political. People get promoted because they asked, or because they might leave, not because they cleared a bar. A framework turns "trust me, you're ready" into "here is the level you're operating at, and here is what the next one requires."

Pay confusion. Levels are the link between roles and pay. Once roles are leveled, you can attach salary bands to each level so pay is consistent and easy to explain. (More on that split in the next section.)

Hiring calibration. A leveled framework lets you write a job posting that says "this is an IC3 role" and know exactly what scope, autonomy, and pay that implies before the first interview.

For a founder still doing HR themselves, that structure is a force multiplier. It is also a prerequisite for most of the compensation and growth work you will tackle next, starting with compensation planning and clearer career growth conversations. If you are building the people function from scratch, our people operations guide covers the wider setup.

Job leveling vs job grading vs pay bands

These three terms get used interchangeably, but they answer different questions. Getting the distinction right saves you from re-doing work later.

Concept Question it answers Output
Job leveling How big is this role? What scope and impact does it own? A level (e.g. IC3, M2) attached to every role
Job grading / job evaluation How does this role rank against others for pay purposes? A grade or band assignment, often via a scoring method
Pay bands What salary range should this level earn? A minimum-to-maximum dollar range per level

Think of it as a sequence. Job leveling defines the role structure: the ladder of levels and what each one means. Job evaluation or grading is the method you use to sort roles into that ladder consistently; SHRM's job evaluation guide walks through the formal approaches. Pay bands are the dollars that attach to each level once the ladder exists.

This article is about the first step: building the role-level framework itself. The pay ranges that sit on top of it are a separate exercise; we cover those in depth in our salary bands guide, so we will not re-explain range spreads and midpoints here. Build the levels first; attach the money second.

How to build a job leveling framework (step by step)

You can build a first-pass framework for a 30-person team in a focused afternoon. Here is the sequence.

Step 1: Audit your current roles

List every role you have today, grouped by function (engineering, sales, marketing, ops, and so on). For each one, write two or three sentences describing what the person actually does (not their title, their real scope). Note who they report to and who reports to them.

You are looking for the truth on the ground, which is often messier than the org chart suggests. Two people with the same title frequently operate at different levels. That gap is exactly what the framework will surface and fix.

Step 2: Define your level structure

Pick how many levels you need. Resist the urge to copy Google's 11-level ladder. For a team under 100, a lean structure is a feature, not a compromise.

A solid small-team starting point:

  • IC track: IC1, IC2, IC3, IC4, IC5 (entry → junior → mid → senior → staff)
  • Management track: M1, M2, M3 (team lead → manager → director/VP)

Many teams under 50 only need three or four IC levels and one or two management levels to start. You can always add rungs as you grow. The two tracks should be "parallel," meaning IC4 and M1 carry roughly equal scope and pay, so moving into management is a lateral choice, not the only way up.

Step 3: Write your level descriptors

This is the heart of the framework. For each level, describe expectations across three dimensions:

  1. Scope: how much they own. A single task? A feature? A whole product area? A department?
  2. Autonomy: how much guidance they need. Closely directed? Self-directed within a project? Setting direction for others?
  3. Impact: how far their work reaches. Their own output? Their team's? The company's results?

These three dimensions (scope, autonomy, and impact) are the columns of your job leveling matrix. (Deel's guide to building a job leveling matrix uses a similar set of criteria.) Keep descriptors short and behavioral. Instead of "strong communication skills," write "resolves cross-team disagreements without escalating to a manager." You want a bar someone can be measured against, not a vibe.

Step 4: Map existing employees to levels

Now place every current employee onto the ladder using the descriptors, not their title. Read each descriptor and ask, "which level best matches how this person actually operates today?"

Expect surprises. You will find people operating a level above their title (a promotion case) and people with an inflated title operating below it (a coaching or re-leveling conversation). Do this calibration with at least one other leader in the room to reduce individual bias. Document your reasoning for each placement so you can defend it later.

Step 5: Connect levels to compensation bands

Once every role sits on a level, attach a pay range to each level. This is where leveling and money finally meet. Pull market data for each function, set a minimum-midpoint-maximum for each level, and check that nobody's current pay falls wildly outside their new band.

We will not go deep on band mechanics here; that is a full topic on its own. Our salary bands guide covers range spreads, overlap, and market positioning, and a free salary calculator can help you sanity-check individual numbers. As SHRM notes on building salary structures, the pay ranges should reflect both external market value and internal consistency across levels.

Video thumbnail: Chutes & (Career) Ladders: Architecting a Scalable Comp Plan | Startup Boston Week 2022▶ Optional deeper dive · 57:27: Chutes & (Career) Ladders: Architecting a Scalable Comp Plan | Startup Boston Week 2022
Startup Boston's workshop connects career ladders and compensation philosophy, with practical considerations for growing teams. Opens YouTube after a click. Source: Startup Boston on YouTube.

From levels to career paths: ladder, lattice or dual track

A leveling framework tells you where every role sits today. A career path shows how a person can move from one level to the next, or sideways into a different role. Once your levels exist, career pathing is mostly a matter of connecting them and writing down what "ready" looks like.

The classic model is a career ladder: IC1, then IC2, then IC3, then up into management. It is clean and vertical, and it stalls on a 25-person team, because there is rarely an open role above someone the moment they are ready for it. A career lattice treats growth as movement in any direction: up a level, sideways into an adjacent function, or deeper expertise in place with more scope but no new title.

Dimension Career ladder Career lattice
Direction of growth Vertical only Vertical, lateral, and deeper expertise
Best fit Large, layered orgs Flat, small teams
What "advancement" means A promotion More scope, skill, or impact
Risk Stalls when no roles open above Keeps people growing without new headcount
Example move Analyst → Senior Analyst → Manager Marketing Coordinator → Product Manager

A dual track is the IC and management tracks from Step 2 used as career paths. At the senior level (IC4), someone can either move across into management at M1, which carries roughly the same scope and pay, or keep growing as an individual contributor toward staff level (IC5). That keeps your best specialists from taking a management job just to earn a raise. Most small teams end up with a hybrid: ladders where clear levels exist, such as engineering and sales, and lattices where they don't, such as a two-person ops team.

An experienced contributor can grow through a specialist track or a management track, with lateral moves between them.
Two paths can offer comparable growth: deeper expertise or responsibility for a team.

To make a path something an employee can work toward, add a "signal you're ready to move up" line to each level. On a small marketing team, these three levels map roughly to IC1, IC3 and IC5 in the examples below:

Role family: Marketing
Level 1: Contributor
  Skills: executes campaigns, writes copy, uses core tools
  Scope: owns individual tasks with guidance
  Signal you're ready to move up: runs a channel end to end

Level 2: Owner
  Skills: plans campaigns, reads analytics, manages a budget
  Scope: owns a channel or program independently
  Signal you're ready to move up: sets strategy others follow

Level 3: Lead
  Skills: sets marketing strategy, mentors others
  Scope: owns outcomes across multiple channels
  Signal you're ready to move up: opens a management or specialist track

Make each signal checkable: a project shipped, a certification earned, a metric hit or a person mentored. Revisit each person's path in your regular one-on-one meetings and at review time, and write the agreed next step into an employee development plan. A path drawn once and never revisited is worse than no path, because it signals that growth talk is theater.

Job leveling and career pathing examples by department

Abstract levels click into place once you see them applied. Here is what IC levels look like across four common small-team functions, with the career paths that typically run through them. Titles vary by company; the scope descriptions are the load-bearing part.

Engineering

Level Title Scope and expectation
IC1 Junior Engineer Ships small, well-defined tasks with review. Learning the codebase.
IC3 Engineer Owns features end to end. Works independently within a project.
IC5 Staff Engineer Sets technical direction for a product area. Impact spans teams.

Career paths:

  • Ladder: Junior Engineer → Engineer → Senior Engineer → Tech Lead
  • Lattice: Engineer → DevOps focus, or Engineer → Product Engineer (owning features end to end)
  • Dual track: at senior level, Engineering Manager (people) or Staff Engineer (deep technical, no reports)

Sales

Level Title Scope and expectation
IC1 SDR Books qualified meetings against a set playbook.
IC3 Account Executive Owns a full pipeline and closes deals independently.
IC5 Strategic AE Handles the largest, most complex accounts and mentors reps.

Marketing

Level Title Scope and expectation
IC1 Marketing Coordinator Executes campaigns others plan.
IC3 Marketing Manager Owns a channel and its results end to end.
IC5 Principal Marketer Sets marketing strategy across channels.

Career paths:

  • Ladder: Marketing Coordinator → Marketing Manager → Head of Marketing
  • Lattice: Content Marketer → Product Marketing, or Coordinator → Growth/Analytics focus
  • Small-team reality: most marketers grow by owning a new channel, not by adding reports

Operations / People

Level Title Scope and expectation
IC1 Ops Associate Runs recurring processes with guidance.
IC3 Ops Manager Owns a function (e.g. all of HR ops) independently.
IC5 Head of Ops Designs company-wide systems and standards.

Career paths:

  • Ops ladder: Ops Associate → Ops Manager → Head of Ops
  • People ladder: People Coordinator → People Specialist → People Lead → People Manager
  • Lattice: Ops → People/HR, Finance or Program Management; People Ops → Recruiting or Learning & Development. Ops is the most natural lattice hub on a small team, since it touches everything.

Notice the pattern: at every function, IC1 executes defined tasks, IC3 owns a domain independently, and IC5 sets direction beyond their own team. That consistency is exactly what leveling gives you: an IC3 in sales and an IC3 in engineering are genuinely comparable, even though the work is not. The career paths show a second pattern: on a small team, the lattice branch is often the move that actually happens. You may not have room for three engineering managers, but you always have room for someone to become the person who owns your deployment pipeline.

Job leveling template (free)

Here is a complete, usable template. Copy it into a spreadsheet or doc, swap in your own functions, and fill the descriptor cells. It is deliberately small; start here and add levels only when you feel the pinch.

Part 1: Level descriptor matrix

Fill one row per level. The three columns are your grading dimensions.

LEVEL   | SCOPE (what they own)          | AUTONOMY (guidance needed)        | IMPACT (how far it reaches)
--------|--------------------------------|-----------------------------------|------------------------------
IC1     | Single, well-defined tasks     | Close direction and review        | Own output
IC2     | A set of related tasks         | Regular check-ins                 | Own output, reliably
IC3     | A feature / domain end to end  | Self-directed within a project    | Their team's results
IC4     | A major area or several domains| Sets own priorities               | Cross-team results
IC5     | A whole product / function     | Defines direction for others      | Company-level results
--------|--------------------------------|-----------------------------------|------------------------------
M1      | A small team (2-5 people)      | Owns team delivery                | Their team's results
M2      | A team or function             | Owns strategy for the function    | Multi-team results
M3      | A department / multiple teams  | Sets department direction         | Company-level results

Part 2: Role mapping sheet

One row per employee. Use it to place people and spot gaps.

NAME        | CURRENT TITLE      | FUNCTION     | ASSIGNED LEVEL | PAY BAND | NOTES / FLAGS
------------|--------------------|--------------|----------------|----------|----------------------
Jordan P.   | Senior Engineer    | Engineering  | IC4            | Band D   | Operating above title
Sam R.      | Marketing Manager  | Marketing    | IC3            | Band C   | On track
Alex T.     | Sales Lead         | Sales        | M1             | Band D   | New to management

Part 3: Promotion checklist (per level)

For each move up, confirm the person is already operating at the target level's descriptors, not just capable of it. Promote for demonstrated scope, not potential.

[ ] Consistently meets the target level's SCOPE descriptor
[ ] Consistently meets the target level's AUTONOMY descriptor
[ ] Consistently meets the target level's IMPACT descriptor
[ ] Manager and one calibrator agree on the placement
[ ] Pay falls within (or moves into) the target level's band

That is the whole framework: define the ladder (Part 1), place your people (Part 2), and gate promotions against it (Part 3). Pair the promotion checklist with your performance review examples so leveling and reviews reinforce each other instead of drifting apart.

Common job leveling mistakes to avoid

Small teams tend to make the same handful of errors. Sidestep these and your framework will hold up as you grow.

Building too many levels. An 11-rung ladder for a 25-person team creates artificial distinctions and constant "why am I not level 7 yet" friction. Start lean. You can add rungs, but you can rarely take them away without upsetting people.

Leveling the person, not the role. Levels describe the work, not the individual. If you level around your current star performer, the framework breaks the moment they leave. Write descriptors that would apply to anyone in that seat.

Confusing level with title. Titles are for the outside world; levels are for internal consistency. Keep the two loosely coupled so you can fix a title inflation problem without re-doing your whole ladder.

Skipping calibration. One manager's "senior" is another's "mid." Placing people without a second reviewer bakes in bias and pay inequity from day one. Always calibrate with at least one other leader.

Treating it as set-and-forget. Roles evolve. Revisit the framework once or twice a year, ideally alongside your review cycle and any succession planning work, so the ladder keeps matching reality.

Bolting pay on before the levels are solid. If you attach dollars to a shaky ladder, every re-leveling turns into a pay fight. Get the levels right and agreed first, then map pay to them.

How Tiny Team helps with work structure

A job leveling framework only helps if it lives somewhere people actually look, not in a spreadsheet that goes stale by Q3.

In Tiny Team, the structure tools are shared across the workspace, which new customers activate with their first module payment. Work Structure is where you set up departments, job titles, work locations and custom profile fields, so you can keep one agreed list of titles and add a dropdown field that records each person's level on their profile.

If you also use the HR module, each person's private HR profile keeps their compensation history: amount, currency, pay period, effective date and the reason for each change, such as a promotion from IC3 to IC4. HR has a module plan for your whole organization, with no per-seat fees. It does not run payroll. See current prices, or browse the other Tiny Team modules, which are sold separately. If you need a people org chart, our roundup of org chart software covers tools that build one.

Frequently asked questions

What is the difference between job leveling and pay bands?

Job leveling defines the role structure: the ladder of levels (like IC1 through IC5) and what scope, autonomy, and impact each one requires. Pay bands are the salary ranges that attach to each level once the ladder exists. You build the levels first, then map compensation onto them. A single level can even carry different pay bands across functions if the market rates differ.

What is the difference between job leveling and career pathing?

Job leveling defines the structure: the levels (like IC1 through IC5 and M1 through M3) and the scope, autonomy, and impact each one requires. Career pathing uses that structure to show each employee how they can move, whether up a level, sideways into another function, or onto the management or IC track. Build the levels first, because career path conversations stall when nobody can say what the next level requires.

How many job levels should a small company have?

Fewer than you think. A team under 100 people usually needs three to five individual-contributor levels and one to three management levels. Starting lean avoids artificial distinctions and endless "why am I not the next level yet" friction. You can always add rungs as the company grows; it is much harder to remove them.

What are the dimensions of a job leveling matrix?

The three most useful dimensions for a small team are scope (how much a person owns), autonomy (how much guidance they need), and impact (how far their work reaches). Each level raises the bar on all three. Keep the descriptors behavioral and specific so someone can actually be measured against them.

Should individual contributors and managers be on the same ladder?

They should be on parallel ladders that are calibrated to match in scope and pay. This lets a strong engineer, designer, or salesperson keep growing in level, influence, and compensation without being forced into management. A common pairing is IC4 sitting level with M1, so moving into management is a lateral choice rather than the only path up.

How often should we update our job leveling framework?

Review it once or twice a year, ideally alongside your performance review cycle. Roles evolve, new functions appear, and people grow into higher levels, so a framework that never gets revisited quickly drifts from reality. Treat it as a living document, not a one-time project.

Do I need job leveling if we only have 15 people?

Yes, and 15 is a good time to start. The pain of title inflation, vague promotions, and inconsistent pay usually shows up between 15 and 30 people. Building a simple framework early (even three IC levels and one management level) means you set structure before problems calcify, rather than untangling them at 50 people.