Individual Contributor Track

For a long time there was exactly one way up: become a manager. Put in the years, do the work well, get a team; do that well, get a bigger one. No other justification for a raise existed, so the only thing a company could offer a strong performer was more people to look after.

The outcome was usually the same. The best engineer on the team becomes the manager, and a year later spends the whole day in meetings and reviews with almost no time in the code. The company has traded an excellent practitioner for an average manager. The person is doing work they never wanted and has drifted away from work they were great at. When they resign and say they want to go back to building, there is no seat to offer them, because offering one would mean cutting their pay.

The individual contributor (IC) track is the second road built at that dead end. Write a path into the framework where level and pay go up without taking on reports, and someone who wants to keep building no longer has to leave to do it. The name says what it is: a route for people who deliver results with their own hands rather than through an organization.

Two tracks run side by side, and the mechanism that makes the arrangement real is paying the same range at the same level on both. Job levels — the grades a company assigns by capability and scope of responsibility — form the vertical axis, and the two branches are drawn on top of it. A common shape is a single column up to level 5, splitting into management and craft above that, since below that point the work looks much the same either way.

The second mechanism is what changes as you climb. The management branch moves up with the number of people and the results of the organization; this one moves up with the size of the problem. Level descriptions read roughly like this.

1. Finishes an assigned piece of work alone. Someone else decides what the work is.
2. Decides what the work is. Breaks the problem down, sequences it, and clears the blockers without being asked.
3. Solves problems that span several teams. Finds the issues no single team can fix and pulls the right people together.
4. Owns judgment calls that shape company direction. This person's decisions set the technical choices for years.

A senior individual contributor has influence but not authority. Other engineers lean on their judgment, but they don't write anyone's performance review or set anyone's salary. Everything has to move by persuasion rather than instruction. Without a manager's leverage, the case has to be better made — a design someone at level 6 wants adopted across four teams gets adopted because the reasoning held up in review, not because a reporting line required it.

Promotion runs through the same machinery: collect two or three quarters of examples matching the next level's description, then have a panel of managers review them together. The shape of the evidence differs, though. The management branch writes about how a team was built; this one writes about which unsolved problem got solved, and on what judgment.

The most frequent place is a growth conversation. In a quarterly one-on-one — the recurring private conversation between a manager and a team member — the two of them confirm which direction the person is heading, and the answer gets written into an individual development plan. For anyone approaching the level where the tracks split, that question doesn't get left blank.

It shows up in job postings and offers too. Keeping both tracks open when hiring senior people means not losing candidates whose condition is that they want to keep building. A posting that describes only the management route filters those candidates out before they apply, and the team never learns which applications it missed.

It also serves as the way back for someone who managed for a while and wants to return to building. When the pay ranges match at every level, that move counts as internal mobility rather than a demotion. When they don't match, the framework can describe two roads and people will still only see one.

"I want to stay on the IC track. Taking a team isn't right for me at this point."

Turning down a management offer while making clear it isn't a decision to stop growing.

"We need to open a level 6 IC seat or we can't land that candidate."

There's no box that pays what the candidate wants without giving them a manager title.

"This isn't a call for the manager to make — it should come from the IC side."

The question is a technical judgment, not an organizational one, so a different person decides.

Pagedeck built its first level framework at 45 people, and this branch is the piece Grace spent the longest on. An engineer who had been there since the founding had turned down a team twice, and each refusal left them in the same slot, because nothing justified a raise.

Once both tracks were written into the framework with matched pay ranges, and every level from 3 up carried a description on each side, Theo moved up without ever taking reports. Today Theo owns the hardest technical problems at Pagedeck and other engineers lean on those calls, but writes no one's review and sets no one's salary.

The most common misreading is that it's where people go when they can't be managers. Management was the traditional promotion, so everything else looks like the fallback. But the two tracks sit beside each other rather than above and below, and companies that build it properly nail that down by matching the pay ranges level for level. Once it reads as second best, people who want to keep building move into management seats they don't want, and the reason the track was created disappears.

The other common misreading is that it's a solo path. The word individual invites that. Individual here means not managing an organization, not working alone — and in practice the higher the level, the more the work spans teams, and the more time goes into convincing and coordinating. Anyone who picked this road hoping for quiet solo work tends to find, somewhere around level 5, that the job is nothing like what they expected.