Job search
How to Write a Software Engineer Counteroffer Email with a Clear, Supported Ask
Build a clear compensation request from the actual engineering offer, relevant ownership and comparable salary evidence, with two complete fictional unsent emails.
A software engineer counteroffer email should name one clear request, explain the relevant evidence and leave room for a conversation. Start from the actual offer: specify whether you want a change to annual base salary, a sign-on payment or another term. Support the request with comparable role information and your own contribution, rather than a fabricated competing offer or an unsupported market average.
Use email when the recruiter invites a written proposal, when time zones make an asynchronous exchange appropriate, or to follow up accurately after a discussion. It is not automatically the best channel for every negotiation. If you are still evaluating other roles, browse recent roles on LandOffer.ai without treating an interview process as an offer you already have.

Establish the offer and the communication channel
This article starts after you have a specific engineering offer to consider and before accepting it. Record the title, level, work location, annual base, bonus structure, equity terms, decision deadline and appropriate recruiter contact. If a component or deadline is unclear, clarify it before using the package to justify a new base-salary request.
That preparation is separate from correcting a letter that contradicts a recruiter conversation. A counteroffer proposes a change to an understood offer. It should not accidentally describe your requested amount as something the employer already promised.
Harvard College's negotiation guidance favors a real-time conversation and discourages email negotiation, while recognizing exceptions such as time-zone differences. Its advice also places negotiation before a verbal or written commitment. If the recruiter prefers a call, use a short email to arrange it instead of assuming a lengthy written argument is required.
Harvard Extension School's offer guide describes a carefully worded follow-up email as useful for recording what was agreed, if anything. A follow-up must distinguish an unresolved request from an agreement. Neither a sent email nor an encouraging reply establishes revised terms by itself.
LandOffer.ai publishes this guide. We reviewed current public career guidance and the Bureau of Labor Statistics' wage definitions on October 22, 2026. We did not handle anyone's private offer, contact an employer or test a negotiation outcome. Both complete examples below are fictional, unsent drafts; their employers, experience records, posting ranges and salary figures are invented for instruction, not measured market data.
Build a small evidence record before drafting
For engineering roles, start with the work the employer is actually hiring you to do. A backend role involving transaction processing, service ownership and on-call participation has a different scope from a staff architecture role or a short-term migration contract. Similar titles do not guarantee comparable responsibility.
Match salary evidence to location, level, employment arrangement and compensation measure. Save the source URL, date accessed, data period, range or figure, and relevant limitations. A recent posting's stated base range may inform your research, but it does not prove that you should receive its top figure or that the range applies to every location.
The BLS OEWS FAQ explains that its estimates cover occupations and geographic areas. Its wage measure excludes nonproduction bonuses and employer costs for benefits; it is not an employer's complete compensation package. The FAQ also discusses how differences in responsibility and experience affect comparisons. Do not label an occupation-wide figure as a precise offer for your engineering level.
Treat an AI-generated salary answer as a research lead until its underlying sources can be checked. An uncited “market rate” does not become reliable because the prose sounds specific. Likewise, a friend's total-compensation headline is not automatically evidence about your annual base.
Finally, connect your contribution to the offered scope. Specify what you implemented, reviewed or operated. Keep team outcomes separate from your own ownership and use measured impact only when you can support it. Relevant evidence can be valuable without a dramatic percentage or a claim that you led the entire system.
Make one request the recruiter can evaluate
A useful email usually has five parts: appreciation, continued interest in a specific part of the work, the requested change, a short justification and a practical next step. This is an editorial structure, not a proven formula for obtaining a raise.
Name the compensation component and unit. “Could the annual base salary be adjusted to $164,000?” is clearer than “Could you get closer to $164,000?” when the package also includes a bonus and equity. A single supported target lets the recruiter identify the proposed change without guessing which benefits you want adjusted. Your private walk-away point does not need to appear in the message.
Keep the evidence short enough that the recruiter can forward the request without rewriting it. One relevant experience point and a carefully characterized compensation reference can be sufficient to explain the reasoning. Keep the detailed source record for your own review; attach only information that is relevant and appropriate to share.
Avoid presenting interest as acceptance. Do not write that a change will make you sign immediately unless that is true and you intend that commitment. You can express enthusiasm and ask for review without inventing either an ultimatum or a promise.
Worked email: relevant ownership and a specific base request
Fictional case: Ren has an external Backend Software Engineer offer with $156,000 annual base salary and a $12,000 sign-on payment. The invented role is in Denver and includes payment-event processing and on-call participation. The recruiter has explicitly invited a written compensation request. Ren has four years of industry experience and has not accepted the offer.
Ren completes this evidence record before writing:
| Evidence item in the fictional record | Use in the counteroffer |
|---|---|
| The offered role's saved posting lists a Denver annual-base range of $145,000–$175,000. | Relevant context for the $164,000 request, not proof of entitlement to the top of the range. |
| Ren implemented an idempotency table and retry-handling changes for a payment-event consumer. | Specific contribution relevant to the offered transaction-processing scope. |
| An SRE colleague reviewed recovery behavior; a separate engineer owned the payment API. | Keep those contributions distinct; do not claim sole ownership of the payment platform. |
| A staff-engineer posting in another region lists a much higher range. | Exclude it from the email because level and location differ. |
| No competing offer exists. | Do not add one for leverage or invent a response deadline. |
The proposed $8,000 base increase is a request, not an achieved result. Its relationship to the fictional posted range does not establish market value or employer flexibility. Ren's complete unsent email reads:
Subject: Backend Software Engineer offer — compensation discussion
Hi Morgan,
Thank you for the Backend Software Engineer offer. I enjoyed learning about the payment-event processing work and the team's approach to service ownership.
After reviewing the offer, could the annual base salary be adjusted from $156,000 to $164,000? The transaction-processing and on-call scope aligns with my experience implementing idempotency and retry-handling changes for a payment-event consumer. The role's posted Denver base range of $145,000–$175,000 also provides context for this request.
I remain interested in the opportunity and would appreciate your review. Please let me know if a call would be helpful or if you need further context about my relevant work.
Thank you, Ren
The draft names annual base, gives a concrete target and explains why the experience matters. It does not claim that the employer owes $164,000, that another company offered it, or that Ren built every component of a larger platform. The sign-on payment is left unchanged, so the recipient does not have to infer which part of the package Ren wants adjusted.
Ren's completed preparation decision is ready for personal review, not sent. Before any real use, the writer would replace every fictional fact with verified information, check the recipient and offer deadline, and decide whether the request matches their own priorities. No employer response or salary increase is asserted here.
Worked revision: a higher package is not a higher base
Separate fictional case: Devon has two written software engineering offers at comparable levels in the same city. The recruiter for the preferred role has asked for a written proposal. All figures and grant assumptions below are invented; neither company nor offer is real.
| Component | Preferred offer A | Other offer B |
|---|---|---|
| Annual base | $168,000 | $162,000 |
| One-time sign-on | $20,000 | $35,000 |
| Total equity grant over four years | $80,000 | $96,000 |
| Illustrative first-year total with even vesting and unchanged assumed grant value | $208,000 | $221,000 |
The illustrative totals are $168,000 + $20,000 + $20,000 = $208,000 for A and $162,000 + $35,000 + $24,000 = $221,000 for B. Each uses one quarter of the grant, not the entire four-year amount in year one. Actual vesting, valuation, conditions and realization could differ. Offer B's modeled first-year total is $13,000 higher, while its base is $6,000 lower. These calculations do not make its equity spendable cash or determine which job Devon should take.
An intentionally flawed fictional draft says, “I have a higher base offer elsewhere, so please match $221,000 in salary by tomorrow.” Devon rejects it for three reasons: B does not have a higher base; $221,000 is a modeled package total, not base salary; and the record contains no tomorrow deadline. The corrected request targets $174,000 annual base and keeps the comparison accurate.

Devon's complete revised, unsent email reads:
Subject: Software Engineer offer — base salary request
Hi Casey,
Thank you for the offer and for explaining the API platform team's priorities. I remain particularly interested in the service-reliability work we discussed.
Would you be able to review an annual base salary of $174,000, compared with the offered $168,000? My experience maintaining a request-processing service and documenting recovery procedures is relevant to the role's operational responsibilities.
I am also considering another written offer with a $162,000 base and a $35,000 sign-on payment. Its components differ from this package, so I am not presenting it as a higher-base offer or asking you to match a total-compensation headline. My primary request here is the base adjustment above.
I appreciate your consideration and am happy to discuss the request at a convenient time.
Thank you, Devon
Devon has finished a truthful comparison and a clear proposal, not a negotiation result. The alternative offer is mentioned as specific context rather than inflated leverage. There is no claim that the preferred employer must match every component, and no invented commitment to accept if it agrees.
Review the message without manufacturing certainty
Read the email once for factual claims and once for the requested action. Every number should have an identified component and period. Every experience claim should match your actual contribution. Another interview, a recruiter saying an offer is likely, and a written competing offer are different facts; describe only the one that exists.
Remove unsupported urgency. If an actual decision deadline matters, identify it accurately and ask about the review timeline without pretending it will automatically extend. A counteroffer request does not suspend the original deadline or guarantee that the employer will negotiate.
If the recruiter says base is fixed, pause before converting that response into another demand. You can ask whether an alternative term is open for discussion if it matters to you, or evaluate the existing offer. An earlier salary-review date is not an agreed raise; a requested sign-on payment is not approved compensation.
When terms change, ask for the updated offer details through the employer's normal process and compare them with what was actually agreed. Keep your request, the response and the revised terms separate. This article does not send, accept, reject or determine the legal effect of any offer communication.
Finish with a supported request you can stand behind
The useful output is a concise message whose recipient can identify the ask and understand its basis. The message can be clear even when the employer declines to change the offer. Avoid judging the quality of the email solely by a promised salary outcome.
Browse recent roles on LandOffer.ai if you need more search options. Before using a counteroffer email, check each offer component, write one specific request and remove claims your evidence cannot support. Review the final wording personally and use the communication channel agreed with the recruiter.



