The question remote work forces on you
The moment you hire someone who works from a different city than your office, an old assumption breaks: that a job has a salary. Now the same role might be filled by someone in a high-cost metro and someone in a low-cost small town, and you have to decide whether — and how — where they live changes what they earn. There's no consensus answer, big companies do it every possible way, and the choice you make shapes both your budget and how fair your team perceives your pay to be.
This is a framework for reasoning about geographic pay, meant to sit alongside your work on compensation bands. It is general compensation guidance, not legal advice — pay decisions intersect with pay-equity and pay-transparency law, and those specifics deserve their own attention.
The three postures
Companies land in roughly one of three camps, and it helps to name yours deliberately rather than drift into one:
- Location-based pay. You define geographic tiers (or index to local market data) and pay the same role differently depending on where someone lives. A high-cost metro pays more than a low-cost region for identical work. This is what most large companies do, because it tracks local labor markets and controls cost.
- Location-agnostic pay. The role pays the same regardless of location — often set to a single high or national-market number. Simpler, perceived as fairer by employees, and a genuine recruiting edge for candidates in lower-cost areas. More expensive, and you may "overpay" relative to local markets in cheaper regions.
- A hybrid. A national band with a modest geographic adjustment at the extremes, rather than a fine-grained tier for every zip code. Many small companies land here because it captures the biggest cost differences without the overhead of a complicated matrix.
None is "correct." Location-based controls cost and matches markets; location-agnostic wins on simplicity and perceived fairness. Pick the one whose tradeoffs you can live with and, critically, explain.
If you go location-based, make the rule mechanical
The danger with location-based pay isn't the concept — it's applying it by hand, case by case, which is how you back into a discrimination or pay-equity problem. If two employees in the same city doing the same job at the same level earn different amounts and the only explanation is "that's what we negotiated," you have a defensibility problem waiting to surface in a pay-equity audit.
Make it a formula, not a negotiation:
- Define the tiers or the index up front and write down which locations map to which. Employees in the same tier and role get the same band. The geography adjusts the band; it doesn't license case-by-case improvisation.
- Decide the rule for someone who moves before it happens. If an employee relocates from a high-cost to a low-cost area, does their pay change? Reasonable companies answer both ways, but you must answer consistently — a policy applied to everyone, not renegotiated per person and per mood.
- Keep the band tied to the role, not the person. Location shifts the band; the person's level and performance place them within it. Muddying those keeps you from being able to explain any given number.
Transparency changes the math
Pay-transparency laws — spreading fast across states and cities — increasingly require a salary range in the job posting itself, and remote roles are the hardest case because "the range" now depends on location. A remote posting open to candidates in several states may be subject to the disclosure rules of each of those states. Practically, this pushes many companies toward posting a single honest range that spans their geography, or toward simpler geographic structures precisely because a fine-grained tier matrix is painful to disclose cleanly.
The deeper point: geographic pay is getting harder to keep quiet, and a structure you'd be uncomfortable explaining to the whole team is a structure with a problem. Build one you could publish. For the underlying obligations, see salary transparency laws — and treat the specifics as a moving target that warrants current, jurisdiction-specific advice.
Multi-state hiring drags along more than pay
Geographic pay is one thread of a bigger knot: the moment you employ someone in a new state, you inherit that state's rules — tax registration, wage-and-hour law, required notices, sometimes paid-leave mandates — regardless of where your office is. Don't let a location-based pay conversation obscure the location-based compliance one. The full picture lives in hiring across state lines; the pay differential is the visible tip of a larger obligation.
Retention is where this quietly bites
Geographic pay is usually framed as a hiring and budgeting question, but its sharpest edge is retention. Two failure modes:
- The pay-cut-by-moving surprise. An employee relocates for family reasons, discovers their pay drops under a location policy they didn't know applied to moves, and feels blindsided. The policy might be perfectly defensible — the surprise is what corrodes trust. Communicate the move rule before anyone needs it.
- The fairness murmur. Teammates doing the same work for visibly different pay, with no explanation they find legitimate, is a slow-acting morale problem. If your structure is sound, explaining it — this is a tiered market-based policy, here's the tier map, here's how your number was set — turns a resentment into an understood tradeoff. Pay you can't explain is pay that erodes retention, which is why this belongs next to your broader retention strategy.
Where the product fits
Hosting HR keeps compensation attached to structure instead of memory. Your bands and tiers live where the role lives, so an offer is generated against a defined band rather than improvised, and the reasoning — level, tier, where in the band and why — stays on the record. When you run a fairness check across a role, you're comparing against a documented structure in reports, not reconstructing a dozen one-off negotiations from old emails. Consistent, explainable pay is a retention tool; making it consistent by design is how you avoid the version that quietly drives people out.