Remote salary adjustments are one of those topics that sounds simple on paper — your pay changes based on where you live — but gets complicated the moment you try to figure out whether it’s fair. A late-2025 study from researchers at Harvard, Brown, and UCLA found that the average tech worker would accept roughly a 25% pay cut to keep a partially or fully remote job, even when the actual cost-of-living difference between cities is often smaller. That gap between what people are willing to give up and what companies actually save is where the real negotiation lives.
Career/income Negotiation Logistics/setup
Heads up — this post may include links to things I use or like, and I might earn a little something if you shop through them. Doesn’t cost you anything extra, and I only mention stuff I’d actually recommend.
The Two Flavors of Location-Based Pay
Not all remote salary adjustments work the same way, and the difference matters more than most people realize. Companies generally choose between two models: cost-of-labor and cost-of-living. Cost-of-labor adjusts pay based on what local employers in that city are offering for the same role — so if engineers in Austin typically earn 85% of what they’d make in San Francisco, your pay lands around that mark. Google, Meta, and Apple use this approach, and the typical adjustment for a mid-cost city like Austin or Denver runs between 5% and 20% below the Tier 1 hub rate.
Cost-of-living adjustments, by contrast, look at how much cheaper it is to actually live somewhere — housing, groceries, transportation. Those cuts tend to be steeper. The same Austin move under a cost-of-living model could reduce pay by 15% to 35%, depending on the index a company uses. The Bureau of Economic Analysis Regional Price Parities show the San Francisco–Austin spread at roughly 20–23%, which is closer to the employer adjustment than the cost-of-living gap implies, but still not a perfect match.
The core tension is which metric you’re being measured against. If your company uses cost-of-labor, they’re essentially saying “we pay what the local market pays.” If they use cost-of-living, they’re saying “we pay what we think you need to live there.” Those aren’t the same number, and they produce very different outcomes for the same relocation.
For a senior engineer moving from San Francisco to Raleigh, a cost-of-labor model might apply a 10–15% reduction, while a cost-of-living model could cut pay by 30–35%. Raleigh’s tech talent market has grown significantly, but housing remains cheaper than the Bay Area — so the two models pull in opposite directions. The gap isn’t small, and it’s worth asking which one your employer uses before you accept a number.
✦
What the Numbers Actually Say About the Trade-Off
The headline figure from the Harvard/Brown/UCLA study — a 25% average willingness to sacrifice — is eye-catching, but it comes from a specific population: tech workers on the Levels.fyi platform, averaging about seven years of experience and total compensation around $239,000 a year. That group has more leverage and more alternatives than a typical remote worker in a less specialized field. The same study also found that about 40% of workers would take at least a 5% pay cut to keep remote work, and nearly 10% would give up 20% or more.
On the other side of the ledger, the savings from working remotely are real but not always enough to offset a large adjustment. Global Workplace Analytics estimates that remote workers save between $6,000 and $12,000 annually on commuting, meals, work clothes, and incidental childcare. If your pay cut is $21,000 and your savings are $9,500, you’re net down $11,500 — not a break-even trade. The Economic Policy Institute has noted that cost-of-living calculations miss categories that don’t change with location, like federal taxes, student loan payments, and investments, which means a cut based purely on local costs can overstate the actual financial benefit to the company.
It’s easy to look at a 20% cut and think “I’ll save on rent and commuting, so it evens out.” But rent might drop 30% while your student loan payment stays the same, your 401(k) contributions don’t change, and your streaming subscriptions cost the same whether you’re in San Francisco or Boise. The savings are lumpy and don’t always align with the cut. Running the actual numbers — your specific spending, not a generic index — is the only way to know.
✦
How to Know If the Cut Is Fair
Fairness in remote salary adjustments isn’t just about the percentage — it’s about the methodology and the transparency. Companies that publish their compensation philosophy, like Buffer and GitLab, give employees a clear sense of how the number was reached. Buffer uses Numbeo cost-of-living data and publishes every employee’s salary formula. GitLab combines Radford cost-of-labor data with country-level adjustments and documents it all in a public handbook. When you can see the inputs, you can judge whether the output makes sense.
Most companies aren’t that transparent. They set an anchor market — usually their headquarters city — and apply a tier structure with three to five zones. A typical structure might have Tier 1 (San Francisco, New York, Seattle, Boston) at 100% base, Tier 2 (Austin, Denver, Chicago, Miami) at 88–92%, and Tier 3 (everywhere else) at 75–82%. The exact numbers vary, but the pattern is consistent: the further you are from the headquarters city, the more your pay drops, regardless of whether the local labor market actually supports that discount.
The fairness question comes down to data. If your company is using cost-of-labor data from a reputable source like Levels.fyi or Radford, and the adjustment matches what you could actually earn locally, it’s defensible. If they’re using a cost-of-living index that produces a 30% cut for a city where competing employers are paying only 10% less, you’re being over-adjusted. In that scenario, the cut is more about margin capture than fairness.
When a company applies a location-based cut that exceeds the actual cost-of-living difference by more than five percentage points, it’s a signal about how they value remote talent. If they won’t negotiate and won’t explain their methodology, the cut isn’t just a financial hit — it’s a statement about what kind of employer they are. That matters for your long-term satisfaction and career trajectory, not just your paycheck this year.
✦
Negotiation Moves That Actually Work
If you’re facing a remote salary adjustment and the number doesn’t feel right, the standard advice to “ask for more money” rarely works inside rigid compensation bands. What does work is shifting the conversation from your personal expenses to market data. Lead with specific numbers from sources your HR team already respects: “Based on Levels.fyi data for this role at this level in my city, the median total compensation is $X. That’s 10% higher than the adjusted offer I’m seeing.”
Another effective move is to propose a hybrid arrangement if full remote is the sticking point. Some companies maintain separate pay bands for hybrid versus fully remote roles, and the hybrid cut is often smaller — even if you only come in two days a month. Asking “What would the hybrid band look like?” can save tens of thousands without changing where you actually sit most of the time. It’s worth testing before you accept the full remote number.
If salary is genuinely locked, negotiate the total package instead. Many companies have flexibility on equity refreshes, sign-on bonuses, professional development budgets, or additional PTO. A $5,000 annual learning stipend or an extra week of vacation changes the effective compensation without touching base salary. The research summary notes that backfill costs for technical roles can run 50–200% of annual salary per SHRM turnover research, so making it easy for your manager to justify an exception with a one-page summary of your output metrics — projects shipped early, revenue influenced, tickets resolved — can tip the scale.
If you’re negotiating a new offer, be direct about the adjustment early. A candidate in a recent example took a £7,000 pay cut (roughly $9,300) for a fully remote role and documented it publicly — but that was after knowing the number upfront. The worst scenario is discovering the adjustment late in the process, after you’ve already invested time. Ask in the first conversation: “Can you explain how location affects the compensation range for this role?” If the answer is vague, that’s a red flag.
- Lead with market data (Levels.fyi, Payscale) — not your rent or commute costs. HR cares about retention risk, not your personal budget.
- Ask about the hybrid pay band before accepting the full remote adjustment. Two days in office per month might save you tens of thousands.
- If salary is locked, push for equity refreshes, sign-on bonuses, or a professional development budget. A $5K learning stipend changes the math.
✦
When to Walk Away
The strongest position in any remote salary negotiation is knowing your walk-away point. If the cut exceeds the actual cost-of-living difference by more than five percentage points and the company won’t negotiate, that tells you something about how they view remote workers — and that’s unlikely to improve over time. Some employers, like Airbnb and Zillow, pay location-agnostic salaries because they’ve decided the talent pool breadth is worth the cost. Most don’t, but the ones that do are worth seeking out if location-based pay is a dealbreaker for you.
Even with a reasonable adjustment, the role needs to have real career upside: a path to senior leadership, vesting equity, or learning from a strong team. If the cut is fair but the role is a dead end, the financial trade-off might still not be worth it. And if the adjustment is applied uniformly — the same 20% cut for a senior engineer and an entry-level coordinator — it indicates the company isn’t adjusting for individual contribution, which is a separate problem worth considering.
On the other hand, if you’ve verified that your savings will exceed the cut, and the role offers genuine growth, the adjustment can be a reasonable price for the flexibility. The key is running the numbers before you accept, not after.
Remote salary adjustments aren’t going away, but they’re not a single number you have to accept or reject. Understanding the model — cost-of-labor versus cost-of-living — and running your own savings calculation gives you a factual baseline. From there, negotiation is about market data, hybrid alternatives, and total package flexibility. The companies that are transparent about their methodology are easier to trust; the ones that aren’t deserve harder questions. Ultimately, the best outcome isn’t the smallest cut — it’s the one that leaves you feeling fairly valued for the work you actually do.