From senior IC to HI-C

You are good at the work and it is no longer the constraint. The ceiling you are hitting is not skill — it is that nobody hands you problems big enough to matter.

This is the largest group and the one with the least defined path. You already have the thing that cannot be shortcut. What is missing is not craft; it is the permission, scope and reach that turn craft into outcomes — and none of that arrives by being better at your current job.

Where this leads

A senior professional with no direct reports who takes a project from hypothesis to measurable outcome alone, using AI to cover the adjacent functions that previously required a team. Read the full definition →

What transfers

You are not starting over. These are assets you already hold, and several of them are scarce among people who never left this track.

Depth in one discipline
The non-negotiable prerequisite. Adequacy in adjacent functions only works when anchored by real depth somewhere — otherwise there is no judgment to evaluate what AI produces.
Working taste
You already recognise when something is wrong before you can articulate why. That is the dimension AI does not supply and the reason the role stays senior.
Delivery reliability
You ship. The credibility that buys you a larger mandate is already earned; it is usually just not being spent.

What is missing

Stated plainly, because a transition plan built on flattery does not survive contact with the work.

  1. 01

    You are given slices, not outcomes

    Your scope is defined by someone else, and success is measured as completing what you were assigned. Nothing about doing that better changes it.

    What closes it

    Take an unowned problem with visible business consequences and close it without being asked. That is the transition, and it is not a promotion you request.

  2. 02

    Adjacent functions still route through other people

    You file tickets for design, wait on data, and hand off go-to-market. Each handoff is a queue you do not control.

    What closes it

    Pick the function that blocks you most often and cover it yourself with AI at merely-acceptable quality. Adequate and immediate beats excellent and queued.

  3. 03

    No distribution of your own

    Your reach is granted by your title. If you changed employers tomorrow, your audience would be zero — which is also why your influence caps at whatever the org chart allows.

    What closes it

    Build one channel that survives changing employer: writing, a maintained project, a community presence. This is the slowest of the gaps to close and the most durable once closed.

  4. 04

    Judgment tested only inside a defined spec

    You make excellent calls when the problem is framed. Framing the problem is a different skill, and it is the one staff-level promotions actually test.

    What closes it

    Practise deciding what should be built, not only how — and write the reasoning down so it can be checked against outcomes later.

The compensation conversation

This transition usually pays through level rather than through a title change, because most companies have no HI-C band to put you in.

The practical path runs through the existing ladder: senior to staff to principal, with Staff Engineer median base around $244K and Principal around $243K in the United States in 2026, and total compensation considerably higher at the largest employers.

The leverage you build is what makes the case for the level. Be careful of the inverse trap: doing HI-C work at senior pay for years because the output is impressive and nobody had to relevel you to get it.

A 90-day plan

  1. Days 1–30

    Find the unowned problem

    Something with visible business consequence that no team has claimed. It usually sits in the gap between two teams, which is exactly why nobody owns it.

  2. Days 31–60

    Close it without handoffs

    Cover the adjacent functions yourself with AI rather than queueing them. Note the elapsed time versus what the handoff path would have cost — that number is your argument.

  3. Days 61–90

    Publish the reasoning, not just the result

    Write what you decided and why, where people outside your team can read it. This starts the distribution you do not have and doubles as the promotion artifact.

The trap specific to this route

⚠ Waiting to be given the scope

The trap here is treating the transition as a promotion to request rather than a way of working to adopt. Staff-level scope is almost never granted in advance — it is recognised after someone demonstrates it. If you are waiting for a larger mandate before operating end to end, you will wait indefinitely, because the mandate is the reward for having already done it once without permission.

Where do you actually stand?

A one-page self-assessment: score yourself 1–5 on each of the five dimensions, read the lower- and higher-end anchors, and see where your largest gap is — because that gap is your next move. It cites the framework by DOI, so every claim in it is verifiable.

No spam. Published under CC BY 4.0 — yours to keep and share.

Frequently asked questions

How do I become a staff engineer without managing?
Staff level is recognised after the fact rather than granted in advance. Senior is rewarded for delivering assigned work well; staff is rewarded for identifying work nobody assigned and being right about it. The practical move is to find an unowned problem with visible business consequences — usually in the gap between two teams — and close it end to end without being asked, covering adjacent functions yourself rather than queueing handoffs.
What is the difference between a staff engineer and a HI-C?
A staff engineer owns a system across team boundaries but still depends on other functions to ship — design, data, go-to-market. A HI-C owns the entire outcome, staffing those adjacent functions with AI instead of handing off. Staff is a level on a scope-based ladder; HI-C is defined by leverage. In practice many staff engineers are already partway there and are levelled by a system that does not measure what they actually do.
Do I need my own audience to be a HI-C?
It is one of the five dimensions, and the slowest to build. Own distribution means being able to reach an audience or a decision-maker without organisational permission — through writing, a maintained project, or a community presence. It matters because reach granted by title disappears when you change employers, and because influence otherwise caps at whatever the org chart allows. You can operate as a HI-C without it, but your ceiling stays organisational.

Keep reading