Imagine being trusted to redesign your company's flagship product, but not trusted to have an honest conversation about your career.
Sounds absurd?
Well, welcome to another episode of Professional Antipatterns.
A great opportunity
Picture this.
A company has a successful legacy flagship product. It has been around for years, but the time has come to modernize it.
Not just a small refactoring effort.
We're talking about building a modern, SaaS-ready version of the product. A complex greenfield project involving a multinational engineering team.
Management approaches an experienced engineer with an exciting opportunity.
They want this person to:
- Lead the technical direction of the entire project.
- Act as the lead architect.
- Make the important architectural and technical decisions.
- Coordinate and technically lead engineers across multiple countries.
- Take responsibility for turning a complex legacy product into a modern platform.
That's a pretty significant assignment.
It requires technical expertise, leadership, accountability, and the ability to make decisions that could influence the company's future for years.
Naturally, the engineer is interested.
But there's one small detail.
The promotion question
The engineer has been waiting for a promised promotion for years.
So, with this enormous new responsibility on the table, the engineer asks a perfectly reasonable question:
Could we finally discuss that promotion?
After all, if the company trusts someone to lead one of its most important engineering initiatives, perhaps their formal position should reflect that responsibility.
A reasonable discussion might follow.
Maybe the promotion is possible. Maybe there's a budget constraint. Maybe there are formal requirements that still need to be met.
There are plenty of legitimate answers.
But management takes a different approach.
They get angry.
The question is interpreted as blackmail.
As if asking about a long-promised promotion while discussing a major expansion of responsibilities were somehow an attempt to hold the company hostage.
And just like that, the conversation is over.
No constructive discussion. No clear expectations. No agreement on a path forward.
Apparently, the engineer crossed a line.
By asking about their own career.
The interesting interpretation of trust
What fascinates me about this situation is the contradiction.
Management's position essentially becomes:
We trust you to:
- Redesign our most important product.
- Lead an international engineering team.
- Make decisions involving significant technical and business risks.
- Take ownership of a complex, long-term initiative.
But we don't trust you to:
- Ask whether your position should reflect those responsibilities.
That's a rather selective definition of trust.
You're qualified to make architectural decisions affecting the company's future, but asking about your own future is apparently a dangerous escalation.
One might even argue that the promotion conversation is considerably less risky than the architecture of an entire SaaS platform.
But what do I know? I'm just an engineer.
Why this is a professional antipattern
The problem isn't that every request for promotion must be approved.
Of course not.
Companies have budgets, organizational structures, promotion processes, and legitimate business constraints.
The problem is turning a reasonable professional discussion into an accusation.
When someone is asked to take on substantially greater responsibilities, discussing recognition, authority, compensation, and career progression isn't blackmail.
It's part of defining the role.
And there's a deeper problem here.
When management reacts emotionally to a legitimate question, it teaches employees something important:
You can discuss what the company needs from you, but discussing what you need from the company might be dangerous.
That's not a particularly healthy foundation for engineering leadership.
Especially when the company expects engineers to show initiative, take ownership, and communicate openly.
What a healthy conversation would look like
Even if the promotion wasn't possible immediately, management could have responded with something like:
"We recognize that this project involves responsibilities beyond your current role. Let's discuss what that means for your position and what we can commit to."
Or even:
"We can't promise a promotion right now, but we can define the expectations, timeline, and criteria together."
Neither response requires the company to give anything away immediately.
Both demonstrate basic professional respect.
And more importantly, both keep the conversation open.
Instead, treating the question as a personal attack creates a situation where the engineer learns that discussing career development is somehow incompatible with being a team player.
That's a strange lesson to teach someone you're asking to lead a team.
The real cost
There's an irony in all this.
The company wants someone to take ownership.
To think strategically.
To make difficult decisions.
To challenge assumptions.
To communicate openly.
Yet when that same person initiates a difficult but perfectly legitimate conversation, the response is anger and dismissal.
It's hard to build a culture of ownership when ownership only works in one direction.
And it's even harder to retain experienced engineers when additional responsibility becomes an expectation while career progression remains an indefinitely postponed conversation.
The punchline
In the end, perhaps the most amusing part is the contrast.
The company wanted a completely modernized flagship product.
A fresh architecture.
A modern SaaS platform.
A greenfield engineering initiative.
But apparently, the management processes were still running on the legacy system.
And that was the one system nobody was allowed to modernize.
This is part of my Professional Antipatterns series, where I write about strange, counterproductive, and occasionally absurd things I've encountered in software engineering — without naming the companies or people involved.
Original article: https://blog.lezli01.is-a.dev/blog/professional-antipatterns-promotion-silent-treatment/
Have you ever been asked to take on the responsibilities of a higher position while being told that discussing the actual promotion was inappropriate?
I'd love to hear your stories.
