The Remote Work Salary Adjustment That Makes No Mathematical Sense

When I moved from Chicago to a small town in Wisconsin in 2021, my employer offered me a choice: keep my Chicago salary and come into the office twice a week, or take a 15% pay cut and go fully remote. The cut was presented as obvious, even generous — cost of living in this Wisconsin town was roughly 30% lower than Chicago, so really, they explained, I'd be coming out ahead after taxes and housing costs. The math checked out. I took the cut. But here's what's been bothering me for five years now: if the salary adjustment was about cost of living, why does it only work in one direction?

Last month, a friend who works for the same company moved from Austin to Brooklyn. Her salary stayed exactly the same. No adjustment upward to account for the fact that a one-bedroom apartment in her new neighborhood costs $1,200 more per month than her old place. No conversation about how her grocery bill just increased by 40%. Nothing. The cost-of-living calculator that justified my pay cut apparently doesn't run in reverse. And when I started asking around, this turned out to be the standard practice across dozens of companies with remote-first policies. Salaries get adjusted down when you move somewhere cheaper. They almost never get adjusted up when you move somewhere more expensive. If you think about this for more than thirty seconds, the internal logic collapses entirely.

The usual explanation goes like this: your salary is tied to your value to the company, which is (theoretically) independent of where you live. But when you move to a lower cost-of-living area, the company is doing you a favor by letting you keep most of that value, because you don't need as much money to maintain the same lifestyle. It's a correction, not a punishment. Except this falls apart the moment someone moves the other direction, because suddenly value-to-the-company is the only thing that matters again. The cost of living is your problem now. The asymmetry is so glaring that I'm surprised it doesn't generate its own gravity well.

Let's put actual numbers on it, because I built SalaryHog specifically to avoid the hand-wavy "you'll come out ahead" promises that HR departments love. Say you're making $95,000 in San Francisco. You move to Nashville. Your company cuts your salary to $76,000 — a 20% reduction that they say mirrors the cost-of-living difference. Run those numbers through a take-home calculator and you'll find that after federal taxes, FICA, and state income tax (California vs. Tennessee), your take-home drops from about $67,400 to about $58,900. That's a $8,500 hit. Meanwhile, if your rent dropped from $3,200 to $1,800 a month, you're saving $16,800 annually. So yes, you do come out ahead. By about $8,300 a year, assuming everything else stays constant, which it won't, but let's pretend.

Now reverse it. You're making $76,000 in Nashville. You move to San Francisco for personal reasons — partner's job, family, doesn't matter. Your employer says sorry, we pay based on role, not location. Your salary stays at $76,000. Your take-home actually increases slightly to about $57,200 because Tennessee has no state income tax and California does, wait no, I have that backwards — California's income tax is going to eat another chunk, so your take-home drops to roughly $55,100. And your rent just jumped from $1,800 to $3,200. You're now $16,800 deeper in the hole annually on housing alone, and your take-home is $3,800 less than it was. The company's position, implicitly, is that this is entirely your problem. You chose to move. We pay for the work, not the ZIP code.

But that's also what they said when they cut your salary for moving to Nashville. We pay for the work. The work is location-independent. Except they reduced your pay based on location. Both of these things cannot be true simultaneously.

The Revealed Preference

Here's what the asymmetry actually reveals: salary adjustments for remote work are not about fairness, and they're not about cost of living as a neutral geographic fact. They're about leverage. When you move somewhere cheaper, the company has leverage — you've already decided to move, you want the remote arrangement, and they can credibly argue that you're not losing purchasing power. When you move somewhere more expensive, you have negative leverage. You've made yourself more expensive to employ (in your own life, not to them) without providing additional value. They'd be idiots to pay you more. And they don't.

This is perfectly rational behavior from the company's perspective, by the way. I'm not even criticizing it as unethical. I'm criticizing it as incoherent. You can't claim the salary adjustment is a cost-of-living correction and then refuse to correct in both directions. That's not a policy. That's just "we pay you less when we can get away with it," which is how employment has always worked, but usually companies don't dress it up in spreadsheet logic.

The other thing this reveals is that the salary you were making in the expensive city was never really tied to the cost of living there in the first place. If it were, companies would be forced to raise salaries when people moved to more expensive places, or they'd lose talent. But they don't lose talent, because people move for reasons other than money all the time, and they tolerate the pay cut (relative to their new expenses) because the job is otherwise good, or the move is otherwise necessary, or they don't realize how much the math has shifted until six months in.

I think what actually happened is this: for decades, companies paid people more in expensive cities because that's where the talent was, and if you wanted to hire someone in San Francisco or New York, you had to match the market rate, which was elevated because of housing costs and concentration of employers bidding for the same workers. Cost of living was a factor, but it was embedded in market competition, not a direct calculation. Then remote work severed the link between location and market rate, and companies discovered they could pay people less if those people weren't competing in the same geographic labor market anymore. Someone in Nashville isn't competing with other San Francisco workers for San Francisco jobs. They're competing with other remote workers, many of whom also live in cheaper places.

Which would be fine — labor markets are supposed to adjust — except companies are still pretending the adjustment is about cost of living, when it's really about market segmentation. You're being paid less because you're in a different market now, and that market has lower rates. The fact that your rent also happens to be lower is a happy accident that makes the pay cut easier to swallow.

What the Math Actually Says

I spent an embarrassing amount of time building cost-of-living adjustments into SalaryHog, and here's what I learned: the math is never clean. A 20% difference in cost of living doesn't mean you need 20% less salary to maintain the same lifestyle, because cost of living indices are averages across spending categories, and your actual spending doesn't match the average. If you don't have kids, the fact that childcare is cheaper in Nashville doesn't help you. If you own your car outright, lower transportation costs are irrelevant. If you eat out twice a week at mid-range restaurants, the 18% difference in restaurant prices will matter, but not as much as the 40% difference in rent — unless you're splitting a house with roommates, in which case the rent difference compresses.

And then there's taxes, which everyone forgets about until April. Moving from California to Texas saves you 9.3% on state income tax for your top bracket, which sounds huge until you realize it's 9.3% of your California-taxable income, not your gross. On a $95,000 salary, that's about $6,200 a year, which is real money, but it's not "now you can take a $20,000 pay cut and come out ahead" money. The federal tax brackets are the same everywhere, and FICA doesn't care where you live. Most of your tax burden is unchanged by moving states.

The actual break-even point for a salary cut depends on so many variables that any company claiming they can calculate it accurately is lying to you or to themselves. What they're really doing is applying a formula they found on a compensation consulting website, and the formula is designed to save the company money while remaining defensible in an exit interview. It works because most people don't run the numbers themselves, and the ones who do run the numbers usually find that yes, technically, they come out slightly ahead, so they accept the cut and feel vaguely good about it.

I accepted my 15% cut. I did come out ahead, by about $6,000 a year after accounting for rent, taxes, and the fact that I stopped paying $180 a month for a parking spot. That's not nothing. But I also would have come out ahead if they'd only cut my salary by 10%, or 8%, or frankly if they hadn't cut it at all, because the rent savings alone were enormous. The 15% figure wasn't mathematically necessary. It was the number they knew I'd accept.

The Honest Version

Here's what I wish companies would say: "We're paying you less because we can. You're no longer competing in a high-cost labor market, so we don't need to match high-cost rates. We're adjusting your salary to reflect the new market you're in, which happens to be cheaper for you to live in, so this works out for both of us. If you move somewhere more expensive, that's on you — we're not going to subsidize your lifestyle choices, and we don't have to, because you've already accepted the job at this rate."

That would be honest. It would also be consistent. You could disagree with it, but you couldn't call it incoherent.

Instead, we get this weird hybrid where the salary cut is justified by cost of living when it benefits the company, and ignored when it doesn't, and the whole thing is presented as a value-neutral calculation rather than a negotiation where one side has more leverage. And the frustrating part is that most people don't notice the asymmetry because most people only move once, in one direction — usually from expensive to cheap, because that's the whole point of going remote. The people who move from cheap to expensive are rare enough that the policy failure doesn't generate backlash.

I think about this every time I see a job posting that says "remote, salary adjusted for location." It sounds neutral. It sounds like they've thought it through. But what it actually means is "we'll pay you less if we can, and we won't pay you more if we can't, and we've built a formula that makes this sound like math instead of leverage." Which, again, is how employment works. I just wish we'd stop pretending the math is doing something it isn't.