From Backend Engineer to Technical Leader

The hardest part of moving from senior IC to technical leader wasn't delegation. It was learning that my job had changed from shipping code to shipping clarity.

The shift

For eight years, my value was measured by what I could build. PRs merged, incidents resolved, systems designed. The feedback loop was tight. You shipped, it worked, dopamine.

The moment I started leading, the loop broke. The work I was doing on Monday might pay off in a month, if at all. If I measured my day by PRs, every day felt like a loss.

What I learned to value instead

• A clear decision written down. A one-page ADR that unblocks three engineers is worth more than a week of my own commits.
• A teammate growing. If the person I paired with on Tuesday ships the next version without me on Friday, that's my PR.
• A team that can say "no" well. Pushback with reasoning is a sign the team has agency. Silence is a warning.

What I got wrong

I tried to keep coding at the same rate. It didn't work. My code got worse — context-switched, rushed, done at 10pm. It also crowded out the work only I could do.

The lesson: if you're the only one who can do it, you should be doing it. If two other people on the team could do it, you probably shouldn't.

What I'd tell year-four me

• The title will come. The people skills, if you skip them, won't.
• Write more. Ship more docs than code for one quarter and see what happens.
• Start delegating things you're bad at before things you're good at. The good ones are easier to let go of when the team has already earned trust on the hard ones.