The offer comes by email on a Thursday afternoon. Senior product designer, fully remote, $97,000. You'd been targeting $118,000 — that's what the role pays at comparable companies. You write back and ask about flexibility. The recruiter replies the next morning: "Our comp is location-adjusted. Based on your location in Nashville, the band for this role is $93,000–$99,000."
You're a senior product designer with nine years of experience. Your Figma files don't know what city you're in. Your stakeholders don't care. But apparently your salary does.
What "Location-Based Pay" Actually Is
Companies introduced geo-based compensation at scale in 2020 when remote work forced them to hire across the country. The framing they use with employees is fairness — you live where costs are lower, so your salary reflects that.
Here's what it actually is: a way to capture savings that should, by any reasonable argument, be shared.
Think about what your employer is not spending when you work remotely. Commercial real estate in major cities runs $15,000–$25,000 per employee per year. Add equipment refresh cycles, office management, facilities staff, and the overhead of putting bodies in buildings — you're looking at $20,000–$30,000 annually per seat that simply evaporates when someone works from home.
You freed up that money. They kept it. Location-based pay is how they take a second bite — paying you less than your San Francisco counterpart while also not paying for the San Francisco office you're not sitting in.
That's not fairness. That's a pricing strategy dressed up as one.
The Case Remote Workers Deserve a Premium (Not a Discount)
Most salary advice treats location-based pay cuts as a given — an immovable fact of the market. But here's the thing almost no one says out loud: there's a legitimate argument that remote employees should earn more, not less.
Your output goes into the same codebase, the same product, the same customers. If a piece of work is worth $X to the company, that value doesn't change based on where the laptop is sitting. A CPA in Kansas charges the same as a CPA in Manhattan for the same work done the same way. A freelance copywriter doesn't adjust their day rate because a client is headquartered somewhere cheaper.
The "local market" argument only works if you accept that your labor is a local commodity. It isn't. It's remote — the entire point is that it untethers from location.
You don't need to make this argument in the negotiation. But knowing it changes how you hold yourself in the conversation.
How to Find Your Real Number Before You Push Back
Before you say anything to the recruiter, you need a defensible number — not a feeling.
Here's the research approach that actually holds up:
Check what the company pays in high-cost cities. Many states now require salary ranges in job postings. Go to their careers page and search the same role with a San Francisco or New York location filter. That tells you what the role is worth to them — and reveals that their "local-adjusted" number isn't the market, it's a choice.
Pull from three sources separately. Use Levels.fyi, Glassdoor, and LinkedIn Salary for the same title and experience level. Don't average them — find where two of three overlap. That's your range.
Search by role, not location. Filter for the position at companies of similar size and industry. Set the location to the company's headquarters or the highest-cost market where they hire. That's the benchmark you're anchoring to.
If you want this done in three minutes with live market data, SalaryAsk will pull benchmarks for your exact role and experience level — so you're walking in with actual numbers, not a gut feeling. It tells you what the market pays before you send a single email, which changes every word that follows.
How to Frame the Pushback
The mistake most people make is arguing the principle of location-based pay. "That's unfair because my work is the same" is an emotional argument. Recruiters have a script for it. They've heard it. They'll nod, say they understand, and tell you the policy comes from above.
What they don't have a script for is a calm, specific market data point delivered without apology.
Here's what to say — by email or phone, your preference:
"Thanks for the clarity on the comp structure. I've done some research on the market rate for senior product designers at companies at your stage — the median sits around $118,000–$125,000 regardless of location. I'd like to ask for $120,000. That's where I'd feel completely committed and not be fielding other conversations on the side. Is there flexibility to get there?"
A few things about that script:
- You're not fighting their philosophy. You're naming a number backed by data.
- "Not fielding other conversations" is a soft reference to market optionality without fabricating a competing offer. It's honest — and it lands.
- You're ending with a yes/no question, which forces a real answer rather than a non-committal "we'll look into it."
If you don't have a competing offer to point to, this guide covers exactly that scenario — the principles are the same whether the role is remote or not.
When the Band Is Genuinely Firm
Sometimes it is. The recruiter isn't bluffing — the band is set, the hiring manager can't move it, and the base salary conversation is over.
When that happens, every other variable becomes fair game.
Signing bonus. This often runs from a different budget line than base salary and is much easier to flex. A $12,000–$20,000 sign-on is realistic for senior roles and closes a meaningful comp gap in year one. The ask is simple: "If base is at its ceiling, is there room for a sign-on to bridge the difference?" Here's exactly how to negotiate that conversation.
Equity or RSUs. If they have a stock program, ask for additional grant units. The value is uncertain but real, and asking for it signals you're thinking long-term — which tends to land well with hiring managers.
An earlier review date. Ask for a committed 6-month performance review with a specific raise tied to clear targets — written into the offer letter, not a handshake. At a 12-month timeline you've already lost six months of higher earnings. Compressing that matters.
Remote-specific budget. Home office stipend, internet reimbursement, co-working allowance. Some companies quietly offer $1,000–$2,000 annually for this. If it's not in the offer, ask. The question costs nothing.
The goal isn't to max out every line item. It's to close the gap between what you need and what they've offered — by whatever route is actually open.
What to Do If They're Asking You to Take a Pay Cut to Stay Remote
This is a different but increasingly common version of the same problem. Your employer wants you back in the office. Staying remote means taking 10–15% less.
Treat it like an offer negotiation. Because it is one.
The bet your employer is making: you value remote work highly enough to accept lower pay rather than go looking elsewhere. Maybe that's true. But before you accept, verify it — get a few conversations going with other companies. Not necessarily to take another job, but to understand what your options actually are. If you could make $140,000 elsewhere and your employer wants to cut you to $118,000, that's useful information for the conversation you're about to have.
Most people accept these cuts without knowing whether they'd need to. Don't be most people.
FAQ
Does disclosing my location hurt my negotiation?
Sometimes, especially early in the process with companies that use automated geo-pay tools. If location isn't required at the application stage, you don't need to volunteer it. Once you're in salary discussions, keep the conversation anchored to the role's market rate — not your specific city.
Can companies legally pay remote workers less based on location?
In most US states, yes — there's no law requiring location-neutral pay. Some states have pay transparency laws that require posting salary ranges, which is useful for your research, but they don't dictate how companies set those ranges. Your leverage is market data and optionality, not legal protection.
What if I move cities after accepting a remote role?
This depends entirely on your employer's policy. Some adjust comp (up or down) automatically based on your registered address. Before you sign anything, ask explicitly: "If my location changes, how does that affect my compensation?" Get the answer in writing — not just a verbal "we'll figure it out."
How do I negotiate remote work itself as part of an offer?
If the role isn't listed as fully remote but you want it to be, it's easier to raise after you have the offer in hand — not before. Accept in principle, then open a separate conversation using the same data-driven framing. Know what you're asking for, don't argue the principle, and be specific about what "remote" means to you (fully remote, hybrid, how many days). For the full offer negotiation playbook, start here.