11 min read
You'll run a salary negotiation checklist in this order: confirm the employer band in writing, restate three scope lines from the posting, match your resume bullets to those lines, then send one counter email that puts scope before your number. That's the whole play for US mid-level tech once you've got a written offer. Everything below is detail on each gate.
You've cleared the panel and the recruiter wants to talk numbers. Most mid-level engineers and data folks either blurt a forum median before anyone names a band, or they say they're flexible and hope the first offer's fair. Neither version gives finance a reason to move. Check your resume for free against the same posting before you negotiate. If your bullets still read like a generic IC profile while the req owns payments APIs and an on-call rotation, you're already priced below the band they'll use for strong matches.
Job searching's already draining. This isn't a pep talk. It's a gate-by-gate pass you can run tonight so your counter doesn't sound like you refreshed a comp thread five minutes ago.
Quick Wins
- Ask for the band and internal level before you name a target.
- Pull three scope lines from the posting into your counter draft.
- Match resume bullets to systems and on-call load you'll cite in email.
- Send one written counter per turn. Recruiters forward short notes in Greenhouse.
Why band plus scope beats a naked median for mid-level tech
Mid-level tech comp is not one number. It's base, annual bonus, equity refresh, signing bonus, geo tier, and sometimes on-call stipend or learning budget. Candidates who open with a hard base ask sound rigid before anyone explains level mapping or equity mix. Candidates who write I was hoping for more without naming systems, customers, or pager load sound vague in the opposite direction.
The bar your counter must clear: you restate what the role owns in production, you confirm the band for this level, you tie your ask to scope the hiring manager already sold internally, and you keep tone professional when finance pushes back.
A composite backend engineer whose top bullet still reads Responsible for API development gets priced like a generalist even when the panel spent twenty minutes on billing microservices and weekly on-call for the payments squad. A composite data engineer who never mentions the warehouse stack from the req gets filed under overpriced when they counter. The file and the email disagree.
Public ranges help you spot when an offer sits low for a title and metro. They do not replace the band the recruiter can share for this req. Use the employer band to decide where inside your range the counter belongs.
Read how to handle salary expectations early when you're still in screening. This page starts where you already have a verbal range or written offer on the table.
If the portal asked for a short note with your application, generate a cover letter that mirrors the systems language you'll reuse in the counter. Hiring managers notice when the letter and the negotiation email tell the same story.
Four gates on your salary negotiation checklist before you reply
Pass each gate in order. Dollar figures in the examples below are illustrative templates only. Swap in the band the recruiter named, the scope from your interviews, and the levers your contact said finance can move.
Gate 1: Band and level confirmed in writing
Ask three questions on the first comp call: What's the pay band for this level? Which internal level does this req map to? Does compensation follow a geo tier or one national rate for this team?
Write the answers at the top of a one-page doc. Everything else hangs off that band. Without it, you're negotiating against a guess.
Before: Thanks for moving me forward. Based on my research I'm looking for [target base]. What can you do?
After: Thanks for the update. Before I share a target, can you confirm the band for this level and whether pay follows a geo tier? The posting mentions ownership of the billing microservices and an on-call rotation for the payments squad. Once I know the band, I can suggest a base that fits the scope.
Edge case: the recruiter will not share bands. Reply with scope and level mapping only, then ask what number they can approve without you naming a floor first. You still sound prepared when finance holds the band back.
Gate 2: Scope map pulled from the posting and panel
Open the req and highlight three proof lines: systems you'll own, customers or revenue you'll touch, and team shape. Add anything the hiring manager repeated in the panel. That's your scope map. Every counter email should echo at least two of those lines.
For mid-level tech, scope usually means production systems, on-call load, customer segment, and which squads you partner with.
Gate 3: Resume bullets match the scope you'll price
Pull your strongest dated bullets that match the scope map. If the req owns Kubernetes in production and your top bullet is generic cloud experience, fix the resume before you counter. Finance approves exceptions when the file proves the scope you're pricing.
Before: Built and maintained backend services for multiple product lines.
After: Owned billing microservices on Kubernetes for four product lines, cut p99 latency 18% in Q2, and rotated on-call for the payments squad with weekly incident readouts to platform leadership.
Edge case: you're a generalist IC without classic revenue metrics. Use adoption, cycle time, or incident reduction tied to a launch. Pair the counter line with a refreshed bullet so both documents agree on scope.
Gate 4: One written counter with scope before the number
Structure every counter as acknowledge, restate scope, reference band context, propose one package. Keep it to one screen. Recruiters forward short notes to hiring managers. Walls of text get skimmed.
When base is at band max, shift levers in priority order: signing bonus, annual bonus target, equity refresh, learning stipend, extra PTO, or a written six-month compensation review tied to a milestone from interviews. Name one primary ask and one secondary ask. Save the rest for a second turn if they counter.
Before: Hi, I got your offer at [their number]. Can you do better? I have another option.
After: Hi Morgan, thank you for the written offer at [their number] base. I'm ready to join and can start in three weeks. Based on the scope we aligned on, ownership of the data platform for four product lines, weekly exec readouts, and mentoring two junior engineers, I would feel comfortable at [your counter] base. If base cannot move, please confirm a six-month compensation review tied to the dashboard rollout milestone we discussed.
Calls are fine for tone. Email is where packages get approved. After each call, send a short note that lists what you understood and what you're asking for.
Copy-paste counter block
Copy 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 number] base. I'm excited about [one specific system or squad from interviews]. Based on the scope we aligned on, [systems, customers, or on-call load you will own] and the band you shared for [level], I would feel comfortable at [your counter] base. If base is fixed, please confirm [stipend, bonus, PTO, or review clause] in the written offer. I can start on [date]. Happy to hop on a brief call if helpful.
Tighten your file before you send. See how to tailor a resume to a job description so the scope lines in your counter match bullets on the PDF the hiring manager already read.
When this checklist does not apply (and where counters stall)
No written offer yet. Do not counter on vibes from a phone call. Wait for the letter or official email with base, bonus, equity grant details, and start date. Verbal ranges shift when finance attaches the package.
You're underqualified for the scope. A tight checklist will not raise an offer on a role where your file does not prove the systems list. Fix the resume or target a better fit before you burn the thread.
Opening with a hard number before you hear the band. It forces the recruiter to defend policy instead of exploring scope. You sound like you skipped the homework question.
Treating a public median like an employer offer. Ranges online rarely match level mapping, equity mix, or geo tier on the req you're holding. Use them to build your range. Don't paste them into email as if the company already agreed.
Negotiating only on a call. Verbal yeses fade. Hiring managers approve written packages. Send the short email after every call so notes match what you think you agreed to.
I've forwarded tech counters where the candidate quoted a comp-site median but never restated the squad scope from the posting. The hiring manager assumed they had not read the req. The counter died in forwarding.
Accepting without reading the letter. Stipends, equipment, PTO, equity grant details, and review language often live outside the base line recruiters quote on the phone. Ask for the full written package before you yes.
Countering with ultimatums on the first turn. You can walk away. You usually get one clean counter before tone sours. Make it specific, scoped, and professional.
Confirm scope on the file before you send the number
Negotiation assumes you already cleared the screen. Paste the posting into the free ATS checker and confirm your Experience bullets still mirror the systems scope you plan to cite in email. A counter that references platform ownership lands flat if your resume never mentioned platforms.
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 one-page doc so you know which scope lines you can defend if the hiring manager pushes back on level or band placement.
Run the salary negotiation checklist gates tonight
A salary negotiation checklist for mid-level tech treats comp as a scope conversation with a number attached, not a number fight with scope forgotten. Confirm the band, map systems ownership from the req, align resume proof, counter once in writing, and name the lever you need if base is fixed.
Pick the before/after pair closest to your role. Paste the copy-paste block into a draft. Replace every bracket with language from your interviews and the posting. Send it after your next call, not instead of one.
This will not raise an offer on a role you're underqualified for. It does stop strong mid-level tech candidates from leaving money on the table because they replied with a bare median and no systems context.
Read more
Frequently asked questions
Start when you have a verbal range or written offer, not during first screening. Run the file and scope gates before the comp call if you can. Mid-level engineering and data roles often stall when candidates negotiate before the hiring manager has sold scope internally. The checklist assumes you cleared the panel and the recruiter is ready to talk numbers.
Not before you have the employer band and you've restated scope from the posting. A median from a public range without level, equity mix, or metro tier attached sounds copied. Ask for the band for this level, confirm whether pay follows a geo tier, then cite the systems, customers, or on-call load you'll own. Your number lands better when it follows band plus scope, not the other way around.
Shift levers. Market reads still tell you whether base sits low, mid, or top of band. When base cannot move, ask about signing bonus, equity refresh, annual bonus target, learning stipend, extra PTO, or a written six-month compensation review tied to a milestone from interviews. Total comp is negotiable more often than candidates assume once the file proves scope match.
Hiring managers approve exceptions when the PDF proves the scope you're pricing. Thin bullets that never mention the stack, customer segment, or team size from the req give finance nothing to defend. Tighten the resume to the posting before you counter so your email and your PDF tell the same story.
Use calls for tone and quick clarifiers. Put the package ask in email so recruiters can attach it in Workday or Greenhouse. Verbal yeses on stipends and review clauses fade. Send a short follow-up after every call that lists what you understood and what you're asking for in writing.