Why Promotions Feel Political (And What to Do About It)

Promotions feel political because calibration committees make decisions with limited, filtered information — so the engineers who advance are those who make their real contributions visible, not necessarily those who do the most work in isolation.

You have done the work. Shipped features. Fixed critical bugs. Made the team better. But when promotions come around, someone else gets the nod — someone who talked more in meetings or had a project with more "visibility."

It feels unfair because it is unfair. And yet, pretending the game does not exist will not help you win it.

Let us talk about why promotions feel political, and what you can actually do about it.

The Visibility Problem

Here is the uncomfortable truth: promotions are decisions made by humans with limited information.

Your skip-level manager cannot see your daily contributions. The calibration committee has not watched you debug a production incident at 2am. The VP does not know you mentored three junior engineers to success.

They only know what they hear about. And what they hear is filtered through layers of communication, each with its own biases and incentives.

This creates a fundamental gap: the work you do is not the same as the work people perceive you doing.

Consider two engineers with nearly identical output over a quarter. Engineer A ships a refactor that cuts build times by 40% but touches no user-facing feature and is never written up. Engineer B ships a new search filter, posts a brief summary in the #engineering Slack channel, mentions it in the all-hands, and gets two teammates to try it in their own workflows and share feedback. Six months later, the committee knows Engineer B's name. Engineer A is a mystery.

The gap is not talent. It is transmission.

Why "Just Do Good Work" Fails

The engineers who get stuck often believe a comforting myth: if I do great work, someone will notice.

Sometimes they do. More often, they do not.

Your manager is busy with their own problems. Your skip-level has twenty people to track. The promotion committee reviews fifty candidates in an afternoon.

In this environment, visibility is not optional — it is essential. Not because politics matter more than competence, but because competence that no one sees might as well not exist. If a tree falls in a forest and no one writes a brag doc, did it ship?

There is also a subtler trap here: the engineers who do the most invisible work are often the most reliable ones. They handle on-call quietly, clean up tech debt that would have become incidents, answer questions in Slack at all hours. Because they are reliable, no one worries about them — and because no one worries, no one advocates for them either.

The Calibration Process, Exposed

Ever wonder how promotions actually get decided?

In most companies, it works like this:

1. Managers nominate candidates
2. Candidates are discussed in calibration meetings
3. A committee (often including people who do not know you) votes or decides
4. Your manager has to "defend" your case against other candidates

Here is what this means in practice.

Your manager needs ammunition. They cannot defend you with vibes. They need specific examples, documented impact, and ideally, external validation. If your manager walks into the room and says "she is really solid, I trust her judgment" but cannot name a single project with measurable results, your case dissolves against a candidate whose manager arrives with a one-page summary of three initiatives and a quote from a partner team lead.

Perception matters at the room level. If people in the room have heard your name positively — "oh yes, she unblocked our team on that API integration" — you start with social capital. If they have never heard of you, you start at zero and your manager has to spend political capital vouching for a stranger.

The committee has to rank people. Calibration is not an absolute standard — it is a relative one. Your record is weighed against other candidates. This means a mediocre candidate with great storytelling can beat a strong candidate with no story at all.

Understanding this is not cynical. It is realistic.

Playing the Game Without Losing Yourself

So what do you do? You cannot pretend the game does not exist. But you also do not have to become someone you are not.

Here is how to build visibility authentically:

Document Your Impact

If you do not write it down, it did not happen. Keep a running record of:

• What you accomplished (the specific change, feature, or fix)
• The measurable impact (latency reduced, error rate dropped, deploy time saved)
• Who was involved or benefited
• What you learned or what the complexity was

A simple weekly notes file works fine. The goal is raw material you can draw on when your manager asks for examples, when you write a self-review, or when you are asked directly "what have you been working on?"

A good impact entry looks like this:

Q2 — search indexing refactor. Rewrote the product search index pipeline to use incremental updates instead of full reindexes. Cut index time from 4 hours to 22 minutes, which unblocked the catalog team from shipping daily product updates (previously batch-gated weekly). Coordinated with infra to roll out during low-traffic window with no customer impact.

That entry, written fresh after the project, takes five minutes. Reconstructed six months later from memory, it takes thirty minutes and is half as credible.

Communicate Proactively

Do not wait for people to ask what you are working on. Share updates before they are needed.

• Send brief weekly updates to your manager (what shipped, what is blocked, what is coming)
• Share wins in team channels concisely — a two-sentence summary is better than either silence or a wall of text
• Write clear handoff docs and postmortems that show your reasoning, not just your output

The goal is not to be loud. It is to make your work legible to people who would not otherwise see it.

A concrete format that works: "Shipped X. It does Y. Next up is Z. No blockers." That is fifty words and takes thirty seconds to read. Do it weekly.

Build Relationships Beyond Your Team

The people in calibration rooms often work in different parts of the organization. If they have never interacted with you, you are just a name on a spreadsheet.

• Participate in cross-team projects and be a reliable partner, not just an executor
• Attend company-wide meetings and contribute thoughtfully when you have something relevant to say
• Help people outside your immediate team, even on small things — answering a question in a shared Slack channel, reviewing a doc, joining an RFC discussion

When someone in the calibration room says "I have worked with them — they are thorough and easy to collaborate with," it provides third-party validation that your manager alone cannot supply.

Choose Projects Strategically

Not all projects are created equal. Some are invisible grunt work. Others have high visibility with leadership.

This does not mean avoiding important-but-invisible work. It means being intentional about balance. If you only take on invisible work, you will be invisible. And when you do handle invisible-but-critical work, document it explicitly so the value is not lost.

Ask yourself before taking a project: "Who will know about this if I succeed? Who will be impacted? How will I tell that story?"

Let Others Advocate for You

The most powerful visibility is not self-promotion — it is when others talk about you positively. Peer advocacy carries a different kind of weight than self-advocacy because it is costly signal: the advocate is spending their own credibility.

• Make your peers successful and they will speak well of you without being asked
• Build relationships with engineers and PMs in other teams who interact with your work
• Ask for feedback from peers regularly, act on it, and thank them explicitly — people remember being heard

When your manager says "I have heard great things from multiple people, not just me," that is stronger than any self-assessment and harder for the committee to discount.

The Trap to Avoid

There is a version of this advice that goes too far. Engineers who optimize purely for visibility become exhausting. They take credit for others' work. They seek spotlight projects while dumping grunt work on colleagues. They narrate everything they do in Slack whether it is useful or not.

Do not be that person.

The goal is to make your real contributions visible, not to manufacture the appearance of contributions. There is a meaningful difference between self-advocacy and self-promotion — between helping decision-makers understand what you actually did, and performing work for an audience.

Authenticity matters. People can sense when you are performing. Build visibility that is consistent with who you actually are and the work you actually do.

When the Politics Are Actually Broken

Sometimes the problem is not you. Some environments are genuinely toxic:

• Managers who hoard information or take credit for reports' work
• Calibration processes with no transparency or consistent criteria
• Favorites who get promoted regardless of merit
• No clear path to advancement, no documented rubric, no feedback loop

If you have tried everything in this article and nothing moves, the environment might be the problem.

Ask yourself: Are other strong performers getting promoted? Is there a pattern of recognition for good work? Do people receive clear, specific feedback on gaps — not just "not yet ready"? Is the rubric written down anywhere?

If the answer to most of those is no, no amount of strategic visibility will fix a broken system. That is a signal about whether to invest further or redirect your energy elsewhere.

The Mindset Shift

Here is the reframe that helps: visibility is not about gaming the system. It is about helping the system work correctly.

If you do great work that no one sees, the company is worse off. They are not rewarding their best contributors. They are promoting the wrong people for the wrong reasons.

By making your work visible, you are helping the organization make better decisions — not manipulating it. You are giving decision-makers the information they need to do their jobs well. That is a contribution in itself.

Your work deserves to be seen. That is not ego. That is reality.

Related reading

• When Your Manager Isn't Advocating for You — When the political problem is specifically your manager, here is how to respond.
• How to Ask for a Promotion as a Software Engineer — Once you have built visibility, this is how to turn it into a formal conversation.
• Am I Ready for Promotion? A Self-Assessment Guide — Make sure your self-assessment is objective before navigating the politics.

Own Your Career Narrative

Seekersy helps you document your impact consistently, so you are never scrambling to remember what you accomplished. Build the evidence that makes your contributions undeniable.

Start Documenting Your Impact