Coding Skills Alone Won't Get You Promoted

Passed Over Twice

I was passed over for senior promotion twice in a row. First time: "not yet." Second time: "your skills are good, but your impact is lacking." I was honestly upset. My code quality was among the top on the team, and I did the most code reviews. I didn't understand why I wasn't getting promoted.

I spent 3 months working in a state of resentment. Watching a colleague who I thought was worse at coding get promoted before me, I concluded "it's all politics."

(Looking back, that colleague wasn't playing politics — I was the one who was missing something.)

Promotion Isn't a Reward for "Good Code"

I realized this after an honest 1:1 with my team lead. "Your coding skills are already at the senior level, but you lack influence," he said. Influence? My code is literally affecting the service right now.

He explained. A senior doesn't just write good code individually — they raise the code quality of the entire team. They set technical direction, help junior developers grow, and collaborate across teams to solve organizational problems.

I'd been quietly writing great code by myself. My PRs were polished, but I'd contributed almost nothing to the team's overall productivity.

What I Changed

One: I started doing knowledge sharing. I proposed a weekly 30-minute team tech session. Only 3 people showed up at first, but after 3 months, it was 8. I covered practical topics — advanced TypeScript patterns, performance optimization techniques, debugging tips.

Two: I invested in documentation. Our team had no onboarding docs, so every new hire asked the same questions repeatedly. I created an onboarding guide, and the average ramp-up time dropped from 3 weeks to 11 days. That was impact I could show in numbers.

Three: I created touchpoints with other teams. I set up regular API spec meetings with the backend team and led component system discussions with the design team. My role shifted from "frontend developer" to "cross-team tech hub."

Third Time's the Charm

Six months later, I passed the promotion review. What changed wasn't my coding ability. I'd expanded the scope of my influence with the same skills. My team lead's feedback: "your technical leadership is visible now."

Promotion Shouldn't Be the Goal

This is a bit ironic, but when I stopped obsessing over promotion and focused on contributing to the team, the promotion naturally followed. The things I did for the team — not for the promotion — are what led to it.

But realistically, every company has different criteria. Some promote purely on technical skill, others look at organizational contribution. My experience doesn't apply everywhere.

If I made one mistake, it was sulking for 3 months after being passed over. If I'd actively sought feedback right away, I might have gotten promoted 6 months sooner.

In the end, coding skill is a necessary condition, not a sufficient one. It took me a while to accept that.