I remember the exact afternoon my career turned. Not a promotion announcement, not a title change on a badge. It was the day I opened a laptop to fix a bug myself, out of habit, and stopped halfway through the fix because I realized the fix wasn't mine to make anymore. Someone on my team needed to make it. My job was to make sure they had what they needed to do it, then get out of the way.
I closed the laptop. I sat there for a minute feeling like I'd lost something, though I couldn't name it right away. It took months before I found the word for it: identity. The work had been mine for so long, I'd stopped seeing where the work ended and I began.
Nobody Tells You What The Job Costs
I came up through the US Army before I ever wrote a line of code for a living. The Army teaches you leadership early and hard: you are responsible for your people, full stop, and their failures are your failures. I carried this lesson into engineering and figured it would translate cleanly into management. It did not, not at first.
What surprised me wasn't the new responsibility. I expected it. What surprised me was the grief. I spent years building a reputation as someone who dug into a hard problem and came out the other side with a working answer. This identity was mine. When I stepped into leadership, I had to hand pieces of it to other people, on purpose, every single day, and watch them get it wrong sometimes in ways I would have avoided.
Nobody warned me the job would feel like giving something away before I had anything solid to hold instead.
Being Good At The Work Is Not The Same Skill
Here's the part which stings if you're an engineer reading this. Being excellent at the technical work is often the exact reason you get promoted into a role where this skill matters least. Companies hand people leadership titles because they were the best builder on the team, then act surprised when the best builder struggles to lead the people who build.
Leading is a different discipline entirely. It's reading a room instead of reading a stack trace. It's asking a question and sitting in the silence after it instead of jumping in with the answer you already know. It's caring more about whether your engineer grows from a mistake than whether the mistake gets fixed in the next ten minutes.
I had to unlearn my favorite move: swooping in to solve the thing myself because I was faster at it. Every time I did this, I was fast at the task and slow at building the team. Those are different races, and only one of them matters once you're leading people.
The First Time I Got It Wrong
Early on, an engineer on my team came to me stuck on a deployment issue. Old habit kicked in. I pulled up the config myself, found the problem in about four minutes, fixed it, and pushed it live. I felt useful. I felt fast.
Then I noticed the look on her face. Not gratitude. Something closer to embarrassment, or resentment. I'd taken the problem from her hands without asking, solved it in front of her, and walked away having taught her nothing except her manager didn't trust her to finish the job.
I went back later and apologized, a sentence I never expected to write about a config fix. I told her next time I'd sit with her while she worked through it, ask questions, and let her own the fix even if it took three times as long. She said this was all she'd wanted in the first place.
This one conversation cost me an afternoon of speed and bought me a team member who trusted me for the next four years. Cheap trade, in hindsight. I did not see it this way at the time, because everything in my training up to this point rewarded me for being the fastest person in the room, not the person who built the fastest room.
What Finally Helped
Three things changed the transition from painful to workable for me.
First, I stopped measuring my day by what I personally produced. A good day as a leader looks like three other people solving problems, not me solving one. It's a hard shift for anyone who built their self-worth on personal output.
Second, I started asking my people what "good support" looked like to them instead of assuming I already knew. Some wanted me close, checking in daily. Some wanted me nowhere near their work until they asked. Treating everyone the way I wanted to be led was a mistake I made more than once before I learned better.
Third, I leaned back on the Army lesson I'd shelved: take care of your people first, and the mission takes care of itself. In tech this means protecting your team's time, fighting for their growth, and telling them the truth even when it's uncomfortable. Bad leadership isn't rare. My own research found 99.5% of people I surveyed have worked for at least one bad boss in their career. I did not want to become another data point in this number.
Fourth, I gave myself permission to be bad at leading for a while. I'd spent years earning the right to call myself a strong engineer. I hadn't earned anything as a leader yet, and pretending otherwise only slowed the learning down. Once I let myself be a beginner again, in public, in front of my own team, the whole thing got easier.
Where I Landed
I still miss the work sometimes. There's a particular satisfaction in closing a hard ticket which leadership never quite replaces. What replaced it instead was watching someone on my team solve a problem I would have struggled with, using a method I never would have thought of, because I got out of their way and let them own it.
This is the trade. You give up being the best builder in the room so you build a room full of people who are better than you at the thing you used to do alone.
If You're Standing At Your Own Fork
If you're an engineer weighing whether to take the leadership path, here's my honest answer: it's a different job, not a better one. Don't take it because it pays more or because it's the "next step" everyone expects. Take it if you'd rather spend your energy growing people than growing code.
And if you've already made the turn and it feels like a loss right now, it is one. Name it. Then go find out what you get to build instead.
Where did your career make its left turn, and did anyone warn you before you took it?