When I was a strong senior engineer, I assumed leadership was just... more of what I was already good at. Bigger systems, harder problems, more code. That assumption was wrong in a way that took me a while to fully absorb: leadership isn't a more advanced version of engineering. It's a different job that happens to require you to have been an engineer.
Fifteen years and a few continents later, here's what actually compounded — the skills that quietly paid off over and over, versus the ones I thought would matter and didn't as much.
What I over-invested in early
Being the person with the answer. As an engineer, knowing the most and solving the gnarliest bug made me valuable. As a lead, that same instinct becomes a bottleneck — if every hard decision routes through me, I've capped the team at my own throughput and robbed everyone else of the chance to grow. Learning to not be the answer was harder than any technical skill.
Chasing the newest technology. Staying sharp matters. But I've watched more value destroyed by teams adopting shiny tools for problems they didn't have than by teams being a version behind. Judgement about when not to adopt something turned out to be worth more than knowing every new framework.
What actually compounded
Writing and explaining clearly. This is the most underrated engineering-leadership skill, full stop. The ability to take a tangled technical situation and make it legible — to an executive, a junior engineer, or a sceptical stakeholder — multiplies everything else you do. Half of architecture is just helping people see the same picture. I wish I'd practised it a decade earlier.
Thinking in trade-offs, not answers. Junior engineers look for the right answer. Senior engineers find the least-wrong trade-off given real constraints. Leaders make those trade-offs visible so the team and the business can decide together. Almost every important decision is a trade-off wearing an answer's clothes.
Growing other people. Nothing I've built has outlasted or out-scaled the engineers I helped become better. A platform ages; a person you mentored into a strong architect keeps paying dividends across their whole career and everyone they go on to grow. If I could give my younger self one priority, it would be this.
Connecting work to outcomes. Early on I measured myself by elegance of solution. Now I measure by whether the business is measurably better off. That shift — from "is this good engineering?" to "does this create value?" — is the one that changes how you're trusted with bigger and bigger problems.
The uncomfortable truth about the transition
You have to be willing to get worse at the thing you were best at. Your hands-on edge dulls a little as you spend your time on people, direction, and decisions. That felt like loss until I understood the trade: I gave up being the best individual contributor in the room to make the whole room better. For me, fifteen years in, that's been the right trade every single time.
If you're a strong engineer eyeing the step up, don't think of it as a promotion into more of the same. Think of it as starting a new craft — one where the tools are clarity, judgement, and other people.