The single most important question most candidates skip
Across every salary dataset we've reviewed for 2026 — software engineering, DevOps, cybersecurity, product management — one factor consistently determines whether a remote offer lands near the top or bottom of a role's range: whether the employer pays location-adjusted or location-agnostic compensation. GitLab, for instance, publicly uses a location factor system, meaning identical roles pay differently by geography. Automattic, by contrast, pays senior engineers the same $130,000–$180,000 globally regardless of where they sit, and Basecamp deliberately pays top-of-market San Francisco rates to every engineer, anywhere.
Asking this question directly — "is compensation for this role location-adjusted or location-agnostic?" — before discussing specific numbers is the single highest-leverage negotiation move available to a remote candidate in 2026, and it's a question multiple recruiters note candidates frequently forget to ask until after an offer is already on the table.
Know the ceiling before you name a number
The most consistent advice across 2026 remote compensation guides is to research the specific role's range using Levels.fyi, Glassdoor, and a recruiter-surveyed guide like Robert Half's before any conversation about numbers begins. Candidates who cite a specific, sourced range ("data from Levels.fyi and this year's Robert Half guide puts this role at $X to $Y for my experience level") are reported to negotiate meaningfully better outcomes than those who simply ask what the budget is.
Lead with output, not location
For candidates in the UK, Canada, or Australia specifically negotiating with US-headquartered employers, framing your value around what you deliver — shipped projects, measurable impact, specific technical ownership — rather than justifying your ask based on cost of living, consistently performs better in practice. Employers offering location-agnostic pay are explicitly not weighing your location in the decision; leading with a cost-of-living argument in that context can undercut your own position rather than strengthen it.
A simple script that covers the main scenarios
For the compensation-philosophy question: "Before we discuss specific numbers, can you tell me whether compensation for this role is based on a US/national band or adjusted by location?" For countering a lowball offer: "Based on [Levels.fyi/Robert Half's 2026 guide], this role typically lands between $X and $Y for someone with my experience — I'd like to discuss getting closer to that range." For a genuinely strong candidate facing a fixed-band employer: "I understand the band is fixed — is there flexibility in signing bonus, equity, or review timeline instead?" Each of these keeps the conversation anchored in data and specifics rather than an unstructured back-and-forth.
Frequently asked questions
What's the most important question to ask before negotiating a remote salary? Whether the employer's compensation is location-adjusted or location-agnostic — this single factor often explains a 20% or larger gap between two otherwise similar offers.
Should I mention cost of living when negotiating with a US company from the UK, Canada, or Australia? Generally no, if the company pays location-agnostic rates — lead with your output and impact instead, since a cost-of-living argument can undercut your position with employers who've already decided not to weigh location.
Where should I research salary data before negotiating? Levels.fyi and Glassdoor for self-reported figures, and a recruiter-surveyed guide like Robert Half's annual salary guide for a view closer to what employers are actually budgeting.