Setting compensation for a distributed team is one of the hardest decisions a company makes — and one of the most consequential. Pay too little and you lose people. Pay too much and your burn rate makes investors nervous. Pay inconsistently and you breed resentment the moment two colleagues in different countries compare numbers.
There’s no universally right answer to “how should we pay remote employees.” But there are frameworks that help you make the decision deliberately rather than ad hoc, and there are mistakes that are entirely avoidable if you know to look for them.
Compensation Philosophies for Remote Teams
Before you set a single salary, you need to decide your philosophy. The three main approaches are location-based, role-based, and hybrid — and each has real trade-offs.
Location-based compensation
You pay based on where the employee lives. A software engineer in San Francisco earns more than an equally skilled engineer in Lisbon, because the cost of living (and the local talent market) is different.
The case for it: It’s how most companies have always operated, it feels intuitively fair, and it controls costs. If you’re hiring in lower-cost markets partly to extend your runway, location-based pay is the honest approach.
The case against it: It creates a system where the same work has different value depending on geography. An engineer shipping the same features from Lisbon as from San Francisco contributes the same value to the company but earns significantly less. As remote work matures and employees can easily compare compensation, this becomes harder to defend — and harder to retain people on.
Role-based compensation
You pay based on the role and level, regardless of location. A mid-level product designer earns the same whether they’re in London or Lagos.
The case for it: It’s simple, transparent, and treats the work as the unit of value rather than the location. It eliminates the perception of unfairness and makes compensation conversations straightforward.
The case against it: It’s expensive. If your benchmark is US market rates, you’re paying San Francisco salaries to people in markets where that money goes five times further. It can also create local distortions — an employee earning a US salary in a low-cost market may be so far above local norms that they have no realistic alternative employment, which creates an unhealthy dependency dynamic.
Hybrid compensation
You use a base rate (often pegged to a specific market like San Francisco or New York) and apply a location factor — typically 70-100% of the base depending on the employee’s location. This is the most common approach among distributed companies with more than 50 employees.
The case for it: It acknowledges that location matters without creating extreme disparities. It gives the company cost advantages from hiring globally while maintaining a principled framework.
The case against it: The location factor is inherently arbitrary. Is Lisbon 75% of San Francisco or 80%? Is that based on cost of living, local salary data, or a blend? The methodology matters, because employees will scrutinize it — and they should.
What companies usually get wrong
They pick a philosophy and then apply it inconsistently. The CEO hires a VP in a high-cost market at top of range, while HR applies the location factor rigorously to a junior engineer in the same city. Or they start with role-based pay when the team is small, then quietly shift to location-based when the headcount grows and the budget tightens. Inconsistency destroys trust faster than any individual compensation decision.
Setting Remote Pay Scales
Once you’ve chosen a philosophy, you need data. Feelings about what’s fair aren’t a compensation strategy.
Data sources
Compensation benchmarking platforms (Radford, Mercer, Pave, Levels.fyi, Glassdoor) provide market data by role, level, and geography. The quality varies — Radford and Mercer are considered the gold standard for structured benchmarking, while Levels.fyi and Glassdoor provide more granular but self-reported data. Use multiple sources and triangulate.
Your own offer acceptance data is underrated. If you’re losing 50% of your offers in a specific market, your comp is below market — regardless of what the surveys say. If everyone accepts immediately, you might be overpaying. Track offer acceptance rates by market and adjust.
Recruiter feedback from your own team or external partners provides real-time market intelligence that surveys — which are typically 6-12 months old by publication — can’t match. If recruiters tell you the market has shifted, listen.
Building the scale
A compensation framework typically includes: levels (a structured progression from junior to senior to lead to director), pay bands per level (with a minimum, midpoint, and maximum), location factors (if using location-based or hybrid pay), and clear criteria for placement within the band.
The band width matters. Too narrow (e.g., a 10% spread from min to max) and you have no room for tenure-based progression or market adjustment. Too wide (e.g., a 50% spread) and the band is essentially meaningless. Most companies use 20-30% spreads for individual contributor roles and wider bands for leadership.
Updating the scale
Compensation data gets stale. Review your benchmarks at least annually — ideally semi-annually — and adjust bands based on market movement, your own retention data, and your financial position. The companies that set bands once and ignore them for three years end up with a retention crisis and a correction that costs more than annual adjustments would have.
Compensation for International Employees
Total compensation isn’t just salary. When you’re hiring across countries, the non-salary components vary so dramatically that comparing base salaries alone is misleading.
Tax impact
A gross salary of $100,000 has a very different net value in the US (where effective tax rates for this income level might be 25-30%) versus Belgium (where marginal rates can approach 50%) versus the UAE (where there’s no income tax). If you’re comparing total cost of employment across countries, use total employer cost — not just gross salary.
Statutory benefits
In countries with universal healthcare and generous public pensions, the employee’s base salary doesn’t need to cover these costs. In the US, where health insurance alone can cost $15,000-25,000 per year per family, the base salary needs to be higher to maintain equivalent total compensation. Account for this when comparing packages across borders.
Supplementary benefits
What you offer on top of statutory benefits matters differently by market. A generous health insurance plan is transformative in India (where public healthcare is limited) and irrelevant in Denmark (where public healthcare is comprehensive). A retirement contribution is highly valued in markets without strong public pensions and less differentiated where statutory pensions are generous.
The best global compensation packages offer a core component (salary + statutory) plus a locally relevant supplementary package designed for each market. This is more complex to administer but significantly more effective at attracting and retaining talent.
What companies usually get wrong
They export their home country’s benefits package globally. A US company offering a $500/month health insurance stipend is generous in some markets and laughably inadequate in others. Understand what employees in each market actually need and value, and design the package accordingly.
Pay Transparency and Communication
How you communicate compensation matters almost as much as what you pay. The trend globally is toward more transparency, driven by regulation (EU Pay Transparency Directive, various US state laws) and employee expectations.
Levels of transparency
Full transparency means publishing all pay bands and individual salaries. Buffer famously did this early, and several other companies have followed. It eliminates pay negotiation, ensures equity, and builds trust — but it also means every compensation decision is visible, which requires high confidence in your framework.
Band transparency means publishing the pay bands for each level and role, but not individual salaries within bands. This is the most common approach among companies moving toward transparency. It gives employees enough information to evaluate their own compensation and career progression without exposing individual negotiations.
Process transparency means explaining how compensation decisions are made — the philosophy, the data sources, the approval process — without publishing specific numbers. This is the minimum viable transparency for a company that wants to build trust around compensation.
Building a framework employees trust
Employees trust compensation frameworks that are: consistent (same rules apply to everyone), explained (the methodology is documented and accessible), reviewed regularly (not set and forgotten), and connected to career progression (employees can see how their pay will grow as they advance).
The biggest trust-killer isn’t low pay — it’s inconsistency. If two people at the same level doing the same work earn significantly different amounts without a clear reason, the framework has failed regardless of how well-designed it is on paper.
Managing compensation conversations
Train managers to have compensation conversations. Most managers are uncomfortable discussing pay, which leads to either avoidance (the employee never gets a straight answer) or defensiveness (the manager gets flustered and makes promises they can’t keep). Give managers the tools: talking points for band explanations, answers to common questions, and clear escalation paths for requests they can’t address.
This guide is part of the RemotePass resource library. For payroll and payment operations, see our payroll guide. For hiring and offer strategy, see our hiring guide. For contractor rate benchmarks, see our contractor rules guide.