Remote work did not just change where people open their laptops. It also walked into the compensation department, put its coffee on the desk, and asked the uncomfortable question: “So… are we paying people for where they live or for what they do?”
That question sits at the center of today’s remote pay debate. As more employees work from homes, coworking spaces, spare bedrooms, and occasionally suspiciously beachy “home offices,” companies have had to rethink salary structures that were once built around headquarters, commuting zones, and local labor markets. Two major approaches now dominate the conversation: location-based pay and job-based pay.
Location-based pay adjusts compensation according to where an employee lives or works. Job-based pay, sometimes called role-based or value-based pay, focuses on the responsibilities, skills, seniority, and market value of the job itself, regardless of the employee’s address. Both models can work. Both can cause headaches. And both can become wildly confusing if a company rolls them out with the communication style of a printer error message.
This guide breaks down the main types of remote pay, the difference between location-based and job-based models, the pros and cons of each, and how employers can build a fair compensation strategy without turning salary discussions into a corporate escape room.
What Is Remote Pay?
Remote pay refers to how companies compensate employees who work outside a traditional office location. It applies to fully remote employees, hybrid workers, employees who move to another state, and distributed teams spread across multiple regions or countries.
Before remote work became mainstream, compensation was usually tied to a physical job market. A software engineer in San Francisco, a marketing manager in Chicago, and a customer support specialist in Atlanta might all have different pay ranges because employers benchmarked salaries against local competition. The office location was the anchor.
Remote work pulled up that anchor. If a company in New York hires a designer in Ohio, should that designer be paid based on New York salary levels, Ohio salary levels, a national average, or the company’s own internal salary band? That is the remote pay puzzle.
The Two Big Remote Pay Models
Most remote compensation strategies fall into two broad categories:
1. Location-Based Pay
Location-based pay adjusts salary based on geography. The employer may consider cost of labor, cost of living, local salary survey data, state or metro-area pay trends, payroll taxes, and talent competition in the employee’s location.
For example, a company may set one salary range for employees in high-cost labor markets such as San Francisco, New York City, or Seattle, and a lower range for employees in smaller or less expensive markets. Some companies use city tiers, regional zones, state-based salary bands, or country-specific pay ranges.
2. Job-Based Pay
Job-based pay focuses on the job itself. Under this model, employees doing the same role at the same level are paid within the same salary range, regardless of whether they live in Boston, Boise, or a town where the main traffic jam involves one tractor and a very confident goose.
This model usually relies on role scope, skills, experience, seniority, performance, and internal equity. A senior product manager earns senior product manager pay because the job carries a certain level of responsibility and market value, not because the employee’s rent is expensive.
How Location-Based Pay Works
Location-based compensation is built around the idea that labor markets vary by geography. Employers do not usually pay based only on how expensive groceries or apartments are in a city. Instead, they often look at the cost of labor, meaning what employers in that area typically pay for similar talent.
A common structure might look like this:
- Tier 1 markets: High-cost, high-pay cities such as San Francisco, New York, Seattle, or Boston.
- Tier 2 markets: Competitive but slightly lower-cost metro areas such as Denver, Austin, Atlanta, or Chicago.
- Tier 3 markets: Smaller cities, rural areas, or lower-cost regions with lower local salary benchmarks.
Some companies create broader national zones instead of city-by-city differences. Others use salary survey data to assign a geographic differential, such as paying 10 percent above or below a national midpoint depending on the employee’s market.
Example of Location-Based Pay
Imagine a remote cybersecurity analyst role with a national midpoint salary of $110,000. A company might adjust that salary like this:
- San Francisco or New York City: $125,000 to $140,000
- Chicago or Austin: $110,000 to $125,000
- Smaller Midwest or Southern market: $95,000 to $110,000
The work is similar, but the pay changes because the company is pricing the role according to local labor markets. From the employer’s point of view, this can help manage costs and stay competitive in each region. From the employee’s point of view, it can feel fair if explained clearlyor unfair if it sounds like, “Congratulations on moving closer to your family; here is your pay cut.”
Pros of Location-Based Pay
It Reflects Local Market Competition
Employers often compete for talent differently in different places. A data engineer in a major tech hub may have more local high-paying options than someone in a smaller market. Location-based pay allows companies to compete where competition is intense without overpaying in every location.
It Helps Control Compensation Costs
Remote hiring can expand a company’s talent pool, but if every employee is paid at the most expensive market rate, payroll costs can rise quickly. Location-based pay gives companies more control, especially when hiring across many states or countries.
It Can Support Global Hiring
For international teams, local pay practices, taxes, statutory benefits, currency, and employment rules vary widely. Location-based pay can help companies stay aligned with local market expectations and legal requirements.
Cons of Location-Based Pay
Employees May See It as Unequal Pay for Equal Work
The biggest criticism is simple: if two employees do the same job and deliver the same results, why should one earn less because they live in a less expensive city? Employees often care less about compensation theory and more about the emotional reality of seeing a colleague earn more for similar work.
It Can Be Hard to Explain
Location-based pay requires clear rules. What happens if an employee moves? How often are locations reviewed? Is pay reduced immediately, gradually, or only for new hires? Are employees paid by home address, office location, state, metro area, or country? Without transparency, the policy can feel random.
It Adds Administrative Complexity
Tracking employee locations, updating salary bands, managing payroll registrations, reviewing tax exposure, and complying with state employment laws can become complicated fast. Remote employees may trigger new tax withholding obligations, workers’ compensation requirements, unemployment insurance rules, paid leave laws, and wage-and-hour considerations.
How Job-Based Pay Works
Job-based pay starts with the role. Companies define salary bands based on job function, level, skill requirements, business impact, and market data. Geography may still be considered at a broad level, but it is not the main driver.
Under a job-based approach, a company might create one U.S. salary range for a remote role. For example:
- Customer Success Manager I: $70,000 to $90,000
- Customer Success Manager II: $90,000 to $115,000
- Senior Customer Success Manager: $115,000 to $145,000
Employees move within the range based on experience, performance, skills, and scope. Their ZIP code does not automatically move their pay up or down.
Example of Job-Based Pay
Suppose a remote-first software company hires two senior engineers. One lives in Los Angeles and the other lives in Tulsa. Both have similar experience, handle similar architecture decisions, mentor junior engineers, and contribute to high-value product work. Under job-based pay, both may fall into the same salary band because the company is paying for the role’s value, not the employee’s cost of living.
Pros of Job-Based Pay
It Feels Simpler and More Transparent
Employees understand job-based pay quickly: same role, same level, same range. It is easier to explain in job postings, offer letters, and internal compensation conversations. Nobody needs a spreadsheet named “Final_Final_GeoDifferential_v7_REAL.xlsx.”
It Supports Internal Equity
Job-based pay can reduce resentment among remote employees by emphasizing equal pay for equal work. It may also help support pay transparency efforts because salary ranges are easier to publish and defend.
It Can Improve Recruiting
A national or role-based pay band can attract candidates in lower-cost areas who might otherwise be offered less under a strict geographic model. For remote-first companies, this can become a powerful talent advantage.
Cons of Job-Based Pay
It Can Be Expensive
If a company uses high-market salary benchmarks for every employee, payroll can rise. Paying San Francisco-level salaries to employees everywhere may delight candidates but give finance teams a facial expression usually reserved for surprise dental bills.
It May Overpay in Some Markets and Underpay in Others
A single national range can be too high for some regions and too low for the most competitive talent markets. If the range is not carefully designed, the company may struggle to hire in expensive cities while paying more than necessary elsewhere.
It Still Requires Structure
Job-based pay is not “make up a number and hope.” Companies still need job architecture, salary ranges, promotion criteria, performance systems, and market reviews. Without structure, job-based pay can become just as messy as any other model.
Location-Based vs. Job-Based Pay: Key Differences
| Factor | Location-Based Pay | Job-Based Pay |
|---|---|---|
| Main driver | Employee location or labor market | Role, level, skills, and job value |
| Best for | Companies hiring across many regions with cost-control needs | Remote-first companies prioritizing simplicity and internal equity |
| Employee perception | Can feel practical or unfair depending on transparency | Often feels clearer and more equitable |
| Complexity | Higher administrative and payroll complexity | Simpler, but still requires strong job leveling |
| Cost control | Usually stronger | Depends on salary benchmark strategy |
Hybrid Remote Pay Models
Many companies do not choose a pure location-based or pure job-based model. They use a hybrid approach because, in compensation, “it depends” is practically the national anthem.
National Pay With Geographic Exceptions
A company may use one national salary band but add premiums for a few high-cost or high-competition markets. This keeps the structure simple while still allowing flexibility for expensive talent hubs.
Broad Geographic Zones
Instead of dozens of city-specific rates, companies may use three or four geographic zones. This reduces complexity while recognizing that labor markets are not identical across the country.
Role-Based Pay Plus Location Floors
Some employers primarily pay by job but ensure salaries meet local legal and market requirements. This is especially useful for multistate employers dealing with minimum wage rules, salary thresholds, paid leave laws, and pay transparency requirements.
Which Remote Pay Model Is Better?
There is no universal winner. The better model depends on company size, budget, hiring goals, culture, industry, and where employees work.
Location-based pay may be better for companies that hire across many markets, need tight payroll control, operate globally, or rely heavily on local salary data. It can also make sense for organizations with offices in multiple cities and a long history of geographic pay differentials.
Job-based pay may be better for remote-first companies, startups competing for specialized talent, organizations with strong transparency values, or employers that want a simpler employee experience. It works especially well when the company has clear job levels and can afford consistent salary bands.
The worst model is not location-based or job-based. The worst model is the mysterious model, where employees have no idea how pay is determined and managers explain compensation with the confidence of someone assembling furniture without instructions.
How Employers Can Build a Fair Remote Pay Strategy
Define the Compensation Philosophy First
Before choosing a pay model, leaders should answer a bigger question: What is the company trying to reward? Skills? Performance? Market competitiveness? Internal equity? Cost efficiency? Retention? The pay model should support the company’s values and business strategy.
Use Reliable Market Data
Whether a company chooses location-based or job-based pay, it needs current salary data. Guessing is not a compensation strategy; it is a future employee-relations problem wearing business casual.
Create Clear Salary Bands
Salary bands should show the minimum, midpoint, and maximum for each role or level. They should also explain how employees move through the range, whether through performance, promotion, skill growth, or expanded responsibilities.
Set Rules for Employee Moves
If employees relocate, the company should define what happens before the move occurs. Will pay change? When? Are there protected transition periods? Are moves to certain states or countries restricted because of payroll, tax, legal, or security issues?
Communicate Like Adults Are in the Room
Employees do not expect every compensation decision to be perfect, but they do expect honesty. Explain the “why,” not just the “what.” A clear explanation can prevent frustration, rumors, and the classic workplace sport of Slack-channel speculation.
What Employees Should Ask About Remote Pay
Job seekers and current employees should not be shy about asking how remote pay works. Useful questions include:
- Is salary based on my location, the company’s location, or the role?
- What happens if I move to another city or state?
- Are salary ranges national or location-specific?
- How often are pay bands reviewed?
- Does the company publish salary ranges in job postings?
- Are remote employees eligible for the same bonuses, equity, and benefits?
These questions are not rude. They are practical. Choosing a remote job without understanding the pay model is like renting an apartment without asking whether the “cozy kitchen” means “adorable” or “you can stir soup from the shower.”
Experience Section: What Remote Pay Looks Like in Real Life
In practice, remote pay is not just a spreadsheet decision. It affects morale, hiring conversations, relocation choices, and how employees feel about their value. One common experience is the employee who moves from a high-cost city to a lower-cost area after going remote. Under a location-based model, that person may face a salary adjustment. On paper, the company may argue that the employee no longer needs a high-market premium. In real life, the employee may feel punished for making a personal life decision, especially if their workload and performance remain unchanged.
Another common experience happens during recruiting. A candidate may see a remote job posting with a wide salary range, apply enthusiastically, and then learn that the top of the range only applies to a few expensive metro areas. The candidate is not necessarily angry because the company uses geographic pay. They are angry because they discovered the rule too late. Transparency matters. If the range depends on location, saying so early can save everyone time and awkwardness.
Managers also feel the tension. A manager may supervise two strong employees doing similar work from different states. If one earns noticeably more because of geography, the manager needs a clear explanation. Without one, performance reviews become uncomfortable. The manager may support the policy in theory but struggle to defend it when an employee asks, “Why is my work worth less?” That question is not easy to answer with a smile and a slide deck.
On the other hand, job-based pay can create its own real-world challenges. A small company paying one national rate may find that candidates in expensive cities reject offers because the salary is not competitive enough. At the same time, candidates in lower-cost regions may see the offer as excellent. This can subtly shape where the company hires, even when the policy appears location-neutral.
Some employees strongly prefer job-based pay because it feels cleaner: same job, same level, same range. They see it as a trust-building move. Others understand location-based pay if it is consistent, predictable, and not used as a surprise cost-cutting tool. The emotional difference often comes down to communication. A thoughtful policy says, “Here is how we price work, here is how location affects pay, and here is what happens if your situation changes.” A poor policy says, “Ask HR,” which is not a policy; it is a scavenger hunt.
The best remote pay experiences usually happen when companies combine structure with empathy. They use data, but they do not hide behind it. They control costs, but they do not treat employees like map pins. They explain trade-offs honestly and review policies as the labor market changes. Remote work gave people more freedom over where they live. Remote pay determines whether that freedom feels like a benefit or a fine-print trap.
Conclusion
The debate over location-based pay vs. job-based pay is really a debate about what companies value most: local market alignment, cost control, simplicity, fairness, or talent competitiveness. Location-based pay can be practical and financially disciplined, but it must be transparent to avoid damaging trust. Job-based pay can feel fair and easy to understand, but it requires strong salary architecture and a realistic budget.
For employers, the goal is not to copy whatever the trendiest remote company is doing. The goal is to build a compensation system that matches the business, supports hiring, keeps employees engaged, and survives hard questions. For employees, the goal is to understand the rules before accepting an offer, moving across the country, or assuming “remote” automatically means “same pay everywhere.”
Remote pay is still evolving, and there is no perfect formula. But there is a perfect starting point: clarity. Pay people thoughtfully, explain the system plainly, and do not make employees decode their salary like a mystery novel with benefits.
