Why Companies Are Hiring From Everywhere But Paying Based on Where You Live

You are a senior backend developer. You passed the same technical interview as a candidate in San Francisco. You solve the same problems, push to the same repository, attend the same sprint meetings, and ship the same features. The person in San Francisco earns $185,000. You earn $45,000. You both work for the same company.

This is not a hypothetical. It is the standard practice at hundreds of companies that hire globally. They call it "localized compensation" or "geo-adjusted pay." Workers in developing countries have a more direct name for it: the location discount.

This article examines how geo-based pay actually works in 2026, what the real salary differentials look like, how companies justify it, and what it means for professionals in Nigeria, India, the Philippines, Egypt and Pakistan who are increasingly doing the same work as their colleagues in high-cost countries. It also lays out, with numbers, what the discount costs you over a full career and the four routes people are taking out of it.

How Geo-Based Pay Works in Practice

Most companies that hire globally use one of three compensation models.

Model 1: Cost of Living Adjustment (COLA)

The company sets a base salary for a role (usually benchmarked to US rates) and then applies a multiplier based on where you live. The multiplier is derived from cost of living indices.

Example: Senior Software Engineer Base = $160,000 (San Francisco)

Notice the ratios. A developer in Lagos earns 25 cents on the dollar compared to San Francisco. In Lahore, it is 20 cents. The work output is identical.

One thing to watch: the multiplier is rarely audited by the worker. Cost-of-living indices vary wildly between providers (Numbeo, Mercer, the company's own internal data), and the version the company picks is usually the one that produces the lowest number. Two engineers in the same city, hired 18 months apart, can end up on different multipliers simply because the benchmark was re-run.

Model 2: Local Market Rate

The company does not start from a US base at all. Instead, they benchmark against local market salaries in each country and offer a premium above that. This is often described as "competitive local pay."

Example: Senior Software Engineer local market rates and typical remote company offers

This model feels generous because you are earning 2-3x what you would locally. But compared to US or European compensation for identical work, you are earning 20-35% of the total package. It also quietly ties your pay to the weakest reference point available: the local median, which in several of these countries has been eroded further by currency depreciation since 2023.

Model 3: Equal Pay Everywhere

A small number of companies pay the same rate regardless of location, or apply only a light location factor. These include:

These companies are the exception. The vast majority of remote-first companies, including large ones such as Shopify, Spotify, Stripe and Meta, apply location-based adjustments. Buffer, long cited as the poster child for location-independent pay, moved in 2023 to a system that still contains a location band, so "equal pay everywhere" describes fewer employers today than the phrase suggests.

Real Salary Data: Same Role, Same Company, Different Countries

Let us look at salary bands that have been publicly disclosed, reported on platforms like Glassdoor, Levels.fyi and Blind, or shared in compensation transparency reports. Figures are total compensation ranges as of early 2026 and will vary by company and negotiation.

Software Engineering (Mid-Senior Level)

All figures in USD unless noted. TC = total compensation including equity.

Product Design (Senior Level)

Data Science / ML Engineering (Mid-Senior)

The pattern repeats across every discipline. The higher the equity component of the role, the wider the gap becomes, because equity grants are usually scaled by base salary. We come back to that below.

For a deeper single-corridor breakdown with take-home figures, see our Naira vs dollar tech salary comparison.

The Company Justification (And Where It Falls Apart)

Companies give several reasons for geo-based pay. Let us examine each one honestly.

"Cost of living is lower, so you don't need as much"

This is the most common argument. Rent in Lagos is cheaper than rent in San Francisco, so a lower salary goes further.

There is some truth here. Monthly living costs for a comfortable middle-class lifestyle:

But the argument breaks down when you examine what cost-of-living adjustments actually measure versus what they exclude.

What COLA captures: rent, groceries, transport, utilities, local services.

What COLA does not capture:

• International travel (same price everywhere)
• Technology (an iPhone or a MacBook costs the same, often more, in Lagos as in London)
• Quality healthcare (frequently more expensive in developing countries when you want international-standard care)
• Children's international education (same or higher cost)
• Savings and investment (your savings rate is what matters, not your spending rate)
• Property as an investment (global real estate markets do not adjust for your local salary)
• Retirement planning (you need roughly the same absolute amount to retire comfortably)
• Currency risk (your local currency may lose 20-50% against the USD in a single year)

That last point is not theoretical. The Nigerian naira lost more than 60% of its dollar value across 2023-2024 after the currency was floated, and the Egyptian pound was devalued sharply over the same period. If your salary is quoted in local currency, a "generous" number can shrink in real terms while you sleep. Workers who negotiate USD-denominated pay protect themselves from this; many contracts do not offer that option.

Let us illustrate with real numbers. A Nigerian developer earning $40,000 and a US developer earning $160,000:

The developer in Lagos earns 25% of the SF salary but saves only about 16% as much in absolute terms. Over a 20-year career the SF developer accumulates well over $1.2M in savings; the Lagos developer accumulates a fraction of that. Both did exactly the same work. We break the day-to-day version of this down further in Lagos vs London: the real numbers.

"We pay well above local market rates"

This is true, and it is why many remote workers initially feel grateful. Earning $40,000 in Lagos when local companies pay $12,000-$18,000 is transformative.

But the comparison to local market rates is misleading. You are not doing local market work. You are doing work that generates the same value as someone in San Francisco. The company is not paying you based on the value of your output. They are paying you based on the accident of your coordinates.

"The labour market sets the price"

Some companies argue they simply pay what the market requires. If they can hire excellent engineers in Nigeria for $40,000, why would they pay $160,000?

This is economically rational from the company's perspective. It is also the core of the problem. The labour market for remote work is not a free market. It is distorted by:

• Visa restrictions that prevent workers from relocating freely
• Credential recognition barriers
• Banking and payment infrastructure limitations
• Time-zone preferences that create unequal bargaining power
• Information asymmetry about compensation at other companies

If the Nigerian developer could freely relocate to San Francisco, the company would have to pay the SF rate to retain them. The location discount exists precisely because mobility is restricted. That is also why relocation, covered below, is the one move that resets the entire equation. See remote work abroad vs migrating for how the two paths diverge.

The Real Impact: A Career-Length Analysis

Let us model what geo-based pay means over a full career. Consider two developers who start at the same time with equivalent skills.

Developer A: based in Bangalore, India. Works remotely for US companies. Strong performer, promoted at the same rate as peers.

Developer B: relocates to Toronto, Canada. Works for the same kinds of companies in-person or hybrid.

Developer B earned roughly $970,000 more over 15 years. Even accounting for higher living costs in Toronto (roughly $15,000-$20,000 more per year), Developer B is ahead by $650,000-$720,000 in cumulative savings.

And this does not account for:

• Employer-matched retirement contributions (typical in Canada: 3-6% match)
• Stock options and equity (significantly larger grants for higher-base employees)
• Health and dental insurance (largely employer-paid in Canada)
• Employment insurance and government benefits
• Mortgage access (a functioning banking system versus mortgage rates of 20%+ in Nigeria or double digits in India)
• A pathway to citizenship and a stronger passport, which compounds across the next generation

The Equity Gap Is Even Worse

For tech companies a significant portion of compensation comes through equity (stock options or RSUs). Here is where the location discount becomes most extreme, because grants are scaled off base salary.

A US-based staff engineer might receive $105K-$155K in equity annually. Their counterpart in India might receive $10K-$20K. If the company's stock appreciates 3x over five years (common for successful startups), the US engineer gains $315K-$465K in stock appreciation. The India-based engineer gains $30K-$60K. Same code, same product, a tenfold difference in wealth created from ownership.

How Companies Are Structured to Maintain This

The geo-based pay system is reinforced by several structural mechanisms.

Compensation Bands by Zone

Most global companies divide the world into compensation zones:

Moving between zones usually requires relocation and a fresh offer. Some companies even reduce pay if you relocate from a higher zone to a lower one. Google and Meta both introduced location-based pay adjustments for employees who moved away from expensive offices, and the policy remains in force.

Salary Transparency Laws Are Not Global

In the US, pay transparency laws in states such as Colorado, California, New York, Washington and Illinois (whose posting requirement took effect in 2025) now require companies to publish salary ranges on many job listings. The EU Pay Transparency Directive will push similar rules across member states, with national laws due to be in place by June 2026. But these ranges apply where the law reaches. The same company posting a $150K-$210K range for a US-based engineer has no obligation to disclose what it pays for the same role in Nigeria or India.

This information asymmetry is powerful. US and EU-based employees can negotiate against disclosed ranges and peer benchmarks. Remote employees in developing countries often have no idea what their counterparts earn for identical work.

The "You Can Always Leave" Argument

Companies know that, even with a location discount, they are offering far more than local alternatives. A Nigerian developer earning $40,000 has limited leverage to demand $80,000 because:

1. Local alternatives pay $12,000-$18,000
2. Other remote-first companies also apply location discounts
3. The pool of companies willing to pay "equal pay everywhere" is tiny
4. Visa restrictions prevent the developer from simply relocating

This creates a market where the buyer (the company) holds structural power over the seller (the worker) — not because of any skill difference but because of mobility restrictions.

What Workers Are Doing About It

Remote workers in developing countries are responding to geo-based pay in several ways. Some are far safer than others.

Strategy 1: Using VPNs and False Locations

Some workers misrepresent their location to qualify for higher pay bands, claiming to be in Lisbon or Dubai while actually working from Lagos or Bangalore. This is risky. It can be grounds for immediate termination, may constitute contractual fraud, and creates serious tax exposure in both the claimed and the actual country. Payroll providers increasingly flag mismatched IP, banking and tax-residency data, so the approach is also becoming easier to detect. We do not recommend it.

Strategy 2: Working for Multiple Companies

Because they are often paid as contractors, some workers take on two or three "full-time" remote positions at once. At $35,000-$50,000 each, three positions can yield $105K-$150K. This practice, sometimes called "overemployment," is growing. It works until deadlines overlap, an on-call rotation collides, or an employer discovers the arrangement and enforces an exclusivity clause. It also multiplies your tax filing and, in many contracts, breaches the agreement you signed.

Strategy 3: Building Location-Independent Businesses

Rather than working for foreign companies at a discount, some professionals build their own products, agencies or consultancies that charge global rates. A Nigerian design agency can charge US clients $150-$200/hour — the same rate as a US agency — when the work quality matches. The trade-off is that you take on sales, client risk and irregular cash flow in exchange for removing the location cap on your income.

Strategy 4: Relocating

This is the most definitive response. When the gap between remote pay from a developing country and on-site pay in a developed country is large enough, and once you factor in career progression, equity, benefits and long-term wealth building, many professionals conclude that relocation is the economically rational choice.

The math often looks like this:

When you frame it this way, the relocation cost of $15,000-$25,000 is recovered inside the first year. Every subsequent year is upside — plus benefits, equity, and a route to permanent residence that the remote path never provides.

If you are weighing this, Canada's points-based system is one of the more accessible routes for engineers and other in-demand professionals. Start with our Canada Express Entry guide for developing countries and the migrate to Canada overview.

A Practical Playbook If You Are Stuck on the Discount

If relocation is not yet on the table, you still have moves. In rough order of leverage:

• Get paid in a hard currency. Insist on USD or EUR-denominated pay to remove the currency-depreciation tax. This is often the single highest-value negotiation you can win.
• Benchmark against the role, not your city. When you renew or interview, quote the company's own US or EU band (much of which is now published by law) as your anchor, not the local median.
• Target "light location factor" employers. GitLab, Oyster, Automattic and 37signals publish or minimise their location adjustment. There are more each year; find them before you accept the first offer.
• Push equity, not just base. If base is capped by zone, negotiate a larger equity grant or a signing bonus, where the location multiplier is often applied less strictly.
• Understand your tax position early. Working for a foreign company as a local contractor has real filing consequences. Our tax trap for remote workers guide covers the traps before they cost you.
• Keep a relocation option warm. Even if you stay, maintaining IELTS scores, an up-to-date CV of quantified impact and a document file (references, degree evaluations) means you can move fast when a sponsored role or a points-based opening appears.

Frequently Asked Questions

Is geo-based pay legal? Yes. Paying different salaries by location is legal in essentially every jurisdiction, provided the difference is based on location and not on a protected characteristic such as race, sex or nationality. It is a business practice, not a breach of employment law.

Do any big companies really pay the same everywhere? Very few. 37signals (Basecamp) benchmarks globally to a top US market rate, and Oyster runs single global bands per role. Most others, including firms once famous for location-independent pay such as Buffer, now apply at least a location factor. "Equal pay everywhere" is rarer in 2026 than the marketing suggests.

If I move to a cheaper city, will my company cut my pay? It can, if it operates zoned bands. Google and Meta both adjust pay for employees who relocate away from high-cost offices. Check your contract's remote-work clause before moving.

Is claiming a fake location worth the risk? No. It can be grounds for dismissal, may be treated as fraud, and creates tax problems in two countries at once. Payroll and tax-residency checks make it increasingly easy to catch. Pursue hard-currency pay, better employers or relocation instead.

Does relocating actually beat a high remote salary? Usually, once you count equity, benefits, retirement matching, currency stability and a path to residence and citizenship. The one-time relocation cost is typically recovered within a year, and the cumulative gap over a decade runs into the hundreds of thousands. See remote work abroad vs migrating.

The Bigger Picture

Geo-based pay is not going away. Companies have strong financial incentives to maintain it, and the global labour market lacks the mechanisms to correct it. There is no global minimum wage for remote workers, no international labour-standards enforcement, and no free movement of workers across borders.

But understanding the system is the first step. When you know exactly how much the location discount costs you — not just in today's salary but in career-long wealth accumulation, equity and currency risk — you can make informed decisions.

Some of those decisions involve negotiating harder. Some involve choosing employers who minimise the discount. Some involve building independent income streams that charge global rates. And some involve changing your location entirely, so the discount no longer applies.

The companies hiring from everywhere but paying based on where you live are not doing anything illegal. But they are benefiting from a system that systematically transfers value from workers in developing countries to shareholders in developed ones. Understanding that transfer is essential to deciding what to do about it.