Picture this: a senior software engineer in Lisbon delivers the same output as her counterpart in San Francisco. Same deadlines. Same Slack messages. Same product shipped. But one earns 40% less simply because of her zip code.<\/p>\n\n\n\n
She knows it. And so does her recruiter at the competing company offering location-agnostic pay.<\/p>\n\n\n\n
This is the quiet talent war playing out inside distributed companies right now. The rules have changed, and the organizations still clinging to “geographic pay bands” are losing their best people to the ones that aren’t. Location-agnostic compensation paying employees based on the role, not the region has moved from radical experiment to retention essential. Here’s why it’s working, and what it actually looks like in practice.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Let’s be precise, because there’s a lot of confusion around this term.<\/p>\n\n\n\n
Location-agnostic pay<\/strong> doesn’t mean everyone earns the same dollar amount regardless of where they live. It means compensation is determined by the role, responsibilities, skills, and seniority level<\/em> not adjusted downward just because someone happens to live somewhere with a lower cost of living.<\/p>\n\n\n\n Compare that to the more common approach: location-based pay<\/strong>, where a company anchors salaries to local market rates. Move from New York to Medell\u00edn? Expect a pay cut. Stay remote in Austin instead of commuting to the Seattle HQ? Your offer gets geo-adjusted.<\/p>\n\n\n\n The distinction matters enormously to the person on the receiving end of the offer letter.<\/p>\n\n\n\n None of these are perfect. But they all move away from the idea that your address should be your biggest compensation determinant.<\/p>\n\n\n\n <\/p>\n\n\n\n Remote work didn’t invent location-agnostic pay but it forced the conversation.<\/p>\n\n\n\n When COVID sent millions of workers home in 2020, many companies discovered something uncomfortable: their distributed teams were producing excellent work from everywhere. The justification for geographic pay differences office proximity, local market competitiveness, cost-of-living “fairness” started looking flimsier by the month.<\/p>\n\n\n\n Then came the talent market pressure.<\/p>\n\n\n\n Startups and remote-first companies began poaching talent from traditional employers with a simple pitch: we pay for the role, not the region<\/em>. Mid-level engineers in Eastern Europe, designers in Southeast Asia, and marketers in Latin America suddenly had access to compensation that reflected what their skills were actually worth on a global scale.<\/p>\n\n\n\n The companies that didn’t adapt? They watched their best people leave.<\/p>\n\n\n\n <\/p>\n\n\n\n Here’s what the research and real-world experience are showing:<\/p>\n\n\n\n Pay transparency tools like Levels.fyi, Glassdoor, and LinkedIn Salary Insights have made it impossible to keep pay gaps invisible. When remote employees discover a colleague doing the same job earns 35% more because they live in a different city, the damage to morale is immediate and lasting.<\/p>\n\n\n\n Location-agnostic pay removes the variable they can’t control and replaces it with variables they can, like performance and scope of responsibility.<\/p>\n\n\n\n Companies using global salary bands can recruit from a much wider candidate pool while still attracting top-tier talent. A senior designer in Warsaw who might have previously been filtered out by a US-anchored salary expectation is now a competitive candidate \u2014 and often brings perspectives, language skills, and market context that local hires can’t.<\/p>\n\n\n\n When employees don’t have to hide where they’re moving to avoid a pay cut, they’re more honest, more stable, and more loyal. The fear of “if I move cities, will HR adjust my salary?” creates low-grade anxiety that quietly erodes trust.<\/p>\n\n\n\n Location-agnostic pay eliminates that entire category of worry.<\/p>\n\n\n\n Whether companies intend it or not, how they pay communicates what they believe. A company that cuts your salary because you moved to a lower-cost country is implicitly saying: your contribution is worth less now<\/em>. That message lands. And it lingers.<\/p>\n\n\n\n <\/p>\n\n\n\n GitLab<\/strong> is perhaps the most cited example. As an all-remote company with team members in 65+ countries, they use a formula that anchors pay to San Francisco market rates with regional adjustments but the adjustments are transparent, published, and consistent. No surprises.<\/p>\n\n\n\n Buffer<\/strong> has openly shared its salary formula for years, including how location factors in. The transparency itself has become a recruiting advantage.<\/p>\n\n\n\n Automattic<\/strong> (the company behind WordPress.com) also operates on global salary bands and has consistently cited its compensation philosophy as a key reason for low attrition in a competitive talent market.<\/p>\n\n\n\n What these companies share isn’t just a compensation model. It’s a commitment to treating remote work as a real<\/em> work arrangement, not a temporary accommodation.<\/p>\n\n\n\n <\/p>\n\n\n\n If you’re a founder, HR leader, or people ops professional thinking about making this shift, here’s a grounded approach:<\/p>\n\n\n\n Start with role clarity.<\/strong> Location-agnostic pay only works when roles are well-defined. You need clear job levels, responsibilities, and performance benchmarks before you can set global salary bands.<\/p>\n\n\n\n Benchmark against global remote salaries.<\/strong> Use tools like Radford Global, Mercer, Levels.fyi, or remote-focused platforms (including niche job boards in your industry) to understand what top talent actually commands globally.<\/p>\n\n\n\n Decide on your anchor market.<\/strong> Most companies that go location-agnostic anchor to a primary market \u2014 usually where they’re headquartered or where the highest concentration of talent is. They then apply consistent logic from there.<\/p>\n\n\n\n Be transparent about the formula.<\/strong> Employees don’t need every variable, but they should understand how<\/em> their pay was determined. Opacity breeds suspicion, even when the numbers are fair.<\/p>\n\n\n\n Phase in changes carefully.<\/strong> If you’re transitioning from a geo-based model, sudden changes can create winners and losers internally. Consider grandfathering existing compensation while applying the new model to new hires, then adjusting over time.<\/p>\n\n\n\n <\/p>\n\n\n\n If you’re a remote employee or freelancer reading this, the shift toward location-agnostic pay is genuinely worth tracking \u2014 because it affects your negotiating position.<\/p>\n\n\n\n A few things to keep in mind:<\/p>\n\n\n\n The conversation around remote work has matured. It’s no longer about whether distributed teams can be productive \u2014 that question’s been answered. Now it’s about whether companies are willing to build compensation structures that reflect the actual value of distributed work.<\/p>\n\n\n\n Location-agnostic pay isn’t a moral crusade. It’s a pragmatic response to a talent market that no longer respects geographic boundaries. The companies embracing it are retaining people. The ones resisting it are writing their best employees a slow, polite rejection letter.<\/p>\n\n\n\n The question isn’t whether your company can<\/em> afford to go location-agnostic. It’s whether you can afford not to.<\/p>\n\n\n\n If you’re job hunting in the remote space<\/strong>, make compensation philosophy part of your research before you apply. Platforms like MyRemoteAlly.com surface remote-first employers who are transparent about pay which is a good place to start.<\/p>\n\n\n\n Q: What is location-agnostic pay and how does it differ from standard remote compensation?<\/strong> Location-agnostic pay sets salaries based on the role and skills required, not the employee’s geographic location. Standard remote pay often applies geo-adjustments that reduce compensation for employees living in lower cost-of-living areas.<\/p>\n\n\n\n Q: Does location-agnostic pay mean everyone earns the same salary globally?<\/strong> Not exactly. It means geography stops being the primary<\/em> pay driver. Most companies still use role levels, experience, and performance as key variables \u2014 they just remove or minimize the location penalty.<\/p>\n\n\n\n Q: Is location-agnostic pay better for remote workers?<\/strong> Generally, yes \u2014 especially for those in regions where local market rates are lower than the global value of their skills. It removes a disadvantage that was never tied to performance.<\/p>\n\n\n\n Q: What companies currently offer location-agnostic pay?<\/strong> GitLab, Automattic, Buffer, Basecamp, and several Y Combinator-backed startups are among the most visible. The list is growing as remote-first hiring becomes the norm rather than the exception.<\/p>\n\n\n\n Q: How can I find remote jobs with location-agnostic compensation?<\/strong> Look for companies that publicly share salary formulas or ranges, job boards focused on remote-first employers, and roles that explicitly list pay transparency as part of their hiring process. Filtering for “remote-first” companies (not just “remote-friendly”) is a reliable starting signal.<\/p>\n","protected":false},"excerpt":{"rendered":" Picture this: a senior software engineer in Lisbon delivers the same output as her counterpart in San Francisco. Same deadlines.<\/p>\n","protected":false},"author":1,"featured_media":901,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[48],"tags":[],"class_list":["post-898","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hiring-management"],"_links":{"self":[{"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/posts\/898","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/comments?post=898"}],"version-history":[{"count":1,"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/posts\/898\/revisions"}],"predecessor-version":[{"id":899,"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/posts\/898\/revisions\/899"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/media\/901"}],"wp:attachment":[{"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/media?parent=898"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/categories?post=898"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/myremoteally.com\/blog\/wp-json\/wp\/v2\/tags?post=898"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}The Models Companies Are Using<\/h3>\n\n\n\n
\n
Why Companies Started Doing This in the First Place<\/h2>\n\n\n\n
The Real Retention Case for Location-Agnostic Pay<\/h2>\n\n\n\n
1. It Eliminates a Major Source of Resentment<\/h3>\n\n\n\n
2. It Expands the Talent Pool Without Lowering Standards<\/h3>\n\n\n\n
3. It Builds Psychological Safety<\/h3>\n\n\n\n
4. It Signals Company Values \u2014 Loudly<\/h3>\n\n\n\n
Companies Getting This Right<\/h2>\n\n\n\n
Practical Steps for Implementing Location-Agnostic Pay<\/h2>\n\n\n\n
What This Means for Remote Workers and Freelancers<\/h2>\n\n\n\n
\n
Frequently Asked Questions<\/h2>\n\n\n\n