Too Good to Move: How Competence Becomes a Career Cage

Here's a scenario that's probably more familiar than it should be. Someone joins a company, figures out a gnarly process faster than anyone expected, and starts delivering results that make their manager look like a genius. Six months in, they're the go-to person for everything related to that function. A year in, they're training new hires, writing the documentation, and fielding Slack messages at 9pm because, well, they're the only one who really gets it.

Two years in, they're still in the same role. Their title hasn't changed. Their salary has nudged up a bit. And every time they raise their hand for a new opportunity, someone in a meeting somewhere says, "We just can't afford to move them right now."

Welcome to the competence penalty.

The Trap Nobody Talks About in the Offer Letter

When people talk about career growth blockers, the usual suspects get trotted out — bad managers, office politics, lack of visibility, not knowing the right people. All real. All worth discussing. But there's a subtler mechanism at work in plenty of companies that doesn't get nearly enough airtime: the act of becoming indispensable to a broken or under-resourced process.

Organizations — especially ones that have grown fast or haven't invested properly in documentation and knowledge transfer — develop what you might call single points of human failure. One person who knows how the legacy billing system actually works. One person who has the relationships with the three key vendors. One person who can navigate the labyrinthine internal approval process without losing their mind.

Those people are valuable. Companies know it. And so, consciously or not, those people don't go anywhere.

The brutal irony is that the more you solve problems, the more problems get routed to you. Competence attracts load. And load, over time, becomes a cage.

Why Organizations Do This (Even When They Know Better)

It's tempting to frame this as malicious — a cynical management strategy to extract maximum value from high performers while dangling the carrot of future opportunity. Sometimes that's exactly what it is. But more often, it's structural stupidity rather than calculated exploitation.

Here's what actually happens at most companies: there's no formal succession planning below the VP level. Knowledge transfer is treated as something that happens organically, not something that gets resourced or prioritized. When a high performer raises their hand for a new role, the conversation in leadership goes something like, "They're great, but who replaces them?" — and since nobody has an answer, the promotion gets deferred.

That deferral becomes permanent.

In tech, this plays out constantly with senior individual contributors who have become the load-bearing walls of a particular system or codebase. They understand the architecture at a level nobody else does. Moving them to a new team or a new challenge feels like an operational risk. So they stay put, watching newer hires with less institutional knowledge get tapped for growth opportunities because those people are, paradoxically, more movable.

In corporate environments, it tends to happen to the person who is genuinely great at execution — the operator who keeps the machine running while everyone around them gets elevated into strategy roles. They're too useful where they are to be "risked" somewhere new.

The Employee's Side of the Math

Here's what makes this particularly corrosive: high performers often don't realize it's happening until they're already stuck. The early signals feel like success. More responsibility. More visibility. Being the person people come to. That all feels good, especially early in a career.

The realization usually lands somewhere between year two and year three, when the pattern becomes undeniable. Peers who were less capable have been promoted. New opportunities got filled internally — just not by them. The feedback in reviews is glowing, but the trajectory isn't moving.

At that point, a lot of people do the logical thing: they leave. They take their institutional knowledge, their process expertise, and their reliability to a competitor or a new company where they haven't yet been typecast. The company that trapped them then has to scramble to replace them, usually with two people, and spends the next year wondering why everything in that function is falling apart.

The irony is almost poetic. The indispensability that kept someone stuck becomes the catastrophe that proves they should have been developed and promoted all along.

The Specific Flavor of This in Tech

Software and tech companies like to believe they're meritocracies, but the competence penalty hits hard in these environments for a specific reason: technical debt and organizational debt accumulate fast, and the people who learn to navigate that debt become load-bearing in ways that are genuinely hard to replace.

A senior engineer who knows why a particular service was architected the way it was in 2019, and what breaks if you touch it, is not easily substituted. Neither is the product manager who has the muscle memory of how to get things through a particular company's prioritization process. That knowledge has real value — but it's value that accrues to the company, not necessarily to the person holding it.

The engineers who move fast and break things (to borrow a phrase that's aged poorly) often advance more quickly than the ones who maintain the things that got broken. Maintenance and operational excellence are structurally undervalued in most tech cultures, and the people who are great at them get rewarded with more of the same work.

What Actually Fixes This

For individuals caught in the trap, the most effective moves tend to be uncomfortable. Deliberately documenting and transferring knowledge — even when nobody asked you to — removes the "we can't move them" argument. Proactively identifying and developing a backup for your own role is a career move as much as it is a team contribution. And being explicit about growth timelines in conversations with managers, rather than assuming performance will speak for itself, matters more than most people want to admit.

For organizations, the fix requires treating succession planning as an operational necessity at every level, not just at the top. If someone is genuinely indispensable to a process, that's a process problem, not a reason to keep them in place. Building in forced knowledge distribution — rotations, documentation sprints, structured cross-training — is the kind of thing that sounds like overhead until the person who knows everything quits on a Friday afternoon.

The companies that actually get this right tend to have a specific belief baked into their culture: that developing someone beyond their current role is always worth the short-term disruption. That's not a universal belief. Not even close.

The Bottom Line

Being good at your job is supposed to be the point. It's supposed to create options, open doors, build a reputation that carries you somewhere interesting. And for a lot of people, it does exactly that.

But for a meaningful slice of the workforce — particularly the reliable, the thorough, and the quietly excellent — competence becomes the thing that holds them in place while the less reliable, more movable people get the opportunities. That's not just a personal frustration. It's a genuine organizational dysfunction that costs companies their best people at the worst possible moments.

The cage is real. And most of the time, the company built it by accident.