12 min read
You finished the system design loop. The hiring manager liked your tradeoff story. Then the recruiter sends a base number that sits below the range printed on the req three weeks ago. You're tired. You want to say yes and stop interviewing. That's when most senior engineers leave money on the table for years, not because they can't negotiate, but because they never built the checklist before the offer showed up.
This salary negotiation checklist for US senior software engineers is built for that gap. You'll gather comp data while you're still interviewing, separate base from equity before you counter, and use scripts tied to proof that's already on your resume. No survey citations. No invented medians. Just the folder, spreadsheet, and language that hold up on a recruiter call.
Before you reply to the offer, check your resume for free so your scope metrics match the senior band you're pricing. A clean file in Workday or Greenhouse shortens the back-and-forth when finance asks why base should move.
I've watched senior counters land when the candidate opens a spreadsheet row, cites the posted band, and names one outcome from the resume we already screened. No drama. No fake competing offers. Just prep they could've finished in an evening while waiting on reference checks.
Quick Wins
- Screenshot base and equity ranges from three senior reqs in your target city tonight. Save URLs and dates in one folder.
- Add one scope metric to your top resume bullet before the offer call: team size, services owned, or latency cut on a named system.
- Open a blank spreadsheet with columns for base, bonus, signing, equity grant, vest years, cliff, and refresh so the first offer lands in a row you control.
What a data-driven salary negotiation checklist actually covers
Data-driven here does not mean quoting a forum salary or a survey you cannot verify. It means you walk into the offer stage with three artifacts: saved ranges from comparable postings, a resume whose top bullets prove senior scope with metrics, and a total-comp spreadsheet that splits base from equity before you pick your ask.
Recruiters in Greenhouse and Workday map you to an internal level using that resume long before they read your counter email. Senior in the US usually means you own ambiguous technical decisions, mentor other engineers, and ship outcomes that show up in reliability, revenue, or cost. If your file still reads like a mid-level task list, you get mid-level comp even when you cleared the architecture round.
The checklist is front-loaded. Most of the work happens before the verbal offer: collecting band signals, tightening proof, and modeling whether you should push base or equity first. The counter itself is a short email or call that points back to data you already saved.
Read total compensation vs base salary when two offers look close on headline base but diverge on vest schedules and bonus targets. That comparison belongs in your spreadsheet, not in your gut after a long week of interviews.
Salary negotiation checklist: six steps for US senior software engineers
Step 1: Build a comp research folder before the offer
Save posting ranges for roles that match your title, city tier, and remote policy. Note whether equity appears and if the req lists level (Senior vs Staff). Ask recruiters during the process: "What band did you budget for this level?" Many share a spread before final rounds if you ask directly.
Before: No saved comps, guessing from a friend's anecdote from two years ago.
After: Folder with Role, Location, Base min, Base max, Equity yes/no, Level title, Source URL, Date saved for three live reqs.
Triangulate patterns instead of chasing a single magic number. When three similar senior backend reqs in Denver list base bands that cluster, you have a defensible range. When only one req shows a range, pair it with the recruiter's verbal band and your own cost-of-living notes for that metro.
Step 2: Strengthen resume proof for your level band
Senior counters fail when scope is invisible. Add team size, services owned, on-call load, or cost and latency outcomes. Put the strongest metric in the first bullet under your current role before the offer call, not after you've mentally accepted.
Backend engineer example:
Before: "Worked on microservices and improved API performance for the platform."
After: "Owned checkout API for 2.1M daily requests; cut p99 latency from 420ms to 180ms and reduced AWS spend $38K annually across three services."
Platform engineer example:
Before: "Helped migrate infrastructure to Kubernetes."
After: "Led EKS migration for 14 production services with a team of four; cut deploy time from 45 minutes to 8 and documented runbooks adopted by two squads."
Step 3: Model base vs equity before you pick the ask
Line items beat gut feel. For US senior offers include base, target bonus percent, signing bonus, equity grant size, vest schedule and cliff, refresh policy, health stipend, 401k match, and PTO. Compare offers on four-year value, not year-one base alone.
Push base when you need predictable cash, carry dependents, or the employer is public with liquid stock. Push equity or signing when base is band-locked at a pre-IPO shop, when refresh timing matters, or when a modest base bump plus a larger grant changes effective pay more than another $10K on salary.
Copy-paste spreadsheet columns: Base · Target bonus % · Signing · Equity grant · Vest years · Cliff months · Refresh · 401k match · Health stipend · PTO days · Level title · Geo tier · Notes
Step 4: Pause, then ask clarifying questions
When the offer arrives, thank the recruiter and ask for the full breakdown in writing. Clarify level title, performance review timing, and whether headroom exists on base versus signing or equity. Silence is processing time you're allowed to use.
Phone script: "I'm excited about the team and the scope on the distributed systems work. Can you send the full comp breakdown including bonus targets and equity vest? I'd like to review and come back within forty-eight hours."
Step 5: Send a data-backed counter
Anchor politely to the posted range and your proof. Ask for movement on base first if cash matters most, or on signing bonus if the band is rigid. Keep the tone collaborative so you can start on good terms.
Before: "I was hoping for a bit more based on my experience. Can you do better?"
After: "Thank you for the offer. The posted range was $185K to $210K base. Given my ownership of the checkout API serving 2M daily requests and the latency reduction on that path, I was expecting base at $205K. If base is fixed at $198K, is there room for a $25K signing bonus or an equity refresh at twelve months?"
Copy-paste email block: "Thank you for the Senior Software Engineer offer. I'm excited about the payments platform scope. The posted range was [X to Y] base. Based on my recent work owning [metric outcome on named system], I was expecting base closer to [target]. Is there flexibility to move to [specific number] or add a signing bonus while keeping the start date on [date]? Happy to discuss on a quick call this week."
Step 6: Confirm the updated offer letter
Verbal yeses on equity refresh, remote tier, or signing fade. Request the revised letter before you resign. Match every line item to your spreadsheet row: base, bonus target, grant size, vest, cliff, signing, and level title.
See how to negotiate salary without competing offers for respectful counter language when you only have one option on the table.
Edge case: Staff title on the req but Senior offer
If you interviewed for Staff scope but the letter says Senior, ask whether the level was downgraded and why. Title affects band, refresh, and promotion path. Counter with resume proof that matches Staff expectations: cross-team design ownership, production incident leadership, or hiring bar participation.
If they won't move title pre-start, negotiate an earlier level review in writing at six months with explicit criteria. Do not assume a verbal promise survives a manager change.
Edge case: pre-IPO equity vs public-company base
Pre-IPO grants need share count, vest cliff, refresh policy, and what happens to unvested equity if you leave before liquidity. Public employers often move on bonus target or grant size when base is rigid. Model both paths in your spreadsheet before you argue for one lever.
Remote geo tiers in Colorado, New York, and California postings often list adjusted bands. Confirm which tier applies to your address before you counter. If base is geo-discounted for remote, ask about re-tier reviews when you relocate to a higher-cost market.
Where senior engineer salary counters stall
Accepting the first number on a video call. Pause. Ask for the breakdown in writing. Most recruiters expect one round of negotiation when your proof matches the scope they sold internally.
Negotiating base only. Bonus, equity, signing, and refresh often move when base cannot. Run total-comp math first so you know which lever actually changes your four-year outcome.
Quoting data you cannot defend. A single forum post or a friend's old offer is not a source. Stick to saved posting ranges, recruiter band language, and metrics on your own resume.
Weak resume proof at offer time. Band was set from the file they already parsed. Fix bullets before the counter, not after you sign.
Inventing competing offers. Recruiters verify. Use posting range and your metrics instead.
Ignoring level title on the letter. Senior vs Staff changes band and promotion path. Clarify before you accept.
Skipping the updated offer letter. Verbal promises on equity refresh or remote tier do not protect you. Get it in writing.
Prep your file before you counter
Run the free ATS resume checker on your latest PDF. Parsing errors and missing senior keywords can drag you to the low end of the band before negotiation starts.
Paste the req into job match score and confirm your top bullets name the systems and outcomes the posting emphasizes. Strong match proof supports a cleaner counter call.
Draft a short follow-up with the cover letter generator when you need professional tone for a counter email. Repeat the same metrics you used on the resume so the thread stays consistent.
Save a named copy of the resume you used for this employer before you send the counter. When the recruiter asks which version they saw, you want one answer, not three attachments.
Run the checklist, then sign with clarity
This salary negotiation checklist for US senior software engineers works when you front-load the data: saved posting ranges, resume bullets with scope metrics, base-vs-equity math, and a calm counter tied to both. That workflow helps you accept faster with fewer what-ifs hanging over the first paycheck.
- Collect comp ranges before the offer email arrives.
- Align resume proof to the senior band you are pricing.
- Counter on total package, then confirm everything in the updated letter.
Open your latest resume, run the free ATS check , add one metric to your top bullet, and save the offer row in a spreadsheet before you reply. That is preparation that pays you back on every future raise and referral negotiation.
Read more
Frequently asked questions
Start when you submit the application, not when the offer email lands. Save posting ranges, tighten resume bullets with scope metrics, and open a total-comp spreadsheet before final rounds. Recruiters set your band from the file they already parsed in Greenhouse or Workday. Waiting until the verbal offer means you are negotiating with half the data you could have had.
Collect the employer's posted base range, level title on the req, equity yes or no, vest schedule if shared, bonus target, signing history for the team if the recruiter mentions it, and your own resume proof: team size, systems owned, and one outcome metric. Triangulate two similar live reqs in the same city tier. That folder beats a single number from a forum thread you cannot defend on a call.
Push base when you need cash flow, have dependents, or the company is public with liquid stock. Push equity or signing when base is band-locked at a pre-IPO shop or when refresh policy matters more than year-one paycheck. Run both scenarios in your spreadsheet before you pick the ask. Many senior counters split: modest base bump plus signing or refresh at twelve months.
Yes. Anchor on the posted range, your resume metrics, and total package math. Never invent fake competing offers. Ask which levers stay open when base is fixed: signing bonus, grant size, refresh timing, remote stipend, or an earlier level review. Recruiters expect one professional counter round when your proof matches the scope they sold to the hiring manager.
Hiring managers approve exceptions when the resume proves the scope you are pricing. Thin bullets that never mention stack, customer segment, or on-call load give finance nothing to defend. Align the file to the posting before you counter so your email and your PDF tell the same story. A parser-clean PDF also keeps your level tag from drifting during ATS import.