From engineering manager to HI-C

You took the team because it was the only promotion available. The work you were good at is now something other people do while you sit in the meeting about it.

This is the most common route into the role — common enough that the archetype was largely coined to describe it. You are not starting over. You are recovering one capability while keeping several that most individual contributors never develop.

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.

Knowing which problems are worth solving
Years of watching work fail for non-technical reasons. Most ICs pick problems by what is interesting; you pick by what matters, and that judgment is the part AI does not supply.
Organisational literacy
You know how decisions actually get made, who has to be convinced, and which objections are real. A HI-C operating end to end needs this constantly and rarely has it.
Written communication under scrutiny
Management forces you to write things that survive contact with skeptical readers. That is exactly the skill that makes a one-person output legible to an organisation.
Scoping and sequencing
You have spent years breaking work into pieces and ordering them. Doing it for yourself is the same skill with less negotiation.

What is missing

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

  1. 01

    Hands-on fluency, and it decayed faster than you think

    Not the concepts — the muscle memory. Tooling moved, and the gap feels larger than it is because you are comparing yourself against your best day rather than your average one.

    What closes it

    Rebuild by shipping something real and small, not by studying. The fastest route back is a project with a user, even a user of one.

  2. 02

    Comfort with being the one who is wrong

    As a manager, being wrong was expensive and public, so you learned to hedge. Building requires being wrong quickly and often.

    What closes it

    Deliberately work where the feedback loop is short enough that being wrong costs minutes.

  3. 03

    The instinct to delegate

    Your reflex when hitting an adjacent function is to find the person who owns it. The HI-C reflex is to staff it with AI and keep going.

    What closes it

    Notice the reflex. The next three times you would have filed a ticket, do it yourself with AI assistance and compare the elapsed time.

The compensation conversation

The fear is a pay cut, and it is usually misplaced — but for a reason worth being precise about.

At companies with a real IC ladder, engineering manager maps to staff, and senior manager or director to principal. The bands are comparable: Staff Engineer median base pay was roughly $244K in the United States in 2026, and Principal Engineer around $243K, with total compensation reaching well beyond that at the largest employers.

So the negotiation is not about track. It is about level. The failure mode is accepting a downlevel because moving to IC feels like a step back — and downlevelling is very hard to undo.

At companies where the IC ladder stops at senior, the pay cut is real. That is a fact about your employer, and it is usually the signal that the move requires changing companies rather than changing teams.

A 90-day plan

  1. Days 1–30

    Ship one thing end to end, alone

    Small scope, real user, no handoffs. The point is not the output — it is discovering exactly which parts of the loop you can no longer close without help.

  2. Days 31–60

    Staff your weakest adjacent function with AI

    Whatever you reflexively wanted to delegate in month one. Do it yourself with AI covering the craft you lack, and keep the result honest about where it is merely adequate.

  3. Days 61–90

    Make the output legible

    Write up what you built and what it changed, in the register you used as a manager. This is the artifact that makes the case internally, and the one most returning managers skip.

The trap specific to this route

⚠ Managing without the title

The failure specific to this route is drifting back into coordination — becoming the person who unblocks everyone, reviews everything, and mentors constantly, while shipping nothing of your own. It feels productive because it is the shape of work you are good at, and it is rewarded socially. But it produces no artifact, and at review time there is nothing to point at. If most of your week is spent making other people's work possible, you did not change tracks; you changed titles.

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

Is it hard to go from engineering manager back to IC?
The hard part is narrower than people expect. Organisational literacy, judgment about which problems matter, and written communication all transfer intact — and most individual contributors never develop them. What decayed is hands-on fluency and tolerance for being wrong quickly. Both rebuild through shipping something small and real, not through study. The bigger risk is social rather than technical: drifting back into coordination work because it is the shape you are good at.
Will I take a pay cut moving from manager to IC?
At companies with a formalised IC ladder, usually not. Engineering manager typically maps to staff engineer, and senior manager or director to principal, with comparable bands — roughly $244K median base for staff and $243K for principal in the United States in 2026. The negotiation is about level, not track, and the failure mode is accepting a downlevel because the move feels like a step back. At companies whose IC ladder stops at senior, the cut is real, and that usually means the move requires changing employers.
How long does it take to get technical again after managing?
Expect a productive first month and a genuinely useful third. The concepts did not leave; the muscle memory and the tooling did. The gap also feels larger than it is because you are comparing your current output to your best day as an IC rather than your average one. Shipping one small thing end to end, alone, surfaces the real gaps faster than any amount of catching up on reading.

Keep reading