Free · No signup · Instant

Software Engineer Salary Negotiation Email Templates & Guide

Built for tech. Covers total comp, RSUs, equity, and competing offers — two polished drafts, instantly.

STEP 01 What's your situation?
STEP 02 Choose your tone.
STEP 03 Your details.

No account needed. Generated locally — nothing is stored.

Guide

1. Understanding Tech Total Compensation (TC)

Most salary guides treat base pay as the whole picture. In software engineering, base is often the smallest lever — and the hardest to move. The full package has three components, each negotiated separately:

  • Base salary. The fixed annual cash component. Large tech companies (Google, Meta, Amazon) set base within a level band — typically $20K–$40K wide. Recruiters often open at the low end of the band. Asking for a specific higher figure, anchored to Levels.fyi data for your level and location, is how you move it. If they claim the band is fixed, that is a negotiating position, not a hard ceiling.
  • RSU grant (equity). Restricted stock units vest over four years, typically on a 1-year cliff followed by quarterly or monthly vesting. The grant is quoted as a total dollar value or share count at offer time, then divided by the vest schedule. RSUs are often the easiest component to negotiate upward: if base is capped at band, ask recruiters to increase the RSU grant. Even $20K in additional RSUs is worth roughly $5K per year after vesting — often more meaningful than a $3K bump in base.
  • Sign-on bonus. A one-time payment made at hire, sometimes split across year one and year two. Sign-ons exist to bridge the gap when a candidate loses unvested equity by leaving their current employer. Even if you are not forfeiting equity, a sign-on can compensate for a weak base offer. It does not compound into future raises or bonuses, so evaluate it separately — but it is frequently a strong fallback ask when base and RSU movement stalls.

When negotiating, always quote and compare TC as a single annualized number. A Levels.fyi lookup for your role, level, and metro area gives you the market median — that is your anchor, not the initial offer.

2. The Software Engineer Salary Negotiation Email Format

Tech recruiters read dozens of negotiation emails. The ones that get movement are short, specific, and structured. The format that consistently works in the industry follows four parts in order:

  • Positive opening. Confirm your genuine interest in the role and the company. This sets a collaborative frame and signals that you are negotiating to close, not walking. Recruiters are measured on offer acceptance rates — they want to find a number that works.
  • Specific TC target. State your target as a concrete number or range. Reference Levels.fyi, Glassdoor, or a competing offer by name if you have one. "Based on Levels.fyi data for L5 engineers in New York and a competing offer from [Company], I'm targeting $X in base with a $Y RSU grant" is far stronger than vague language. Specificity signals preparation and makes it easy for the recruiter to go to bat for you internally.
  • Component breakdown. Unlike general salary negotiation, tech emails benefit from specifying which component you want to move first — base, equity, or sign-on. If the band constrains base, say you would welcome an equivalent adjustment through the RSU grant. Giving the recruiter a flexible path to yes dramatically increases the chance of a positive outcome.
  • Collaborative close. End by inviting dialogue and reaffirming your enthusiasm. Never send an ultimatum in a written negotiation email — keep the door open. A line like "I'd love to find a structure that works for both sides and am happy to hop on a call" converts the email into a conversation rather than a demand.

The generator above applies this exact structure to your details. Use the Confident & Assertive tone if you have a competing offer or strong Levels.fyi data; use Professional & Direct for FAANG recruiting pipelines where a matter-of-fact ask is the norm.

3. Tech-Specific Negotiation FAQ

How do software engineers negotiate total compensation (TC) instead of just base salary? +
Total compensation at tech companies includes base salary, RSU grants, and a sign-on bonus — each negotiable separately. The most effective approach is to reference your target TC as a single annualized number and let the recruiter decide how to allocate it across components. If they resist moving base due to band constraints, push for a larger equity grant or a one-time sign-on. Always benchmark against Levels.fyi for your target level and company before naming a figure — recruiters expect candidates who have done this research.
How do I use a competing offer from another tech company to negotiate? +
A competing offer is the single strongest lever in tech salary negotiation. Disclose it factually and early: state the company, the total TC, and the component breakdown if you know it. Avoid ultimatums — frame it as information that helps the recruiter make the case internally. Most tech recruiters have a re-leveling or comp-exception process specifically for competitive situations. You do not need to show the offer letter, but naming the company and approximate TC is far more persuasive than vague references to 'other conversations.'
Do tech companies have fixed salary bands — can they actually move the number? +
Most large tech companies have defined salary bands per level, but the bands are wider than recruiters imply. Base salary often has $20K–$40K of range within a single level. If you hit the top of the base band, recruiters can usually increase the RSU grant, add a sign-on bonus, or recommend a level re-evaluation. 'The band is firm' is a negotiating position, not a hard ceiling. Responding with a calm request to explore equity or sign-on alternatives almost always unlocks movement.

Ready to send your email?

Free. No login. Two polished drafts, instantly.

Generate your email →