Nobody drifts into the right career. Yet the most consequential decision in a senior engineer's career — Staff/Principal or Engineering Management — is usually made by drift: a manager leaves, someone has to step up, and five years later you're wondering whose career you're living.
I made this decision twice, in both directions. I went from senior engineer to Engineering Manager on Apple's Identity team, then to Senior EM building a team from zero in India, and later back to being the person who writes the code — as a founder. Neither path was wrong. But the first time I chose, I chose by drift, and I paid for it in a year of feeling slightly off. Here's the framework I wish I'd had.
For two weeks, at the end of each day, write down the one piece of work that left you with more energy than it took. Not the work you were praised for — the work that felt like you.
Patterns show up fast. If it's the afternoon you spent untangling a gnarly design and the code that came out of it, that's data. If it's the 1:1 where someone on your team finally clicked, that's data too. Most people already know the answer; they've just never let themselves count it.
Both tracks are about leverage — doing things whose effect outlasts and outsizes your own hours. The difference is the medium.
Staff leverage runs through systems: the architecture that lets ten teams move independently, the migration that removes a class of incidents, the standard that stops the same argument recurring. Management leverage runs through people: the hire that changes a team's ceiling, the feedback that unlocks someone, the org design that removes a hand-off.
Ask which medium you actually enjoy being accountable for. Not which you can do — you can probably do both — but which you want to be judged on when it goes wrong.
The tracks are not symmetric everywhere. At some companies Staff is a real, respected, well-paid role with a clear ladder. At others it's a title with no scope, and the only path to influence is management. Look at the org chart of the companies you actually want to work at in five years and count: how many Staff+ engineers per hundred? Do they have decision rights, or advisory rights? Are managers of managers former Staff engineers or career managers?
Do not decide in the abstract. Decide for the market you'll be in.
Both doors swing both ways, but not equally. Moving from Staff to management is common and usually welcomed. Moving back from management to IC is possible — I've done it — but it costs you: your technical currency depreciates faster than you'd think, and some organisations read the move as a step down even when it isn't.
That asymmetry argues for a rule: if you're genuinely torn, stay technical longer. You can spend the option later; you can't un-spend it.
Becoming an EM for the title. It looks like progress. It pays more, in some places. And within a year the engineer who loved building things is running a calendar and quietly resenting the people they're supposed to be growing. Their team notices before they do.
Staying IC out of fear. “I'm not a people person” is sometimes true and sometimes a story. If your energy audit keeps pointing at the moments where you helped someone else level up, and you're refusing the management path because it feels risky, that's fear dressed as identity.
You do not need a new title to test a track. For 90 days, borrow the job:
At the end, re-run the energy audit. The answer will be clearer than any amount of thinking about it.
The point isn't to pick perfectly. It's to pick on purpose — because a decided engineer is easier to promote, easier to hire, and much easier to be. If you want a second pair of eyes on your specific fork, that's exactly what a Career Diagnostic is for.
I run this decision with senior engineers in the Career Diagnostic — one session, your specific situation, a written summary and a next step. $149.
