The Loyalty Discount

That story, laid out in detail on r/ExperiencedDevs this week, pulled in dozens of replies from people describing the exact same shape at their own companies. Not a bad-apple manager, not a budget crunch. A senior engineer, doing 0-to-1 work leadership openly called critical, getting paid less every year relative to what the market would pay a stranger to do his job. The thread’s most common answer to “why does this happen” wasn’t cruelty. It was inertia: nobody wanted to open the door to “everyone renegotiating at once.”

Sit with that reasoning for a second, because it’s not stupid, it’s just aimed at the wrong risk. The fear is that if you fix one person’s comp outside the normal cycle, you create a queue. The actual risk already happening is that your best people are running their own market analysis every time a recruiter messages them, and they don’t need your permission to act on what they find.

The Number Everyone Already Knows

Here’s what makes this pattern so avoidable: the market rate isn’t a secret. It’s on levels.fyi. It’s in every recruiter DM your senior engineers already ignore, until the day they don’t. Your company will pay that number, in full, without a second thought, to a stranger who’s never shipped a line of your code, understands none of your incidents, and needs six months of ramp before they’re half as useful as the person already sitting in the seat. The same company will not pay that number to the person already producing at that level, because the process for paying a new hire and the process for paying an incumbent run through entirely different machinery, one built to win a negotiation, the other built to avoid one.

Put yourself in the seat making that call. You’re not choosing between “give this raise” and “hold the line on fairness.” You’re choosing between a known, bounded cost today and an unbounded, invisible cost that shows up as a resignation letter in a quarter you didn’t pick. The incumbent’s comp negotiation is the only one you get to see coming. Every other one arrives as a two-weeks notice.

Naming the Reflex

Call it the loyalty discount: the gap that opens, year over year, between what a company will pay someone new to do a job and what it will pay the person already doing it well. It isn’t designed. Nobody sets out to underpay their best people. It’s the byproduct of two systems that were never built to talk to each other, an external hiring band that moves with the market because it has to, in order to close candidates, and an internal comp ladder that moves on an annual cycle because that’s administratively simpler. The market band is reactive and current. The internal ladder is scheduled and stale. Every year those two lines drift further apart, and the person absorbing the drift is the one who stayed.

The discount compounds quietly because the incumbent doesn’t feel it as a single bad decision. They feel it as a slow erosion, an in-line raise here, a “we’ll revisit next cycle” there, each one individually defensible, until eighteen months later the gap is wide enough that a recruiter’s opening offer beats their current total comp without even negotiating. By the time leadership notices, the conversation isn’t “should we close this gap,” it’s a counteroffer scramble against a signed competing offer, the worst possible position to be negotiating from and, not coincidentally, the version of this conversation companies are far more willing to have.

The Math That Never Gets Run

Run the actual replacement cost against the “we can’t set a precedent” fear and the precedent fear loses badly. A senior engineer two years into 0-to-1 ownership carries context no job description captures: which three past decisions this new feature can’t repeat, which stakeholder actually needs to sign off versus who just likes being asked, which parts of the system will break in ways the runbook doesn’t mention. None of that transfers with a hiring bonus. Replacing him means a search, a ramp measured in months not weeks, and a real chance the first thing he built gets rebuilt worse by whoever inherits it half-understood.

Weigh that against the actual size of most retention gaps, which are rarely as large as the fear makes them feel. Closing a comp gap on your most load-bearing senior engineer is one of the highest-return budget lines available to a technical leader, and it’s routinely the one that gets deferred to “next cycle” because it doesn’t have its own line item. It competes with headcount plans and tooling spend for the same pool of attention, and it loses precisely because the cost of not acting is invisible until the day it isn’t.

The fix isn’t a blanket policy, more bands, more automatic escalators, more rules designed to make the decision so nobody has to make it. It’s the opposite: someone with the standing and the technical context to look at a specific engineer’s specific value and make a specific call, on a timeline that doesn’t wait for the annual cycle. That’s a judgment call, not a policy, and it’s exactly the kind of call that’s hard to make well from inside an HR system built to treat every case the same.

That’s the gap fractional technical leadership sits in well. Someone advising engineering strategy from outside the org chart isn’t protecting a budget line or defending last year’s banding decision. They’re positioned to say, plainly, this specific person is worth more than the policy says, and here’s the replacement math that proves it, before the resignation letter makes the argument moot.

If you’re watching a senior engineer’s comp drift below what you’d pay to replace them and the process keeps deferring the fix to next cycle, that’s not a policy problem waiting for patience. It’s a decision waiting for someone willing to make it now.