How to get more VISIBILITY as a software engineer, according to people who study promotions

No credentials drama, I am a mid level engineer who got passed over twice, got annoyed, and went researching how promotions actually work instead of complaining in retros. What follows is part literature, part scar tissue. It is long because the problem is real.

The core finding that reframed everything for me: engineering has a "glue work" problem, named by Tanya Reilly in her famous talk. The vital invisible work (unblocking people, fixing the docs, keeping the project coherent) is career poison when nobody sees it, and career fuel when they do. Visibility is not vanity. It is making the invisible 40 percent of your job legible to the people scoring it.

The principles:

1) Write more than you code, slightly. Every promotion committee artifact is text. Design docs, postmortems, decision records. Engineers who write clearly get described as "strategic" in calibration meetings, the highest compliment the genre has. One good design doc circulates further than a quarter of silent commits.

2) Demo small, demo often. Waiting for the big reveal is the classic introvert trap. A 4 minute Friday demo of an unfinished thing beats a polished demo nobody scheduled. Frequency builds the "always shipping" reputation, and mere exposure research says familiarity itself breeds positive evaluation.

3) Send the monthly three bullet email. To your manager: what shipped, what moved, what is at risk, numbers attached. Managers assemble promo cases from whatever is lying around their memory. Stock their memory deliberately.

4) Answer questions in public channels. Same answer you would have DMed, posted where 200 people see it. Six months of this and you are "the person who knows things". The work is identical, only the surface area changed.

5) Volunteer for the cross team thing nobody wants. Cross team exposure is how skip levels learn you exist, and skip levels are who the room listens to.

Quick hits by category:

Career mechanics:

• keep a brag doc, weekly, with metrics
• read your company's actual promotion rubric, most engineers never have

Communication:

• practice saying what your project does in 2 sentences without the word "basically"
• this is where I did actual reps btw. I fixed the talking about work part on my commute with BeFreed, an audio app where the goal I set was literally "communicate like a staff engineer". It assessed me, then queued daily 15 minute lessons built from engineering leadership books and executive interviews, the Will Larson genre but sequenced so it compounds. Before my last review cycle I used its live practice mode to run my promo pitch out loud and got coached on delivery, which is exactly the rep no engineer gets at work. The phrase "make the invisible work legible" came from one of those lessons. It is doing for my soft skills what leetcode never did

Boundaries (the anti burnout section):

• visibility work caps at ~3 hours a week or it becomes your job
• decline glue work that has no audience, kindly, unless it is genuinely critical

Philosophical:

• the engineers we call lucky are usually just legible
• your manager is not withholding the promotion, they are losing a debate you did not arm them for

Visibility is not self promotion. It is debugging the information flow between your work and the people who decide what it was worth.

P.S. yes this all feels gross for about 6 weeks. The feeling fades around the time the calibration meeting says your name without you in the room.

What visibility move actually worked for you, and which one backfired? Collecting data, always.