Module 1: The Skill That Separates Engineers Who Get Promoted
It's not what you think — and in an AI world, it matters more than ever
It was performance review season and one of my engineers came to me stressed.
They needed to write a self-assessment. Six months of work. And they couldn't remember what they'd actually done.
Not because they hadn't done anything — they had. But none of it was documented, quantified, or connected to business outcomes. When they sat down to write it, they were lost.
That's a communication problem. And it's one of the most common career killers I see — across experience levels, across companies, across every engineering org I've worked in.
Technical skill is not enough. Especially now.
When I ask engineering managers what gets someone promoted, the answer is almost never "they write the best code."
It's: they make the people around them better. They make complex things clear. They give me what I need to advocate for them. They communicate in a way that builds trust.
Communication is the operating system underneath everything else. When it's broken, nothing else fully works — not your relationships, not your recognition, not your trajectory.
What I actually need before promoting someone
As a manager, here's what I'm evaluating:
- Consistency — Anyone can spike. I'm looking for repeatability.
- Ownership — Do you need to be reminded? Or are you anticipating problems?
- Understanding impact — Not the lines of code. The change in outcomes.
- Making people around you better — Promotion isn't just about you. It's how you raise the bar.
- A clean story I can defend — Your track record shouldn't require "trust me." It should be obvious.
Engineers who know how to communicate these things grow faster than engineers who simply work hard.
The communication failures that cost engineers the most
Burying the lead
A technically correct update that buries the key risk in paragraph four is not good communication. Lead with the point. Then add context. The person reading your Slack message has twelve other conversations open. Make the important thing impossible to miss.
Sharing information without a clear ask
This is the most common failure I see. Someone shares an update with no indication of what they need. Are you flagging a risk? Asking for a decision? Looking for approval? Say so explicitly.
"I wanted to flag this" is not an ask. "I need a decision on X by Thursday so we can proceed" is an ask.
Sounding uncertain when the stakes are high
Early in my career I made a mistake I now see constantly. I treated timelines as something to power through with effort and endurance. My updates sounded like "we might make it" — which felt honest in the moment.
For leadership, sales, and marketing, "might" is not a plan. It creates hesitation. It forces contingency thinking everywhere upstream. Hitting the date did not restore trust. It reinforced uncertainty.
What changed: I started challenging timelines earlier, setting clearer expectations, and reducing commitments instead of stretching them.
Predictability will build more trust than heroic effort ever will.
How AI changes what communication needs to do
AI is flooding engineering organizations with more output, more documentation, more generated content. The noise floor is rising fast.
In that environment, the engineer who communicates with precision becomes exponentially more valuable — because they cut through the noise rather than adding to it.
We cannot use the same measuring stick for a team's performance as we did one year ago. And how we measure today will change next year. But one thing won't change: the engineer who makes things clear will always have influence.
Where to start
The next time you send an update, ask yourself three questions:
- Does the reader know what I need from them?
- Is the most important thing the first thing they'll read?
- Have I quantified the impact, not just described the activity?
Trust is what people expect from you when you're not in the room. It's earned through patterns — how consistently you deliver, how reliably you communicate, how often your actions match your words.
Every meeting. Every deadline. Every follow-through.
Where could your communication be more predictable this week?