How To Set Salary For Remote Roles (Without Guessing)
Figuring out how to set salary for remote roles is one of the most frustrating parts of building a distributed team. You know the role, you know the budget, but the moment you open a salary survey, you find data for San Francisco, New York, and Austin that are wildly different from each other, and you are left guessing which number actually applies to your situation.
When you get this right, you stop losing top candidates to competitors who simply communicated their pay logic better. You also reduce the risk of paying two people in the same role very differently for no defensible reason, which tends to surface during performance reviews and cause real trust problems.
This guide walks you through every step, from building a pay philosophy to keeping your bands current as markets shift. We Work Remotely put this together to give hiring teams and HR leads a clear, repeatable process they can apply to any remote role. Read on, and you will have a working system by the end.
Start With A Pay Philosophy
Your pay philosophy is the single decision that makes every other compensation choice easier or harder, and most teams skip it entirely. Getting it in writing before you run any benchmarks saves you from having to relitigate the same internal debates every time you open a new role.
Location-Based vs. Location-Agnostic Compensation
These two approaches represent genuinely different bets on what your company values, and each one carries real trade-offs for your hiring funnel.
Location-based pay ties a person's salary to the cost of labor or cost of living in their home city or state. A software engineer in Austin earns less than one in San Francisco for the same role. This approach is common and keeps your compensation data cleaner because you are always benchmarking against a defined local market.
Location-agnostic pay sets a single rate for a role nationwide, regardless of where the person lives. Some companies anchor this to the highest-cost market, others to a national median. The benefit is simplicity and a strong message to candidates that output matters more than zip code. The risk is that you may overpay relative to local norms in lower-cost areas, which stretches your budget.
The right choice depends on where your candidates come from and how dispersed your team is. If 80% of your hires live in three metro areas, location-based pay is manageable. If you hire across 30 states, a simpler national band may serve you better.
Internal Equity Before External Benchmarking
Before you pull any external salary data, map what your current team earns across similar roles. External benchmarking tells you what the market pays; internal equity tells you whether your own team is in a fair relationship with each other.
A new hire offer should not leapfrog a two-year employee doing the same job. That gap creates resentment the moment it becomes visible, and in remote teams, salary information travels fast. Identify your current pay distribution by role and level first, then use market data to validate or adjust your bands, not to build them from scratch while ignoring what already exists.
Choose The Market You Will Price Against
Picking the wrong labor market to benchmark against is one of the most common and costly mistakes in remote compensation. Your choice here shapes whether your offers land competitively or consistently miss the mark.
Candidate Location, Team Hub, Or Revenue Market
Three markets compete for your attention when you set remote pay: where your candidates live, where your company has physical offices, and the revenue market your company competes in.
Candidate location pricing means you match the local labor market for each hire. It keeps costs lower in smaller cities but adds administrative complexity as your team spreads across more states.
Team hub pricing anchors everyone to the city where most of your workforce is located, even if the new hire lives elsewhere. This is simple to administer but can make you uncompetitive in high-cost markets and over-budget in low-cost ones simultaneously.
Revenue market pricing ties pay to the economic tier your company operates in, not where employees sit. A startup generating revenue from enterprise clients in New York often uses New York market rates even if the team is fully distributed. This approach attracts candidates who know their work drives high-value outcomes and expect to be paid accordingly.
Most teams use a blend: revenue market anchors the ceiling, candidate location guides adjustments within a defined range.
When To Use Salary Bands Instead Of Single Rates
A salary band gives you a minimum, midpoint, and maximum for a role. Single rates, where everyone in a job title earns the same dollar amount, are easier to explain but harder to defend as your team grows.
Use bands when you have more than a few people in the same role, when you hire across multiple experience levels within that role, or when you operate in geographically diverse locations. Bands let you place a new hire at the lower end while giving a tenured employee room to grow toward the top without requiring a promotion.
A practical starting point is a bandwidth of 40% to 50% between the minimum and maximum. That gives you meaningful room to differentiate without creating a situation where two people doing the same work earn dramatically different amounts.
Build A Defensible Compensation Formula
A compensation formula turns your pay philosophy into a number you can explain to a candidate, a board, or a skeptical team member without flinching. The key is grounding it in role-specific inputs, not just market percentiles.
Role Scope, Level, And Scarcity Signals
Three inputs drive the base rate before you factor in any location adjustments: scope, level, and how hard the role is to fill.
Scope means the actual complexity and accountability of the job. A senior engineer who owns a critical product surface earns more than one who handles maintenance tickets, even when they share the same title and years of experience. Write scope definitions for each level before you attach a number.
Level maps to a career ladder, and your career ladder needs to exist on paper before you set pay. If you pay people at the same level differently with no documented rationale, you create a compliance risk and an equity problem at the same time.
Scarcity is the market signal that tells you when the standard band is not enough. If you are hiring a machine learning engineer in mid-2026 and qualified candidates have multiple offers, your band ceiling may need to move.
Track time-to-fill and offer decline rates—especially for roles requiring courses boosting remote salaries—as early signals that your bands are falling behind the market.
Adjustments For Cash, Bonus, And Equity Mix
Total compensation is what actually competes for talent, and base salary is only one part of it.
A lower base paired with a meaningful performance bonus may match or exceed a higher base with no variable pay. Be explicit about this trade-off in your offer communications, because candidates who receive three competing offers will compare total comp, not just base.
Equity is particularly relevant for startups and growth-stage companies. A candidate who accepts a lower base in exchange for equity is making a bet on your company, which means you need to give them enough information to evaluate that bet fairly. Vague descriptions of "options" are not a compensation offer; a share count, current strike price, and vesting schedule are.
When you adjust base downward to reflect a higher equity component, document that decision so future pay reviews do not treat the person as simply underpaid. Understanding how to make an offer with the right balance of equity is key to successful negotiations.
Account For Compliance And Employment Costs
The salary you post in a job listing is not the full cost of that hire, and in remote work the gap between listed pay and total employer cost can be substantial. Knowing this number before you make an offer prevents budget surprises later.
Employer Taxes, Benefits, And Local Statutory Costs
Payroll taxes, employer-side FICA contributions, state unemployment insurance, and workers' compensation premiums all sit on top of the salary figure. In most U.S. states, these add roughly 10% to 15% to the cost of an employee's base compensation.
State-specific rules add another layer. California requires specific meal and rest break premiums, has strict expense reimbursement laws, and imposes additional employment taxes. Texas has no state income tax, which affects how candidates evaluate net pay—sharing remote work tax tips can help candidates understand these regional differences. When you hire in a new state, verify statutory minimums before finalizing your offer.
Health insurance, retirement contributions, and paid leave are not optional considerations for competitive roles. A candidate evaluating two similar offers will weigh the benefits package heavily, which means a $5,000 lower salary paired with a fully paid health plan can outperform a higher base with thin benefits.
Contractor Rates Compared With Employee Pay
Contractors typically quote a higher hourly or project rate than employees earn on a comparable annual salary. That premium exists because contractors pay self-employment tax, fund their own benefits, and absorb their own equipment costs.
A rough rule of thumb: the rate for remote contract jobs should be 20% to 30% higher than the equivalent hourly rate for remote full-time jobs to reflect the shift in cost burden. If a contractor quotes you a rate lower than your employee equivalent, investigate potential misclassification risks.
Misclassifying an employee as a contractor is one of the costlier compliance mistakes a remote company can make, particularly in California and New York where enforcement is active.
Communicate Offers And Updates Clearly
Even a well-designed pay structure fails if your team cannot explain it clearly and consistently. The biggest source of distrust in compensation among remote teams is not the numbers themselves but the silence around them.
How To Explain Geographic Differences Fairly
If you use location-based pay, candidates and employees will ask why someone in Denver earns less than someone in Seattle doing the same job. You need a prepared, honest answer grounded in your pay philosophy, not an improvised one.
The clearest explanation ties pay to local labor market rates. Something like: "We benchmark compensation against the competitive pay for your location, which means your salary reflects what it takes to attract and retain talent in your market." That answer is defensible as long as your benchmarking data is up to date and applied consistently.
What damages trust is inconsistency. If you apply location adjustments to some roles but not others without a documented reason, employees will notice. Write your geographic pay rules into your compensation policy and make that policy accessible to all employees, not just managers.
Pay transparency laws in Colorado, New York, California, and Washington now require salary ranges in job postings. Even if you hire in states without these requirements, posting ranges reduces the friction in early-stage conversations and signals confidence in your pay structure.
Manager Talking Points For Salary Conversations
Managers who cannot articulate why someone is paid what they are paid become a liability in retention conversations. Give them a script, not just a policy document.
A practical talking-point framework:
- What the role is benchmarked against: "This role is priced against national data for [job family] at the [level] tier."
- Where this person sits in the band and why: "You are at the midpoint because you joined with two years of relevant experience, which is our standard placement for that profile."
- What movement within the band looks like: "As you demonstrate [specific outcomes], we review band placement during the annual cycle in [month]."
Train managers to deliver these points without reading from a script, and practice with them before performance review season. A manager who stumbles through a salary conversation sends a signal that the company does not have a real system, even if it does.
Keep The System Current As Markets Change
A salary band you built in 2023 is likely out of position in mid-2026, especially in technical roles where compensation has moved sharply. A static system becomes a retention risk faster than most teams realize.
Review Cadence And Trigger Events
Set a scheduled review at least once per year, and tie it to a specific date so it does not slip. Many companies align compensation reviews with their fiscal year-end or the start of hiring season. Annual reviews keep your bands from drifting too far from the market without requiring constant analysis.
Beyond the calendar, define trigger events that force an off-cycle review. These include: a significant shift in hiring difficulty for a role, a wave of counteroffers above your band ceiling, the entry of a well-funded competitor into your talent market, or a macro event like the inflation spikes seen in 2022 and 2023. Waiting for the annual cycle after a trigger event means you lose people you could have retained.
Practical Salary Band Audit Exercise
Run this exercise once per year, or whenever a trigger event occurs:
- Pull the current salary for every person in each role and level.
- Calculate where each person sits as a percentage of the band midpoint. This is their compa-ratio. A ratio below 80% signals potential underpay; above 120% signals compression risk.
- Compare your band midpoints with at least two current data sources, such as a paid compensation survey and aggregated job-posting data for similar roles.
- Flag any band where the midpoint is more than 10% below the median of your benchmark sources.
- Prioritize adjustments starting with the roles where you are currently hiring or where your turnover rate is highest.
- Document all changes, the data you used, and the date of the review.
This exercise takes two to three hours for a team under 50 people and gives you a defensible record if a compensation decision is ever questioned.
Frequently Asked Questions
Should remote employees be paid based on where they live or where the company is located?
Both approaches are used by real companies, and neither is universally right. Location-based pay keeps your costs tied to local labor markets, while paying based on company location applies one consistent standard to everyone. Your choice should be documented in a written compensation policy so candidates and employees can understand the logic behind their offer.
What factors do companies use to determine pay for fully remote positions?
Most companies weigh role scope, experience level, and market benchmarks for the relevant labor market. Scarcity of qualified candidates, internal equity for existing team members, and the total compensation mix, including benefits and equity, also factor in. The goal is a number that is defensible internally and competitive externally.
How can I benchmark competitive pay ranges for a remote role in the U.S.?
Use at least two data sources: a paid compensation survey such as Radford or Mercer and aggregated salary data from job postings for equivalent roles. Cross-reference both to find the median and 75th percentile for your role and level. Update your benchmarks at least once per year, since remote job market data shifts faster than traditional in-office role data.
How do state-specific rules (like California or Texas) affect remote pay decisions?
California requires employers to reimburse necessary work expenses, pay specific premiums for missed breaks, and comply with stricter classification rules. Texas has no state income tax, which affects how candidates evaluate net pay without changing your gross pay obligation. Whenever you hire in a new state, review that state's wage-and-hour laws before finalizing the offer.
What's the best way to handle cost-of-living differences when setting remote compensation?
Decide upfront whether you are adjusting for cost of living or cost of labor. These are not the same thing. The cost of labor reflects what it takes to hire qualified people in the market; the cost of living reflects what people spend day-to-day. Most compensation professionals recommend anchoring to labor market data rather than cost-of-living indices, since your talent competition operates in the labor market.
How can candidates negotiate salary and benefits for a remote job offer?
Research the market rate for your role and level using salary data specific to your target employers and location. Frame your ask around total compensation, including base, bonus, equity, and benefits, rather than base salary alone. Identify the component with the most room to move, since some companies have rigid base bands but flexible signing bonuses or equity grants.
Put Your Pay System to Work
Building a compensation system for remote roles is not a one-time project. It is a process that starts with a clear philosophy, runs through defensible benchmarking and formula-building, and stays accurate through regular audits and honest manager conversations.
The companies that retain remote talent longest are the ones whose employees feel like the pay system is fair and explainable, not secretive or arbitrary. That feeling comes from consistency: consistent benchmarks, consistent band placements, and consistent conversations when the numbers change.
If you are ready to put this into practice, We Work Remotely is a strong place to start. Whether you are hiring or searching, find remote jobs or post a remote role and reach a focused audience of distributed-work professionals.