Ghost Employers:
What Happens After the Interview Goes Quiet
A candidate finishes a second interview for a dispatcher role on a Thursday afternoon. The hiring manager says he’ll follow up early next week with next steps. Next week comes and goes. So does the one after that. No call, no rejection, no update, just the kind of silence that makes a person start checking their email for a message that already arrived and got missed. It didn’t. The company simply stopped responding.
Defining a Ghost Employer
A ghost employer is a company that goes silent on a candidate somewhere between the interview and a decision. It’s a different problem than a ghost job. A ghost job means the posting itself was never real, a role that’s already filled, was never open, or exists to collect resumes. A ghost employer means the opposite: the role was real, the interview happened, and the company that was evaluating the candidate simply stopped responding before it reached a decision or never closed the loop on the job being filled.
That distinction is an important one. A ghost job gets solved by pulling a listing that shouldn’t be live. A ghost employer gets solved by someone picking up a decision that’s already sitting on their desk and sending it. One is a posting problem. The other is a follow-through problem.
This isn’t the same as a slow process, either. Candidates understand that scheduling takes days and that a manager covering a shift can’t always call back same day. What makes it ghosting is the absence of any signal at all and the candidate is left wondering whether they’re still in the running or whether the decision happened without them.
How Often It’s Happening
The numbers back up what candidates currently job seeking already know. Criteria Corp’s 2026 Candidate Experience Report, covered by Fortune, found 53% of job seekers were ghosted by an employer in the past year, the highest rate measured in three years and up from 38% in 2024. From the other side of the desk, Resume Genius’s 2026 Hiring Trends Report, a Pollfish survey of 1,500 U.S. hiring managers, found 86% admit to ghosting candidates themselves, most often citing applicant volume as the reason.
LiveCareer’s Ghosting Consequences Report, based on a survey of more than 1,000 U.S. workers, found 45% have been ghosted by an employer during the hiring process, and 45% believe employers ghost more than candidates. The gap in perception is the real problem here. Hiring teams tend to chalk their own silence up to being busy. Candidates read the exact same silence as a decision about them personally.
What it Costs
The cost splits depending on which version of silence actually happened, and the candidate never finds out which.
If the seat is genuinely still open, unfilled because nobody made the call either way, that’s a direct hit to time to fill. A candidate who made it to a second interview was close to a hire. Once they give up waiting and take another job, as most of them do, that seat doesn’t just need a decision anymore. It needs new sourcing, new screening, new first interviews, for a seat that was one step from done. That’s weeks added back onto a req that should have closed.
If the seat already went to someone else, the time-to-fill cost doesn’t apply. The cost there is entirely about the candidate who didn’t get picked, and what they do next. LiveCareer found 48% of candidates won’t apply to a company again after being ghosted, and 42% say it makes them trust the company less. For an employer running the same roles on a rolling basis, which is standard in frontline hiring, that candidate isn’t lost once. They’re removed from every future opening too, at the exact moment the employer needs the applicant pool to stay warm.
Either way, the employer paid a cost that a single email would have prevented.
Signs You’re Already Ghosting Candidates
Most hiring teams doing this don’t think of themselves as ghosters. A few patterns say otherwise.
Candidates are the ones following up. If someone has to call or text a second time just to find out where they stand, the loop already broke on your end.
“No” only goes out when someone asks for it. If a rejection is a response to a complaint rather than a routine step, silence is the default outcome, not an exception.
No one owns the candidate after the interview ends. A manager who moves straight to the next interview without closing out the last one isn’t skipping a courtesy. That’s the exact point where candidates fall through.
Status lives in one person’s head, not a system. If a manager calling in sick means every candidate they spoke with that week hears nothing, the process was never built to survive a normal day off.
You can’t say, right now, how many open interviews are waiting on a decision. If that number isn’t trackable in under a minute, it isn’t being managed. It’s accumulating.
How to Stop Ghosting Candidates
Fixing this doesn’t take a bigger team. It takes treating a decision as the end of the process instead of treating silence as an acceptable one.
Set a response deadline for every candidate who interviews and hold it even when the answer is no. A short “we’ve moved forward with someone else” costs a manager thirty seconds and keeps that candidate open to your next posting instead of closing the door on your company entirely.
Give someone, not something, ownership of every open interview until it resolves either way, whether that’s a recruiter, a shift lead, or whoever ran the interview in the first place.
Build a way to see, at a glance, which candidates are waiting and for how long, whether that’s an ATS stage, a shared tracker, or a weekly five minute review before the next batch of interviews starts.
The fix isn’t more process. It’s making sure a decision made in someone’s head reaches the person it’s about.