How to handle a counter-offer when you are hiring

Most counter-offers are a reaction to convenience, not commitment

The CIPD's recruitment factsheet is a sound reference on running a fair, well-planned hiring process.

A counter-offer usually appears when the current employer realises the person is serious about leaving. That does not mean the underlying problem has vanished. It usually means the current employer has noticed the risk and is trying to keep a useful person in place.

That is why a counter-offer often sounds generous and still fails. The title might change. The package might move. The promise of a future promotion might appear. But if the candidate started looking because the role had stalled, the manager was absent, or the work no longer fit, the same frustrations are still there.

You should treat the counter-offer as a signal, not a solution. The candidate is being reminded that they are valued. That is not the same thing as being well managed.

A practical example. A sales engineer tells you they are looking because their current team keeps changing priorities and they never get proper support on deals. The counter-offer arrives with more pay and a nicer title. The real problem is still the same. The person is still in a team that has not fixed how it works.

Use a short checklist when a candidate mentions any risk of a counter-offer:

If the answer to most of those points points back to the same pain, assume the counter-offer will not hold.

• Why did they start looking in the first place.
• What, if anything, has changed since then.
• Whether the current manager knows they are unhappy.
• Whether the current employer is likely to move fast.
• Whether the candidate is likely to be swayed by short-term money.

Ask early enough to see the counter-offer coming

Speed and clarity count, because your hiring process is a product demo.

You do not wait until the offer stage to find out that a candidate has options, doubts, or a current employer who reacts quickly. You ask early. Not in a heavy-handed way, but plainly enough that there are no surprises later.

The right questions are simple and direct:

These questions are not about prying. They are about shortening the distance between conversation and truth. If a candidate hesitates, that matters. If they say their current employer is already hinting at a raise, that matters too.

You should also ask about process timing. Notice periods vary, and some companies respond faster than others. That is not a reason to delay your own process. It is a reason to manage it tightly and keep the candidate engaged.

Most of this starts with what a good job brief contains.

A good brief gives you more than a title and a list of skills. It gives you the reason the role exists, the problems the person must solve, and the shape of the team they are joining. That makes it easier to spot whether the candidate is genuinely pulled by the role, or only browsing until their current employer wakes up.

• How long have you been thinking about a move.
• What would make you stay where you are.
• Have you told anyone at work that you are open to moving.
• Is there anything at your current company that could be used to keep you.
• If your manager offered you more money tomorrow, would that change the reason you are looking.

The first 48 hours decide whether the candidate stays engaged

When a counter-offer lands, the first two days matter more than most hiring managers think. That does not mean you panic. It means you move with pace and keep the candidate close.

Your aim in the first 48 hours is not to outbid the current employer on money. Your aim is to help the candidate make a clear decision based on the real role, not the emotional rush of being wanted twice.

A strong response usually has four parts.

First, check in quickly. Ask what was said, who said it, and whether anything in the current situation has genuinely changed. Keep it factual.

Second, restate why they were interested in your role. Bring the conversation back to the original reason they spoke to you in the first place. If they were leaving for growth, autonomy, technical depth, or a better manager, say that plainly.

Third, keep the offer process moving. Send the paperwork, confirm timelines, and make the next step very clear. Lingering gives the counter-offer more room to breathe.

Fourth, make space for the candidate to think. Pressure usually backfires. A calm conversation, handled quickly, is more persuasive than a long pitch.

A useful rule of thumb. If the candidate only seems confident after you explain the role again, they were not sold on the current job. If they only seem confident after the current employer throws money at them, they were probably never leaving for the right reason.

It helps to know how a specialist search runs before you brief anyone.

That matters because specialist hiring is not only about sourcing. It is about managing the whole search well enough that the best people stay in play. Market mapping, shortlist quality, interview feedback, and offer management all affect whether a candidate reaches the finish line or gets pulled back into the old one.

Do not try to beat the counter-offer with pressure or guilt

The worst response is to make the candidate feel disloyal, indecisive, or ungrateful. That sort of pressure may get a quick answer. It does not get a good one.

You should also avoid bargaining from a weak position. If you start matching the current employer without checking the real issue, you are paying more for the same risk. That is not hiring. That is papering over a problem.

Here is what not to do:

You should also not oversell the role to compensate. If the job has a weak brief, a disorganised interview loop, or a manager who cannot explain the business problem, a counter-offer will expose that. It does not create the weakness. It reveals it.

In technical and GTM hiring, this happens often enough to plan for. Security engineers, sales engineers, senior developers, and data people usually know their value. They are not moved by noise. They are moved by clarity, the team, and the work.

Speed matters here because the hiring process is the product demo, and slow processes tell the candidate what working with you will feel like.

• Do not ask the candidate to promise they will not take a counter-offer before they have had the conversation.
• Do not assume a pay bump will solve a management or product problem.
• Do not slow your own process to see if they “really want it”.
• Do not disappear for a week and then expect enthusiasm.
• Do not guilt them about loyalty, notice, or inconvenience.

Keep the candidate moving through notice with steady, honest contact

Once the offer is accepted, the job is not done. The notice period is where a lot of good searches slip. A counter-offer can arrive late, when everyone thinks the deal is secure.

This is where steady contact beats busy contact. You do not need daily paragraphs. You do need regular, relevant check-ins. The candidate should feel that the process is still alive and that the future manager is still confident in them.

Keep the touchpoints practical:

A concrete example helps. A candidate signs the offer, then their current manager becomes unusually friendly and suggests a revised plan in the next quarter. If you have been silent for two weeks, that conversation gets louder. If you have kept in touch with clear steps and honest context, the candidate has a better frame for the decision.

This is also where honesty matters most. If the role has downsides, say so. If the first six months will be intense, say so. If the team is small and the hire will need to shape things, say so. Candidates trust the process more when nobody is pretending it is easier than it is.

A useful guardrail is to keep the reason for the move front and centre. If the person wanted better scope, a stronger manager, or a more technical environment, remind them of that. A counter-offer can only win if it replaces the real reason they wanted to leave. Most of the time, it does not.

• Confirm the start date and any paperwork quickly.
• Check whether the notice period has changed.
• Ask whether anything unexpected has come up at their current company.
• Keep any promised introductions or onboarding steps moving.
• Stay available without hovering.

The right questions are better than the wrong promise

A lot of hiring managers want a script that will stop a counter-offer in its tracks. There is no script that does that. There is only a better search process and better judgement.

So ask questions that surface risk early and honestly:

The last question is often the useful one. It gets past money and into motive. That is where the real answer usually lives.

For employers hiring in cyber security, software, data and AI, or commercial roles, this matters even more because these candidates usually have options. They are often approached more than once, and the current employer may only react when the offer is real.

That does not mean the candidate is unreliable. It means the market is active. Your process has to be sharper than the counter-offer, not noisier.

If you are hiring for a role like this, talk to KOLY about how the search would run.

• What would your current employer need to change for you to stay.
• Which part of your current role has made you want to move.
• If nothing changed at your current company, would this new role still appeal.
• How likely is your manager to fight to keep you.
• What would make you regret not taking the new role.