The Geographic Pay Zone Reference, Each Location Rule Keyed to Its Cut
Name the location rule behind any zoned or pay-depends-on-location posting, place your address, put a percentage on your cut, and confirm it in one email.
Key takeaways
- In the employer postings checked for this reference, the second pay zone sits about 6 to 13% below the top zone and the third zone about 12 to 22% below it.
- Toast's zone cuts stay the same (about -13% and -22%) whether the top-zone minimum is $106,000 or $230,000, so a single posting can show you an employer's whole step size.
- Zone letters are not standard: Avesis labels its lowest-paying zone Zone A, so always find the top zone by its dollar figures, not by its letter.
- Dropbox aims most new-hire offers between the minimum and the middle of the range, so a realistic ceiling is the midpoint of your own zone, not the top of the posting.
- Fewer employers apply location pay at the top: in WorldatWork figures, 37% applied differentials at executive level against 81% for non-exempt staff, and GitLab capped its director cut with a 0.8 US floor.
- In Refolk's index, only 2 of 11 mapped US engineering directors with 'remote' in their headline live in a Dropbox-style Zone 1 metro, a small sample that hints remote senior talent mostly sits outside the top zone.
This reference is for anyone applying to remote or multi-city roles where the posting lists Zone A, B, and C ranges or just says "pay depends on location." For any posting it helps you work out which location rule the employer uses, which zone your address falls in, and how many percent below the top zone that puts you. It ends with the one recruiter question that confirms all of it before anyone names a number.
What does a Zone A, Zone B, or Zone C salary mean on a job posting?
A lettered or numbered zone is a group of locations that share one pay range for the role. A posting that shows three zones is really showing three salaries, and only one of them applies to you. The posting tells you which zone pays most. It does not tell you which one you're in. For that you need the employer's zone map and its assignment rule.
Location pay is common but not universal, and the survey figures move from one year to the next:
- Prevalence. In a WorldatWork study of 1,063 organizations, 62% had US geographic pay policies, and 44% of those were considering changes or had recently made them because of full-time remote work.
- Direction of travel. In WorldatWork's follow-up survey of 858 US organizations, 24% said base pay depends on location (down from 33% the year before) and 25% said it does not (up from 19%).
- Mechanics. 41% apply differentials as a premium or discount to a structure or to individual pay. 33% build a separate base pay structure for each location.
- Number of zones. No named survey publishes a typical count of US zones. In live postings I found 3 zones at Toast, Dropbox, Atlassian, Webflow, and Avesis, and 4 at Block and in GitLab's sales table.
Two terms come up throughout. A location factor is a multiplier applied to the top-zone pay, so 0.85 means 85% of the top rate. A cut is how far your zone's range sits below the top zone's range, as a percentage.
The seven location rules, one entry each
Every geographic pay policy reduces to one of seven rules. The rule decides which zone you're in and how big your cut can be. Find the entry that matches what the posting or careers page shows. Each entry covers what the rule looks like, how your zone gets set, how big the cut is, how the rule misleads, and the question that confirms it.
National band
- What you see: one range, and no zone or location wording on the employer's own page.
- How your zone is set: it isn't. Everyone in the country gets the same structure.
- Size of cut: zero, by policy. In WorldatWork's survey, 25% of US employers reported a single structure with no location differences.
- How it misleads: a single range on an aggregator is often several zones merged together. One practitioner blog says most employers post the widest applicable range with a pay-depends-on-location note. That claim is unverified as a statistic, but it matches what aggregators show.
- Confirming ask: "Is this range the same for every US location, or does it vary by where I live?"
HQ or office anchor
- What you see: a city named next to the range, or a hybrid role tied to an office.
- How your zone is set: by the office, not your home. For in-office and hybrid staff, WorldatWork found pay location is most often set by nearest work location (45%) or reporting location (31%).
- Size of cut: whatever the anchor office's zone pays. No public source gives a typical figure.
- How it misleads: a remote hire assumes the HQ rate travels with them, but more than half of full-time remote workers are tied to where they live instead. Separately, New York's transparency law covers any role reporting to a New York supervisor or office, even if the work is done entirely out of state. So a New York range can appear on a role you would do from somewhere cheaper.
- Confirming ask: "Is my pay tied to my home address, my nearest office, or my manager's location?"
Lettered or numbered zones
- What you see: two to four labelled ranges (Zone A/B/C, Zone 1/2/3), usually in the posting footer.
- How your zone is set: by a published map of metros or states, with "all other US locations" as the bottom zone. Dropbox's Zone 1 is the San Francisco, New York City, or Seattle metro, and its Zone 3 is all other US locations.
- Size of cut: about 6 to 13% for the second zone and 12 to 22% for the third, based on the postings in the next section.
- How it misleads: the letter order isn't standard, some listed zones are excluded from hiring, and some ranges are base while others are OTE.
- Confirming ask: "Which zone does my zip code fall in, and is the range base only?"
County map
- What you see: a list of counties per pay area. This is how the federal GS system works.
- How your zone is set: each locality area is a list of counties. If the duty station's county is on a list, that rate applies. Otherwise the Rest of U.S. rate applies.
- Size of cut: in the GS schedule I checked, Rest of U.S. works out about 20% below San Francisco (see the second table below).
- How it misleads: county lines make cliffs. Calaveras County, CA is in the San Jose-San Francisco-Oakland area at 46.34%, while neighbouring Tuolumne is Rest of U.S. at 17.06%. No survey publishes how many private employers assign zones by county.
- Confirming ask: "Do you assign zones by county, and if so which county list am I on?"
Metro radius
- What you see: "within X miles of" a named metro.
- How your zone is set: Dropbox sets zone by zip code, and anyone within 100 miles straight-line of a listed metro is in that metro's zone.
- Size of cut: the same as the lettered zone the radius feeds into.
- How it misleads: the radius is straight-line, not driving distance, so it reaches into exurbs. An address two hours' drive from the city can still get top-zone pay. Someone just outside the circle drops a full zone.
- Confirming ask: "Is the radius measured straight-line from the metro centre, and from which point?"
City differential
- What you see: "pay depends on location," sometimes with one wide range, sometimes with per-city figures.
- How your zone is set: by city or metro. WorldatWork found 56% of employers use city or metro area as the basis for differentials, and that cost of labor outweighs cost of living in how the figures are set.
- Size of cut: varies. ERI reports the two most popular geographic banding widths are 5% and 10%, which means cities get grouped in steps of that size.
- How it misleads: the single posted range may be the widest range the employer would pay anywhere, so the top of it is not your number.
- Confirming ask: "What is the range for my city specifically?"
Country factor
- What you see: a global remote role with a location factor, or a calculator.
- How your zone is set: by country first, then sometimes by area within the country. GitLab used a location factor and set a Global Director minimum of 0.7, below its US Director minimum of 0.8.
- Size of cut: not established publicly for country factors in general. GitLab's floor capped the director cut at 30% globally.
- How it misleads: public calculators go away. GitLab has retired its compensation calculator, and its output had been given as base plus variable equals total target cash, not base alone.
- Confirming ask: "What location factor applies to my country and region, and does it apply to base only or to total cash?"
How big is the cut from the top zone?
In the employer postings I checked, the second zone sits about 6 to 13% below the top zone and the third about 12 to 22% below it. Block's fourth zone was 17% below its top. The cut is a fixed step, so one posting gives you the employer's whole pattern.
| Employer, role | Top zone min | 2nd zone cut | 3rd zone cut |
|---|---|---|---|
| Toast, Data Engineer | $106,000 | -13.2% | -21.7% |
| Toast, Associate Counsel | $152,000 | -13.2% | -22.4% |
| Toast, Sr Principal PM | $230,000 | -13.0% | -21.7% |
| Atlassian, Data Engineer (older posting) | $129,600 | -10.0% | -17.0% |
| Webflow, Sr Developer Educator | $129,000 | -5.8% | -12.4% |
| Block (older posting) | $167,300 | -7.0% | -12.0% |
The cuts are derived from the minimums. The maximums match within half a point. Block's fourth zone sits 17.0% below its top.
What this table proves:
- Steps are fixed. Toast's ratios stay at about -13% and -22% whether the top minimum is $106,000 or $230,000. Each zone looks like a fixed percentage of the top zone, so if you know Toast's top-zone figure for any role, you can estimate your own zone's figure.
- Step sizes differ by employer. Webflow's third zone is shallower than Toast's second. Don't carry one employer's cut over to another.
- Dropbox runs at a constant 11.1% between Zone 2 and Zone 3 in all four of its postings I checked.
For the Toast Data Engineer, that works out to a second-zone minimum of about $92,000 and a third-zone minimum of about $83,000.
The federal benchmark
Federal GS locality pay gives you a public, county-based yardstick for checking whether a private employer's cut is unusual. In the current schedule, locality payments run from 17.06% to 46.34% across 58 locality pay areas. GS locality percentages were frozen at the prior year's levels, with a 1.0% base increase, so re-check the schedule before relying on these figures.
| GS locality area | Locality | Pay vs SF (derived) |
|---|---|---|
| San Jose-SF-Oakland | 46.34% | 0% |
| New York | 37.95% | -5.7% |
| Washington-Baltimore | 33.94% | -8.5% |
| Dallas-Fort Worth | 27.26% | -13.0% |
| Rest of U.S. | 17.06% | -20.0% |
The derivation is (1 + local %) ÷ 1.4634. Private and federal cuts land at similar depths, and WorldatWork says both rely on cost-of-labor data rather than cost of living. If an employer's bottom zone sits much further below its top than 20 to 22%, ask why.
What the cut applies to: base, OTE, bonus, and equity
Most zone ranges are base salary. Whether the cut also reaches bonus and equity depends on how those are calculated, and for equity it isn't publicly established. Check the scope before you compare any two numbers.
| Item | What the evidence shows | Falls with zone? |
|---|---|---|
| Base salary | Toast labels its zone ranges as base salary | Yes |
| Bonus | Webflow sets bonus targets as a % of base | Probably (inferred) |
| OTE | Dropbox's People Partner range is "salary/OTE" | Yes, whole figure |
| Total target cash | GitLab's old calculator gave base + variable | Yes |
| Equity | Not established publicly | Ask |
Toast says its total rewards also include bonus or commission if eligible, equity, and benefits, on top of the zoned base. When the bonus is a percentage of base, a zone cut on base cuts the bonus by the same percentage. My reading is that this applies at Webflow, but Webflow doesn't state it.
Two related things are not location pay and should be kept apart:
- Remote versus office differentials. Some employers may pay remote and office staff differently regardless of location. Nothing in the sources I used sizes such a differential, so if you suspect one, ask about it as a separate question from your zone.
- Where in the range you land. Dropbox targets most new-hire offers between the minimum and the middle of the range. That positioning sits on top of the zone cut.
From posted range to your realistic number
- Merged rangeWhat aggregators show, spanning every zone from lowest minimum to highest maximum
- Your zone's rangeThe single row that matches your assigned address
- Same-scope figureBase only, with bonus and OTE separated out
- Offer targetMinimum to midpoint of your zone, where employers like Dropbox aim new hires
How your address gets assigned to a zone
Your zone comes from one of five inputs: home zip, a metro radius, county, nearest office, or reporting manager. WorldatWork found more than half of full-time remote workers are tied to where they live (Fortune reported 54%), while in-office and hybrid staff are tied mostly to their nearest office (45%) or reporting location (31%).
How to place yourself under each input:
- Home zip under a metro list. Check whether your city is named. If it isn't, you're in the "all other" zone.
- Home zip under a radius. Measure straight-line distance to the listed metro. Dropbox uses 100 miles.
- County. Look up your county. Where an employer doesn't publish its list, OPM's locality pay area definitions page is a usable proxy for how county lines cluster around metros, but it isn't the employer's map.
- Nearest office. Find the employer's closest office and that office's zone.
- Reporting manager. You often can't know this until a hiring manager is named, so ask.
Moving after you are hired
Moving doesn't automatically change your pay, and it doesn't automatically protect it either. If you're assigned by home address, a move to a cheaper area can drop you a zone. If you're assigned by office or manager, a home move may change nothing until the employer reclassifies you. Ask how and when a relocation triggers a change before you sign, not after you move.
Living in a lower zone can help you get hired
Some employers recruit in their lower zones on purpose. Several Dropbox remote roles state they are not available in Zone 1, and GitLab has said it may favour applicants with a lower location factor. Toast does the reverse for some legal roles, saying candidates in hub cities will be prioritized. A lower zone shrinks your band but can widen your shortlist.
Aim or skip by cut and hiring intent
Where location pay stops by level
Differentials thin out as seniority rises. Executive level is the usual cutoff, and director level is a partial one: many employers still apply a cut there but cap it.
| Level | WorldatWork, earlier | WorldatWork, two years later | Culpepper |
|---|---|---|---|
| Non-exempt or professional | 82% | 81% | 87% (professional) |
| Management or director | 87% | 62% | 77% |
| Executive | 47% | 37% | 38% |
Shares are of employers applying geographic differentials at each level. In the WorldatWork figures shown in ERI's slides, exempt staff came in at 83% in the later year.
What to take from it:
- Senior roles are less likely to carry a cut at all. Management-level application fell from 87% to 62% across the two WorldatWork surveys.
- Floors cap the cut where it remains. GitLab set a US Director minimum location factor of 0.8 and a Global Director minimum of 0.7. A US director there loses at most 20%, even in a zone whose factor would otherwise be lower. GitLab's sales table ran Zone 1 at 1.00, Zone 2 at 0.85, Zone 3 at 0.75, and Zone 4 at 0.60, so the floor matters most in the bottom two zones.
- Remote senior talent mostly lives outside the top zone. That's one more reason employers loosen differentials at this level.
How to place yourself and price the cut, step by step
The whole job takes about 40 minutes per employer. Most of it is finding the map and the assignment rule, and the arithmetic takes two. On an employer's own page the map usually comes before the range. On an aggregator you only see a merged range, so you can't compute the cut until you've found the employer's map.
Zone lookup procedure
- Read the comp blockNote the zone labels, how many zones are listed, and any line saying the role is not available in a zone. Done when you know which zones are listed and which are excluded.
- Find the zone mapLook for the map on the employer's careers page (Webflow keeps one in a pay zones section) or in the posting footer, not on an aggregator. Done when the map is found or its absence is noted.
- Identify the assignment ruleWork out whether the zone is set by home zip, metro radius, county, nearest office, or reporting manager. Done when you can name the rule in one phrase.
- Place your addressCheck your zip against the metro list or radius, or your county against the employer's list, using OPM's county lists as a proxy. Done when you have one zone, or two if you sit on a border.
- Compute the cutDivide your zone's minimum by the top zone's minimum, then do the same for the maximums. Done when you have the cut as a percentage and your zone's midpoint in dollars.
- Check the scopeConfirm whether the range is base, OTE, or total, whether the bonus is a percentage of base, and whether equity is mentioned. Done when every figure you compare uses the same scope.
- Check the level cutoffAt director level and above, look for a floor such as GitLab's 0.8 or an exemption. Done when you know whether your cut is capped.
- Ask the recruiterSend one email with the confirming question before the first pay conversation. Done when your zone, scope, and relocation rule are in writing.
Keep the arithmetic in one place so you can compare employers side by side:
Employer and role: Location rule (national / office anchor / lettered zones / county / radius / city / country): Assignment input (home zip / radius / county / nearest office / manager): Top zone, found by highest dollars: min $______ max $______ My zone: ______ min $______ max $______ Cut at minimum = (my min / top min) - 1 = ______% Cut at maximum = (my max / top max) - 1 = ______% Realistic ceiling = (my min + my max) / 2 = $______ Scope: base / OTE / total cash Bonus as % of base? Y / N Equity mentioned? Y / N Level floor or exemption: Excluded zones or priority lines:
Fill one copy per employer and keep them together so you can compare cuts.
Then send the confirming question. Ask it before the first pay conversation, not during it. That way the recruiter answers a factual question rather than a negotiating one.
Subject: Pay zone for the [Role] posting - one quick check Hi [Name], Before we talk about compensation, I want to make sure I am reading the posted ranges correctly. I live in [City, ZIP], in [County] county. Which pay zone does that place me in for this role, and is that zone's range base salary only, or does it include bonus or OTE? If I relocated after joining, how and when would a zone change be applied? Thanks, [Your name]
Swap in your role, city, zip, and county; delete the relocation line if you are not planning a move.
Once you know which postings put you in a zone you can live with, the slow part is making each application match the role. Refolk writes your resume from your own history, tailors it to each of those postings, and scores how well you actually fit, so you spend the 40 minutes on the zone and not on rewriting bullets.
How zone reading goes wrong
Most mistakes come from reading a number that isn't yours: a merged range, a zone you can't be hired into, or a range with a different scope. Each failure mode below has a false positive and a check that catches it.
- Trusting the zone letter. False positive: you assume Zone A is highest and treat its figure as the top. Avesis's Zone A is its lowest, 14.7% below Zone C. Check: rank the zones by dollars before anything else.
- Reading an aggregator's merged range. False positive: you take the top of a wide range as your number. Indeed showed Avesis as $55,790 to $109,040, which merges all three zones. Webflow's structured data showed $143,000 to $205,000 across zones. Check: compute only from the employer's own posting.
- Aiming at a zone that isn't hiring. False positive: you see your zone's heading and assume it's open. Dropbox prints a Zone 1 heading on some roles and then says they're not available in Zone 1. Toast says hub-city legal candidates will be prioritized. Check: search the posting for "not available," "prioritized," and similar lines.
- Treating the range top as reachable. False positive: you name your zone's maximum as your target. Dropbox aims new-hire offers between the minimum and the midpoint. Check: treat your zone's midpoint as the realistic ceiling.
- Comparing mixed scopes. False positive: you compare a Dropbox "salary/OTE" range with a Toast base range and conclude one cut is deeper. Check: write the scope next to every figure and compare like with like.
- Using the wrong boundary rule. False positive: you assume your exurb is out of the top zone, or that your county is in it. A 100-mile radius pulls in exurbs, while county lists split neighbours (Calaveras at 46.34%, Tuolumne at 17.06%). Check: name the rule before placing your zip.
- Assuming a move changes pay, or doesn't. False positive: you plan a move expecting no pay effect, or expecting an automatic raise. Office- and manager-based assignment (45% and 31% for in-office and hybrid staff) can leave pay unchanged until reclassification, while residence-based assignment can drop it. Check: get the relocation rule in writing.
Two more limits on the evidence itself:
- No law forces zone-by-zone disclosure. No state requires every zone's range to be listed, so a single merged range is legal. Colorado requires the posting to show what the role pays in Colorado, says a location-based pay note can't replace an actual range, and treats a remote posting as covered even if it says Coloradans won't be considered. That gives you a Colorado number, not your number.
- Survey shares drift. The share of employers using location pay moved by several points between consecutive WorldatWork surveys. Treat any single prevalence figure as a snapshot.
A merged range is the employer's whole country on one line. Your number is one row of it.
Keeping your zone read current
Zone maps, factors, and calculators change without notice, so re-check them at three points: when you first aim, before the first pay conversation, and before you sign. Each time, record the date you checked and where you found the map.
What to re-check, and where:
- The employer's zone map. Look at the careers page and the posting footer. Webflow and Dropbox both publish theirs in those places, and Toast lists Zone A/B/C ranges on postings.
- Public calculators. Assume they can disappear. GitLab retired its calculator, and its handbook is now the reference.
- GS locality figures. Re-check OPM's current locality pay area definitions before using the federal benchmark, since percentages can be frozen or changed each schedule.
- Prevalence figures. If you cite survey shares to a recruiter, check the latest WorldatWork geographic pay survey first.
When you're running this across a dozen postings, the zone worksheet tells you where to aim and the recruiter's reply tells you what to ask for. Refolk can then draft a cover letter for each posting that clears the bar, so the number you've just worked out goes out with an application that fits.
Before you name a number
- I ranked the zones by dollar figures, not by letter or number.
- I took every figure from the employer's own posting or careers page, not an aggregator.
- I named the assignment rule: home zip, radius, county, nearest office, or reporting manager.
- I placed my address in one zone, or flagged that I sit on a border.
- I computed my cut at both the minimum and the maximum, and wrote down my zone's midpoint.
- I confirmed whether the range is base, OTE, or total cash, and whether bonus is a percentage of base.
- I checked for any "not available in" or "prioritized" line for my zone.
- For a director-level or higher role, I checked for a floor or exemption.
- I sent the confirmation email and have my zone, scope, and relocation rule in writing.
Questions job seekers ask
What does Zone A, Zone B, Zone C salary mean on a job posting?
It means the employer pays different ranges for the same role depending on where you live or work, and each letter is a group of locations. Usually Zone A is the highest-paid group, often the biggest metros, and later letters pay less. That order isn't guaranteed, though. Avesis's Zone A is its lowest. Find the zone with the highest dollar figures, then check the employer's zone map to see which group your address falls in.
How much less do remote jobs pay based on location?
In the employer postings I checked, the second zone ran about 6 to 13% below the top zone and the third about 12 to 22% below. Block's fourth zone was 17% below its top. Federal GS pay shows a similar gap: Rest of U.S. comes out about 20% below San Francisco. Your actual cut depends on the employer, so work it out from their own posting by dividing your zone's minimum by the top zone's minimum.
Will my salary go down if I move while working a remote job?
It might. Whether it does depends on how your employer assigns zones. More than half of full-time remote workers are tied to where they live, so moving to a cheaper area can move you into a lower zone. In-office and hybrid staff are more often tied to their nearest office (45%) or their reporting location (31%), so a home move may change nothing. Before you move, ask HR in writing how a relocation is handled and when it takes effect.
How can I tell national pay from location-based pay on a remote posting?
A national band shows one range and has no zone or location wording anywhere on the employer's own page. A single range alone proves nothing, because aggregators often merge every zone into one wide range and some employers post the widest range they could pay. Check the employer's careers page for a zone map or a pay-depends-on-location line. If it's unclear, ask whether the range is the same for every US location.
Can I negotiate a geo pay adjustment on a remote offer?
Usually you get more by negotiating where you land inside your zone than by trying to change the zone. Start by confirming you were placed in the right zone, especially near a radius edge or a county line. Then check that the range covers the same scope as the offers you're comparing it with, and look for a director-level floor. Dropbox aims offers between the minimum and the midpoint, so arguing for the upper half of your zone is a concrete ask. I haven't found public evidence of how often employers grant zone exceptions.
Which pay zone am I in if I live just outside a big metro?
That depends on the rule. Under a metro radius like Dropbox's, any address within 100 miles straight-line of a listed metro counts as that metro's zone, so an exurb can land in the top zone. Under a county-based rule, the line is exact and neighbouring counties can be far apart. In the federal system, Calaveras County is in the San Francisco area at 46.34% while neighbouring Tuolumne is at 17.06%. Find out which rule applies before you place your zip.
Put this to work
Paste your career in once. Every application after that is written for you.
Drop a resume or a LinkedIn URL. I rank the live openings against it, rewrite the resume and write a cover letter for the best of them, and fill in the employer's form when you press the button. You read, you decide what goes out.
01Drop your resume
A PDF or a LinkedIn URL. About a minute, once.
02I rank the openings
Every weekday morning, the live catalog scored against your history. Up to 20 worth your time, not two hundred links.
03Each one is written up
Resume rewritten for the posting, a cover letter, a fit score. Press send, or let me fill in the form.
- New matches ranked and written before you are up.
- Every bullet stays inside what your history supports. Nothing invented.
- Queued, submitted, interviewing, offer: one screen, not a spreadsheet.
Free, no card. Up to 25 applications sent a week, and nothing is sent until you say so.