US Remote Tech Salary Negotiation Checklist

11 min read

Remote US tech candidates lose comp when they treat the recruiter's first verbal number as final before they've mapped base, bonus, equity, and geo band on one page. You don't need a dramatic speech. You need to know which lever is actually stuck: posted range, level mismatch, or timing before written approval.

If you're staring at an offer email and can't tell whether you're lowballed or just reading the wrong line item, you're not alone. Remote bands are wider, tiers vary by state, and the person on the phone often can't see equity in the same screen you do. Before you reply, check your resume for free against the posting one more time. Tight scope bullets give your hiring manager cover to push inside the approval flow.

I've watched strong remote engineers accept base that sat mid-band while bonus target and equity grant were still blank on the worksheet. The recruiter wasn't hiding anything. Nobody had lined up the pieces on one page before the call ended.

Below is a salary negotiation checklist built for remote US tech: the symptom you'll recognize, three causes I see most, how to tell which one is yours, fixes with copy-paste counter language, and the moves that look like negotiation but burn goodwill.

The symptom remote tech candidates describe after the recruiter call

The pattern sounds like this: "They said the number is firm." You hang up, compare the base to your current pay, and either accept too fast or draft an angry email you'll regret. Both reactions skip the same step.

You never confirmed what "the number" included. Remote offers bundle base, annual bonus target, equity refresh, signing bonus, and sometimes a home-office stipend across different emails and attachments. Recruiters quote what they're cleared to quote on the phone. Equity often lives in a separate doc the hiring manager summarizes from memory.

The second symptom is quieter. You assumed the posting range applied to your state tier. The written offer cites a lower geo band. Nobody lied. The tier table wasn't in the job post, and you didn't ask before the panel ended.

A salary negotiation checklist for remote tech US roles starts here: name the symptom before you pick a tactic. If you can't list four comp line items from the call, you're not ready to counter. You're ready to ask clarifying questions.

Remote work didn't remove bands. It spread them across tiers and documents. Your job is to make the full picture visible on one page before you argue about any single line.

Three causes that stall remote offers, and how to fix each

Cause 1: You're negotiating base while bonus and equity are still fuzzy

Recruiters hear "I need more" and translate it to base only. Approval workflows in Greenhouse and Workday often treat base as the hardest line. Bonus targets and equity grants sometimes move on a manager signature with a one-sentence business case.

Before: "Thanks for the offer. I was hoping for a higher salary based on my experience."
After: "Can we walk through base, bonus target, and equity grant separately? I want to make sure I'm comparing total comp, not just the first line you quoted."

Fix: open a blank doc. Row for base, bonus target percent, equity grant or refresh, signing bonus, PTO, title level, remote stipend. Fill what you know from the call. Circle blanks. Your next email asks only for the blanks, not a fight about base yet.

Cause 2: Your level doesn't match the band you think you're in

Remote postings say "Senior Software Engineer" while the offer letter says "Software Engineer II." That half-level gap can sit thousands below the band you researched. Candidates blame the recruiter. Usually the panel split on seniority and the offer landed conservative.

Before: Countering base without mentioning title level.
After: "The posting read senior scope on distributed systems ownership. The offer title is mid-level. Can we align level first, then revisit the band?"

Fix: pull three interview notes where you owned architecture, on-call, or cross-team delivery. Send them to your recruiter as bullet proof, not as attitude. Ask whether re-leveling is possible before base moves. Managers re-open reqs when the proof is already in Greenhouse feedback.

Cause 3: You're anchoring to old W-2 instead of the posted range

Your last employer paid well. This employer's band is public. Recruiters can't bridge a personal gap that ignores their tier table. Anchor to the high end of what they published, plus scope from interviews, not to what you used to make in a different cost market.

Fix: screenshot the posting range. Mark where your interview scope sits (top third, middle, stretch). Your counter cites that mark and one outcome the panel already praised. Keep old W-2 in your private notes only unless they asked for current comp on a form.

How to tell which cause is yours in ten minutes

Run this triage before you write anything emotional.

• If two or more worksheet rows are blank, Cause 1 is primary. Ask for missing lines.
• If title on the offer differs from the posting seniority, Cause 2 is primary. Fix level first.
• If base sits mid-band but your proof matches senior scope, combine Cause 2 and a band-top ask.
• If you're comparing to last year's W-2 and ignoring the posted range, Cause 3 is primary. Re-anchor.

Subject: [Role title] offer - quick comp clarification

Hi [Recruiter name],

Thanks for walking me through the offer yesterday. Before I respond on numbers, could you confirm:

1) Base salary and bonus target percent
2) Equity grant size and vesting schedule
3) Which geo tier my [state] address maps to
4) Official title level on the offer letter

Once I have those four, I can reply with a thoughtful counter the same day.

Best,
[Your name]
              

{`Hi [Recruiter name],

I'm excited about the team and the distributed systems scope we discussed.

Based on the posted range for this level and the ownership we covered in interviews, I'd be comfortable signing at:

- Base: [top-third of posted band or specific anchor]
- Bonus target: [percent if discussed]
- Equity: [grant size if applicable]

If base is fixed at [their number], is there flex on signing bonus or an earlier equity refresh review?

Happy to jump on a 20-minute call tomorrow.

Best,
[Your name]`}
              

Edge case: the employer won't share equity until after you sign. Ask for a written summary of grant size and vesting start date before you accept base. Verbal equity promises without a doc are where remote candidates lose the most.

Edge case: you're relocating from a high-cost state to a lower tier while staying remote. Negotiate tier placement with HR using your target start date and permanent address. Don't accept a band label you never confirmed.

Timing matters. Counter within two business days of the written offer unless you asked for more time in writing. Silence reads as disinterest. A same-day emotional reply reads as unprepared. Clarify first, counter second.

Phone beats email for the actual counter once your worksheet is full. Email locks numbers in text recruiters forward upward. Voice lets them probe which lever you care about. Send the clarifying questions by email, save the anchor for the call.

Start date, PTO, and signing bonus are valid levers when base is hard-capped. Remote candidates forget PTO because they focus on cash. A extra week off or a four-figure signing line sometimes clears faster than another base round.

Keep a paper trail without sounding litigious. "Per our call, confirming base X pending equity doc" is professional. Screenshots of verbal promises you never follow up in writing don't help you later.

If the recruiter says "that's all we can do," ask which approver owns the band. Sometimes a hiring manager can add signing bonus even when talent acquisition can't move base. You're mapping the system, not picking a fight.

Moves that look like negotiation but burn remote offers

These are the misdiagnoses I see after the real cause was fixable. They feel active. They usually end the conversation.

Countering with no worksheet. A single base number without bonus, equity, or tier context tells the recruiter you didn't listen. They stop advocating upstream.

Threatening to walk before you asked about levers. Remote reqs are often backfilled from pipeline. A polite ask about signing bonus lands better than an ultimatum on day one.

Quoting a competing offer you can't substantiate. Recruiters verify. Fake competing numbers destroy trust faster than a weak counter.

Negotiating in the application form and again on the offer without new proof. Repeating the same range without interview scope feels like drift. Tie each ask to something the panel already validated.

Before: "I need 20% more because my rent went up."
After: "The posting band tops at [X] for this level. Given the on-call ownership we discussed, I'd like to land in the top third on base or offset with signing bonus."

This checklist won't fix applying at the wrong seniority. It stops a qualified remote engineer from leaving five figures on the table because nobody lined up the comp rows before the deadline.

For broader context on pay friction, see why candidates get rejected over pay . Sometimes the issue is alignment earlier in the funnel, not the final counter.

Align resume proof before you counter on remote tech offers

Paste the posting into score your job match and tighten the top two bullets under your current role. Those bullets become the proof you cite when you ask for band-top base or a level correction.

If you need a clean one-column file for forms that parse in Greenhouse, build your resume before you submit the counter, so the scope the manager remembers matches the file in the system.

When the employer asks for a brief note on why you're requesting band-top base, generate a cover letter that cites the same interview outcomes you list on the worksheet.

What to do before you reply tonight

A salary negotiation checklist for US remote tech professionals isn't a motivational talk. It's a worksheet, a triage, and a counter that names levers recruiters can actually move.

• List base, bonus, equity, signing bonus, PTO, title, and tier on one page.
• Identify whether the block is missing data, level mismatch, or bad anchoring.
• Email clarifying questions before you counter base alone.
• Anchor to posted range plus interview scope on the phone.
• Ask about signing bonus and start date when base is firm.

Open the posting you interviewed for. Run a free ATS check , tighten two bullets, then send the clarifying email while the panel still remembers your work.