Career paths for senior engineers beyond management

A friend at Shopify got offered an EM role last year. She spent two weeks agonizing over it — not because she wanted it, but because turning it down felt like admitting she was stuck. She turned it down. A year later she's a staff engineer owning the platform migration, she's paid more than the EM job offered, and she's happier.

The "up or out" trap in engineering is mostly fake, but it still catches people. If you're a senior engineer wondering if management is your only way forward, it isn't. The IC track past senior is real. It's also more interesting than most people think.

What the IC ladder actually looks like

Most tech companies have something like: Senior → Staff → Senior Staff → Principal → Distinguished → Fellow. The titles vary. The pattern is consistent.

At Senior, you own features or services. At Staff, you own systems or problem areas that cross teams. At Principal, you're shaping the technical direction of an org. At Distinguished/Fellow, you're shaping the company.

Each step isn't "more coding." It's a different job. The code you write at Staff is often less than at Senior. The impact you create is much higher.

The four Staff archetypes

Will Larson and Tanya Reilly wrote the books on this, and their framing still holds up. Staff engineers tend to fall into one of four patterns:

The Tech Lead — attached to a team, drives their technical direction, partners with the EM. Closest to what Senior looked like. Good for people who love shipping.

The Architect — owns technical direction for a specific area across multiple teams. Less hands-on coding, more systems design and decisions.

The Solver — parachutes into hard problems. Reliability incidents. Failing migrations. Ambiguous new spaces. Great for generalists who get bored on one team.

The Right Hand — works as the technical arm of a VP or CTO. Strategy, cross-cutting initiatives, technical judgment on business decisions.

If you're considering going past senior, figure out which of these you'd actually want. "Staff engineer" as a generic title tells you nothing about day-to-day.

What changes past senior

The biggest shift: your job stops being "write code" and starts being "ensure the right code gets written."

This means:

• More writing. Design docs, RFCs, technical strategy memos.
• More meetings, but higher-stakes ones. You're in the room where decisions happen.
• More mentoring. Not because HR wants you to, but because scaling yourself through other engineers is how you multiply your output.
• More ambiguity. Nobody hands you tickets. You find the problems worth working on.

People who hate this: ones who got into engineering because they wanted to code and be left alone. That's fine. You can stay Senior and be excellent. Senior is not a failure.

People who thrive here: ones who notice organizational dysfunction, care about systems thinking, and like explaining things.

Alternatives to the ladder

Not every IC path runs through Staff-at-a-big-company. Some real alternatives:

Independent consulting. Experienced engineers charging $250-500/hour for a few months at a time. Kent Beck, Martin Fowler, Camille Fournier — and a lot of less-famous people making great livings this way. Requires a network and a specialty.

Developer tools / DevRel. If you can write and speak, companies like Vercel, Supabase, and Stripe pay senior engineers serious money to be the bridge between product and community.

Technical founder. You already know this one. Most engineers shouldn't do it, but some should. The skills that make you good at Staff (ambiguity, systems thinking, decision-making under uncertainty) map to founding.

Specialized IC at a smaller company. Sometimes the best move past senior at FAANG is becoming the VP of Engineering at a Series B without the title. You do Staff-level work, you have more ownership, and the equity might matter.

Research / applied AI roles. If you have the chops, Anthropic, DeepMind, and the major labs pay IC researchers well past any EM salary you'd be offered elsewhere.

Why management gets pushed on you

A tangent worth including: if you're getting pushed toward management when you don't want it, understand why.

Most companies have more ICs than EMs, but the management pipeline is harder to fill than the IC one. So when someone shows EM-adjacent skills — mentoring, communication, strategic thinking — the org tries to convert them. This is not always in your interest.

The cost of going into management and finding out you hate it is high. You lose 1-2 years of IC skill growth. Going back is possible but awkward. The cost of declining an EM offer is basically zero — you just keep doing what you were doing.

If you're not sure, decline and see how you feel in six months. The offer will come back if you're the right candidate.

What to work on if you want to go past senior

Concrete things that move you:

• Write an RFC that changes how your org does something.
• Lead a project that crosses 3+ teams.
• Mentor a junior or mid-level engineer through a promotion.
• Own an incident post-mortem that results in a systemic fix.
• Become the person people ask about a specific domain.

None of these require a title change. They're what the title change recognizes later.

The takeaway

Management is one path past senior. It's not the only one, and for a lot of engineers it's the wrong one. The IC track is real, well-paid, and suits the people who actually like engineering.

If you're at the crossroads, don't pick based on what the ladder looks like at your current company. Pick based on what you want to spend your days doing. If that's writing design docs and mentoring, management might fit. If it's solving hard technical problems and shaping systems, stay IC and push for Staff. Both paths pay. Only one of them will let you do what you actually enjoy.