12 min read
Don't counter until you've read every line of the offer packet. Remote tech comp isn't one salary box anymore. You'll see base, bonus target, equity grant, geo pay zone, and equipment stipend spread across a PDF, a Greenhouse email, and a benefits portal. You're not being greedy when you pause. You're reading the full number before you reply.
Most US remote reqs still run through Workday, Greenhouse, or Lever. The posting band you saw at apply often sets the ceiling the comp analyst uses when your recruiter requests an exception. Your resume bullets are the evidence file they attach to that request. Weak proof means a fast no even when you ask politely.
Before you draft a counter, check your resume for free against the req you already cleared. Interviewers said yes to your stories. Compensation only sees what parsed. Fix title match and bullet proof first, then run the steps below.
Job searching's draining enough without sending a counter that ignores the posted band or your own portal salary row. Solid salary negotiation strategies US remote tech hires use start with the packet, not the phone call. The sections below cover how remote bands work, six steps after the verbal offer, mistakes that stall counters, and copy-paste lines you can send tonight.
Quick Wins
- Download the offer letter and equity schedule before you reply.
- Compare base to the posting band saved from the original ad.
- Pull three quantified bullets that match the req level.
- Counter in writing with one specific ask, not a range speech on a call.
How remote tech pay bands differ from a single salary number
US remote tech offers usually bundle base salary, annual bonus target, equity, and sometimes a location adjustment. Recruiters present the story on a call. Finance stores the parts in separate systems. When you counter, you need to know which component has flex and which one is locked by a geo table you confirmed at apply.
Greenhouse postings in pay-transparency states often show a band before you interview. That band is not decoration. Comp analysts use it when your recruiter asks for an exception. Offers that land at the bottom of a wide band with staff-scope bullets are the most common underpay pattern on remote reqs.
Your portal salary row still matters at offer stage. If you entered expected compensation in Workday at apply, the recruiter already stored that number next to your file. A counter far above that row without new scope proof triggers a longer approval chain. I've screened remote backend offers where the candidate countered before reading the equity schedule and lost signing bonus flex because the ask sounded arbitrary.
Remote does not mean location-agnostic pay at every company. Some employers pay one national band. Others map your work state to zones A through D. Edge case: you moved since apply. Update the work location field in the portal before offer review if your state changed. Edge case: the req is US remote but the team syncs to East Coast hours. That constraint rarely changes base, but it can affect level mapping when they compare you to local peers.
Read should you put salary requirements on US applications if your counter will land far from what you typed at apply. Misalignment between portal data and your email counter slows approvals more than a high but documented ask.
When the offer matches the band bottom
A band bottom offer is not automatically fair. It means you cleared interviews at the minimum budget slot. If your resume shows lead scope, production ownership, and cross-team delivery, you have room to ask for band midpoint with evidence.
Before: Accept because the number "fits the range" without checking where you sit in it.
After: Posting showed 140000 to 175000. Offer base is 142000. Counter asks for 158000 base citing two lead-level bullets and on-call ownership the req listed as required.
When equity is the bigger gap
Early-stage startups sometimes hold base tight but hold refresh grants for strong hires. Later-stage public companies often treat RSU grants as formula-driven with less room than base. Read the equity appendix before you counter base alone and leave shares on the table.
For how base and equity trade off in US offers, see total compensation vs base salary before you pick which line to push first.
Salary negotiation strategies US remote tech: six steps after the verbal offer
Run these in order after the recruiter says they'd like to extend an offer. Stop when you have a written counter ready and a 24-hour pause on your calendar.
Step 1: Freeze the packet and read every line
Ask for the full written offer before you negotiate on a call. You want base, bonus target percent, equity grant size and vest schedule, start date, at-will language, and remote work location clause. Screenshot the Greenhouse or Lever posting band if the ad is still live.
Before: Counter on the phone with "I was hoping for more" before you see equity vesting.
After: Email: "Thank you for the offer. I'll review the full packet and reply with questions by Thursday." Calendar a 24-hour review block before any acceptance language.
Step 2: Map the band to your level proof
Open the req posting and your resume side by side. Highlight three bullets that prove scope at the higher end of the band. If the posting asked for lead experience and your top bullet still reads "worked on backend services," rewrite it before you counter so comp sees the same story interviewers heard.
Before: Led platform migration for payments team.
After: Led payments platform migration across four services, cut deploy time from weekly to daily, owned on-call rotation for 12 engineers.
Edge case: internal level codes like L5 versus Senior II differ by company. Anchor to posting language and years of scope, not your last employer's title string.
Step 3: Choose base-first or total-comp counter
When the offer sits below band midpoint and the recruiter has not said base is frozen, counter base with a single number, not a five-minute speech. When base is fixed, shift to signing bonus, equity grant, extra PTO, or next-cycle review written into the letter.
Edge case: contract-to-hire remote roles quote hourly in Lever. Counter in the same unit the letter uses. Mixing annual base language on an hourly letter confuses approval routing.
Step 4: Draft the written counter
Copy-paste templates for common remote tech counters:
Base counter when offer is below band midpoint (posting 150000 to 185000, offer 152000):
Subject: Offer for Senior Backend Engineer
Thank you for the offer. I'm excited about the team and the scope we discussed. Based on the posted range and my experience leading the payments migration and on-call program I outlined in interviews, I'd like to discuss a base salary of 168000. I'm happy to jump on a call this week.
Total-comp counter when base is fixed:
I understand base is set at 145000 for this zone. Would the team consider a 15000 signing bonus and a six-month performance review with comp adjustment noted in the letter?
Short reply when you need time:
Thank you for sending the packet. I'm reviewing the equity schedule and benefits summary and will follow up by end of day Friday.
Step 5: Run the call with one ask
On the follow-up call, restate enthusiasm first. Present one primary ask tied to two bullets. Let silence sit after you ask. Recruiters often need a moment to check whether the ask needs manager or comp approval.
Do not bring up personal bills, rent, or student loans. Comp teams route on level and band fit, not your monthly expenses. Scope proof and band alignment move numbers. Sob stories do not.
Step 6: Get revisions in writing before you accept
Verbal yes from a recruiter is not a signed offer. Wait for an updated PDF or DocuSign that lists every change. Signing bonus, equity, and start date must appear in the document, not just in a Slack message from your future manager.
Track employer, req title, offer base, counter sent, final base, equity grant, and sign date in a spreadsheet. Remote candidates often run two processes at once. You'll forget which counter belongs to which company without a row per offer.
If the posting required expectations in a letter, keep counter numbers identical across letter and email. Generate a cover letter skeleton with one compensation sentence, then read how to mention salary expectations in US cover letters so form, letter, and counter do not contradict each other.
Where remote tech salary counters stall out
Countering before you read equity vesting. Four-year grants with a one-year cliff change year-one value more than a small base bump. Read the appendix before you fixate on base alone.
Quoting a band from the wrong req level. Senior and staff postings at the same company carry different ceilings. Saving the wrong screenshot at apply leads to counters that sound uninformed.
Ignoring the geo zone you selected. Workday stores your work state from apply. Countering a Zone A number while your profile says Zone C kills trust fast. Fix the portal row or align the ask to your zone before you email.
Negotiating on the first call without a written packet. You'll miss bonus targets, equity refresh language, and at-will details. Always ask for the document first.
Listing five different target numbers. Email says 165000. Call says mid-170s. Portal still shows 155000 from apply. Pick one primary base ask and match it everywhere.
Accepting verbal promises about review timing. "We'll revisit in six months" without letter language is not enforceable. Ask for review timing in writing or take the offer as-is with eyes open.
Countering with no resume proof attached. Comp needs bullets they can paste into the approval form. If your file still shows the wrong title or scrambled dates, fix parsing before you ask for more money.
Edge case: acquihire or team lift-outs sometimes carry legacy grant structures. Base may be firm while retention equity has room. Ask which pool your recruiter is drawing from.
Edge case: four-day work week trials. Some remote employers trade base for schedule flex. Decide whether schedule or cash is your priority before you open the conversation.
This will not fix negotiating above a staff req with mid-level proof. It stops qualified remote engineers from leaving money on the table because they countered the wrong component or skipped the band screenshot.
Align resume proof before you counter
Compensation approvers read your resume, not your interview notes. Run the file through the free ATS resume checker with the req attached. Title parsing, date order, and keyword match still decide whether your bullets land in the packet they forward to comp.
Use score your job match on the same posting before you draft the counter. Gaps in must-have skills weaken band exceptions. Either close the gap in a bullet rewrite or shift the ask to signing bonus instead of base.
Re-read the offer after you update bullets. A stronger resume file pairs with a cleaner counter email. Sending both the same day signals you prepared, not that you're fishing for any number that sticks.
Tonight's checklist before you send the counter
Open the offer packet and the saved posting band. Mark where base sits in the range. Pull three bullets that prove the higher end. Draft one written ask with a specific number or one total-comp alternative if base is fixed.
Salary negotiation strategies US remote tech candidates use successfully share one trait: they tie the ask to band data and resume proof, not gut feeling. You're not reopening the interview. You're giving comp a reason to move you inside a band they already published.
Pause 24 hours if the packet is new. Reply with gratitude and a clear deadline for your written response. On the call, make one primary ask and let the recruiter check approval paths.
Do not sign until the letter matches what you agreed. Verbal promises about reviews, bonus, or equity refresh belong in the PDF or they did not happen.
If you're juggling multiple remote processes, sort offers into two lists: band headroom and band max. Tailor counters per list instead of reusing one target because it felt safe on the last call.
Negotiation happens after they picked you. Your job now is to make the approval form easy: right level, right band reference, right bullets. Get that clean and the counter email is a formality, not a fight.
Read more
Frequently asked questions
Yes when your resume proves scope above the listed level or when the band spans more than one internal grade. Posted ranges in Greenhouse and Lever often cover junior through mid or mid through senior. Matching the bottom of a wide band with staff-level bullets leaves money on the table. No when the offer sits at the band max and your title matches the req exactly. Countering without new proof reads like noise.
You can ask to revisit terms before you sign the written offer, but tone matters. Frame it as clarifying after reviewing the full packet, not reversing a promise. Once DocuSign is executed, changes need HR approval and often restart approvals. Verbal yes without a signed letter still leaves room. Verbal yes after signature does not.
Often yes on US remote tech reqs. Many employers run geo tables in Workday that map your selected work state to a pay zone. Countering a San Francisco band while your portal profile lists a lower-cost state can trigger an auto-deny even when the work is fully remote. Read the offer letter location clause and the state you entered at apply before you pick an anchor number.
Treat base as fixed and move to signing bonus, equity refresh grant size, start date, or annual review timing written into the letter. Ask which component has flexibility instead of repeating the same base ask. Recruiters who say final sometimes mean base only. Hiring managers occasionally hold a spot-bonus pool that never appears in the first draft.
Only when it is real, expiring, and for a comparable role level. Vague references to other processes invite skepticism and can slow background checks if they ask for proof. Stronger move for most candidates: cite posted band overlap plus two resume bullets that show delivery at the higher level. Comp teams respond to scope proof more reliably than bluff pressure.