There is a version of career growth that sounds very clean from the outside.

• You do good work.
• Someone notices.
• You get the next opportunity.
• You keep growing.

For a long time, I think I believed some version of this.

Not because I was naive. But because many of us are taught that good work speaks for itself. Especially in engineering, we are trained to respect competence. If the system works, if the release goes out, if the team can rely on you, that should be enough.

But over time, I learned that good work does not always explain your ambition.

• It may prove that you are reliable.
• It may prove that you are strong in your current role.
• It may even make people trust you more.

But it does not automatically tell people where you want to go next. That part has to be made visible.

The first shift

I started as a lead frontend engineer.

I liked the craft. I liked building things. I liked understanding how product ideas became real through code, systems, reviews, tradeoffs, and all the small details that make software usable.

But I also knew I wanted to grow beyond frontend engineering. Not because frontend was small. It is not. But because I was curious about the larger system.

I wanted to understand what happened before the code reached me and after the code left me. I wanted to understand infrastructure, delivery, team dynamics, business pressure, stakeholder expectations, and eventually people management.

At some point, I had to say that out loud. That was the first real shift for me.

I spoke with my manager about my ambition. I did not have a perfect plan. I did not have every skill yet. But I knew I wanted to take on broader responsibility, and I wanted to be useful in areas where the team needed help.

That conversation changed something. Before that, growth felt like something that might happen if I kept doing good work. After that, growth became a partnership. It was no longer just: “Here is my work, please evaluate me.” It became: “Here is where I want to grow. Where can I help in a way that also helps the team?”

That difference matters.

Growth is easier when it is useful to others

The most helpful career advice often sounds simple, but it is not easy to practice.

• Do your current job well.
• Ask where help is needed.
• Take on the work.
• Deliver.
• Use the trust from that delivery to expand your scope.

I did not have a name for this when I was doing it, but looking back, this was the loop I kept repeating.

I was already trusted as a frontend engineer. Then I stepped into DevOps responsibilities. That was not just a random skill expansion. It helped the team, and it helped me understand a different part of the engineering system.

Then, over time, that broader understanding helped me move into management.

I did not become a manager because I suddenly stopped caring about engineering. I became a manager because I had started caring about the conditions under which engineering work succeeds.

The code matters. But so does the team. So does clarity. So does trust. So does knowing when someone is blocked but not saying it loudly. So does creating enough structure for people to do their best work without feeling controlled by the structure.

Management, at least for me, became another form of system design.

In the next part, I will talk about starting again from zero, either at the current company but a new role, or a new company & a new role altogether and how this magic career loop still works.