Did you do the hard work while someone else got promoted?
Here's why being the best engineer in the room doesn’t matter if the right people don’t know it
Dear Future Leaders,
Have you ever stayed late fixing a critical production issue, only to watch someone else present the solution in the morning meeting?
Maybe you’ve delivered a project weeks ahead of schedule, but when leadership talks about it, they credit the person who “coordinated” rather than the team that built it?
Or maybe you’ve been the one solving problems that other teams couldn’t figure out, but when promotion time comes, leadership says they just don’t know enough about what you’ve accomplished?
Meanwhile, you’ve probably watched engineers who are less technically skilled than you get promoted because they were better at making their work visible.
And let’s be honest:
It’s frustrating.
It feels unfair.
And it’s completely avoidable.
Let me show you what’s actually happening and how to fix it.
How I watched someone else take credit for my work
On a Saturday afternoon, a manager sent an email to the executive team about a critical project a team had been working on.
He wrote something that seemed harmless at first: “I will work with the team to give you an update on the progress.”
But here’s what the executives didn’t know.
I had spent weeks working overnight to solve complex technical problems.
I diagnosed the root cause, coordinated with multiple vendors, tested solutions across dozens of locations, and delivered the fix ahead of schedule.
The executives read that email and saw the manager as the person driving it forward. They had no idea that I had done all the actual technical work to make it happen.
The manager controlled how the story was told.
I did the work. The manager got the credit.
When I realized this wasn’t just about one email
A few days after that happened, a colleague from another team called me. She sounded frustrated.
She’d been hearing feedback from leadership that this same manager “gets things done while other teams don’t.” And because of that perception, a program her team had owned for years was being transferred over to him.
Not because his team was actually more effective. Just because leadership perceived him that way based on how he communicated about his work.
That conversation made something click for me.
I’d been operating under the assumption that if I just kept my head down and delivered great results, eventually the right people would notice and recognize my contributions.
But that’s not how it actually works.
Working hard doesn’t automatically mean getting recognized.
Being competent doesn’t automatically mean being visible.
Delivering results doesn’t automatically mean getting promoted.
Rather, the person who controls the narrative about the work is the person who controls the outcome.
Once I realized that, I knew I had to change how I was communicating about my work.
What I changed about how I communicate
I stopped waiting for my manager to be the only person telling leadership about what I accomplished.
When we delivered something significant, I started sending my own updates to key stakeholders.
I didn’t ask my manager for permission first. I just framed it as keeping people informed since our work might affect their areas.
I also changed the language I used in those updates.
Instead of writing passive sentences like “The project is complete,” I started being more direct: “I delivered this solution two weeks ahead of schedule.”
Instead of vague updates like “We’re working on the issue,” I started writing “I’m coordinating with the other teams to have this resolved by Friday.”
It felt a little uncomfortable at first because I’d been taught that good work speaks for itself. But I kept thinking about that colleague’s program getting transferred away just because someone else was better at talking about their work.
Before a organizational change happened, I also started setting up individual meetings with every major business stakeholder I worked with.
When my manager eventually announced the org changes to leadership, those stakeholders already had a direct relationship with me. They knew what I was delivering because they’d heard it from me, not filtered through someone else’s version.
The shift in how people responded was pretty immediate.
Stakeholders started reaching out to me directly instead of always going through my manager.
Leadership started mentioning my team by name in bigger meetings.
Even my manager started talking about my work differently because he knew other people were already hearing about it.
Why most engineers don’t do this
You might be thinking this all sounds kind of political or self-promotional.
I had the same reaction when I first started thinking about doing it.
But then I kept watching what happened to really talented engineers around me who didn’t make their work visible.
Their managers would get promoted based on work those engineers actually did. Other teams would get credit for solving problems those engineers had solved.
And when it came time for promotions, leadership would say they just didn’t have enough visibility into what those engineers had accomplished.
At the same time, I watched engineers who were honestly less technically skilled keep advancing faster because they were better at making sure the right people knew what they were working on.
Your manager might be great and have the best intentions. But they’re also managing their own visibility and career progression.
Sometimes, without even realizing it, they position themselves as the driving force behind what your team delivers. It’s not malicious. It’s just human nature.
And leadership often can’t tell the difference between who’s coordinating work and who’s actually executing it.
When they see an email from someone saying, “I’m working with the team on this,” they naturally assume that person is the one leading the effort.
Where to start if you want to change this
Think about three people in your organization who should probably know about the work you’re doing but currently only hear about it through your manager.
Then write a short update about something significant you’re working on right now. Keep it to just two paragraphs. Explain what problem you’re solving, how you’re approaching it, and what kind of impact it will have.
Send that update to one of those three people this week.
You don’t need to make it a big formal thing. Just frame it as keeping them in the loop, since your work might touch their area, or they might find it useful to know about.
After you do that once, put 30 minutes on your calendar every week to keep doing it.
The key is making it a consistent habit rather than something you only remember to do when something major ships.
Why timing matters more than you might think
When something important ships that you led or your team built, you realistically have about 24 hours before someone else is going to frame the story about it.
What I started doing was writing down what shipped and what my role was within the first hour. Then I’d send a quick email to the key stakeholders within the first six hours.
The goal was to make sure the people who mattered heard about it from me within that first 24-hour window, before they heard a different version from someone else.
This isn’t about rushing to be the first person talking about every little thing that happens. Instead, it’s specifically about making sure that when something significant happens, the people who need to know about it hear it directly from you.
What I wish someone had told me earlier
Your technical work deserves to be recognized.
You’re putting in the time, solving hard problems, and delivering real value.
But work that nobody knows about stays invisible, no matter how brilliant it is.
I spent years thinking my work would speak for itself. I thought that if I just kept delivering solid results, the right people would eventually notice and I’d get the recognition and promotions I deserved.
What actually happened was that other people ended up speaking for my work. And the version they told wasn’t always the complete story. Sometimes I wasn’t even part of it.
The engineers who get promoted to leadership positions aren’t always the ones with the deepest technical skills. A lot of the time, they’re the ones who figured out how to make sure the right people knew about their skills and contributions.
And that’s not playing politics, but just understanding how organizations and humans actually work.
Your turn
Have you ever done the work while someone else got the credit? What did you do about it?
Tell me your story.
Because learning to make your work visible is what separates engineers who stay stuck from those who advance to leadership.
Remember: The person who controls the narrative controls the outcome.
Don’t let someone else control yours.
Let me show you how to get promoted faster↓
Knowing how to frame what you say to your boss, stakeholders, and business partners is the most underrated skill in tech.
I’ve seen brilliant engineers derail their own careers with messages like:
“I spent 24 hours and sleepless nights on this.”
“Whoever wrote this code made really bad choices.”
“I have no idea who is working this, and I don’t know how to fix it.”
None of these are lies. But all of them burn bridges, signal helplessness, or shift blame - and they follow you.
The good news? This is a learnable skill.
I’m launching a coaching class: How to Frame Your Ask or Information to Your Boss, Stakeholders, and Business.
Bring me your real message, the one you’re about to send, and I’ll show you how to reframe it so the information lands, the relationship holds, and your credibility grows.
First 25 sessions: $49
Regular rate after that
DM me to grab a spot.
#Leadership #EngineeringCareer #Communication #TechCareers #ExecutivePresence
Want more help with promotion strategies, so that it feels comfortable being YOU when you’re preparing?
Great! Start here:
Become a paid subscriber today and get access to benefits like:
(Yearly subscribers only) An immediate 30-minute coaching call to identify your one real message and reframe it so it lands.
Monthly mentorship opportunity where one engaged subscriber get a free 30-minute coaching call
Personal answers to your specific career questions
A simple 5-Step Visibility Cheat Sheet to get you noticed by key decision makers (with templates and tactics)
Your technical skills got you hired. Now, let’s create the strategic visibility that gets you promoted.
P.S. A typical engineering promotion comes with a $10,000 to $30,000 raise. If this subscription accelerates your promotion by even 3 months, that’s easily a 100x ROI.
Until next time,
Ruchi