My Unexpected Journey From Developer to Team Lead

I never had a grand plan for my career in tech. Nobody sat me down and asked where I saw myself in five or ten years, or helped me map out the different paths available to me. I mostly figured things out as I went along.

I started my career when Windows Forms was still a massive industry, and I stayed in that space for years. If I imagined my future at all, I suppose I pictured myself doing backend development for the rest of my life. Leadership was not something I was working towards. I was focused on becoming better at the technical work in front of me and finding my own way through an industry I was still learning to navigate.

It also did not help that I had a very narrow picture of what a leader looked like. Leaders were confident, outspoken people who always seemed to know what to say. They could walk into a room, take control of a conversation and make decisions while everyone watched. I was deeply introverted and much more comfortable behind a keyboard. Social events made me sweaty and nauseous. Nothing about that made me look at myself and think, “Yes, obvious leadership material.”

And yet, people had already started coming to me for guidance.

I remember a junior developer who was still exploring where they belonged in tech. They were trying to decide whether they should focus on backend development, frontend development or try to do both. They came to me wanting an answer, but I could not make that decision for them. It was their life and their career. All I could do was help them explore it.

We decided that they would try tasks in both backend and frontend development so that they could experience the work rather than choose based on what somebody else told them. From there, they could decide what suited them. Even then, I reminded them that the decision would not be permanent. There is no rule saying you cannot pivot later when you learn more about yourself.

At the time, I did not recognise that conversation as leadership. I was simply helping somebody think through a decision without taking ownership of it away from them. Looking back, that was already the kind of leader I would eventually become.

The possibility became real during a one-to-one with my manager. We were talking about something I can no longer remember when they said they could see me becoming a team lead. I had already started wondering whether leadership might be something I could do, but I was still caught somewhere between maybe I should and maybe I absolutely should not.

Hearing somebody else say it changed something. The idea was no longer living only in the uncertain part of my own mind. Somebody whose judgement I respected could see it too. For the first time, becoming a team lead felt possible.

There was no dramatic transformation after that conversation. I did not wake up the following morning filled with confidence and an unexpected love of meetings. I gradually began doing more of the work before I had the title. I supported people, answered questions and helped where I could. When a leadership position eventually opened at the company, I raised my hand.

Then came my first one-to-ones as a leader, and with them the immediate realisation that I had no idea what I was doing.

People asked me questions I did not know how to answer. They expected guidance about situations I had never handled before. I had spent years becoming comfortable with technical problems, where I could investigate the code, reproduce the issue and work towards a solution. People were not quite as considerate as software. They did not arrive with useful logs.

All I could do was remain calm and be honest. I told people when I did not have the answer, promised that I would find out and got back to them as quickly as I could. I learned that pretending to know everything would not make me a better leader. Being reliable after admitting that I did not know mattered far more.

The hardest adjustment was not simply learning how to run meetings or have difficult conversations. It was accepting that my value was no longer measured only by the code I personally produced. I had spent years building an identity around being a developer. Now, some of my most meaningful work happened through somebody else.

One of the clearest examples was an unpaid intern I mentored. Our work together was not only about teaching code. I watched their confidence develop alongside their technical ability, and eventually they became a paid employee. Seeing them thrive and continue growing was incredible.

Their achievement belonged to them. They did the learning, took the opportunities and built their own career. But knowing that I had helped create some of the conditions in which they could grow made the loss of hands-on coding feel different. I was no longer only building software. I was helping people see more possibility in themselves.

That did not mean leadership suddenly became natural or easy. I still had to learn how to navigate difficult conversations, support different personalities and make decisions when I would have preferred more time to think. There were plenty of mistakes because I never took a course or had somebody guiding me through every new situation. Much of what I learned came from trying, getting something wrong, reflecting on it and trying again.

What did become clearer was that I did not need to turn myself into the kind of leader I had always imagined.

I did not need to become the loudest person in the room. I did not need to manufacture confidence or have an immediate answer to every question. The things that drew people to me before I had the title were still useful after I received it. I listened. I stayed calm. I took people seriously, and I tried to guide them without deciding their lives for them.

Leadership did not suddenly begin when the title appeared beside my name. It had already been happening in quieter moments that I had not known to count.

We often recognise leadership only when it looks like authority. We picture the person directing the room, making the announcement or taking charge in a visible way. That image leaves many people assuming they are not suited to leadership because they do not fit the mould.

I do not fit that mould at all.

For a long time, I thought that meant leadership was not for me. Now I understand that it only meant I would lead differently. The qualities that made me doubt myself were not proof that I could not lead. In many cases, they shaped the way people learned they could trust me.

If you have never thought of yourself as leadership material, do not sell yourself short. Look at the moments people already come to you for perspective, reassurance or honest guidance. Look at the ways you help somebody find their own answer instead of making the decision for them.

Leadership may not arrive as a carefully planned destination. Sometimes you slowly grow into it while believing you are simply helping the person in front of you.