When I started my career, I believed technical skills were everything.

So I learned languages, frameworks, algorithms, and system design.

That foundation was necessary, but over time I realized growth is more about becoming a more impactful engineer.

Legend: 🟦 Technical 🟩 Communication 🟪 Strategic Thinking 🟨 Visibility 🟥 Self-Advocacy

Note: This is my own perspective, not a scientific model.

Technical Skills

Strong technical fundamentals are the base. They build credibility and make it easier to solve real problems.

I still learn new tools and sharpen engineering judgment, but technical skill alone stops being the main driver of impact.

Communication

Great ideas fail when they aren’t communicated clearly.

This is not just public speaking; it is writing docs, explaining trade-offs, mentoring, and aligning the team.

As influence grows, communication becomes one of the most valuable engineering skills.

Strategic Thinking

Solving hard problems matters less than solving the right problem.

Strategic thinking means understanding why something is being built, whether it solves a real problem, and what the long-term trade-offs are.

The best engineers optimize outcomes, not just code.

Visibility

Visibility is not self-promotion.

It means making your work useful beyond your team through docs, design reviews, demos, and knowledge sharing.

If people can’t see your work, it has less impact.

Self-Advocacy

Working hard is not enough.

Ask for opportunities, negotiate fairly, and choose projects intentionally.

You are the owner of your career.

The Biggest Lesson

The exact percentages don’t matter.

Technical skill is the foundation.

Communication, strategy, visibility, and advocacy are the multipliers that increase impact.

Final Thoughts

If I’m honest, I wish someone had told me earlier that being smart wasn’t enough. I spent years just focusing on getting better at coding, assuming that was the only thing that mattered.

The turning point came when I realized my best ideas didn’t matter if I couldn’t explain them well. Or if nobody even knew I had them. Or if I was too afraid to ask for what I deserved.

That shift changed everything. Not because I stopped caring about being a good engineer, but because I finally understood that engineering skills are just the starting point.

The real growth? That comes when you learn to think about the work differently. When you can see the bigger picture. When you actually push back on ideas instead of just executing them. When you make sure people know what you’ve built.

This post isn’t meant to be some universal rule. It’s just what I’ve learned about myself over ten years. Your own journey might look completely different, and that’s fine.

But if you’re reading this and you’re early in your career and everyone’s telling you to just code more, code better, code faster — maybe pause and think about the bigger picture. Because that stuff matters too.