The majority position — and the one most companies currently practice — is to adjust pay to local market rates rather than pay a single global figure. The minority position is that a single global rate is the more principled approach. Both are defensible, and the right answer depends on what a company weights most.

The case for location-adjusted pay (the majority view)

Labor markets are local. The same role commands materially different compensation in San Francisco, Warsaw, and Nairobi — not because the work differs, but because the supply of qualified candidates, local cost of living, and competing employers differ. A company that pays a single global rate set at, say, US-market levels will overpay workers in lower-cost regions relative to what it takes to attract and retain them, burning cash that could fund headcount, product, or benefits. Conversely, a global rate set at a median or lower-cost anchor will make the company uncompetitive in high-cost markets where it needs talent.

The practical refinement — endorsed by one input and worth taking seriously — is that "local market rate" should not mean pure cost-of-living arithmetic. It should mean tiered regional salary bands anchored to actual labor market data for each geography. This is more defensible than a mechanical cost-of-living multiplier, which can produce arbitrary results and is harder to explain to employees.

The case for a single global rate (the dissenting view)

The dissenting position is not merely contrarian. Its core claim: the same role, the same responsibilities, the same output — why should the worker's zip code determine their compensation? Location-adjusted pay effectively penalizes workers for living somewhere affordable, entrenches geographic inequality, and creates a two-tier workforce where colleagues doing identical work earn very different amounts. Companies like GitLab and Buffer have experimented with global or near-global rates precisely because they found the equity argument compelling and wanted to signal that all employees are valued equally. There is also a talent-access argument: a global rate opens the company to candidates who might otherwise be priced out of consideration.

The crux

The disagreement lives on two axes simultaneously:

1. Fairness framing: Is "fair" defined as equal pay for equal work (favoring a global rate), or as pay that reflects the actual market value of labor in each context (favoring local adjustment)? These are genuinely different conceptions of fairness, and neither is obviously wrong.

2. Financial sustainability: A global rate set high enough to be competitive everywhere is expensive; set low enough to be affordable everywhere, it fails to attract talent in high-cost markets. Location adjustment solves this problem but introduces the equity tension above.

What would resolve it

This is not a question that more evidence fully resolves — it turns on what the company values. A company that prioritizes internal equity and wants to signal that geography is irrelevant to an employee's worth should lean toward a global rate (or a narrow band). A company that needs to hire competitively across many markets and must manage costs carefully should lean toward location-adjusted bands. A company that wants both should consider a hybrid: a global floor that is genuinely livable everywhere, with location-based adjustments above it.

One practical note: whatever approach a company chooses, transparency about the methodology matters enormously. Employees who understand the logic — even if they disagree with it — are far less likely to feel arbitrarily penalized than those who discover pay disparities without explanation.