Global pay arbitrage is the gap between what your skills earn in the strongest market that will hire you and what they earn where you happen to live. Remote work made that gap tradeable: you can now sell your work into a rich labour market while spending your income in a cheap one, and the difference is yours to keep.
That’s the whole concept in two sentences. The rest of this piece is about how big the gap actually is, who ends up capturing it, and how to run the trade without getting burned on tax, contracts, or the version of arbitrage that works against you.
How location-based pay actually worked before remote
For most of economic history, your salary had a zip code. Employers priced jobs against the local market: what the company across the street would pay for the same person. A great accountant in Lisbon earned Lisbon wages and a mediocre one in Zurich earned Zurich wages, because neither could sell their labour anywhere else without physically moving. Moving meant visas, upheaval, and the full cost of restarting a life, so almost nobody did it, and local wage levels held.
This wasn’t a conspiracy. It was a market with high walls. Labour was the one major input companies couldn’t source globally. Capital moved, goods moved, supply chains moved. Workers stayed put, so their price stayed local.
Then, between 2020 and roughly 2023, a large slice of knowledge work proved it could be done from anywhere with a laptop and decent internet. The walls didn’t fall for everyone (nobody is fixing a boiler over Zoom), but for software, design, data, marketing, finance operations, and writing, the local-market pricing model quietly lost its enforcement mechanism. Most people still haven’t priced that in. If your pay has felt stuck for years despite doing good work, this is one of the structural reasons: we cover the others in why your salary stopped growing.
The same developer, five price tags
Here’s the arbitrage made concrete. Take one mid-level software developer, identical skills, identical output, and price them five different ways:
| Situation | Approximate annual pay |
|---|---|
| Local job in Lisbon | $35,000 |
| Local job in Berlin | $75,000 |
| Local job in London | $90,000 |
| Remote for a US company, living anywhere | $140,000 |
| On-site in San Francisco | $220,000 |
Same human, same code, a 6x spread from top to bottom. You can see the full country-by-country breakdown in our software engineer salary comparison, and the Germany-specific data shows how much variation exists even inside one country.
The row that matters is the fourth one. The San Francisco engineer earns the most on paper, but pays San Francisco rent, San Francisco childcare, and California taxes. The remote-for-US engineer in row four keeps Lisbon or Berlin living costs while earning a near-US salary. After housing and taxes, the person in row four frequently has more disposable income than the person in row five. The gap between where you earn and where you spend is the entire game.
Who captures the spread
The spread between $35k and $140k doesn’t vanish. Someone pockets it, and the split depends on the employer’s pay policy. There are two models, and knowing which one you’re negotiating against changes everything.
Location-adjusted pay. The company sets a benchmark (usually its home market) and applies a discount based on where you live. A role benchmarked at $160k in the US might pay 65% of that in Portugal. Here the employer captures most of the spread: they get the same work for $60k less and frame the discount as fairness (“we pay competitively for your market”). It’s not fairness, it’s procurement. GitLab publishes its location multipliers openly; most companies apply them silently.
Location-agnostic pay. The company pays the same rate for the same role regardless of address. Here the worker captures the spread, which is why these roles are scarcer, more competitive, and worth actively hunting for. Companies that pay this way usually do it because they’re competing for genuinely scarce skills and can’t afford to lose a great candidate over a geography discount.
Most companies never volunteer which model they use, and the difference can be worth $50k a year for the identical job. Asking “is this role benchmarked to a single global band or adjusted by location?” is a legitimate, professional question, and the answer tells you exactly how hard to negotiate. This is one of many quiet mechanics employers rely on you not knowing; the hidden rules of pay covers the rest of them.
How to actually run the trade
If your work travels, here’s the playbook, in order.
-
Build skills that travel. The arbitrage only pays when the buyer competes for you. Skills with global demand and objective proof of output work best: software engineering, data, product design, growth marketing, technical writing. If you’re weighing a career switch with this trade in mind, software engineering remains the highest-liquidity option, because output is portable and provable.
-
Solve the time zone problem before they ask. Distance is free; time zone gaps are not. A developer in Lisbon has a 4–5 hour overlap with the US East Coast, which is workable. A developer in Manila working for a New York company is answering standups at 10pm. European and Latin American workers targeting US employers have a structural edge here, and you should state your overlap hours in your application before anyone asks.
-
Decide: contractor or employee. US companies hire abroad two ways. Employer-of-record platforms (Deel, Remote.com, Oyster) make you a legal employee in your own country: pension, protections, cleaner taxes, usually a slightly lower headline rate. Direct contracting pays more gross but hands you the tax filing, invoicing, and zero severance. Early career, take the EOR employment. Established with savings, contracting often nets more.
-
Fish where the arbitrage roles are. Location-agnostic and remote-first companies concentrate in specific places: remote-only job boards, US startups between seed and Series C (big enough to pay, too small for a compensation bureaucracy), and open-source communities where your work is already visible. Cold-applying to Fortune 500 postings is the lowest-yield route, because those companies almost always location-adjust.
-
Anchor to the buyer’s market, not yours. The most expensive mistake in this entire trade: a developer earning $40k locally receives a US remote offer and negotiates up from $40k. The company priced the role in dollars against US alternatives. Negotiate down from $140k, not up from $40k. Run the numbers on what any offer is actually worth after tax in your country with our salary calculator, and once you land the role, your first three months set your trajectory: here’s how to play the first 90 days.
The reverse arbitrage: it cuts both ways
Now the part remote-work evangelists skip. The same logic that lets you sell your work into a richer market lets your employer buy the work from a cheaper one. If your job can be done from Porto for less, your company’s CFO eventually runs the same spreadsheet you did.
This is already happening at scale. US companies that went remote in 2020 discovered by 2023 that their “remote” hiring pool didn’t stop at the US border. Routine QA, standard design production, basic bookkeeping, tier-one support: work that is fully remoteable and fully interchangeable is drifting toward a global market-clearing wage, not an American one.
For high-cost-city workers, the implication is uncomfortable but simple: your location premium is no longer paid automatically. A $150k salary in New York for work that an equally skilled person in Warsaw does for $60k is not a stable equilibrium; it’s a pending line item. The defense is the same as the offense: be hard to substitute. Seniority, specialized domain knowledge, ownership of relationships and decisions, work that requires trust built over years. The arbitrage pays people who are scarce. Interchangeable workers don’t capture the spread; they become the spread.
The honest boundary: none of this touches most of the economy. Healthcare, trades, logistics, hospitality, anything involving a physical human or object is structurally immune, in both directions. Nobody in another country can rewire a house in Leeds.
The tax and legal part nobody wants to read
Two things can quietly eat 20% or more of the arbitrage, so handle them before signing.
Tax residency. You generally owe income tax where you live, not where your employer sits. Spend 183+ days in a country and you’re almost certainly tax-resident there, whatever your contract says. Digital-nomad setups that “forget” this work right up until they don’t; tax authorities in Portugal, Spain, and elsewhere have gotten noticeably better at noticing foreign payroll income. Know your residency, file where you live, and check whether your country has special regimes for foreign-sourced income before you assume the sticker salary is yours.
Contractor status. If you invoice one company, full-time, on their schedule, with their equipment, many countries will classify you as a de facto employee regardless of the contract’s label. Misclassification risk lands mostly on the company, but the mess (back taxes, frozen contracts, abrupt termination) lands on you. This is exactly the problem EOR platforms exist to solve, and why serious US employers increasingly insist on them.
One session with a cross-border accountant costs a few hundred dollars and typically pays for itself many times over in the first year. Do it before you sign, not at filing time.
Geography used to be destiny in pay. Now it’s a variable you can set deliberately. Start by finding out what your skills are worth in every market that could hire you, not just the one you live in: our global salary data covers exactly that. The people winning the next decade of remote work aren’t the ones with the best home office. They’re the ones who noticed their salary and their cost of living no longer have to share an address.