Why Engineers Reject Your Offer and Accept a Counteroffer

If a senior engineer verbally agreed to join you and then accepted a counteroffer from their current employer, the offer stage is not where you lost them. It is where the loss became visible. Counteroffers succeed when the candidate's reason for leaving was money, or when nobody on your side ever established what the real reason was. The fix sits four weeks earlier in the process, not in a better closing email.

That said, some of this is structural. In several of the markets where tech hiring is competitive right now, the incumbent employer has an easier time matching than you do. It helps to know which fight you are in before you decide how to respond.

The four reasons an offer gets rejected, and they need different fixes

When a candidate declines, the stated reason is almost always compensation. The actual reason is usually one of four things:

  • Compensation was genuinely below market and nobody checked. The candidate interviewed in good faith, got to the number, and the number was wrong. This is the easiest to fix and the most embarrassing to discover at offer stage.
  • The candidate was never leaving. They were benchmarking themselves, testing whether they could get an external offer, or building leverage for an internal conversation. Your process was the instrument.
  • The process created doubt. Three weeks of silence after the technical round, a panel member who was clearly unprepared, a role description that shifted between the first and fourth conversation. The candidate read all of it as a preview of what working there would feel like.
  • A better competing offer exists and you lost on substance — scope, the person they would report to, the technology, the stability of the company. This one is legitimate. You lost fairly.

These look identical in an ATS dashboard. They are the same line item: offer declined — compensation. If your applicant tracking and HR analytics setup records only the stated reason, you will spend the next quarter raising salary bands to solve a problem that was never about salary. Make the recruiter write two sentences of free text on every decline, and read them in aggregate once a quarter.

Why the incumbent can usually outbid you

For the current employer, a counteroffer is cheap. They are comparing a raise against the cost of a replacement search, a three-to-six month ramp, and the risk that a system only this person understands falls over in the meantime. Against that, a thirty percent increase looks like a bargain, and they can approve it in a day because the headcount already exists in the budget.

You, meanwhile, are hiring into a band, and raising the offer breaks internal equity with the three engineers already on the team at that level. The incumbent is making a retention decision. You are making a compensation-structure decision. That asymmetry is why pure salary bidding wars against a current employer are usually a bad trade, even when you win them.

The asymmetry is sharper in some markets than others:

  • Turkey. Inflation-linked salary reviews mean mid-year adjustments are a normal, pre-existing process rather than an exception. A manager can reclassify a counteroffer as an early review and get it signed without an awkward conversation upstairs. Expect counteroffers to be fast and generous, and expect a competing offer in USD or EUR to carry weight beyond the headline conversion.
  • Poland, Romania, and much of Central Europe. Where senior engineers work on B2B contracts rather than employment contracts, the incumbent can raise a day rate almost immediately. There is no compensation committee in the way.
  • Germany and the Netherlands. Long statutory and contractual notice periods hand the current employer a window of one to three months in which to re-recruit someone who has already resigned. You can win the offer and still lose the hire eight weeks later.
  • The UK and the Nordics. Equity and pension structures mean the comparison is rarely like-for-like, and candidates frequently misread their own total compensation. Walk them through it before they ask their current employer to.

The pre-close happens before the final interview, not after

The single highest-leverage habit in technical and specialist recruitment is establishing the candidate's decision criteria early and testing them repeatedly. Not "what salary are you looking for" in the first call and silence after that. Something closer to this, asked more than once and by more than one person:

  • What would have to change at your current job for you to stay? If you took that question to your manager tomorrow, what do you think they would say?
  • What number, from us, would make this an easy yes? What number would make it a no?
  • Who else are you talking to, and where are they in their process?
  • Who at home is involved in this decision, and what do they care about?

The second question is the counteroffer rehearsal. If a candidate cannot articulate anything their employer could do to keep them, you are in a strong position. If they say "honestly, if they fixed the on-call rotation and gave me the lead role, I would stay," you have a candidate who is negotiating internally and using you as a reference price. That is useful information, and it is worth more at week two than at week seven.

Candidates will also tell you the truth more readily when the question comes from someone who is not the hiring manager. There is a reason the "are you actually leaving" conversation is easier for a recruiter: the candidate can answer honestly without worrying about how it reads in the decision.

Make the offer about something money cannot match

A counteroffer can match a number. It cannot easily match a change in scope, a different manager, a different system to build, or a company at a different stage. So the offer conversation should center on the things the incumbent structurally cannot reproduce — and those things have to be real, specific, and ideally already demonstrated during the interview process.

Concretely:

  • Name the first six months. What the person owns, what they will have shipped, who they will hire.
  • Have the future manager make the call, not the recruiter. The relationship with the manager is the thing candidates weigh most heavily and the thing a counteroffer cannot replicate.
  • Put a short written summary of the role and its scope alongside the contract. Candidates reread it when their current employer starts applying pressure.
  • Be honest about what is hard. A candidate who joins knowing the legacy service is a mess does not quit in month four when they find out.

This is also where an honest picture of how the team actually works matters more than perks. If your employer brand and culture work consists of office photos, it does nothing at this moment. If it consists of a clear account of how decisions get made and how engineers are promoted, it does a lot.

At director and C-level, the dynamics shift again — the counteroffer is often a board seat, an expanded remit, or an equity refresh, and the decision window stretches over months. Running executive search means managing that conversation across a longer horizon, with the candidate's current chair as an active participant whether you like it or not.

The gap between signature and start date is part of the process

In markets with long notice periods, a signed contract is a statement of intent, not an outcome. The weeks between resignation and the first day are exactly when the current employer makes its best case, when the candidate's team starts saying they will be lost without them, and when the guilt sets in.

Fill that gap deliberately. A short call from the hiring manager in the first week after resignation. An introduction to one or two future colleagues. Hardware and accounts ordered early and mentioned by name. An invitation to a team lunch or a demo day before the start date. None of this is novel, and most companies skip it because the role already feels closed in the pipeline report.

When to let them go

If a candidate accepts a counteroffer, do not re-negotiate. Thank them properly, say the door is open, and set a reminder for six months out. A meaningful share of people who accept counteroffers leave anyway within the year, because the thing that made them look elsewhere was rarely the salary and the raise did not change it. You want to be the first call when that becomes obvious, and you will not be if the last interaction was an awkward bidding war.

The discipline worth building is simpler than any closing technique: track offer acceptance rate as a real metric, record why people decline in their own words, and review the pattern every quarter. Two or three declines tell you nothing. Twelve of them will tell you exactly which of the four failure modes you have — and whether the problem is your compensation band, your process, or the role itself. That is a question you can answer with your own data, and it is cheaper to answer now than after the next search.

← All posts