Returning to individual contributor work after eight years in management

Six months ago I stepped down from an engineering director role -- eight years in management, the last four running a 40-person org -- to go back to individual contributor work as a staff engineer. I want to write about what actually surprised me, because most of what I read before making this decision either romanticized "getting back to the code" or treated it as an obvious step down, and neither framing matched my actual experience.

The first surprise: how much slower I was, technically, than I expected to be. Eight years is a long time. Tooling changed, patterns I once knew cold had shifted, and for the first two months I was genuinely the slowest person on my team at things I used to consider basic. That was humbling in a way management never was -- as a director, you're rarely in a position where your literal output is directly, visibly comparable to a 26-year-old's, in real time, in the same pull request queue.

The second surprise, and the more important one: how much of my management experience turned out to be directly useful as an IC, in ways I hadn't anticipated. I am dramatically better at scoping my own work realistically than I was pre-management, because I spent eight years watching other people over- and under-scope things and learning to spot the patterns. I'm better at writing a design doc that anticipates the objections other teams will raise, because I spent years sitting in the rooms where those objections get raised. None of that made me faster at writing code, but it made the code I did write land better, the first time, with less rework.

The thing that's been hardest, honestly, isn't technical at all -- it's the identity adjustment. I spent eight years being the person people came to for decisions. Now I'm one senior voice among several, and sometimes my strong opinion loses. That took real, deliberate work to get comfortable with, more than the rusty Kubernetes knowledge did.

I don't think this path is right for everyone, and I don't think it should be framed as more virtuous than staying in management. But if you're considering it: budget for the technical rust being real and temporary, and don't undersell how much of what you learned running an org will still be doing quiet, useful work once you're back in the code.