By Peter Miller · Published August 10, 2026 · Last updated: October 5, 2026
7 min read
The offer letter looks final until you read the level line twice. You're not being greedy if you ask whether Staff scope matches Staff pay.
Senior tech comp is a bundle. Base, bonus target, equity, sign-on, and review timing all move on different levers. This US senior tech salary negotiation checklist keeps you from countering the wrong number.
You don't need a competing letter to ask clear questions. You do need a written offer and a calm list so you don't negotiate against yourself on a phone call.
Check your resume for free if you're still in the interview stage. Strong scope proof in bullet one makes the salary conversation easier later.
Three moves before any counter email
- Highlight the level and scope paragraph in the offer and compare to the job posting.
- Write base, bonus, equity, sign-on, and start date in a single table row.
- Pick one primary ask and one fallback that is not base salary.
What senior tech offers actually contain
Candidates stare at base salary. Companies think in bands tied to level, location, and equity refresh policy.
If the title says Staff but the scope reads Senior, you are negotiating level as much as cash.
Equity language matters. RSU grant size, refresh cadence, and cliff dates change take-home risk. Bonus targets look similar on paper but behave differently when revenue misses.
You are not asking for a favor. You are confirming that the bundle matches the work on the charter doc.
Job searching is stressful at offer stage. A checklist keeps you from sending a counter that sounds angry when you are actually just confused about equity units.
When recruiters say they will check with finance, that is normal. Your job is to make the ask specific enough that finance can answer yes or no without another week of vague back and forth.
Salary negotiation checklist before you counter
Work top to bottom. Check a box only when you can point to a line in the offer or posting.
Group A: Level and scope
- Title on offer matches posting title or you understand the delta.
- People management vs IC expectations are explicit.
- On-call, incident ownership, and architecture scope are named.
- You can cite two past bullets that prove that scope.
Before: Offer says Senior Software Engineer; posting listed Staff Platform Engineer with org-wide migration ownership.
After: You ask whether the band is Senior or Staff, and you attach a one-paragraph scope summary from the hiring manager call.
Group B: Cash and bonus
- Base salary number is annual, not monthly, and matches pay frequency notes.
- Bonus target percent is defined with payout conditions.
- Sign-on bonus has clawback language you can read.
- You researched a range from multiple sources and wrote it down.
Before: You counter with a single base number and no bonus context.
After: You ask whether a sign-on bridge is available if base is mid-band while bonus target stays at company default.
Group C: Equity and benefits
- Grant type, share count or dollar value, vest schedule, and cliff are listed.
- Refresh policy is described or you asked the question.
- Health, 401k match, and PTO match your non-negotiables.
I've closed senior tech offers where the win was a refresh conversation six months in, not another five thousand on base. Know which lever is live.
Group D: Process and timing
- Expiration date on the offer is real and you have calendar space to respond.
- You will send the counter in writing after a short call.
- You will not resign from a current role until written acceptance arrives.
Copy-paste counter email skeleton
Thanks for the offer. I am excited about [team mission]. Based on the scope we discussed ([one line]), I was expecting a range of [range]. Can we explore [primary ask]? If base is fixed, is there flexibility on [sign-on / equity / review timing]?
Counter traps that burn senior candidates
These moves feel bold. They usually stall the recruiter without improving the bundle.
Leading with personal expenses
Rent and daycare are real. They are not the company's pricing model. Anchor on scope and market range instead.
Countering every line at once
A laundry list reads like you never wanted the role. One primary number plus one alternative keeps the conversation open.
Accepting verbally before reading equity footnotes
Enthusiasm is good. Signing without vest detail is expensive. Read the appendix before you celebrate in chat.
This will not fix a role with unclear scope or a toxic on-call pattern you ignored in interviews. It keeps money conversations professional when the fit is real.
Align resume proof before the comp call
Negotiation starts earlier than the offer. Make sure bullet one under your current role shows the same scope you will cite on the call, then run the ATS checker on the file recruiters already have.
If you are still tailoring applications, score your job match on the posting so your proof language matches the req you are pricing.
Send one clean counter
Run the checklist, pick one primary ask, and send a short written counter tied to scope. That is how senior tech offers move without drama.
Read total compensation vs base salary when equity dominates the bundle, and use the cover letter generator if you are still documenting scope in the packet.
Frequently asked questions
After you have a written offer with level, base, bonus target, equity grant type, and start date. Pause at least one business day to run this checklist. Counter with a narrow ask tied to scope you will own, not a vague request to pay more because rent went up.
Yes. Market range research and proof of scope are enough. You do not need to invent competition. Ask what flexibility exists on base, sign-on, equity refresh timing, or title level before you accept.
Ask which parts of total comp can move. Signing bonus, additional equity, extra PTO, remote days, or review timing sometimes flex when base cannot. Get any agreement in writing before you resign.
Send numbers in writing after a short live call. Live builds rapport; email prevents typos on comp parts. Repeat the written offer back point by point so nobody talks past each other.