Remote work changed salary negotiation in ways that most people haven't fully worked out yet. The old model was simple: you applied for a job in your city, the company offered a salary benchmarked against local market rates, and you negotiated within that framework. Remote work dismantled the geographic anchor on both sides of that equation.
Now you can apply for a London role from Barcelona. A US startup can hire you without expecting you to relocate. A Dutch company can offer you a contract while you work from Warsaw. This creates significant opportunity — and a set of new negotiation challenges that require different preparation and different arguments.
This guide covers how to approach salary negotiation as a remote worker: what data to use, how to handle location-adjusted pay policies, and how to make the strongest possible case for compensation based on the value you deliver rather than where you sit when you deliver it.
Understand what model the company uses — before you negotiate
The first step in any remote salary negotiation is understanding which compensation philosophy the company operates under. There are three common models:
- Location-based pay: Your salary is set based on the cost-of-living index for your location. A London-headquartered company might pay you 60–70% of their London rate if you're based in Madrid. This is common at larger, more process-oriented companies.
- Company-location pay: Everyone is paid the same regardless of where they live — based on the company's headquarters location or a fixed global rate. More common at early-stage startups and companies that have deliberately committed to remote-first as a hiring strategy.
- Role-value pay: Salary is set based on what the role is worth to the company and what it would take to hire the best person — regardless of geography. The least systematic approach, but often the most negotiation-friendly for candidates.
Ask directly in the interview process, before you reach the offer stage: "How do you handle compensation for remote employees based in different locations?" This is a professional, reasonable question that tells you immediately what framework to expect and what your negotiating room looks like.
The location-adjusted pay debate
Location-adjusted pay is a legitimate business decision, and it's worth understanding the argument honestly before you push back on it. The logic: if you live in a lower cost-of-living location, you need less gross salary to maintain equivalent purchasing power. A €80,000 gross salary goes further in Warsaw than in Amsterdam. A company that pays everyone London rates regardless of location may be over-paying people in low-cost locations — or under-paying people in high-cost ones.
The counter-argument — and the one you should understand well if you're being offered location-adjusted pay — is about the value of your work, not the cost of your life. The code you ship, the analysis you produce, the deals you close: these have a fixed value to the company regardless of where you sit when you do them. Paying you less for the same output because your rent is cheaper isn't adjusting for value — it's capturing part of your cost-of-living advantage for the company's benefit.
The strongest version of this argument: "I understand your cost-of-living adjustment logic, but I'd prefer to discuss compensation based on the market rate for this role and my experience. The value I deliver isn't location-dependent." This doesn't always work — some companies have hard policies — but it's the right framing.
What data to use in a remote salary negotiation
In a traditional local-hire negotiation, the relevant benchmark is the market rate in your city. In a remote negotiation, the relevant benchmark depends on the company's pay model — and you have more flexibility to argue for the benchmark that's most favourable to you.
If the company uses company-location pay: Benchmark against the market rate in the company's headquarters city. If you're negotiating with a London company, you're competing against London-based candidates for the same role. The London market rate is the relevant comparison.
If the company uses role-value pay: Use whatever benchmark is most accurate for the role's market value. If you're a senior software engineer, the global (or at least European) market rate for senior engineers is a fair anchor — regardless of where you live.
If the company uses location-based pay: You still have room to negotiate within the band for your location. Know the market rate for your role in your local market, and push to the top of that band rather than accepting the middle or bottom.
Use our free salary checker to benchmark your role against multiple European markets — which gives you the data to argue for the most relevant reference point in your negotiation.
Negotiating a pay increase if you move to a lower cost-of-living location
If you're currently employed and planning to relocate — or requesting permission to work remotely from a different country — expect your employer to raise the question of location-adjusted pay. Some will proactively propose reducing your salary. Others will leave it unaddressed until you raise it.
If you're moving to a lower-cost location, the best position is to address it proactively: "I'm planning to relocate to [city]. I know some companies adjust salaries for location — can you help me understand how you handle this?" Getting this in writing before you move is far better than discovering a surprise reduction afterwards.
If they propose a reduction, your position: "I'd prefer to keep my compensation at its current level. My output and responsibilities aren't changing with the move — I'm delivering the same value to the team." Whether this works depends heavily on the company's culture and how firm their policy is, but it's the right opening position.
Negotiating with a company in a higher-salary country while based elsewhere
This is the scenario where remote work creates the clearest opportunity for salary uplift. You live in Barcelona (median mid-level software engineer salary: ~€52,000). A London company hires you remotely. Even with a location adjustment applied, their sense of what "reasonable" compensation looks like is anchored to their London market (median: ~£90,000).
In practice, many such arrangements land somewhere between the two markets — often significantly above what a locally-employed person in your city would earn. The negotiation strategy:
- Understand what the role pays for someone in the company's HQ market
- Open at a number that's ambitious relative to your local market but reasonable relative to theirs
- Anchor your arguments to your deliverables and your qualifications, not your cost of living
- Be explicit about the arrangement's advantages to the company: they get strong talent at a lower cost than a local hire — that's a trade-off worth naming
The tax and contractor dimension
If you're hired as an independent contractor (rather than an employee) by a foreign company, the gross vs. net comparison changes significantly. As a contractor, you're typically responsible for your own social security contributions, pension, health insurance, and taxes — costs that an employer would normally cover partially or wholly.
Before accepting a contractor rate, calculate your true net: gross rate minus tax, social security, health insurance, pension, and any professional costs (accounting, insurance, equipment). A €70,000 contractor rate may net out to less than a €55,000 employed salary once these are accounted for — depending on your location and setup.
If negotiating a contractor rate, factor in these overhead costs explicitly. A rule of thumb: contractor day rates should be 30–50% above what an equivalent employed salary would translate to per day, to account for benefits, tax complexity, and income volatility.
What employers often don't want you to know
Many companies have more flexibility on remote compensation than their initial policies suggest. The policies that exist are often written for the median case — they weren't designed for your specific situation, your specific skills, or the difficulty they'd have replacing you.
If a company wants you badly enough, they'll find a way to make the compensation work. The people who get above-policy outcomes are those who ask clearly, provide solid rationale, and are genuinely prepared to walk away if the number doesn't work. The people who don't are those who accept the first offer because they don't want the discomfort of pushing back.
Come to the conversation with data. Check your market rate for your role and the relevant reference market before you negotiate — and know your walkaway number before you enter the conversation.