Why Your Manager Doesn't Recognize Your Work (And What to Change)

Another review cycle. Your manager's feedback was solid: "reliable," "technically strong," all the things that should translate into something real. And somehow, the person who joined your team eight months after you just got the promotion you've been working toward for two years.

If your manager doesn't recognize your work, you're not alone. The problem is almost never what engineers assume it is.

The belief most engineers carry, that good work speaks for itself, is the thing quietly stalling their career. Not their code quality. Not their delivery rate. The belief.

Why your manager doesn't recognize your work: the real reason

Six in ten managers say they don't know what their direct reports actually want from their careers, according to survey data on manager-employee communication. Most managers aren't withholding recognition strategically. They genuinely don't have the information they'd need to advocate for you.

Your manager has 8 to 15 other engineers on the team. Their own deliverables. Skip-level meetings. Their own performance review coming up. Research on cognitive load in management suggests attention degrades sharply as team size grows beyond 7 or 8 people. The time they spend actively tracking your contributions is a fraction of what you'd imagine.

On Team Blind, engineers describe this as "my manager has no idea what I actually do" or "I do all the work but someone else gets the credit." The resentment is real. So is the underlying dynamic.

What's actually happening (it's a systems problem, not a merit problem)

Here's the piece that's hard to sit with: you're almost certainly overestimating how visible your work is.

Not because you're arrogant. Because of a documented quirk in human cognition.

A 1979 study by Ross and Sicoly found that in collaborative groups (married couples, sports teams, work groups) every participant consistently overestimated their own contribution. When individual estimates were summed, they reliably exceeded 100%. The mechanism: your own intentions, effort, and decisions are far more present in your memory than in anyone else's. Your manager has access to a dramatically smaller slice of your work than you do.

There's a related problem psychologists call the spotlight effect. Gilovich, Medvec, and Savitsky (2000) showed this with students wearing embarrassing T-shirts: participants estimated about 50% of observers would notice. The actual rate was closer to 25%. The engineer who resolved the production incident at 2am assumes the team knows, because it looms large in their own memory. Often, the people making promotion decisions have no idea it happened.

This gets worse for specific categories of work. Julia Evans, who wrote a widely shared piece on engineering brag documents, identified the types of contributions that disappear from view even when genuinely valuable: infrastructure improvements, security work, migration support, mentoring, code quality, the glue work that holds projects together. These don't generate visible artifacts the way feature launches do. If you've been doing this kind of work and wondering why nobody's noticing, the answer isn't that it doesn't matter. It's that it doesn't surface on its own.

The calibration room makes this structural. Promotion decisions at most companies happen in a committee meeting you're not in, where your manager has to make a case using whatever they remember and whatever evidence they've collected. Michael Lynch, a former Google engineer who received "Superb" ratings (roughly the top 5% of employees), was denied promotion after two years of being told he had a great shot. The committee's feedback: they couldn't see the impact he had on Google. Not that he hadn't had impact. That they couldn't see it.

That's the actual problem. Not your output. How legible your output is to the people deciding.

The part you can actually do something about

A lot of what determines whether you get recognized is within your control. Not all of it. Your manager's political capital, the promotion budget, your skip-level's awareness of you: those operate independently. But the gap between what you've actually done and what the right people know you've done? That part you can close.

What actually changes it

Make your work legible

After something significant ships, write it up. Not a brag post: a communication artifact. Two or three sentences in Slack or a message to your manager: what you built, why it mattered, what changed as a result.

Ryan Peterman, a Meta engineer, put it plainly: "If you go and build this amazing feature that nobody knows about, it doesn't matter how good it is, you're not going to get any recognition for it." He describes visibility as "the key last few percent of climbing the career ladder." Frameworks for quantifying your engineering impact help you translate the work you've done into language that lands in calibration.

One pattern from the engineering community: an engineer gave a 10-minute demo of a performance fix at an all-hands meeting. By end of day, the VP of Engineering knew her name. Before that demo, he had no idea she existed, despite months of impactful work. Her output didn't change. What changed was that it became legible to someone with promotion input.

Start a running record of your contributions

You won't remember what you shipped six months ago. Your manager won't either. Julia Evans calls this a brag document: a running list of contributions and impact you update as things happen, not three weeks before review season.

This document has two purposes. It helps you see the actual scope of your own work (most engineers are genuinely surprised when they write it all down). And it gives your manager something concrete when advocating in conversations you're not part of. "They're doing great work" loses to a committee. A specific list of impacts doesn't.

Have the direct conversation

Most engineers have never explicitly told their manager they want to be promoted. It sounds obvious, but it's more common than you'd think. If your manager doesn't know what you want from your career, they can't advocate for it.

The conversation isn't complicated: "I want to understand what promotion would look like for me and what I'm still missing. Can we make time for that?" This opens a different kind of 1:1 than the status updates you've been having. It forces your manager to think about your trajectory, which most managers won't do unless prompted. Specific tactics for making your work visible to the right people covers what to actually do in those conversations.

The earlier in your tenure this dynamic gets established, the better. Setting up your manager relationship in your first week at a new job creates the conditions where this kind of direct conversation feels natural rather than awkward.

Check whether your work aligns to what gets noticed

Not all good work registers equally in promotion discussions. Work that unblocks multiple other engineers, work that addresses a systemic problem, work tied to something your organization's leadership visibly cares about this quarter: this is what calibration committees remember.

Sean Goedecke, a staff engineer, observed that engineers are often frustrated the company doesn't seem to care about their refactoring or infrastructure work, and also frustrated they're not getting promoted. "Those two things are directly related," he noted. Work on what leadership prioritizes. And make sure that work is visible to the people with promotion input. Understanding what "Exceeds Expectations" requires in the calibration room makes it clear which contributions carry weight and which ones are invisible by design.

What people who got promoted did differently

The pattern across Team Blind discussions, Hacker News threads, and engineering career communities: people who got through calibration committees stopped waiting for their work to be noticed and started communicating it.

They wrote things up after shipping. They gave demos. They sent their manager weekly updates. They had the direct conversation about what promotion would require. They asked explicitly what they still hadn't demonstrated at the next level. They also stopped treating visibility as bragging. Making your work visible is not self-promotion, and the engineers who internalized that distinction moved faster.

None of this is comfortable for engineers who built their professional identity around "I just do the work." The belief that good work speaks for itself, real as it feels, is the thing most directly standing between many engineers and getting recognized for what they've actually done.

The system has real problems. But there are moves within it that change outcomes, and they don't require becoming someone who's constantly selling themselves.

---

Build the case your manager needs

CareerClimb tracks your wins and builds your promotion case automatically, so when calibration happens, your manager has the evidence they need to fight for you. Download CareerClimb