What does a strong counter email to a recruiter contain after a written offer arrives?
answer
- Fewer moving parts wins
- Write for a reader you never meet
- Give them one thing to approve
- Ask, reason, and warmth
basics
~20 sA strong counter email carries three things: one specific ask, one justification tied to the level and the benchmarks gathered, and one line keeping the relationship warm. Hedging, apologies and an unranked wish list all weaken it.
solid answer
~50 sThree moving parts, and no more. **One specific ask** — a single number or a single named change, not a menu and not `can you do better`. **One justification** — the level and scope the role was described at, plus the benchmarks you gathered for it, so the recruiter has something to repeat to whoever approves the increase. **One warm line** — you want the job, and this is the thing that would let you sign. Put it in writing, because a recruiter almost always has to carry the ask to someone else, and a written ask travels intact while a phone ask travels as a paraphrase. Keep it short, keep the tone plain, and give one clear thing to say yes to. If you genuinely have more than one ask, rank them and say which matters most.
go deeper
Remember that a counter goes in writing and names one specific thing, plus a reason and a friendly closing line. Ask for the offer in writing first, and never send back only 'can you do better'.
Explain why the shape works: the recruiter has to forward the ask to an approver, so it must be specific enough to repeat and short enough to survive being paraphrased. Be able to turn a benchmark for a level into a single figure with a justification attached.
Show that you can rank asks and read what the written offer implies about which one is actually movable. Judge the sequencing too — call first to learn what is flexible, then write, so the document only contains the ask you already know is worth making.
Own the cost side of the counter: goodwill you spend on the number is goodwill you do not have for scope, start date or the first months on the job. Decide deliberately whether the ask is worth that, and be willing to send no counter at all when it is not.
## Why the counter is a document, not a moment In most hiring processes a recruiter cannot approve an increase alone. They carry the ask to a hiring manager, a compensation partner, or an approval step of some kind — practice varies by employer, but the shape is common. That single fact drives almost every rule below: **you are writing for a reader you will never meet.** Your ask has to survive being forwarded. A phone call is excellent for tone, for hearing what is flexible, and for keeping the relationship human. It is poor at travelling. What gets forwarded is the recruiter's memory of what you said. So a good pattern is: take the call, thank them, ask clarifying questions, say you will come back with your thinking, then send the counter in writing. If the conversation happens live, follow it with a short written confirmation of exactly what you asked for. ## The three parts ### One specific ask Name the thing. A single base figure you can defend, or a single named change. Specificity does two jobs: it gives the recruiter something to request rather than something to interpret, and it tells them what closes you, which is the only piece of information they actually need. The failure mode here is the vague counter — `it's a little below what I was hoping for, is there any flexibility?` It carries no number, no reason and no priority, so the recruiter must guess all three, and guessing is expensive for them, so they guess small. If you truly have more than one ask, **rank them explicitly** and say which one matters most. An unranked list of five wishes reads as a shopping trip; the approver cannot tell which yes would produce a signature, so the safe move on their side is a token improvement to the cheapest item. ### One justification The justification exists so the recruiter can argue on your behalf in a room you are not in. It should be short, specific and repeatable: the level and scope the role was described at during the loop, the benchmarks you gathered for that level and location, and the responsibilities that came up in the interviews. What does not work as justification: your rent, a generic multiplier applied to their number, or an assertion that the offer is `low` with nothing attached. Personal need is not a lever the approver can act on, and arithmetic performed on the employer's own figure concedes that their figure was the right starting point. ### One warm line End with enthusiasm that is real. The recruiter's risk is that they spend political capital on an increase and the candidate declines anyway. A sentence that says the role is the one you want, and that this ask is what would let you sign, converts your email from a threat into an approval request. One more piece of warmth that costs nothing: acknowledge the work they did to get the offer approved in the first place. Negotiation is not adversarial theatre; you are asking a person to advocate for you. ## Worked example: a platform role A candidate has a written offer for a platform engineering role. The recruiter described the base as sitting mid-band for the level. The counter email is roughly six sentences long: - A thank-you and a plain statement that the candidate wants the role. - The ask: one specific base figure, named once. - The justification: the scope discussed in the loop — owning the internal build and deploy tooling for several teams — and the benchmarks the candidate gathered for that level and location. - The closing: `Given the level and the market data I have, I was targeting the upper part of the band — can we get there?` followed by a line saying they are ready to sign on that basis. That email can be forwarded verbatim, and it survives the forwarding. ## Tone and length Short beats long. Every extra paragraph gives the reader another thing to disagree with, and length reads as anxiety. Avoid apologising for asking, avoid explaining at length how difficult the decision is, and avoid framing the ask as an ultimatum unless you are genuinely willing to walk — a threat you would not honour is the one negotiating move that is hard to take back. Also, get the timing right. Ask for the offer in writing before you counter, so you are negotiating against the real terms rather than a remembered summary, and ask when they need an answer so you know how much room you have to think.
- Would you make the counter on a call or in an email, and why?Both, in that order. The call is where I hear what is flexible and keep the tone human; the written note is what actually travels, because the recruiter usually has to carry the ask to an approver and a paraphrase loses the number and the reason. So I thank them on the call, ask clarifying questions, and follow up in writing with the same ask stated once.
- You have more than one thing you want changed — how do you keep the counter from becoming a wish list?Rank them and say the ranking out loud. I name the one that would close me as the ask, and mention at most one secondary item as a lower priority. An unranked list makes the approver guess which yes produces a signature, and the safe guess on their side is a token move on the cheapest item, which is the worst outcome for both of us.
- What justification would you avoid putting in a counter email?Anything the approver cannot act on. Personal costs — rent, a move, family expenses — are real but not levers they can take upstairs. A percentage applied to their own figure is not a reason either; it concedes their number as the correct baseline. I keep it to the level and scope the role was described at and the benchmarks I gathered for it.
saying these in an interview costs you the question
- Countering with 'is there any flexibility?' and no number
- Listing several unranked asks so no single yes closes the deal
- Justifying the ask with personal expenses rather than level and scope
- Apologising at length for asking at all
- Making the ask only by phone, so nothing survives the forward
- Threatening to walk away without actually being willing to