Why technical brilliance alone won’t get you promoted
The hidden communication barrier that quietly decides whose work gets seen and whose gets overlooked
Dear Future Leaders,
If you’ve been delivering excellent work and watching less technical engineers get promoted past you, there’s a career obstacle you’re probably underestimating, and it has nothing to do with your code.
You can deliver flawless projects.
You can put in the long hours.
You can solve problems your peers can’t touch.
And you can still watch people with weaker technical skills get promoted past you, year after year, while nobody can quite tell you why.
The hardest part is that the gap doesn’t show up on any performance review.
It shows up in how your work gets remembered, how your emails get read, and whether your name comes up when leadership talks about who’s ready for more.
I spent years stuck at Principal Engineer before I understood what was actually holding me back.
What I want to share is the moment it became impossible to ignore, what I tried that didn’t work, and what finally moved the needle.
The seamless project that changed nothing
I once led a project so well-executed that when it went live, something unusual happened.
The whiteboards were empty. The engineers had nothing to do. Everything worked perfectly.
The visiting tech team that had flown in to support the launch even shortened their two-week trip and went home early. There was nothing left for them to do.
It was the cleanest cutover I’d ever been part of.
At the team celebration dinner that night, I stood up and shared what had gone into making it look that easy. The countless hours. The complex challenges. The technical hurdles we’d worked through.
The response was silence.
No applause. No acknowledgment. The conversation moved on.
I went back to my hotel room that night and cried.
I’d done everything right.
The work was extraordinary.
And it had landed as nothing.
The pattern that kept repeating
I knew something was wrong, but I couldn’t name it.
So I did what most engineers do when they sense a gap they can’t explain.
I tried everything.
I read business books. I found internal mentors. I took on bigger responsibilities, more visibility, and more stretch projects.
Nothing changed.
For the next project, I tried something different. I asked a colleague to help me craft my progress report.
I had the technical points. He had the words that resonated with leadership.
The result was immediate.
The email I sent generated the kind of response I’d been trying to earn for years.
Senior leaders engaged.
Questions came back.
The work I’d done was finally being seen.
For about four weeks, I thought I’d cracked it.
Then I noticed my colleague’s patience wearing thin.
He had his own work to do. He couldn’t be my translator forever, and it wasn’t fair to ask him to be.
I was right back where I’d started, except now I knew the problem wasn’t the work.
The work had been excellent the whole time.
The problem was that I couldn’t get the work across in a language that landed.
The real problem
As engineers from non-English backgrounds, we face a challenge that technical excellence alone cannot overcome.
We think our code speaks for itself. It doesn’t.
We believe our long hours are visible. They aren’t.
We assume our technical brilliance will be recognized once leadership sees the results. It won’t, not on its own, unless we can communicate it in a way that lands with the people making promotion decisions.
That’s the part of the system nobody explained to me when I started my career.
And it’s the part that hits hardest, because it feels deeply unfair.
You can be the strongest engineer in the room and still be invisible if the people deciding your future can’t quickly understand what you’ve done
The turning point
I finally stopped pretending this wasn’t an issue and worked with a coach.
Here’s the message I sent her, almost word for word:
“I know what I want to say but can’t find the right words. I spend hours writing a simple report and still don’t feel confident. I need help with writing clear, concise, next-level reports”
That sentence is hard to write when you’ve spent years pretending the problem doesn’t exist. It felt like admitting failure.
It was actually the first honest move I’d made about my career in a long time.
The investment changed everything, and the changes were smaller than you’d expect.
Here’s an example of one of the early before-and-after rewrites, taken from a real status update I’d sent.
Before:
“Fred is already engaging with the Infra team to understand why AD password resets are time consuming. The team is working on getting the answers you need. More to come.”
After:
“I agree we need to have a plan to reduce the password reset time. Right now, Fred (the vendor’s expert working with us) is working with the Infra team to understand what the root cause is for these delays. I’ll keep tracking the password reset issue and keep you informed.”
The technical content is identical. Everything that changed is in the framing.
The “after” version acknowledges the leader’s concern up front.
It names who Fred actually is, in plain English, instead of assuming the reader knows.
It frames the work as a root cause investigation rather than vague engagement.
And it ends with ownership of the follow-up.
That’s the entire difference between getting overlooked and getting read.
The result:
Three promotions in three years.
The moment I knew the work had paid off was when a leader said to me, almost in passing, that when an email from me hit their inbox, they opened it because they knew they’d learn something from it.
That sentence is the inverse of the silence at the celebration dinner.
The work hadn’t gotten better. But the communication around the work had.
What this means for you
If any of this is hitting close to home, this is one of the easiest career obstacles to actually fix, and one of the most rarely addressed.
Most engineers in this position do what I did for years.
They tell themselves the work will speak for itself. '
They put in more hours, take on harder projects, and deliver cleaner code.
They wait for the recognition that the work seems to deserve.
It doesn’t come.
The promotion goes to the person whose emails are easier to read.
The visibility goes to the person whose status updates land.
The leadership opportunities go to the person whose communication makes senior leaders feel informed, not confused.
This is harder still if English isn’t your first language, because you’re carrying an extra layer of translation between what you mean and what reaches the page.
The work I did with a coach was specifically about closing that gap, and it’s the single highest-leverage thing I’ve ever spent money on for my career.
But the broader lesson applies to everyone.
The engineers who get promoted are the ones whose communication makes their work easy to recognize.
That’s a skill, not a personality trait, and it can be learned.
I’ve written more about how to improve your communication in these posts:
Your turn
Have you ever watched your technical work get lost in translation?
What changed when you started working on the communication itself?
Tell me in the comments.
Remember: your brilliance deserves to be understood.
Don’t let communication be the barrier that holds you back.
Want help becoming easier to move to the next level?
Paid members get practical help with the parts of engineering careers most people are never taught: how to communicate with managers, handle difficult workplace situations, build visibility, and show up as someone ready for more.
As a monthly paid member, you get:
✅ bi-weekly paid posts
✅ direct answers to your career questions
✅ the promotion and communication toolkit
✅ full archive access
As a yearly paid member, you get:
✅ 50% off member pricing on private coaching
✅ one private 30-minute coaching call included (yearly members only)
This membership is for engineers who want practical help with visibility, communication, and promotion.
Private coaching is $49 for paid members and $89 for non-members.
Two classes on offer right now:
Class 1: 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 or say, and I’ll show you how to reframe it so the information lands, the relationship holds, and your credibility grows.
Class 2: Learn how to solve a real pain point at work with AI. Join my class, bring a real problem, and walk out a AI hero on your team.
DM me to grab a spot.
#Leadership #EngineeringCareer #Communication #TechCareers #ExecutivePresence
Until next time,
Ruchi
Ruchi, this is excellent and I saw this firsthand in Sales. I crushed quota but kept getting passed over. So, I started speaking with context, impact, my perspective and tactical execution. Unfortunately, this is how communication needs to be done in order to progress. Even a masterpiece needs a beautiful frame in corporate.
Hi Ruchi,
Thanks for sharing this and keep doing it. You help us a lot, believe it. Indeed, sometimes all wee need is the right communication, and those who are great on technical side but also develop this important skill will stand out.
Cheers!