11 min read
You've cleared the loop, and you're not sure what to say when the recruiter calls with a number and asks how it feels. Most candidates don't say yes too fast on purpose. They fire back a higher figure with no context instead. Both answers stall the thread because US tech comp isn't one line on a spreadsheet. It's level, sign-on, equity grant, refresh timing, and what gets written into the offer letter before you sign.
Check your resume for free against the posting before you negotiate. If your file still opens with generic responsible-for language while the req asked for scope you actually carry, the hiring manager's already priced you below the band they use for strong matches. Fix the file first, then run the scripts below.
This teardown walks through what strong US tech counters look like in writing: the bar your scripts are judged against, before/after pairs across five roles, what weak versions share, and a copy-paste block you can adapt tonight. Job searching's already draining. These lines aren't a pep talk. They're meant to change what you send. If the posting asked for a short note with your application, generate a cover letter that mirrors the same scope language you'll reuse in the counter.
Quick Wins
- Ask for the band and level before you name your target.
- Restate squad scope and on-call load in every counter email.
- Counter in writing after every comp call.
- Stack rank one base ask and one fallback lever.
The bar US tech salary scripts are judged against
Generic advice treats every offer like a single base number with a thumbs up or down. Corporate recruiters in Workday and Greenhouse are scoring something else: whether your counter matches the level they sold to the hiring manager, whether your scope language matches the panel notes, and whether you can hold a professional tone when finance pushes back.
The standard your scripts must clear: you restate what the role owns, you ask for the band before you anchor, you counter with one clear package ask instead of a wish list, and you put the counter in email so it survives the forward to the hiring manager.
A composite mid-level backend engineer who opens with I need at least $165,000 sounds rigid before anyone explains leveling. A composite product manager who writes I was hoping for more without naming roadmap ownership or stakeholder count sounds vague in the opposite direction. Same mistake, different flavor. Both get filed under difficult without a thoughtful read.
US tech offers also split across base, sign-on, equity grant, and refresh clauses. Strong scripts name which lever they are moving. Weak scripts treat base as the only currency and stall when the recruiter says the band is fixed at L4 max.
Read how to handle salary expectations early when you are still in the screening stage. This page starts where you already have an offer or a verbal range on the table.
Corporate tech hiring runs on levels. Recruiters map your interview feedback to an internal band before they call with a number. When your script references the same scope the panel discussed, you are speaking their language. When your script only names a dollar figure from a public thread, you are asking them to defend a policy conversation they cannot win in one email.
Equity grants add another layer. A base that looks competitive on its own can sit below market when the RSU grant is back-weighted or the refresh cycle runs every two years instead of annually. Strong candidates ask for the full grant outline before they counter, not after they have already said yes on the phone.
Salary negotiation script for US tech roles: before/after pairs
The examples below are templates, not guarantees. Dollar figures are illustrative only. Swap in your scope, your level, and the band the recruiter actually named. Keep the structure: acknowledge, restate scope, ask, propose.
Software engineer: first comp question after onsite
Before: Thanks for moving me forward. I am looking for $175,000 base. Let me know what you can do.
After: Thanks for the update. Before I share a target, can you confirm the level and band for this req? The posting mentions on-call for the payments squad and ownership of the internal API migration. Once I know the band, I can suggest a base that fits the scope we discussed in the panel.
Product manager: counter to a verbal offer
Before: I appreciate the offer but $142,000 is too low for my experience. I need at least $158,000 or I will pass.
After: Thank you for the offer at $142,000 base and the equity grant outlined on the call. Based on the scope we aligned on, two squads, quarterly roadmap reviews with sales, and launch ownership for the billing module, I was expecting something closer to the next band. If base is tight at L5 max, could we add a $15,000 sign-on and confirm the refresh review at twelve months in the letter?
Data scientist: leveling mismatch
Before: The offer is for L4 but I have been an L5 elsewhere. Just pay me what I made before.
After: I am excited about the team. The panel focused on experiment design for the growth squad and mentorship for two junior analysts, which maps to the senior scope we discussed. Can we align the level and band with that scope? If the title must stay L4 for now, I would like a written six-month level review tied to the experimentation roadmap milestone.
Engineering manager: written email counter
Before: Hi, I got your offer. Can you do better on salary? I have another option.
After: Hi Morgan, thank you for the written offer at $198,000 base. I am ready to join and can start in four weeks. Given the scope, eight engineers across two teams, hiring plan for Q1, and on-call escalation for the platform org, I would feel comfortable at $210,000 base. If base cannot move, please confirm a $20,000 sign-on and the annual refresh policy in the letter.
DevOps / SRE: when base is fixed at band max
Before: I guess I can accept if there is nothing else you can do.
After: I understand base is at band max for this level. To make the total package work for owning Terraform modules across three regions and pager rotation every fourth week, could we add a $10,000 sign-on, confirm 20 days PTO in the letter, and schedule a compensation review after the migration milestone we discussed?
Frontend engineer: competing offer without a bidding war
Before: I have another offer for more money so you need to match it or I walk.
After: I am prioritizing this team because of the design-system work we discussed. I do have another process at the offer stage. Before I make a final decision, can we align on base and sign-on for the scope we covered, component library ownership and accessibility audits for three product lines? I want to land here if we can close the gap on total comp.
Technical program manager: early range question
Before: I need $160,000 minimum or I am not interested.
After: For a senior TPM role owning cross-team launches in this stack, I have been targeting bands in the range we discussed for similar scope in the market. Can you share the approved band and level for this req? That helps me confirm fit before we invest more time in the loop.
Copy-paste counter block
Copy-paste this skeleton into your draft and replace the bracketed lines:
Subject: [Role title] offer follow-up
Hi [Name], thank you for the offer at [their base] base and the equity outline on our call. I am excited about [one specific project or team from interviews]. Based on the scope we aligned on, [systems, squads, or regions you will own] and the level discussed for this req, I would feel comfortable at [your counter] base. If base is fixed, please confirm [sign-on, refresh timing, or review clause] in the written offer. I can start on [date]. Happy to hop on a brief call if helpful.
Edge case: the recruiter will not share bands. Reply with scope and level language only, then ask what number they can approve without naming your floor first. You still sound prepared when finance holds the band back.
Edge case: the offer includes a clawback on sign-on if you leave within twelve months. Ask for the clause in writing before you treat sign-on as negotiable headroom.
See how to negotiate salary over the phone when they insist on a live conversation before putting numbers in email.
What weak US tech salary scripts share
Opening with a hard number before you hear the band. It forces the recruiter to defend finance policy instead of exploring scope. You sound like you skipped the homework question.
Citing a forum range with no level attached. L4 and L5 bands in the same city can sit far apart. A number without a level tells the hiring manager you did not listen in the panel.
Negotiating only on a call. Verbal yeses fade. Hiring managers approve written packages. Send the short email after every call so Greenhouse notes match what you think you agreed to.
Listing twelve perks at once. Recruiters forward one clear ask. Stack rank: base first, then sign-on, then refresh or review clause. Save the rest for a second turn if they counter.
Ignoring equity language. Many US tech offers bundle RSUs or options with a vest schedule. If you only counter base, you may leave grant size or refresh timing on the table.
Accepting without reading the letter. Sign-on clawbacks, PTO, and level titles often live outside the base line recruiters quote on the phone. Ask for the full written package before you yes.
I've screened tech offers where the candidate countered with a number but never mentioned the on-call rotation they would inherit. The hiring manager assumed they had not read the req. The counter died in forwarding.
Comparing offers by base alone. Two packages with the same base can differ by tens of thousands in equity value depending on grant size, strike price, and refresh policy. Ask for the full grant schedule in writing before you rank offers.
Threatening to walk without a reason. Ultimatums work only when you will actually walk and the role is not your only option. Scope-based counters keep the relationship intact while still moving the number.
Confirm fit before you send the counter
Negotiation assumes you already cleared the screen. Paste the posting into the free ATS checker and confirm your Experience bullets still mirror the scope you plan to cite in email. A counter that references API ownership lands flat if your resume never mentioned APIs.
Then score your job match against the same req. Low fit after format fixes usually means title or seniority mismatch, not a counter five thousand too high. Fix the file or adjust the target role before you burn the offer thread.
Save the checker output with your draft counter so you know which scope lines you can defend if the hiring manager pushes back. Negotiation emails that cite work you never listed on the resume create a credibility gap that is harder to close than a modest counter would have been.
Send the written counter, not the gut-reaction reply
A salary negotiation script for US tech roles works when you treat the thread like a scope conversation with a number attached, not a number fight with scope forgotten. Ask for the band, restate squad ownership, counter once in writing, and name the lever you need if base is fixed.
Pick the before/after pair closest to your role tonight. Paste the copy-paste block into a draft. Replace every bracket with language from your interviews. Send it after your next call, not instead of one.
This will not raise an offer on a role you are underqualified for. It does stop strong tech candidates from leaving money on the table because they replied with a bare number and no context.
And if you already said yes on the phone, you can still follow up in email to confirm sign-on, equity grant size, refresh timing, and level title before you sign. That follow-up is negotiation too. Finance teams approve written packages, not the relieved sigh you let out when the recruiter said they would check.
Keep one draft counter per active offer. Swap scope language from your panel notes, not from a template you used for a different company last month. The hiring manager can tell when the email could have been sent to any employer in the same zip code.
Read more
Frequently asked questions
Run the script after you have a verbal or written offer and before you sign. Early screening calls need a range, not a hard floor. Once the recruiter names a number, switch to scope language: level, squad ownership, on-call load, and which levers they can move beyond base. A script that opens with I need $X before anyone shares a band reads unprepared. A script that restates scope and asks for the band first reads like someone who read the req.
Use the phone for tone and quick clarifiers. Send email for the actual counter. Recruiters in Workday and Greenhouse attach written notes to your profile. Verbal yeses fade after the call. A one-page email that lists base, sign-on, equity refresh, and start date gives finance something to approve without another round of guesswork.
Ask which levers remain open: sign-on bonus, equity grant size, refresh timing, level title, or a six-month compensation review tied to a shipped milestone. Many US tech employers hold base at band max but still move sign-on or refresh for strong matches. Name one primary ask and one fallback instead of a list of twelve perks.
Yes, when your interview feedback supported a higher scope than the level on the offer. Frame it as alignment: the panel discussed ownership of the payments API and on-call for the core squad, which maps to the next level in your career ladder. Ask whether the title and band can reflect that scope. Level moves sometimes unlock budget that base-only counters cannot reach.
Share a researched range, not a single number, and tie it to level and location. Example: For a senior backend role in the Bay Area I have been targeting L5 bands in the range we discussed for this stack. Then ask what band they have approved for the req. Early scripts that sound flexible but informed keep you in the process without anchoring below market before the screen finishes.