Remote offers / Decision guide
Which location sets your remote offer's pay?
Remote is a work arrangement, not a pay location.
A headquarters address, an approved home office and an employer's salary zone can describe three different things. Confirm the pay rule before selecting a city benchmark.
Go to the question to ask ↓First / Separate the labels
Three locations. Three different questions.
Approved work location
Where may you actually do the job? Confirm the country, state and any office attendance requirement. “Remote US” alone does not answer all three.
Ask: Is my intended home office approved for this role?
Employer pay location
Which place or pay zone sets this role's base salary range? Ask whether the rule is tied to your home office, the assigned office or a location-independent range.
Ask: Which location or pay zone was used for this offer?
Benchmark geography
Which area does your reference actually cover? Keep the occupation, period and wage measure visible. A city label cannot confirm the employer's internal salary band.
Ask: Am I using the same geography the pay policy describes?
Then / Test the distinction
A San Francisco headquarters does not settle an Austin offer
Fictional scenario: your offer says “remote US,” the company is headquartered in San Francisco and you plan to work from Austin. These labels do not reveal which pay range was used.
If the recruiter says “Austin pay zone”
Record that zone and the role's level. Ask how the zone maps to the approved work location. An Austin occupation benchmark can provide context; it does not reproduce the employer's zone or prove the offer is fair.
If the recruiter says “one US range”
Ask for that role and level's range and where this offer sits within it. City benchmarks can still add context, but do not replace the stated policy with the headquarters' median.
These are possible answers to a fictional question, not claims about any employer. A missing or unclear answer means the policy is still unknown.
Next / Get one usable answer
Ask for the location rule in writing
“For this role and level, which work location or pay zone was used to set my base salary range? Is my planned work location approved? If I later request a move, would it require approval or change my base salary, and when?”
This is a clarification prompt, not an email sent by OfferBrief. Keep the answer alongside your offer; do not treat permission to work remotely as permission to move anywhere.
Before you compare, record four things
- Role and level: the actual duties and internal level used for the range.
- Location rule: the approved work location, pay zone or explicit location-independent policy.
- Like-for-like amount: annual base, currency and expected schedule; keep equity and one-time payments separate.
- Move conditions: who approves a change, whether pay changes and the effective date. If unknown, write “not confirmed.”
A public salary estimate cannot establish an employer's permission to hire in a location, its internal band or what will happen after your move. Ask the employer; keep unresolved points separate from your salary comparison.
Why ask instead of assuming?
One employer's published policy illustrates why location is worth checking: GitLab's compensation handbook describes base salary as determined by role, level and location. That is evidence about GitLab's approach, not a universal rule or a statement about your offer.
Read GitLab's compensation handbook ↗ Source checked November 11, 2026; policies may change.
No salary figures or legal conclusions are supplied by this guide. Its output is a clearer question and a record of what remains unknown.
Location rule confirmed?
Browse the existing role and city references, retaining the source period and geographic limits.
Return to salary benchmarks →Open the existing offer analyzer