TL;DR — A pay zone is a geographic tier a company uses to set salary ranges: the same remote role pays a different band in Zone 1 (say, San Francisco or New York) than in Zone 3. Roughly 600 of the 42,612 live remote roles we track name a pay zone or salary band outright — most companies use them without saying so in the ad.
A pay zone is a bucket of locations that share one salary range. A company running zones defines two, three or four of them, assigns every city or country to one, and attaches a band to each. Hire the same engineer into Zone 1 and Zone 3 and the two offers differ by design — not because one candidate negotiated better.
A typical three-zone structure looks like this:
| Zone | Typical locations | Band for one role |
| Zone 1 | San Francisco, New York, Seattle | $180,000 – $220,000 |
| Zone 2 | Austin, Denver, Boston, most of the US | $155,000 – $190,000 |
| Zone 3 | Lower-cost US metros, much of Europe | $130,000 – $160,000 |
The numbers are illustrative; the structure is what matters. Note that the zones overlap: a strong Zone 2 candidate can out-earn a junior Zone 1 one.
What zones are actually indexed to
This is the part worth understanding before you negotiate, because it decides which arguments land.
Cost of labour — what competitors pay for that skill in that market. This is the honest rationale and the most common one.
Cost of living — what it costs to live there. Intuitive, and increasingly out of favour: it implies your pay should fall if you move somewhere cheaper, even though your output did not change.
Most companies say cost of living and mean cost of labour. It is a fair question to ask directly, because the answer tells you whether relocating changes your pay.
The three models you will meet
- Zoned (most common). Bands by location tier, as above.
- Single global rate. One number for the role, anywhere. Rare, and usually a deliberate recruiting stance — GitLab and Buffer built reputations on publishing theirs.
- National banding. One band per country, no city tiers within it.
What to ask before you accept
1. Which zone am I in, and what is its full band? Not just the offer — the range. 2. Cost of labour or cost of living? It predicts whether your pay is re-cut if you move. 3. What happens if I relocate? Some companies re-zone immediately, some at the next review, some never. 4. When are zones reviewed? Zone assignments drift as markets move; a stale zone map can cost you a raise.
If a listing gives no salary at all — and about four in five do not — asking which zone the role sits in is often a faster route to a real number than asking for the range directly.
Frequently Asked Questions
What is the difference between a pay zone and a salary band?
A band is the range for one role at one level. A zone is the geographic tier that decides which band applies to you. One role can have three bands, one per zone.
Can I negotiate out of my pay zone?
Rarely the zone itself — it is usually set by policy and applied consistently. What is negotiable is your position within the band, your level, and sometimes equity, which is more often global than zoned.
Does my pay change if I move to a cheaper city?
It depends on the company's policy, and this is worth asking before you move rather than after. Some re-zone on relocation, some hold your rate, some adjust only at the next review cycle.
Do remote-first companies use pay zones?
Many do — zoning is the majority model even among fully-remote employers. A single global rate is the visible exception, not the norm, which is why it tends to be advertised loudly by the companies that offer it.
RemoteHunt shows the advertised salary on every listing that has one and scores each role against your resume — so you can filter for the ones that name a number. Start for free.