11 min read
You got the verbal offer. Base is fine. Equity is a mystery paragraph. You want to ask for more but you're worried they'll pull it. Most US tech candidates leave money on the table because they show up without ranges, scripts, or proof on paper.
Learning how to negotiate salary in US tech roles is not about bluffing. It's market data, total comp math, and a checklist you run before you reply yes. Recruiters expect one round of negotiation when you have an offer in hand. Founders expect you to understand equity basics at startups.
Before final rounds, check your resume for free so your scope matches the level you're pricing. Weak bullets anchor low offers. Then build your range folder and run the checklist below.
You won't win every ask. You will stop accepting offers you didn't understand. Recruiters respect candidates who counter once with numbers, not candidates who argue without data or accept without reading equity footnotes. Preparation beats confidence alone on the call.
Quick Wins
- Write your target base, bonus, and equity ask on one page before the recruiter calls with numbers.
- Add one scope metric to your top resume bullet if your file still reads junior on paper.
- Ask for the offer letter components list in writing: base, bonus target, equity grant, vesting, sign-on.
What data-driven salary negotiation means in US tech hiring
Data-driven salary negotiation in US tech roles means you anchor asks to role level, geography, company stage, and proof of scope instead of gut feeling. US tech comp is usually total compensation: base salary, annual bonus target, equity grants with vesting schedules, sign-on bonuses, and sometimes relocation or learning stipends.
Recruiters set bands before they meet you. Your resume and interview signals place you inside a band. Negotiation moves you within that band or upgrades level when proof supports it. Random aggressive asks without data get dismissed. Specific counters tied to market ranges and your shipped outcomes get escalated.
Startup offers weight equity heavier. Public tech weights RSUs with clearer dollar values. Both still negotiate on base, sign-on, and level title. Never compare offers on base alone.
This checklist won't fix a role you aren't qualified for. It will stop you from accepting unclear equity or leaving five figures on the table when the company already decided they want you.
Level titles on the offer letter affect the next search more than candidates expect. Negotiating from mid-level to senior on paper can be worth more than a one-time sign-on when RSU bands jump. Bring resume proof that matches the level ask before you make that request.
Benefits worth modeling include health premium coverage, HSA or FSA contributions, 401k match timing, and parental leave paid weeks. They rarely change the base counter but affect four-year value when two base offers look equal.
Signing bonus clawback language matters. Read whether sign-on repays if you leave within twelve months. That changes the true value of a counter that looks generous on day one.
US tech negotiation rule: one data-backed counter, total comp on one page, written confirmation of equity math, and resume proof that supports your level ask.
Step-by-step: negotiate salary in US tech roles
Step 1: Build a market range before the offer arrives
Collect comps for your title, level, metro, and company stage. Use public band sites, peer conversations, and recruiter feedback from prior screens. Save screenshots or notes in one folder.
Define three numbers: walk-away minimum, target, and stretch. Stretch requires proof: team size, revenue impact, on-call scope, or rare stack depth.
Update the folder when you learn the employer's level mapping during interviews. Staff at one company may equal senior elsewhere.
Note whether the employer uses level codes like L5, E4, or IC3. Mapping those codes to your resume scope prevents you from negotiating inside the wrong band. Recruiters can sometimes bump level when interview feedback and resume proof align.
Save recruiter verbal ranges in writing when they share them. Email recap after screening calls creates a paper trail if the written offer arrives below what was discussed.
Step 2: Strengthen resume proof before final rounds
Offers anchor to paper scope. If your resume hides metrics, fix it before the panel ends.
Before: Led backend services.
After: Owned payments microservices in Go serving 2M daily transactions with 99.95% uptime and on-call rotation for six engineers.
Run HireFlow's free ATS resume checker if you're still editing layout. Clean parsing keeps recruiter notes aligned with the file hiring managers saw.
Strong proof supports level bumps that move bands more than haggling $5k on base.
Step 3: Model total compensation on one worksheet
Create rows for base, bonus at target and max, equity grant type, share count, strike or FMV, vesting years, cliff months, sign-on, and expected refresh policy.
For RSUs at public companies, use share count times current price with four-year vesting. For private startups, ask for share count, latest 409A, and preferred price context. Write assumptions explicitly.
Compare offers on four-year value, not headline base. A lower base with higher equity may win or lose depending on stage risk.
Document refresh grant policy if the recruiter mentions it verbally. Some public companies grant refresh on anniversary. Startups may promise future grants without numbers. Ask what has been done for peers at your level in the last two cycles.
Step 4: Prepare scripts for recruiter and hiring manager calls
Use collaborative language tied to data, not ultimatums.
Recruiter script: Thank you for the offer. Based on my research for senior backend roles in Austin and the scope we discussed owning payments and on-call, I was targeting base near $185k. Is there room to move base or sign-on while keeping the equity grant?
Startup script: I'm excited about the role. Can we walk through the equity grant on paper: share count, strike price, last 409A, and vesting cliff? I want to compare total comp fairly against my other process.
Ask for time to review. Twenty-four to seventy-two hours is normal. Do not accept verbally on the call without running your checklist.
Write your scripts on paper before the call. Reading from notes sounds prepared, not weak. Recruiters hear improvised counters that contradict your earlier screening answers. Keep numbers consistent with what you already shared.
Step 5: Trade components when base is rigid
Companies often flex sign-on, equity, start date, remote stipend, or level title when base is fixed by band rules.
If base cannot move, ask for increased sign-on or additional equity with rationale. If equity is opaque, ask for clearer grant numbers before you trade base away.
Title upgrades matter for the next search. Senior vs mid-level on the offer letter affects future bands.
Remote stipends and learning budgets are negotiable at many US tech employers even when recruiters forget to mention them. Ask once. The worst outcome is a clear no you can plan around.
Step 6: Confirm everything in the written offer letter
Verbal promises disappear. Read base, bonus target percentages, equity grant details, vesting cliff, start date, at-will language, and contingencies.
Ask HR to clarify anything vague. Get revised letter before you resign elsewhere.
Save final PDFs and emails in a personal folder. Negotiation history helps if grant paperwork differs from the letter.
Second script for late-stage public tech: *I'm aligned on joining. The RSU grant is below peers at this level in Seattle for similar scope. Can we revisit share count or a sign-on true-up while keeping base as proposed?* Polite, specific, and tied to level bands recruiters can escalate.
Confirm whether bonus is discretionary or guaranteed target. US tech offer letters use both patterns. Misreading bonus language causes regret after you already resigned.
Edge case: competing offers and exploding deadlines
If you have another written offer, share timing honestly without fabricating pressure. Recruiters can sometimes accelerate approvals when process is real.
Exploding offers of forty-eight hours are a red flag unless disclosed upfront. Ask for extension to run your checklist. Ethical companies grant reasonable time.
Do not invent competing offers. Recruiters verify more than candidates expect.
When one offer is base-heavy and another equity-heavy, compare four-year worksheets side by side before you counter either. Candidates lose negotiating room when they ask for base on the wrong package type without reading the grant letter.
Copy-paste preparation checklist before you counter
Before you reply:
1. Market range for title, level, metro, stage saved.
2. Resume top bullets show scope matching your ask.
3. Total comp worksheet with four-year equity assumptions.
4. Primary counter and fallback trades written.
5. Questions on 409A, vesting cliff, bonus target, and sign-on drafted.
6. Calendar reminder to respond within agreed window.
Read how hiring software flags salary mismatches and salary transparency laws by state when you compare packages.
Common mistakes
Negotiating before you have an offer. Early hard demands can end screens. Wait until they want you.
Comparing offers on base salary alone. Model equity, bonus, and sign-on on one four-year view.
Accepting vague equity language. Get share count, strike, vesting, and cliff in writing.
Weak resume scope anchoring a low band. Fix metric bullets before final rounds, not after the offer.
Verbal yes without reading the letter. Confirm every component in the written offer before resigning.
Strengthen your file before you negotiate US tech comp
Run HireFlow's free ATS resume checker before final rounds so recruiters and hiring managers see the same scope you will price. Offers follow paper proof.
Use the free cover letter generator only when letters are required. Keep metrics aligned with resume bullets you will cite on the negotiation call.
Research role ranges on HireFlow salary pages when available for your title and metro. Bring printed notes to recruiter calls.
See how to answer salary expectations with scripts for screening-stage wording that protects your range.
Print your total comp worksheet for the recruiter call. Numbers on paper beat improvising when they ask what would make you sign today. Silence after an offer is normal. Confusion about equity math is not.
Bring your resume PDF to the negotiation call. Referencing the same metrics on paper and in conversation keeps anchors consistent.
Run the checklist before you say yes
How to negotiate salary in US tech roles comes down to market ranges, total comp math, resume proof, and one data-backed counter. Preparation beats improvisation once the offer lands.
- Build your range folder before the recruiter calls with numbers.
- Model four-year total comp, not base alone.
- Confirm equity and bonus details in the written offer letter.
- Keep counter emails and revised letters in one offer folder.
When the offer arrives, pause. Run the checklist, check that your resume still proves the scope you're pricing, send one collaborative counter with data, and read the revised letter line by line. That is how US tech salary negotiation stops being a guess. Save every counter email in your offer folder.
Read more
Frequently asked questions
After you have a written or verbal offer and before you accept. Negotiating too early in screening can disqualify you at some companies. Once they decide they want you, data-backed asks on base, bonus, equity, and sign-on are normal in US tech.
Role level, location, company stage, base range, bonus target, equity grant type, vesting schedule, and recent comparable offers in your market. Bring proof from your resume bullets that justifies the top of band: scope, stack, and shipped outcomes.
Yes when base is below market and equity is a major part of the package. Ask about share count, strike price, latest 409A, vesting cliff, and refresh grants. Get numbers in writing. Do not accept hand-wavy percent lines without context.
Yes. Recruiters anchor offers to the level your resume supports. If bullets hide scope and metrics, you look mid-level on paper even when you operated senior. Fix the resume before final rounds so the offer band matches your proof. Bring the same metrics verbally that appear in your top bullets.
Ask which component is fixed. Sometimes base is rigid but sign-on, equity, start date, or level title flex. Silence is not an answer. One polite counter with data is expected in US tech hiring. If everything is truly fixed, ask for written confirmation so you can compare apples to apples against other offers.