A location adjustment changes your RSU grant because the company is pricing the role against a pay zone, not against your title or your workload. The grant is usually where the company absorbs the difference when it decides your remote address does not deserve the same market rate as an office-hub hire.
TL;DR
A location adjustment changes your RSU grant because the company is pricing the role against a pay zone, not against your title or your workload. The grant is usually where the company absorbs the difference when it decides your remote address does not deserve the same market rate as an office-hub hire.
This is not a fairness problem in the abstract. It is a comp-policy problem, and policy usually beats persuasion once the hiring committee has already approved headcount.
If you want the real number, read the offer as a four-part package: base, sign-on, RSUs, and refresh policy. The headline grant is only the visible layer.
Most candidates leave $20K+ on the table because they skip the negotiation. The exact scripts are in The 0→1 PM Interview Playbook (2026 Edition).
Who This Is For
This is for PM candidates who are interviewing remotely for large tech companies, late-stage startups, or any company that uses city tiers, regional bands, or remote pay zones. It is also for people who already know the role is good but suspect the grant is quietly being shaved because they live outside the company’s preferred labor market.
In a debrief, these are the candidates who hear “competitive package” and assume that means comparable to HQ. It usually does not. The problem is not your performance signal. The problem is the company’s location signal.
How do location adjustments change a remote PM grant?
They change the grant because companies use location as a proxy for labor cost, internal equity, and retention risk.
In one compensation debrief I sat through, the hiring manager argued that the remote PM was functionally identical to the Bay Area PM. Finance did not care. Finance was looking at the pay band tied to the employee’s home address, and the address won. That is the part candidates miss. Not the role, but the policy determines the grant.
The company is rarely saying you are worth less. It is saying your market is priced differently. That distinction matters because the committee does not debate your dignity. It debates comp architecture.
The problem is not that remote work is cheaper to the company. The problem is that remote pay is often built as labor arbitrage, then dressed up as consistency. A remote PM in Austin, Denver, or Atlanta may see a smaller RSU grant than an HQ peer, even when the job scope is identical. The company will call this “alignment.” You should call it a location adjustment.
A common offer shape in large tech is a base salary in the mid-six figures, a sign-on used to soften the first-year gap, and a RSU grant that looks thinner than the office-hub peer’s. Sometimes the headline total comp is close. The equity path is not. That is where the real difference lives.
The committee’s psychology is simple. Once a policy is embedded, managers lose room to improvise. They can fight for exceptions, but they need a story that sounds like retention risk, scarce expertise, or a competing offer. “The candidate is excellent” is not enough. It never was.
Why does the same remote PM job pay differently across cities?
Because the company is buying two things at once: the work and the market you sit in.
A remote PM in a low-cost market is often paid against the company’s internal location grid, not against the scope of the product. That is why two candidates can clear the same loop, receive the same feedback, and get different grants. Not because one is stronger, but because one lives in a more expensive code path inside payroll.
In a Q3 debrief, I watched a hiring manager push for a larger grant after the panel loved the candidate. HR replied with one sentence: the role was already mapped to a remote band tied to the employee’s residence, and the band had not been reopened. The meeting ended there. That is how these decisions usually go. Not dramatic. Administrative.
The judgment is this: remote comp is not calibrated to your interview score alone. It is calibrated to a mix of market data, internal leveling, and the company’s fear of overpaying in one geography while underpaying in another. That is why the same PM profile can produce a different RSU outcome depending on whether the address sits in San Francisco, Seattle, New York, or a smaller metro.
Not every remote offer is discounted in the same way, but the pattern is stable. Fully distributed companies often use narrower gaps because their entire model depends on remote hiring. Legacy companies with headquarters culture often preserve a stronger geographic hierarchy. The location policy is not a side note. It is the spine.
If a recruiter says “we pay nationally,” do not stop there. Ask what the national policy means in practice. Some companies mean a single range. Others mean a range with quiet location tiers inside it. The words sound equal. The grants do not.
What should I do when the company says my address sets the band?
You should treat your address as a comp variable, not a clerical detail.
Before final rounds, ask which address determines the band: home address, tax address, legal residence, or office assignment. If the recruiter cannot answer quickly, assume the company has a location policy but does not want to discuss it until the offer is ready. That is normal. It is also the point where candidates get surprised.
The issue is not the address itself. It is when the address becomes frozen. In some companies, the location is locked the moment the offer is approved. In others, it is reassessed when payroll starts. In either case, waiting until the verbal offer to ask is late.
The remote PM candidate usually tries to argue merit after the policy is already set. That is the wrong battlefield. Not “I deserve more because I was strong in interviews,” but “Which location rule is driving the grant, and can that rule be revisited before sign-off?” The first line is emotional. The second is operational.
There is also a tax and payroll layer that candidates ignore. If you plan to move between offer and start date, the company may reset the location tier based on the final onboarding record. That can change the grant or the salary band. The mistake is assuming the comp team cares about your moving timeline. It cares about what payroll sees.
If you are remote but expected to travel to HQ every month, ask whether the company treats you as remote, hybrid, or office-adjacent. Those categories are not interchangeable. I have seen a candidate think they were in a full remote band, only to learn the travel expectation kept them in a higher-cost classification with no corresponding pay benefit. That is not a perk. It is a mismatch.
Can I negotiate a remote PM grant after the location band is set?
Yes, but you are usually negotiating the structure, not the policy.
This is where many candidates make themselves look naive in the final round. They ask for a larger RSU grant and ignore the location logic underneath it. The hiring manager hears “I want more money.” Finance hears “I want an exception.” Those are different asks, and one is much harder to approve.
The more credible move is to negotiate around the inputs. Ask whether the company can move you to a different location tier, add sign-on to offset year-one compression, or schedule an early comp review tied to vesting or performance. That is not soft language. It is the only language comp teams can actually route.
In practice, exceptions usually come from one of three stories: retention risk, competing offers, or rare scope. If your PM background includes a niche domain, a hard product launch, or a leadership gap the team urgently needs filled, you have leverage. If not, the company will default to policy and call it consistency.
Not every negotiation should focus on the RSU count. Sometimes the better outcome is a larger sign-on, an earlier refresh cycle, or a written commitment to review location classification after relocation. The problem is not your number. It is your leverage shape.
A useful test is this: can the manager explain the gap without hiding behind “bands”? If they can, you have room to talk. If they cannot, you are dealing with a policy boundary, not a negotiation. Boundaries are harder to move than budgets.
The cold truth is that remote PM comp is often decided before the final round ends. By the time you reach the offer, the committee has usually already argued through headcount, leveling, and equity guardrails. You are not entering a blank room. You are entering a room with a decision already half-written.
How do I read the offer letter without getting trapped by the headline number?
You read it as a system, not as a single number.
The headline grant is only one part of the package. The real question is whether the company is compensating for a lower RSU grant with base salary, sign-on cash, or a faster refresh path. If none of those are present, the company is not balancing the adjustment. It is simply discounting the role.
Look for four things. First, the vesting schedule. A four-year vest with a one-year cliff changes what the grant is really worth in year one. Second, the refresh policy. If refresh is discretionary and vague, the company is telling you not to count on it. Third, the location policy. If it can change after relocation, your number is not stable. Fourth, the start-date clause. If your address at onboarding controls the band, a late move can change the package.
This is where candidates misread the offer. Not “the RSUs are small,” but “the RSUs are small and the company is hoping I compare only the headline total.” That is the trap. The company wants you to anchor on the first-year cash flow and forget the four-year comp path.
In one offer review, the candidate fixated on the base salary because it was close to their current job. The RSU grant was materially weaker, the refresh policy was unspecified, and the sign-on simply covered the gap long enough to make the first year look harmless. That is not a strong offer. That is an offer built to be accepted quickly.
If the offer letter is vague on location, ask for the written policy before you sign. Silence is not neutrality. Silence is the company preserving flexibility at your expense.
Preparation Checklist
- Ask the recruiter which location rule controls your band before the final interview loop ends.
- Model the package across four years, not just year one. Base, sign-on, RSUs, and refresh matter together.
- Confirm whether the company uses home address, tax address, or onboarding location for classification.
- Ask what happens if you move after signing but before your start date.
- Compare the remote offer to the HQ offer on vested value, not on headline grant value.
- Work through a structured preparation system (the PM Interview Playbook covers remote compensation negotiation, equity math, and debrief-style offer analysis with real examples) before you try to challenge the band.
- Save the exact wording of any verbal promises about location, review timing, or refresh eligibility.
Mistakes to Avoid
The worst mistakes are not mathematical. They are judgment errors.
- BAD: “I deserve the same grant because I’m doing the same job.”
GOOD: “Which location tier is this offer mapped to, and what would need to change for a different tier?”
The first sounds emotional. The second sounds like someone who understands how comp committees work.
- BAD: “I’ll move later if they pay me more.”
GOOD: “If I move after signing, does the band or grant reset?”
The first is a bluff. The second is a control question. Companies respond better to control questions.
- BAD: “The base salary is close enough, so the package is fine.”
GOOD: “What is the total value over four years, including vesting, sign-on, and refresh?”
The first is how candidates get trapped by year-one optics. The second is how serious candidates avoid being underpaid for the life of the grant.
FAQ
- Does moving cities after I accept change my RSU grant?
Yes, it can. If the company ties the offer to onboarding location or tax residence, a move before start date can trigger a re-banding. After you sign, assume the policy matters more than the conversation.
- Can a remote PM offer ever be better than an HQ offer?
Yes, but only when the company pays for scarcity, not geography. If you have rare product depth, strong domain context, or a competing offer, the company may compensate above the local band. That is leverage, not generosity.
- Is a lower remote RSU grant always a bad sign?
No. It is a bad sign only when the company hides the location policy, refuses to explain the tradeoff, or uses a thin grant without offsetting base, sign-on, or refresh. A clear policy is tolerable. An opaque one is the problem.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.