CA 
VA 
EU 
GL 
Remote-only vs remote-friendly companies pay on opposite logic: remote-only employers use global salary bands anchored to a target market (often US-FAANG or Euro-tier1), so a senior dev in Lisbon earns the same as one in Berlin or Stockholm. Remote-friendly employers (a.k.a. “remote-first” or hybrid-distributed) use HQ-city anchored bands + a location discount (typically 10-30% off HQ rate if you live in a lower-cost EU country). The same role with the same posted band (€75k-€95k) can deliver €95k from a remote-only employer and €75k from a remote-friendly EU one — IF you live outside the HQ city. The signal lives in 3-5 specific job-ad phrases.
TL;DR — how to tell them apart from the job ad alone
| Phrase / Signal | Remote-only ladder | Remote-friendly ladder |
|---|---|---|
| Job ad says “fully distributed” / “no HQ” / “async-first” / “team in 12 countries” | ✅ Strong signal | ❌ Rare |
| Job ad says “remote-friendly” / “remote-first” / “hybrid” / “occasional travel to HQ” | ❌ Rare | ✅ Strong signal |
| Company HQ named prominently (e.g. “we’re a Berlin-based startup”) | ❌ Weak | ✅ Strong signal |
| Salary band given without location qualifier (“€75-95k for senior backend”) | ✅ Likely | ❌ Rare |
| Salary band given WITH location qualifier (“€75-95k Berlin / €60-78k Madrid”) | ❌ Rare | ✅ Strong signal |
| Equity offered as a band (% range) regardless of location | ✅ Likely | ❌ Rare |
| ”Working hours overlap with CET / GMT / etc.” in requirements | Neutral | Slight remote-friendly tilt |
| Public salary calculator on careers page | ✅ Most remote-only post their formula | ❌ Most remote-friendly hide it |
Examples (illustrative 2026 archetypes — verify per-company):
- Remote-only: GitLab, Buffer, Doist, Zapier, Automattic, Wise (early days), Toggl, Charity Water
- Remote-friendly: most EU startup-scale companies (Mollie / Personio / Klarna / Trade Republic / Vinted / Bolt — HQ-anchored bands with location adjustments)
Negotiation implication: at a remote-only employer your leverage is on the band itself + level placement. At a remote-friendly employer your leverage is also on which “location bucket” you’re placed in — sometimes you can negotiate up a tier by living in a higher-cost EU city or by referencing a competing remote-only offer.
Two companies post nearly identical job ads: “Senior Backend Engineer, 100% Remote, €75k–€95k.” The compensation looks the same. The working patterns look the same. But they’re paying on two fundamentally different logics, and that distinction will shape your career for the next 5 years — not just your next paycheck.
The Two Models
Remote-Only (distributed-first)
The company has no headquarters or treats HQ as “just another node.” Everyone works remotely by default. Meetings are asynchronous-first. The company was designed for distribution.
Examples: GitLab, Automattic, Doist, Remote, Buffer, HashiCorp’s platform team, Zapier, Loom, early-stage Y Combinator companies going remote-first from day zero.
Remote-Friendly (HQ-with-remote)
The company has a real headquarters (or 2-3 hub offices) and a cluster of remote employees. Core meetings still happen in the HQ time zone. Promotion decisions happen in person. The company allows remote as a concession.
Examples: the vast majority of tech companies in Europe today — Zalando, Klarna, Adyen, Booking, Delivery Hero, most US-headquartered companies hiring their first European employees.
How They Set Salary (the Real Difference)
This is where the two diverge, and it’s almost never stated in the job ad.
Remote-Only: global bands with geographic multipliers
A remote-only company sets a single global band for “Senior Backend Engineer” (say, $110k–$150k in a global base currency), then applies a cost-of-living multiplier per country:
- USA Tier-1 city: 1.0× (anchor)
- Germany: ~0.70–0.80× → €77k–€105k
- Spain: ~0.55–0.65× → €60k–€82k
- India: ~0.35–0.45× → €38k–€55k
The multipliers are published internally (often externally too — GitLab and Remote have public comp formulas). You can look up your country’s multiplier before you interview. The same role = different pay across geographies, but the philosophy is transparent and defensible.
Key insight: your peer benchmark inside a remote-only company is global, not local. A Berlin-based engineer at GitLab is in the same role band as a São Paulo-based engineer doing the same work. The multiplier is the only thing that differs.
Remote-Friendly: HQ anchor with a discount
A remote-friendly company sets the band at HQ market rate, then discounts remote hires in other cities by 5–20%. The discount is justified with vague phrases like “cost of living adjustment” or “regional market.”
This is where it gets opaque. A Berlin-headquartered company hiring a Berlin senior backend might pay €95k. The same role for a Spain-based remote hire might pay €78k — officially “Spain market,” but really “Berlin rate minus what we think we can get away with.”
The benchmark isn’t global; it’s HQ. Your pay is a discount off your HQ colleagues’ pay, not a standalone global band. That has two compounding problems:
-
Promotion politics: HQ employees are “at the anchor.” You’re “discounted from the anchor.” Even if your work is equivalent, comp-benchmarking conversations at review time feel like “how much can we get away with paying the remote person?” not “what is this role worth globally?”
-
You’re the balancing variable: when the company has a down quarter, HQ comp is protected (they’re the culture). Remote comp bands are where the budget gets tightened.
Three Signals to Tell Them Apart Before You Apply
The job ad usually doesn’t spell this out. Here’s how to decode it:
Signal 1: Where does the team work?
Ask the recruiter: “Of the engineering team I’d be joining, what percentage works from a single office regularly? How often does the team have in-person offsites?”
- “100% remote, nobody in office, offsites once or twice a year” → remote-only
- “40% in our Berlin office, we do weekly team days” → remote-friendly dressed as remote
Signal 2: What’s the offer-letter pay location tied to?
Ask: “Is this band specific to my country or is it a global band with a country adjustment?”
- “Global band, country multiplier published in our handbook” → remote-only
- “This is the band for [your country]” with no global reference → remote-friendly
Signal 3: Are promotions independent of location?
Ask: “When you promoted someone from Senior to Staff last year, was location a factor? Can a fully-remote engineer become a Director without relocating?”
- “Yes, two of our current VPs are fully-remote” → remote-only
- “Hmm, that’s a good question, let me check” or “most leaders are in HQ” → remote-friendly
How to Negotiate Differently at Each Type
At a remote-only company
- Look up their published comp formula (GitLab, Remote, Buffer all publish; most others publish internally — ask).
- Benchmark yourself at the level band, not the geography, because that’s the conversation internally.
- The negotiable axis is which level they slot you at, not the cash number. Getting upleveled from Senior to Staff is worth more than 10% on base.
At a remote-friendly company
- Benchmark using HQ city rates, not your city rates. This is the anchor the recruiter knows internally.
- Counter with “I understand you discount for remote; given my experience and the role scope, I’d be comfortable at a smaller discount — X% rather than the standard Y%.”
- Ask explicitly if they have a policy that lets remote engineers “reach anchor” after some tenure. Some companies do (uncommon but real).
- Push for one-time signing or equity over base. Base sticks in their “remote band” database; a signing bonus doesn’t.
Which Model Is Better For You?
No universal answer — depends on what you optimize for.
| What you want | Pick |
|---|---|
| Maximum cash today (you’re in a high-multiplier country) | Remote-only |
| Career path to senior-leadership roles as a remote | Remote-only |
| Access to HQ-market pay while living somewhere cheap | Remote-friendly (until they rebalance) |
| Stability when layoffs hit | Remote-only (remote isn’t the balancing variable) |
| Shortest path to management track | Remote-only (no in-person-promotion bias) |
| Transparent comp philosophy | Remote-only |
The people getting the most absolute euros short-term are often the ones extracting HQ-rate pay from a remote-friendly company while living somewhere with a lower cost of living. That’s a rational move — but recognize it’s arbitrage, and the arbitrage usually closes within 2–3 years as those companies install formal remote bands.
The 2026 Trend to Watch
Remote-friendly companies are increasingly rebalancing — standardizing their remote pay bands, closing the arbitrage, and publishing formulas that look more like remote-only philosophy. This has already happened at Meta (RTO mandate), Google (location-based pay formula), and most EU scale-ups that hired heavily-remote during 2020–2022.
If you’re currently arbitrage-benefiting from a remote-friendly company’s opaque bands, budget for the next renegotiation cycle: either their formula will catch up to you, or they’ll push you to relocate. Neither outcome is bad, but both are decisions you want to make on your timeline, not theirs.
TL;DR
- Remote-only: global bands × country multipliers. Transparent, defensible, equal access to promotion. Your benchmark is global.
- Remote-friendly: HQ rate with a remote discount. Opaque, rebalanced when budgets tighten, promotion bias favors HQ. Your benchmark is HQ.
- Three signals to decode the job ad: team distribution, pay-location basis, promotion history.
- Negotiate differently: at remote-only, push for level; at remote-friendly, push for one-time or HQ-anchored base with smaller discount.
Want to see actual pay bands for fully-remote vs HQ-discounted roles in your market? Xeito’s salary calculator aggregates from 10+ job providers, letting you filter by role + country. The spread between the two models is often 15–30% for the same level — visible in the data.
And Xeito’s aggregated job search tags roles by employer type in its metadata, so you can filter for fully-distributed-only if that’s your preference.
Want the numbers for your situation? Try the Xeito remote-salary calculator — compare net take-home and cost of living across European tech hubs in 30 seconds.
Related articles
- How to Negotiate Salary for Remote Roles in Germany
- How to Negotiate Your Salary: Strategies That Actually Work
- Why Remote-Only Companies Pay Differently Than Remote-Friendly Companies
- EU Tax Residency for Remote Developers: The Real Rules in 2026
- The Real Cost of Living vs. Remote Salary in Europe (2026)