The Journey from Developer to Senior Engineer: More Than Just Code

Hi reader, my name is Abdiel. I’m a backend developer based somewhere behind your screen, and I’m on a journey I think you can relate to—a journey to becoming a senior engineer. Yeah, engineer, not developer. It makes you wonder what the difference is, right? Or maybe you’re one of those people who actually know the difference. Well, let me tell you.

What Does “Senior Engineer” Mean?

A senior engineer is more than just someone who has spent years writing code. It’s someone who sees the bigger picture. While a junior developer might focus on getting a feature to work, a senior engineer thinks about scalability, maintainability, and long-term implications. They design systems that can grow, adapt, and be maintained easily over time.

Being a senior isn’t just about writing more complex code—it’s about understanding when not to write code. Sometimes the best solution is to simplify, to make the system more flexible and easier to work with for everyone on the team.

Why Am I Pursuing This?

So, why do I want to become a senior engineer? Simply put, I love building things. As a junior, you can build, but what separates a senior from a junior is how they build. A senior looks at the problem from multiple angles, considers edge cases, and collaborates more effectively with product owners, designers, and other developers. They mentor others, share knowledge, and lead by example.

Here’s the difference: A junior builds to get it working, while a senior builds to make it last.

My Motivation

I’ve always been motivated by the joy of problem-solving. But as I’ve grown as a developer, I’ve realized that building a solid, maintainable system that others can easily work with is far more satisfying. Seeing how my code integrates into the larger picture of a project, and how it helps other team members and users, is where the real reward lies.

Becoming a senior engineer is about growth—both personal and professional. It’s not just about writing code, but about writing good code and making decisions that positively impact the entire system and team.

I’m not just on this journey to be a better coder; I’m on this journey to be a better problem-solver, mentor, and leader.

Thanks for coming along with me on this path.