Job Level

Titles are old, but for a long time they were another way of writing down how many years someone had been around. Three years in and you got the next title, then the one after that. Nobody asked what you had to accomplish to move up, because time moved you up anyway.

Software companies were where this broke first. Someone two years into the job would be carrying the hardest problem on the team while earning less than the person at the next desk with seven years in. When that person leaves saying the place makes good work wait its turn, the people who stay start running the same arithmetic. The mismatch runs the other way too: nobody asks for the judgment of someone who moved up purely on tenure.

Job levels exist to close that gap by moving the basis from years to work. Each step is written out as a sentence describing what a person at that step accomplishes, and anyone working that way is at that step regardless of tenure. That makes it unremarkable for someone with five years of experience to sit at level 3 while someone with three years sits at level 4.

The axis that separates steps is not tenure and not title. It's autonomy — how much of the problem you define yourself and how much of the outcome you own yourself.

Most companies run five to seven steps, and three things grow together as the steps climb.

1. Size of problem. Level 3 finishes an assigned piece of work alone. Level 4 decides what the work should be in the first place. Level 5 takes on problems that span several teams.
2. Degree of certainty. Lower steps get work where the answer is known. Higher steps start from a question nobody has answered yet.
3. Reach of impact. It widens from your own work going well, to the team's work going well, to the company's direction changing.

Each step gets written as behavior rather than adjectives. "Works proactively" means something different to every reader. "Proposed what the team should take on this quarter without being asked, and one of those proposals shipped" can be checked. In companies where the descriptions are adjectives, promotion decisions come down to somebody saying that the person works hard.

Writing the steps and applying them consistently are two different problems. Managers differ in how generous they are, so most companies hold a calibration session before any promotion is decided: several managers in one room with the candidates lined up side by side. Let a single manager promote alone and promotions cluster under the generous ones, and a year or two later people at the same step are at visibly different levels of actual capability.

The framework also settles that there is more than one way up. The individual contributor (IC) track climbs through depth of expertise without managing anyone; the manager track climbs by taking on people and organizations. At the same step, both tracks get the same salary range.

Levels are not just written down. They do work in four places.

1. Pay. A pay band attaches to each step — the salary range for that level — and offers and raises happen inside it. Paying outside the band means either raising the level or recording a documented exception.
2. Hiring. The job description states the level, and what the interview loop verifies comes from that step's description. Hire into a level 4 role after asking only level 3 questions and the expectation gap surfaces within six months.
3. Evaluation. Levels give a performance review something to measure against. The review asks not only whether the work went well but whether the person worked the way their current step describes.
4. Growth. When someone writes an individual development plan, the next step's description becomes the list of targets. Pick one line you can't do yet and find a project next quarter that requires practicing it.

How many steps to run is decided by company size. Nine steps at a fifty-person company leaves adjacent descriptions indistinguishable from each other. Three steps at three hundred people packs so much real variation into one step that the salary range stops meaning anything, and the people at the top of a step have nowhere left to go.

"We're reviewing this against level 4. Bring level 5 examples if you like, but they won't count in this round."

Naming the yardstick before the discussion starts.

"The level doesn't support that salary. To go above the band we'd have to put a promotion through at the same time."

Money follows the step, not the other way around.

"The resume says seven years, but against our descriptions this looks closer to level 3."

The step is being judged on the work, not the years.

Grace and Theo wrote Pagedeck's first level table when the engineering team reached eight people. The hard part was the sentence separating level 3 from level 4. The first draft said "develops complex features independently," which put almost everyone at level 4. Only after they rewrote it as "finds and proposes problems without being told what to build, and those proposals change what other people work on" did the two steps actually separate.

In the first review round, one of Theo's two candidates passed. The one who didn't was reliable at finishing what he took on, but Theo was always the one deciding what that would be. Theo handed him a project for the following quarter that starts at the planning stage, so the missing line would have somewhere to be practiced rather than staying an abstract note in a review.

The most common error is reading a level as a restatement of tenure. The older title systems genuinely worked that way, and the job market still talks about which level a given number of years buys. The premise is the reverse: the step comes from the work being done now, so being at the same step after a long stretch can be the system working rather than failing. Missing this, people spend a year arguing that the years are there without ever asking what else the next step requires.

The other error is treating level and title as the same thing. A higher number feels like it should mean running a team, but they're separate axes. A level 5 engineer who manages nobody and a level 4 who leads a team are both normal. Fuse the two and the only way up is a management seat — and since those seats are finite, strong practitioners either get pushed into work they don't want or can't be moved up at all.