19 min read
#Recruiting
07.10.2026

Why Candidates Reject Job Offers: Counteroffers, Late-Stage Losses, and How to Close

See similar blog posts

A candidate rejecting your job offer is the most expensive failure in hiring and the one that stings most, because everything up to that point went right. Salary is what gets cited. It is rarely the whole answer, and the decisive moments usually happened weeks before the offer was drafted.

Quick answer

Candidates reject job offers for more reasons than money, though money is what gets cited. The common causes are a below-market package, a hiring process that took too long, an unresolved concern nobody surfaced, a competing offer that moved faster, and a candidate experience that told them something about your studio they did not like. The last one matters more than studios realise: candidates actively read how your process is run as evidence of how your company is run. Crucially, the decisive variable is usually communication rather than speed. Processes placed on hold for weeks still convert when the hold is explained. Silence is what loses people.

How Often Do Candidates Reject Job Offers?

Candidates reject job offers more often than most hiring managers assume, and the research tracks both outright declines and post-acceptance reneging reasonably well.

A Gartner survey of nearly 3,500 candidates found that half had accepted a job offer and then backed out before starting within a twelve-month period. Among roughly 2,000 who had recently accepted a role, 47% said they remained open to other offers and 42% believed they could find something better if they kept looking. SHRM’s coverage of the same study quoted its author describing candidates as uncommitted to their new employer and keeping one foot in the job market.

The picture softens as the labour market does. Gartner’s more recent quarterly research found 35% of candidates backing out after accepting, down from 48% two years earlier, alongside a fall in candidates receiving multiple offers. Trade coverage of the same release noted that organisations still struggle to attract talent even as candidates see fewer options, because candidates have become more selective about which processes they pursue at all.

That last point is the one to hold onto. A softer job market does not mean candidates are easier to close. It means they are choosier about where they invest their time, and more willing to walk away from a process that is not treating them well.

Why candidates judge your studio by your hiring process

Something has shifted in how candidates interpret a hiring process, and it is worth naming because studios consistently underestimate it.

Candidates now treat the conduct of your process as information about how your company operates. Not as an inconvenience to tolerate, but as data. Feedback that arrives late, interviews cancelled at short notice, a stage that slips twice, an interviewer who clearly has not read their CV: each of these is read as a signal about how much priority the hire carries internally, how decisions get made, and what it would be like to work somewhere that runs this way.

They are usually right. A process that is disorganised, slow to decide, or uncommunicative is rarely an isolated failure of recruitment. It generally reflects something real about how the organisation functions, which is exactly why candidates have learned to read it.

The practical consequence is that your process is not only your assessment of the candidate. It is their assessment of you, conducted with more attention than most studios realise, and the strongest candidates are the most discerning readers because they have the most alternatives.

How a Slow Hiring Process Loses Candidates in Two Different Ways

A slow hiring process loses candidates through two distinct mechanisms, and the two need different responses.

Active candidates who get something faster.

Someone actively looking is usually in several processes. If another studio reaches offer while you are still scheduling a third interview, you lose by default rather than on merit. Nothing about your role or your package was rejected. You were simply not finished when the decision was made.

Passive candidates who lose interest in waiting.

This one is quieter and more costly, because passive candidates are frequently the people you most wanted. They were not looking. Someone persuaded them a conversation was worth having, and that interest is fragile. It was built on momentum, and momentum is exactly what a long silence destroys. They do not reject you. They simply return to the job they already have, which was always the path of least resistance, and the longer the gap the more reasonable that looks.

These require different handling. An active candidate needs you to move. A passive candidate needs you to maintain the reason they were interested in the first place, which is a communication problem rather than a scheduling one.

The exception: why some slow hiring processes still close candidates

It would be easy to read the above as “move faster or lose everyone.” That is not what we observe, and the exception matters more than the rule.

We have seen processes placed on hold for extended periods and still convert. Headcount frozen pending a funding decision, a hiring manager on parental leave, a restructure that paused everything for weeks. Candidates waited, stayed engaged, and signed.

The difference in every one of those cases was that the hold was communicated properly. Someone told the candidate what was happening, why, and roughly when they would know more, then actually came back when they said they would. Treated as adults with a legitimate interest in the answer, people are remarkably patient.

What loses candidates is not delay. It is unexplained delay. Two weeks of silence does more damage than six weeks of honest updates, because silence forces the candidate to invent an explanation, and the explanation they invent is rarely flattering. They assume they are a backup, or that the role is not real, or that this is simply how you communicate.

It is case by case, and that is the point. There is no universal timeline that works. There is a universal obligation to keep people informed, and it costs almost nothing.

Why Candidates Decline Job Offers: The Real Reasons Beyond Salary

When a candidate declines a job offer, compensation is the reason most often given, because it is the easiest to state and the hardest to argue with. It is frequently a polite summary of something less comfortable.

1. The package was genuinely below market.

Sometimes money really is the answer. If this happens repeatedly, the problem is your bands rather than your closing, and no amount of process improvement will fix it. Benchmark against regional data rather than against what you paid the last person. Working with a specialized recruitment agency may also be of use – for example, our standard practice is being honest and transparent with our clients, when we see what they plan to offer is below market standard.

2. An unresolved concern that nobody surfaced.

The most preventable cause. A candidate had a reservation about the tech stack, the reporting line, the project’s funding, or the team’s reputation, and never raised it because the process never created a moment where raising it felt appropriate. They declined citing salary, because that is easier than saying they were not convinced by the engineering manager.

3. The role as described did not match the role as explained.

Common when multiple interviewers describe the job differently, which is itself a symptom of the studio not having agreed what it is hiring for. Candidates notice contradictions and read them accurately.

4. Candidate heard something from the market.

Games is a small industry. Candidates talk to people who worked at your studio, and what they hear about crunch, management, or how the last round of layoffs was handled carries far more weight than anything said in an interview.

5. Lack of flexibility.

Gartner’s research found candidates citing greater flexibility as the single most common driver of accepting an offer, ahead of work-life balance and ahead of higher compensation. A strong package attached to a rigid arrangement loses to a slightly weaker package attached to a flexible one more often than studios expect.

6. Nobody asked them to join.

Underrated. A process that is entirely evaluative, where the candidate is assessed for six weeks and never actively persuaded, produces offers that arrive as a verdict rather than an invitation. People accept jobs they feel wanted for.

Counteroffers in the Games Industry: The Statistic We Will Not Repeat

If you have worked with recruiters, you have heard the counteroffer statistic: that “eighty or ninety per cent of people who accept a counteroffer leave within six months”. We are not going to repeat that, because we cannot verify it.

The figure circulates widely and has no identifiable primary source. When you follow the citation chain it leads to other recruitment firms citing other recruitment firms, with no underlying study at the end of it. It is also worth noticing who promotes it: organisations with a direct commercial interest in candidates refusing counteroffers, since an accepted counteroffer means an unpaid placement. That is not a reason to assume bad faith, but it is a reason to want a source before repeating a number.

We have been through this before with the claim that applicant tracking systems automatically reject most CVs, which turned out to originate in a sales pitch. Statistics that are repeated constantly and sourced nowhere tend to have something in common.

How to handle a counteroffer without the folklore?

Without a number attached, the following is defensible from experience and from reasoning about incentives.

Counteroffers are common, particularly for senior and hard-to-replace people.

If you are hiring someone good, assume their employer will try to keep them. Plan for it rather than being surprised.

Money alone rarely addresses why someone was looking.

If a candidate’s reasons were about scope, management, direction, or project confidence, a salary increase does not touch any of them. Where a counteroffer genuinely resolves the underlying issue, accepting it can be the right decision for that person, and pretending otherwise is self-serving.

The counteroffer is best handled before it arrives.

Ask early what would make them stay, and whether they expect their employer to make an offer. Candidates frequently have not thought it through, and prompting them to do so is more useful than warning them.

A candidate who has clearly articulated non-financial reasons for moving is far less vulnerable to one.

That is a reason to understand their motivation properly rather than assuming it is money, which is also useful for everything else about the close.

How to Close a Candidate: Start at First Contact, Not at Offer Stage

The most common structural error studios make is treating candidate closing as a final-stage activity. By the time an offer is drafted, the decision is largely made.

Everything before that point is either building a reason to say yes or failing to. The candidate’s picture of your studio is assembled from the job description, the responsiveness of your scheduling, how prepared your interviewers were, whether anyone answered their questions properly, and whether they were treated as a person being recruited rather than an applicant being processed.

Establish motivation early and specifically.

Not “why are you looking” but what would have to be true for them to move, and what would make them stay. The answer shapes everything afterwards and tells you what you are actually competing against.

Surface concerns rather than waiting for them.

Ask directly, more than once, whether anything is giving them pause. A concern raised in week two is a conversation. The same concern discovered at offer stage is a rejection.

Confirm the number before you need it.

Salary expectations should be discussed early and revisited before an offer is drafted. Discovering a gap at the final stage means the process was built on an assumption nobody tested. Gartner’s research found that most candidates expect salary information in postings and a substantial share decline to apply when it is absent, which suggests this conversation is one candidates are already willing to have.

Let them meet the team.

People accept jobs because of people. A candidate who has had a real conversation with their future colleagues has a reason to join that a competing offer has to displace.

Ask for the job.

Tell them you want them, specifically, and why. It is remarkable how many processes never include this.

What a Recruiter Learns About Your Candidate That You Never Will

This is a structural point rather than a sales argument. Candidates disclose different things to a recruiter than to a prospective employer, and the gap is wide enough to decide whether an offer lands.

A candidate will tell a recruiter that they were unimpressed by an interviewer, that they are nervous about the project’s funding, that their partner is unconvinced about relocating, that they have a competing process two weeks behind yours, or that they would accept less for a better working arrangement. Almost none of that gets said directly to the hiring manager, because the candidate is still being assessed and does not want to appear difficult, uncommitted, or expensive.

That information is exactly what determines whether an offer lands. A recruiter who knows a candidate is wobbling on the reporting line can surface it while there is still time to address it. A hiring manager usually learns the same thing in the rejection email, phrased as a salary concern.

It works in the other direction too. A recruiter can test a number, float a scenario, or ask an awkward question on your behalf without committing you to anything, which is difficult to do yourself without weakening your position.

Candidate Rejected Your Offer? What to Do in the First 48 Hours

When a candidate rejects your offer, most studios do one of two things: nothing, or an immediate counter. Both waste the opportunity.

Ask why, properly, and do not argue.

A short call, framed as wanting to understand rather than wanting to change their mind, produces far more than an email. Make clear you are not negotiating. People are candid when there is nothing at stake, and defensive the moment they sense persuasion.

Decide whether a counter is worth making before you make one.

If the gap is genuinely financial and within your band, counter quickly and once. If the reason was anything else, money will not fix it and offering more confirms you were not listening.

Leave the relationship intact.

The candidate who declines today may accept in eighteen months, recommend someone next quarter, or end up working with you elsewhere. How you respond to a no is remembered, and games is a small industry.

Record it honestly.

Log the real reason, not the stated one. Three rejections citing salary might be three different problems, and you will only see the pattern if you wrote down what actually happened.

Fix the thing before the next search.

A rejection is diagnostic information about your process, your package, or your reputation. It is only expensive if you learn nothing from it.

What we tell studios about losing candidates at offer stage

The rejections that frustrate studios most are the ones that felt like they came out of nowhere. In our experience they rarely do. The signal was usually available earlier, in a hesitation during a conversation, a question asked twice, or a response time that lengthened between stages.

The single intervention we recommend most often is also the cheapest: tell candidates what is happening, even when nothing is. A message saying a decision is delayed because a hiring manager is travelling until next week takes seconds and prevents the candidate from constructing a worse explanation on their own.

And when a studio asks us to help close someone, the useful question is rarely what to offer. It is what they are actually weighing, which is a question candidates answer honestly to an intermediary and carefully to an employer. That gap is most of what we are for at this stage of a process.


Common Questions About Declined Job Offers

Why do candidates reject job offers?

Most commonly: a below-market package, a process that took too long, an unresolved concern nobody surfaced, a competing offer that moved faster, something they heard about the studio, or an arrangement that was not flexible enough. Salary gets cited more often than it is the whole reason, because it is the easiest explanation to give. Gartner’s research found candidates citing flexibility as the single most common driver of accepting an offer, ahead of both work-life balance and higher pay.

How common is it for a candidate to accept a job offer and then back out?

More common than most hiring managers assume. A Gartner survey of nearly 3,500 candidates found half had accepted an offer then backed out before starting within a twelve-month period, with 47% of recent accepters still open to other offers. More recent quarterly research shows the rate falling to 35% as the market softens, though candidates have become more selective about which processes they pursue at all.

Is it true that most people who accept a counteroffer leave within six months?

We cannot verify it, so we do not repeat it. The claim that 80 or 90 per cent of counteroffer accepters leave within six months circulates constantly and has no identifiable primary source. Following the citation chain leads to recruitment firms citing other recruitment firms, and those organisations have a direct commercial interest in candidates refusing counteroffers. What can be said without a number: counteroffers are common for good people, money rarely addresses why someone was looking in the first place, and the time to handle one is before it arrives.

How do we stop losing candidates to a counteroffer from their current employer?

Ask early what would make them stay and whether they expect their employer to make an offer. Many candidates have not thought it through, and prompting them is more useful than warning them. Understand their reasons for moving properly: a candidate with clearly articulated non-financial motivations is far less vulnerable than one who says they want more money. And make sure they feel wanted, because a counteroffer competes against your offer and also against how the process made them feel.

Does a slow hiring process always lose candidates?

No, and this is the most useful nuance we can offer. We have seen processes on hold for weeks still convert, because the hold was properly explained and someone came back when they said they would. What loses candidates is unexplained delay rather than delay itself. Two weeks of silence does more damage than six weeks of honest updates, because silence forces candidates to invent an explanation and the one they invent is rarely flattering.

Do candidates really judge a company by its hiring process?

Increasingly, yes, and deliberately. Late feedback, last-minute cancellations, slipped stages, and unprepared interviewers are read as evidence of how much priority the hire carries, how decisions get made, and what working there would be like. Candidates are usually right to read it that way, since a disorganised process rarely sits inside an otherwise well-organised company. The strongest candidates read it most carefully, because they have the most alternatives.

What should we do in the first 48 hours after a candidate declines our job offer?

Ask why on a short call, framed as wanting to understand rather than to change their mind, and make clear you are not negotiating, because people are candid when nothing is at stake. Decide whether a counter is worth making before making one: counter quickly and once if the gap is genuinely financial, and not at all if the reason was anything else. Leave the relationship intact, since they may accept in eighteen months or recommend someone next quarter. Then record the real reason rather than the stated one, so you can see patterns across searches.

When should we start closing a candidate during the hiring process?

At first contact. By the time an offer is drafted the decision is largely made, and everything before that point either built a reason to say yes or failed to. Establish early what would have to be true for them to move and what would make them stay. Surface concerns repeatedly rather than waiting for them, because a concern raised in week two is a conversation and the same concern at offer stage is a rejection. Confirm the number before you need it. And ask for the job explicitly, which a surprising number of processes never do.