The Career Path I Didn’t Take

One thought comes to my mind often as a software engineer:

Did I make the right career decision?

🎧 Prefer to listen? You can hear this article as a podcast episode on Spotify: Listen to The Career Path I Didn’t Take

Not in a dramatic way. It is not like I wake up every morning regretting my life choices.

But sometimes, when I look back, I wonder whether I should have taken a different path.

For a long time, I wanted to stay on the technical path.

Software Developer.

Senior Software Developer.

Architect.

That kind of direction.

I liked the idea of becoming better technically, solving harder problems, designing systems, understanding architecture, and becoming someone who could make good technical decisions.

The team lead or people leadership path never felt like the obvious one for me.

At least, that is what I told myself.

But when I look back, there were signs.

Leadership qualities would sometimes come up in performance reviews and conversations with managers.

At the same time, I was quite upfront in my one-on-ones. I would say that I did not want to go down the manager or team lead path. I wanted to stay technical and eventually move towards something like architecture.

And at the time, I genuinely believed that was the right direction for me.

But maybe that was not the full story.

Maybe part of me also avoided the people side because it looked messy.

Code is complicated, but people are another level.

Code gives errors.

People give silence, politics, pressure, emotions, mixed expectations, and unclear feedback.

A broken build is easier to understand than a broken team.

So I stayed closer to the technical path.

And to be fair, there is nothing wrong with that.

Software engineering needs strong technical people. Not everyone has to become a manager or team lead. The industry sometimes makes leadership feel like the natural “next level,” but that is not always true.

It is a different path, not automatically a better one.

Still, I sometimes wonder.

Was I choosing the technical path because it was genuinely what I wanted?

Or was I avoiding leadership because I did not feel ready?

That is the part that stays in my head.

Because when people around you keep noticing something, maybe it is worth paying attention to.

Sometimes other people see qualities in you before you fully accept them yourself.

Maybe I had some leadership ability.

Maybe I was already doing parts of the role without the title.

Helping others.

Taking ownership.

Thinking beyond my own ticket.

Trying to understand the team, not just the code.

Caring about how the work was done, not just whether it was done.

But because I had already decided that I was a technical person, I may have ignored those signals.

I think many engineers experience something similar.

We create an identity for ourselves quite early.

“I am a backend developer.”

“I am not a people person.”

“I am not management material.”

“I just want to code.”

“I want to become an architect.”

Sometimes those things are true.

But sometimes they become walls.

And once we build those walls, we stop testing other possibilities.

The funny thing is that good technical leadership is not always about becoming a manager.

Sometimes leadership is already happening quietly.

In code reviews.

In design discussions.

In helping junior engineers.

In calming down messy situations.

In asking the question nobody else wants to ask.

In saying, “This solution works, but will it hurt us later?”

Maybe leadership starts before the title.

Maybe I was closer to it than I realised.

I do not think choosing the technical path was a mistake.

I still enjoy the technical side of software engineering. I still like building systems, solving problems, and thinking about how different parts of a system should work together.

But I also think I could have been more open.

Maybe I did not need to choose one identity so strongly.

Maybe I could have explored leadership without completely leaving the technical path.

Maybe I could have said yes once, just to see what I would learn.

That is the lesson I take from it now.

Career decisions are not always about choosing the perfect path. Sometimes they are about not closing doors too early.

And it leaves me wondering how many other engineers have made a similar decision.

Have you ever rejected a career path because it genuinely was not right for you?

Or did you reject it because you did not feel ready for it yet?

Maybe the more useful question is not always:

“Which career path should I choose?”

Maybe it is:

“Am I choosing this path because I truly want it, or because the other path makes me uncomfortable?”

Because sometimes the path you avoid is not wrong for you.

It is just the one you were not ready to see yet.