I used to think technical leadership started when somebody gave you a title.
The longer I work in engineering, the less I believe that.
Leadership shows up in small moments
It can look like noticing that a conversation is going in circles and summarising the decision. It can be asking the uncomfortable question everyone else has stepped around. It can be helping another engineer understand the context behind a piece of work rather than simply telling them what to change.
None of those things require authority. They require attention, judgement and a willingness to take some responsibility for how the team works, not just for the code with your name on it.
Ownership is bigger than implementation
For me, ownership increasingly means staying interested in what happens around the code. Does the requirement make sense? Have we thought about failure? Does product understand the trade-off we’re making? Can the next engineer understand why this decision exists?
It also means being prepared to say when you don’t know. Good leadership cannot depend on pretending to have every answer. Some of the strongest people I’ve worked with are comfortable saying “I’m not sure — let’s work it out” and then creating the conditions for the team to do exactly that.
Influence without authority
I’m interested in becoming a technical leader because I enjoy the space between people, product and technology. I like making a complicated problem clearer. I like understanding different perspectives and helping a group move towards a decision.
That is something I can practise now. I can communicate better now. I can mentor, share context, ask stronger questions and take responsibility for outcomes now.
The title can come later. The habits probably need to come first.