Most employers hiring remotely still set pay against a location band. What differs is which location it is keyed to — where you live, where the role is anchored, or a single national rate — and what happens if you move. Those three policies produce very different outcomes for the same person, and the difference is a policy question with a factual answer rather than a matter of negotiation.
Two policies, very different numbers
Location-indexed pay prices the role by where you live. Move somewhere cheaper and your pay is adjusted down; move somewhere expensive and it may not be adjusted up.
A single national rate prices the role by what the work is worth to the employer, wherever you sit. Better for anybody outside the expensive metros, and more likely to be revisited when budgets tighten.
Both are common, both are defensible, and the difference between them can be a large fraction of your salary for identical work.
The argument each side makes
Employers indexing by location argue they are matching the market you actually compete in — if local employers pay less, they need not pay more.
Employers paying one rate argue they are buying the same output regardless of geography, and that indexing penalizes people for a housing market they did not create. They also find it simpler to administer and easier to defend internally.
Neither is obviously right. What matters is knowing which one you are under.
The questions to ask before accepting
Is pay indexed to my location or set nationally? What happens if I move — is it adjusted, and in both directions? Which tier is my location in, and where are the boundaries?
Ask before signing rather than after. An arrangement that adjusts pay downward when you relocate is a materially different job from one that does not, and it is a normal question a well-run employer answers plainly.
Why remote work did not flatten pay
The obvious prediction was that remote hiring would erase geographic differences. It largely has not, and concentration explains why.
A dense market is not just jobs in one place — it is employers competing with each other, colleagues who talk, and a known local rate. Those survive the office closing. A company hiring remotely into San Jose is still hiring against San Jose employers.
Where the wage data cannot help you
Published occupational wages are recorded by establishment location, not by where the worker sits. So the geography in every wage table is employer geography, and for heavily remote occupations that gap widens each year.
Read a metro median for a remote-heavy occupation as what employers headquartered there pay — which is still the number you would negotiate against, but it is not a statement about local living standards.
The tax complication
Working remotely across a state line raises the question of which state can tax the income, and a few states apply rules that tax you as though you worked at the office regardless of where you sat.
This is genuinely unsettled and varies by state pair. It is one of the few situations where paying for an hour of professional advice before accepting is straightforwardly worth it.
The strategy that actually works
Get hired at a national rate, or at the rate of an expensive market, and then decide where to live. That sequence is worth more than any negotiation over a few per cent, and it is only available before you sign.
Employers who index will usually say so early, because it is policy rather than a position. Employers who do not index rarely advertise it, so it is worth asking directly rather than assuming.
If you are already remote and considering a move
Get the policy in writing before you commit to anything. A verbal assurance from a manager does not survive that manager leaving, and pay policies are among the first things a new leadership team revisits.
Then check what your occupation pays in the destination anyway. If the local market pays more than your current rate, indexing is an opportunity rather than a risk — and that reversal is more common than people expect.
Common questions
Do remote employers really still use location bands?
Most do. What varies is whether the band follows where you live, where the role is anchored, or a single national rate — and those produce very different outcomes for the same person.
Will my pay drop if I move somewhere cheaper?
Under a live-where-you-are policy, usually yes. Note the asymmetry: many employers adjust downward on a move to a cheaper area without adjusting upward for the reverse, so ask about both directions.
Why do employers care which state I live in?
Payroll registration, tax withholding, employment law and insurance all follow the employee's location, and each state carries real administrative cost. That is why approved-location lists exist even at national-rate employers.
Which policy is best for me?
A band keyed to an expensive anchor while you live somewhere inexpensive. It is also the one most likely to be revisited, so ask whether the policy is written down.
Has remote work flattened pay geography?
For roles already priced in a national market, substantially. For anything requiring presence, licensure or local knowledge, barely at all.
Do employers pay remote workers by location?
Some index pay to where you live; others set a single national rate. Both are common and the difference can be a large fraction of salary for identical work.
Why didn't remote work flatten geographic pay?
Dense markets are employers competing with each other and a known local rate, and those survive the office closing. A company hiring remotely into San Jose still hires against San Jose employers.
What should I ask before accepting a remote role?
Whether pay is indexed to location, what happens if you move, and which tier your location sits in — in writing, before signing.