frontend
Changing Jobs Mid-Career: Why I Took the Leap
Thoughts from the intersection of code, craft, people, and progress.
It’s not about escape—it’s about growth.
Changing jobs later in a career carries more context, more responsibility and fewer illusions that every new role will be perfect. I made the move because the opportunity to grow outweighed the comfort of staying somewhere I already knew how to navigate.
The useful question behind “Changing Jobs Mid-Career: Why I Took the Leap” is what changes in the work afterwards. A sound idea should improve a real decision, not only give us a neat phrase for describing it.
What makes this interesting is not the fashionable part. It is the effect on the person doing the work after the initial excitement has worn off.
Make the work easier to do well
The leadership part is rarely the grand speech. It is the ordinary environment around the work: whether people can ask an awkward question, whether priorities stay still long enough to act on them, and whether useful effort is noticed.
My practical test is simple: after a conversation, does the other person have more clarity and more agency? Good leadership should not make the leader look essential. It should help the team make sound decisions without waiting for permission at every turn.
Leadership is not having every answer. It is making better answers possible.
Trust is built in small, repeatable moments. Say what matters, make space for challenge, and follow through when somebody takes the risk of being honest.
The details will change from project to project. The underlying habit of paying attention travels well.