The IC career ladder: what each rung actually means
You want to know what is above senior, what each level actually requires, and whether the ladder at your company is real.
Every company publishes a levelling document and most of them are unreadable. Stripped of the language, the IC ladder measures one thing that changes at each rung: the size of the blast radius you are trusted with. Everything else — scope, influence, ambiguity — is a restatement of that.
The rungs, in plain terms
| Level | Trusted with | Evidence people look for |
|---|---|---|
| Senior | A feature or component, end to end | Ships reliably without supervision; other people can build on the result |
| Staff | A system, across team boundaries | Prevented a costly mistake; aligned teams who disagreed; owns a technical direction |
| Principal | A domain, with organisational consequences | Set a direction the company followed; the decision is visible in the architecture years later |
| Distinguished / Fellow | A bet the company is making | Rare, often title-by-reputation; frequently created for a specific person |
The transition people find hardest is senior to staff, and it is not a skill problem. Senior is rewarded for delivering what you were given. Staff is rewarded for identifying what should have been given — which requires visibility into things nobody handed you, and the judgment to be right about them.
Where the ladder stops
Most companies formalise the ladder up to senior and improvise above it. The published document may list staff and principal, but if nobody holds those titles, the levels are aspirational.
Two checks that tell you the truth quickly. Who currently holds the level above you, and what do they actually do? If the answer is "nobody" or "the person who founded the codebase", the rung is decorative. Is there a promotion path that does not require direct reports? If every senior person with real influence also has a team, the IC ladder is a label on the management ladder.
This matters more than the levelling criteria themselves. You cannot be promoted to a level that does not functionally exist, no matter how well you meet its written definition.
Compensation by rung
United States figures for 2026: Staff Engineer median base pay around $244K, ranging roughly $199K–$300K across the middle of the distribution. Principal Engineer averages around $243K base, with total compensation reaching $630K or more at the largest technology employers and past $1M at the very top.
Base pay flattens faster than total compensation. Between staff and principal, most of the increase arrives as equity, which means the number you negotiate matters less than the company you negotiate it at.
The rung the ladder does not have yet
Every level above is defined by scope — more systems, more surface, more of the organisation. That definition assumes the constraint on an individual is capacity, and that scaling past it requires other people.
AI moved that constraint. A senior person who staffs the adjacent functions with AI — design, code, analysis, copy, go-to-market — can carry an outcome that scope-based levelling assumes needs a team.
That is the High-Impact Individual Contributor: a rung defined by leverage rather than by scope. Almost no company has it in a levelling document yet. The work is being done well before the title exists, which is the usual order.
The practical consequence: if you are measuring yourself against a ladder that levels by scope, you may be underrating what you can already do.
Frequently asked questions
- What comes after senior engineer?
- The standard IC ladder continues senior → staff → principal → distinguished or fellow. Staff is trusted with a system across team boundaries; principal with a domain that has organisational consequences; distinguished is rare and often created for a specific person. The hardest transition is senior to staff, because senior is rewarded for delivering what you were given and staff for identifying what should have been given.
- How do I know if my company has a real IC ladder?
- Two checks. First, look at who currently holds the level above you and what they actually do — if nobody holds it, or only the person who founded the codebase does, the rung is decorative. Second, ask whether there is a promotion path that does not require direct reports. If every senior person with real influence also manages a team, the IC ladder is a label on the management ladder rather than a separate track.
- How long does it take to go from senior to staff?
- There is no reliable timeline, because the promotion is not granted for accumulated time. Senior is rewarded for delivering assigned work well; staff is rewarded for identifying work nobody assigned and being right about it. People who make the jump quickly usually do so by finding a problem with organisational consequences that no one owned, rather than by doing more of what earned them senior.
- Is there a level above principal engineer?
- Distinguished engineer and fellow exist at large companies, but they are rare and frequently created for a specific individual rather than filled from a pipeline. More practically, the emerging rung is not higher on the same axis at all: the High-Impact Individual Contributor is defined by leverage rather than by scope — carrying an outcome end to end using AI to cover adjacent functions, rather than being trusted with progressively more surface.