Manager Track

A ten-person company has no use for the word "track." Everyone does the work, everyone knows who is good at what, and the founder sets salaries by feel. Somewhere past forty people that stops holding. Interviews need running, reviews need writing every quarter, and when two teams collide over the same piece of work somebody has to sort it out. None of that fits in the gaps between other tasks — it takes someone's whole week.

The real problem was never who fills that seat. It was that there was nowhere else to go. When the only rung a company can offer is a management seat, that becomes the only way to reward a strong practitioner. So the best engineer on the team gets made the lead.

"Take the team this time. In your current band, that's the only way the salary moves." Six months later that person spends most of the day in meetings, the team has lost the person who used to make its technical calls, and the person themselves is doing work they never wanted while drifting away from work they were good at.

The manager track is the name given to the fix for that dead end. A job level is a grade that describes scope of capability and responsibility, and the fix was to draw two routes up those grades instead of one. One route goes up by taking on people and organizations — this one. The other goes up through depth of expertise without managing anyone, and that is the individual contributor (IC) track. Companies that run both keep the salary bands identical at the same level. If the money differs, people read the second path as decoration no matter what the handbook says.

Moving up this track means the range of people and organization you carry gets wider. It does not mean you personally ship more. The steps are usually drawn as three.

1. Team lead — you carry five to eight practitioners. The number of people one manager carries is called span of control, and it cuts both ways. Below about three, the manager drifts back into the work and starts taking tasks off their own team. Above about twelve, one-on-ones survive as calendar entries and nothing else.
2. Manager of managers — you carry three or four leads. From here you stop working with practitioners directly and work through the leads instead. What you judge changes too: not code or screens, but who sits where and which piece of work goes first.
3. Head of function — you carry a whole organization and its budget. The question shifts from what to build to who goes where and how many people each team runs with.

The way performance gets measured changes at every step. A practitioner's performance review is written against what that person finished during the quarter. A manager can finish nothing with their own hands and still have a strong quarter, because what the team delivered is what they delivered — and if the team delivers nothing, a full calendar doesn't count for anything. When someone on the team goes from needing help to shipping a feature alone in six months, that lands in the manager's column as well.

Where the hours go changes with it. An engineer who becomes a lead typically drops from around thirty hours of coding a week to something like five, and the gap fills with one-on-ones, interviews, cross-team coordination, and writing review documents. Whether that trade is one you want is the actual question behind choosing a track, and it is worth answering before the offer arrives rather than after.

The phrase comes up in four places.

1. Promotion cases — a promotion moves someone to a higher level or role, and the two tracks collect different evidence for it. One side brings a record of hard problems solved; the other brings a record of people grown and a team kept running.
2. One-on-ones — a one-on-one is the recurring private conversation between a manager and a team member, and the track question usually surfaces there first. Good managers ask a year or two ahead of any opening, not after a seat empties.
3. Development plans — an individual development plan (IDP) records where someone wants to go and what is missing today. The chosen track sits on the top line, and the exercises underneath are picked to match it.
4. Job postings — two listings for the same seat read very differently once one of them says manager track. It tells candidates up front that design time will be close to zero.

A track is not a one-way door. Leading a team for two years and then going back to building is common enough, and treating that return as a failure breaks the whole arrangement. Close the way back and people either never move at all, or stay in a seat that doesn't fit and hold a team still with them.

"I'm not interested in the manager track. I want to reach the next level on the one I'm on."

Not a refusal to be promoted — a statement that the route up runs the other way.

"This req is manager track, level 5. Assume close to zero hands-on design time."

Something said in a posting or an interview, warning candidates that the seat is not a practitioner seat.

"Let's write down now that a lead can try it for a year and come back if it doesn't fit."

A proposal to make the track switch reversible before anyone takes it.

At Pagedeck the conversation opened for the first time when engineering reached six people. Grace asked Theo whether he wanted to take the team, and two days later Theo said not now. What Grace did next was not look for another candidate. She wrote the level definitions that let Theo keep climbing as a builder first, because without that table the answer to the same question would come out differently the next time somebody asked it.

The most common misread is that the manager track is the higher track. Managers write reviews, split budgets, and sit in leadership meetings, so of course the seat looks like more authority. But the two tracks are drawn side by side rather than stacked, and at the same level the salary band and the bar for promotion are meant to match. Once people read them as stacked, anyone with no interest in management moves across anyway, and comes back two years later having lost both the team and their own edge.

A second misread is that managing means you no longer need to know the work. Hands-on hours really do shrink, so the conclusion is easy to reach. But a manager on this track has to judge why a date slipped and whether a proposed fix is half a day or two weeks. Without that instinct you end up relaying whatever the team says, word for word, and coordinate nothing in the meetings you exist to coordinate.