A candidate stops replying. No email, no call, no explanation. It happens after a first-round screen. It happens the night before a scheduled interview. It happens, worse, after someone has already signed an offer letter. Recruiters call all three of these “ghosting,” but they’re not the same problem, and they don’t share the same fix.<\/p>\n\n\n\n
Seventy-six percent of recruiters say a candidate ghosted them in the past year. That’s according to a widely cited 2021 Indeed survey. Fifty-seven percent say it’s become more common than ever. If you’re dealing with this regularly, you’re not imagining a trend. You’re just missing a framework for what to do about it.<\/p>\n\n\n\n
Every ghosted candidate costs you the time already spent screening, scheduling, and interviewing them. It also costs you the other candidates you may have deprioritized while that one moved forward. Want to put a real number on that? InCruiter’s guide to calculating your own cost per hire<\/a> walks through the formula. Ghosting doesn’t need its own separate metric. It just makes your existing cost-per-hire number worse, especially when it happens late in the process.<\/p>\n\n\n\n The size of that cost depends on the stage. An application-stage disappearance costs almost nothing a few minutes reviewing a resume. An offer-stage disappearance can cost you a filled shift or a missed start date. It can also cost you a candidate you already told other applicants they lost out to. That’s why tracking ghosting by stage, not as one aggregate number, matters more than it sounds like it should.<\/p>\n\n\n\n This is a candidate who applies, maybe even schedules a first call, then stops responding before anything substantial happens. The cost here is low. The candidate hasn’t invested much time, and neither have you. This kind of ghosting is usually a sign of low intent from the start. Many applicants apply broadly and never seriously consider every role they apply to.<\/p>\n\n\n\n This is a candidate who goes quiet partway through your process, often after one or more interviews. InCruiter has covered the narrowest version of this problem: candidates who don’t show up to a scheduled interview at all. That piece, on reducing interview no-shows with automated scheduling<\/a>, covers the scheduling-friction side of it specifically. But interview-stage ghosting also happens between rounds, when a candidate simply stops answering after round two or three. That’s usually a signal about your process speed, not your scheduling tool.<\/p>\n\n\n\n This is the version nobody wants to talk about. A candidate accepts an offer sometimes verbally, sometimes in writing and then never shows up to onboarding. It’s the most expensive kind, since you’ve typically already closed the requisition and turned other candidates away. It’s also the version most likely caused by a genuinely better offer arriving late. That’s not something your team did wrong.<\/p>\n\n\n\n HireRight’s 2025 Global Benchmark Report identifies four recurring reasons. These come from its own survey data, not any single company’s anecdotal experience.<\/p>\n\n\n\n Low enthusiasm for the role.<\/strong> Candidates sense a mismatch with team fit or company culture partway through the process. Rather than say so directly, they just stop responding.<\/p>\n\n\n\n Skill mismatches.<\/strong> The role’s actual requirements don’t line up with what the candidate expected, or with their career goals. That mismatch usually surfaces once they learn more about the day-to-day work.<\/p>\n\n\n\n Compensation misalignment.<\/strong> The number the candidate has in mind doesn’t match what’s on offer, and rather than negotiate, they disengage.<\/p>\n\n\n\n Competing offers.<\/strong> Someone else moved faster, or offered more. This is the reason least within your control, and probably the most common one behind offer-stage ghosting specifically.<\/p>\n\n\n\n The same report found remote-work availability playing a real role in candidate drop-off. That effect was strongest in EMEA, where 47% of surveyed candidates reported dropping out when remote work wasn’t offered. North America and APAC saw lower rates 30% and 26%, respectively.<\/p>\n\n\n\n At the application stage:<\/strong> don’t over-invest here. A short, honest job description that sets real expectations filters out low-intent applicants before they enter your pipeline. That’s cheaper than losing them three steps in.<\/p>\n\n\n\n At the interview stage:<\/strong> speed and clarity matter more than almost anything else. Long gaps between interview rounds give competing offers time to arrive. Interview scheduling software<\/a> removes the back-and-forth that causes those gaps. For the specific problem of scheduled interviews that candidates simply skip, the no-show-focused fixes covered on this site apply directly.<\/p>\n\n\n\n At the offer stage:<\/strong> move fast on the offer itself. Stay in contact during the gap between acceptance and the start date. Teams running high-volume hiring often manage this through structured interview-as-a-service<\/a> processes. A single ghosted offer there can leave a shift or a cohort short. Keeping candidate communication consistent at scale matters even more in that setting.<\/p>\n\n\n\n Most teams that measure ghosting track a single rate: how many candidates went silent, out of how many entered the pipeline. That one number hides more than it reveals, blending a cheap problem with an expensive one.<\/p>\n\n\n\n A more useful approach: track application-stage, interview-stage, and offer-stage silence separately. Each rate points to a different fix. A high application-stage rate usually means your job posting oversells the role. A high interview-stage rate usually means your process moves too slowly. A high offer-stage rate is worth investigating hardest. It’s the most expensive kind, and the most likely to repeat if left unaddressed.<\/p>\n\n\n\n This isn’t a formal industry framework. It’s a practical starting point: three numbers instead of one, each pointing toward a specific part of your process. That beats a vague sense that “candidates ghost a lot.”<\/p>\n\n\n\n It’s tempting to treat every ghosted candidate as something to fix. Sometimes that’s right. A pattern of application-stage ghosting might mean your job description oversells the role. A pattern of interview-stage ghosting might mean your process takes too long. But a candidate who takes a materially better offer at the last minute isn’t a process failure. That’s a market outcome, and no amount of faster scheduling changes it. The useful question isn’t how to get ghosting to zero. It’s which stage is losing you the most, and whether that’s something you can actually control.<\/p>\n\n\n\n Not every disappeared candidate represents a broken process. Some of it is simply the market working the way markets work. The goal isn’t zero ghosting. It’s knowing which stage is costing you the most, and fixing the part that’s actually yours to fix.<\/em><\/p>\n\n\n\n Reference:<\/p>\n\n\n\nGhosting Happens at Three Stages and Each Has a Different Cause<\/strong><\/h2>\n\n\n\n
Application-stage ghosting<\/strong><\/h3>\n\n\n\n
Interview-stage ghosting<\/strong><\/h3>\n\n\n\n
Offer-stage ghosting<\/strong><\/h3>\n\n\n\n
The Real Reasons Candidates Disappear<\/strong><\/h2>\n\n\n\n
How to Reduce Ghosting at Each Stage<\/strong><\/h2>\n\n\n\n
Track Ghosting by Stage, Not as One Number<\/strong><\/h2>\n\n\n\n
When Ghosting Is a Signal, Not Just a Problem<\/strong><\/h2>\n\n\n\n
\n\n\n\n