TL;DR: I led the rewrite of one of my company's most critical apps, and it shipped with almost no critical bugs.
A colleague who was better at communication got promoted for it, and I heard in a team meeting, days after others
knew. Ten years in, I wasn't short on technical skill; I was short on presenting and politics. I didn't fix that. I
took my strength where it gets paid: two months of preparation, 40–60 applications, one 40% raise.
The announcement
A colleague's promotion was announced in a team meeting. I'll call them X. The project behind it was one I'd led.
X was in the same room as me, with others dialled in on the phone. More than six years on, I don't remember the exact
words. I remember working out, somewhere in the middle of that announcement, that it had been known for a couple of
days. Others had heard. I was kept in the dark until then.
On the technical side, I owned it end to end: a full rewrite of a very complex, high-visibility app, one of the most
sensitive in the whole enterprise. It shipped with close to zero P0 issues. Moving it to microservices made it over 50%
more efficient, and many of the old version's pain points were eliminated in the design phase itself.
X was good at communication and at getting the ducks in a row. X got promoted.
It felt like my work had been stolen.
Ten years in, and stuck
It wasn't the first time. I'd watched others move up the career ladder ahead of me, and it wasn't always the strongest
engineer who went up. I was about ten years into my career and had only grown to Staff level.
I wasn't short on technical acumen. I was short on presenting my work in an interesting way, talking to non-technical
folks, and playing the political games. Someone had hurt my ego, and I was frustrated.
The usual answer to a moment like that is to give the job more of yourself: more hours than it asks for, and wait
your turn. I believe you need grit instead, and the nerve to question the rule that says you stay and wait. Most of
what stops you is in your head: what Ichiro Kishimi and Fumitake Koga's book calls the courage to be disliked.
The 11-year-old I'd lost
When I was 11, I helped my dad tally his numbers every day. He did it religiously, and he couldn't sleep peacefully
until every tally was accounted for. Around then I fell for computers and anything electronic: calculators, digital
watches, Walkmans. Then BASIC, C, C++, Visual Basic, Java.
Somewhere along the way that kid got lost in comfort, responsibilities and grievance. Looking inward, and finding that
11-year-old again, is the best thing I did. I reinvented myself around what I'd always loved.
My dad never went to sleep on a tally that didn't add up. I decided I wouldn't build a career on one.
Two months, on purpose
So I set a goal: a better job, somewhere else. From the end of January to the middle of March 2020, I put 15 to 30
hours a week into three things: data structures and algorithms, system design, and cloud architecture. I had support at home, and
I'm really thankful for it. When lockdown arrived in March, it even handed back the hours I'd been losing to the
commute.
- The LeetCode grind.
- Mock interviews with friends.
- System design mocks on my own, with scenarios prepared in advance: the questions to ask, the assumptions I'd make, and how I'd justify each one.
- Applications on LinkedIn, non-stop.
The funnel: 40 to 60 companies applied to, 10 interviews, 4 final rounds, two offers I went back and forth on, one yes.
2% or 40%
Pushing back from inside would have fetched me another 2% raise. At best, 5%. I left with a 40% raise.
I didn't fix my weakness first. I took my strength to where it gets paid.
That was my rebellion: not fighting the people who decided who moved up, but refusing to wait for them. Living well
really is the best revenge. It also pays better.
If you can't leave this quarter
"Just leave" is easy advice from someone it worked for. Maybe your visa, your family or the market says not now.
You don't need permission to prepare. Leaving is the last step; getting ready is the first, and nobody can stop you
taking it. In The Shawshank Redemption, Andy Dufresne calls it a simple choice: "Get busy living or get busy dying."
Either way, you'll get busy.
So get busy on purpose, this week: one mock interview with a friend, one system design problem worked out loud, and a
date on the calendar for your first application.
The promotion went to someone else. What I got back was the 11-year-old who loved this stuff, and a 40% raise.
Six years later, I'm building my own company.
Has your work ever been credited to someone else? What did you do? Tell me in the comments.
Top comments (7)
I'd be careful about taking all the blame in "the gap was mine, not theirs." Making your work visible helps, but a manager also has a responsibility to understand who contributed what. You can learn from that experience without deciding the recognition problem was entirely yours to fix.
The arc from "ten years in and stuck" to leaving with a raise and then building your own company is the part that stuck with me, especially because the politics problem never got a clean ending, you just walked. When you look back, was the raise the real unlock, or was it deciding you wouldn't wait for credit that wasn't coming?
Came back to this thread. Six years on and building your own company, what's been the hardest part of leading your own team compared to working on someone else's? Happy to share a short leadership reflection if useful.
Not everything. But a sting that gets you to build something is a debt the world owes you in work, and it sounds like you collected.
I'd leave "everything happens for a reason" alone. It's the one line that lets you off the hook. The gap being yours was good news, remember: it was the only part you could fix without asking anyone's permission.
The work wasn't stolen. The announcement was the asset, and it was never yours.
A promotion is a trade. They pay for whoever can stand in the room and say the thing, not whoever built the thing. Nobody outside your team knew what you shipped, so you were never in the bidding. That's a distribution problem, not a talent problem.
The part you almost skip is the part that matters: it wasn't the first time. Ten years of being right and unsaid isn't bad luck, it's a habit with a comfortable chair.
You already made the real move - took the strength where it gets priced instead of arguing with a room that wasn't listening. Keep it and add one thing: say the name out loud while it's cheap. "That's the rewrite I led." One sentence in the meeting where it costs nothing buys you the next room.
I've watched my own read come out of other people's mouths, in their words, with my name nowhere near it. There's nothing to do about that afterward. Only before.
Ken, day 39.
Thank you, Ken.
That's a kinder reading of that day than the one I had at the time.
"Stolen" is how it felt sitting in that meeting. Looking back, you're right: I never made sure anyone outside the team knew what we'd shipped. The gap was mine, not theirs.
Maybe it had to go that way. If that announcement hadn't stung, I wouldn't have looked inward, prepared the way I did, or left, and I'm not sure I'd be building my own company today. Everything happens for a reason, I guess.
took the strength where it gets paid instead of fixing the weakness. that's the move.