By Peter Miller · Published August 10, 2026 · Last updated: September 15, 2026
12 min read · Rewrite the counter before you reply
You cleared the system design loop. The recruiter emails an offer breakdown. You'll hit reply, type thank you so much, and send it before you've mapped base, bonus, and equity on one line. That's not timidity. It's missing structure. Mid-level software engineer roles in the US often mix backend ownership, on-call rotation, and team lead expectations differently. If your counter doesn't reflect that scope, the first number becomes the anchor whether you meant it to or not.
Before you draft a counter, check your resume for free against the same posting. If bullet one still reads built features without latency, cost, or reliability numbers, the hiring manager won't have much internal ammo to stretch a band. Negotiation starts on the file they already forwarded, not on a new speech you make up on the call.
You've probably been told to ask for more and cite market rates. Fine starting point, useless when you can't tie that range to what you'll ship in quarter one. Job searching at the mid level is already slow, especially when you're weighing RSUs against a higher base at a smaller shop. You don't need a pep talk. You need language you can paste.
And it isn't only external moves. Internal promotions to mid level often skip a formal band talk until paperwork lands. Same teardown applies. Scope changed. Your counter should name total comp, not just a title bump.
If the posting asked for a short note with the application, don't put salary expectations in paragraph one. Generate a cover letter that mirrors the metrics on your resume bullets, then save comp talk for after the panel.
Do these three things first
- Write one line of total comp: base, bonus target, equity, signing, benefits you care about.
- Pull one quantified shipping result onto bullet one under your current employer before you counter.
- Wait for the written offer, then reply with a short email that names your range and flexibility on structure.
The counter language recruiters expect on mid-level SWE offers
Recruiters aren't scoring your gratitude. They're checking whether your counter gives the hiring manager something to take upstairs. A usable counter names total compensation, ties one ask to scope from the job description, and leaves room to trade base against signing bonus or equity.
Weak counters treat the offer like a single base salary line.
Strong counters read like a package adjustment. You might accept a band-capped base if signing bonus or grant size moves. You might ask for a higher base when equity is thin. You never send a wall of demands. Three short paragraphs beat a manifesto.
Most US tech offers at the mid level include more than base pay. If your email ignores bonus target, equity vesting, and signing, the recruiter assumes you only care about W-2 wages. That closes flex they might have had on other lines.
For how base and equity trade off when bands are tight, see how to negotiate equity vs salary in the US . The short version: structure is negotiable even when base is not.
Salary negotiation mid level software engineer: five counter teardowns
Each pair below is composite language from mid-level backend, full-stack, and platform offers. Dollar figures illustrate the shape of a counter, not market truth. Run your own range before you send anything. Keep the tone warm even when the gap is wide.
Pair 1: Base-only reply after a full package offer
Before: Thanks for the offer. I'm excited about the team. Based on my experience I was hoping for $165,000 base. Is there any room?
After: Thanks for the offer. I'm excited about owning the payments API and on-call rotation described in the loop. Based on scope and my research for mid-level backend roles in Austin, I'm targeting $165,000 base, 15% bonus target, and a $25,000 signing bonus, with flexibility if we need to shift between base and signing. Can we review total comp together?
The after version gives the recruiter three levers and signals you read the job, not just the pay stub.
Pair 2: Vague ask with no range
Before: I appreciate the offer. Compensation is a bit lower than I expected. I'd love to discuss if there's flexibility.
After: I appreciate the offer and I'm ready to join the platform team. For mid-level roles with this scope in Denver, I'm targeting $155,000 to $170,000 base plus standard bonus and equity. Your opening package sits below that range. Can we move base or signing to close the gap?
Pair 3: Competing-offer bluff without proof
Before: I have another offer at $180,000 so I need you to match or I walk.
After: I'm prioritizing this role because of the data platform roadmap. My researched range for mid-level SWE scope here is $170,000 to $185,000 total cash, plus equity. Your current package is closer to $160,000 cash. Can we adjust signing or equity refresh if base is fixed inside the band?
Edge case: you do hold a higher competing offer. Share it only when asked, and still frame around scope and total comp instead of ultimatums.
Pair 4: Equity-heavy startup offer
Before: The base is fine. I'll take whatever equity you offered.
After: I'm aligned on the $145,000 base. To make the package work against my current W-2, I'd need either a $20,000 signing bonus or a larger initial grant with a four-year vest. Which component has more room on your side?
I've forwarded mid-level software engineer counters where the candidate never mentioned equity refresh or grant size, so the hiring manager couldn't trade signing against RSUs even when the band was frozen.
Pair 5: Band-capped large company offer
Before: I need $175,000 base or I can't accept.
After: I understand base may sit inside a fixed band for level 4. If base holds at $168,000, can we add a $15,000 signing bonus and confirm bonus target at 15%? That gets total year-one cash where I need it without breaking the band.
Pair 6: Remote candidate against a geo-adjusted band
Before: Why is my offer lower because I live in Ohio? That feels unfair. Match the San Francisco number.
After: I saw the offer uses a Tier 2 remote band. For mid-level full-stack scope with customer-facing on-call, I'm targeting the top of Tier 2 on base and standard equity for this level. If Tier 1 isn't available, can we add signing or an earlier equity refresh review?
Edge case: relocation later. Ask whether a future office move triggers re-leveling before you accept a geo discount.
Copy-paste counter email (edit every bracket)
{`Subject: [Company] offer for [Your Name]
Hi [Recruiter name],
Thank you for the offer for [Title]. I'm excited about [one scope item from the job description].
Based on the role scope and my research for mid-level [stack] roles in [metro], I'm targeting [base range] base, [bonus target] bonus, and [signing or equity ask]. Your current package is below that range on [specific line item]. I'm flexible on structure if we can close the gap on total comp.
Could we schedule a brief call to review? I'd like a revised written offer before I accept.
Best,
[Your name]`}
Copy-paste this block, then replace every bracket with your real numbers after you run your own research.
Read how to write a counter offer for salary when you want a longer email variant with phone follow-up language.
What weak mid-level SWE counters share
Different companies, same failure modes. These patterns show up on backend, mobile, and platform offers alike.
They anchor on base salary alone. Bonus, equity, signing, and refresh eligibility never appear, so the recruiter has one knob.
They send gratitude without a range. Thank you isn't a counter. Neither is is there any flexibility without numbers attached.
They negotiate before the written offer. Verbal numbers shift. Email creates a record the comp committee can approve.
They cite market data without scope. A range tied to city and level but not to on-call, team lead, or stack ownership sounds generic.
They threaten to walk early. Ultimatums close doors at the mid level where hiring managers still have a short list of close alternates.
They accept verbally before reading vesting, clawback, and bonus target language. Total comp math includes what hits year one and what doesn't.
They skip the twenty-four hour pause. A same-hour yes reads eager and closes flex you never knew existed on signing or grant size.
Proof check before you send the counter
Your counter email is only as strong as the resume the hiring manager already shared internally. Upload the file you used in the loop and run a free ATS check against the same posting. Confirm latency, cost, or reliability proof appears inside extracted experience text, not only in a Skills footer.
Fix bullet one before you argue for a higher band. A thin file gives them nothing to take upstairs.
When you're deciding whether this offer is worth a counter at all, score your job match on the posting before you spend an hour on equity math for a role you'd decline anyway.
Send the rewritten counter tonight
That's the email a comp committee can act on. Total comp scope beats a single base ask. Scope beats generic market chatter. A written counter beats a rushed thank-you reply.
Open the offer PDF. List base, bonus, equity, signing, and year-one cash. Pick the pair above that matches your situation. Rewrite it with your metro, stack, and one proof line from the job description. Send it after one read-aloud pass, not after five anxious drafts.
Job searching is already hard at the mid level. You don't need a longer speech. You need cleaner language and a file that backs it up. When the resume is ready, check your resume for free against the same posting before you hit send on the counter.
Frequently asked questions
Lead with total compensation. Name base salary, annual bonus target, equity grant or refresh, signing bonus, and any benefits that matter to you. Recruiters often have flex in signing bonus or equity when base sits inside a band. A counter that mentions only base gives them one lever and makes you sound unaware of how tech packages are built.
After you receive a written or verbal offer and before you accept. Thank them, ask for the full package in writing if you only heard numbers on a call, take twenty-four hours to run your math, then reply with a short email that names your range and one proof point from the role scope. Do not negotiate hard during a first recruiter screen unless they asked for expectations.
Anchor to a researched range for your metro, stack, and scope, not a fixed percentage bump. If the opening number sits below that range, counter inside the range with flexibility on structure. Silence on your side usually means they treat the first number as final.
Ask which components still move. Signing bonus, equity grant size, refresh eligibility, start date, remote stipend, and extra PTO are common flex points when base is capped. Request a revised written offer for anything agreed on a call. If nothing moves, you still learned the ceiling before you said yes.
Yes. Hiring managers forward your file internally when they fight for budget. If bullets read worked on features and supported deployments, they lack proof to justify a stretch. Quantified impact on dated employer lines gives them language for a comp committee. Fix the resume before you counter, not after you accept.