Why Employers Ghost Candidates After Interviews
Workplace
Silence is a decision. It just never feels like one to the person making it.
Greenhouse has been asking job seekers about this for a few years now. In its 2024 report, 61% said they had been ghosted after an interview, which was nine percentage points higher than six months earlier. By the 2025 edition the figure was 63%. Among Gen Z candidates in the US it was 78%.
Note the qualifier. This is not people who applied and heard nothing, which is common enough that most candidates expect it. This is people who took time off, prepared, showed up, answered questions, and were then told nothing at all.
| Share of candidates | |
|---|---|
| Ghosted after an interview (2024) | 61% |
| Ghosted after an interview (2025) | 63% |
| Gen Z candidates in the US ghosted after an interview | 78% |
| Candidates from underrepresented groups ghosted | 66% |
| White candidates ghosted | 59% |
Nobody sets out to do it
Almost no employer decides to ghost someone. What happens is smaller and duller than that, and it usually looks like one of five things.
The role goes on hold. Not cancelled, just paused while a budget conversation happens upstairs. There is no honest message to send, because the honest message is "we do not know", and nobody wants to put that in writing. So the message waits for clarity that takes eleven weeks to arrive.
Nobody owns the no. The recruiter thinks the hiring manager is closing the loop. The hiring manager thinks the recruiter did it when the offer went to someone else. Both are busy and neither is wrong about the other's job.
Legal caution hardens into silence. Somewhere along the line a team was told to be careful about giving reasons for a rejection. That advice was about reasons, not about answers, but the practical version that survives in most companies is to say nothing at all.
The tooling makes it a chore. In plenty of systems, rejecting a candidate is a manual action on a record, one at a time, with a template that reads like a parking fine. Sending forty of those is a job. It gets deferred, then it gets stale, and after a month sending it feels worse than not sending it.
And then there is the volume. LinkedIn now sees roughly eleven thousand applications submitted every minute, up around 45% in a year, much of it written with AI. Popular roles collect several hundred applicants in a long weekend. Teams that were coping in 2023 are not coping now, and the first thing to fall off a stretched process is the part with no deadline attached.
Nearly two in every three US candidates say they were ghosted after a job interview.
What it costs, in things you can count
The reputational argument gets made a lot and lands softly, so here is the operational one instead.
You lose the runner-up. In most hiring rounds the second-place candidate is genuinely good and would have taken the job. Six months later, when the role reopens or the hire does not work out, that person is the cheapest hire available to you. If the last thing you did was disappear, they will not answer.
You lose the referral. Interviewed candidates talk to people who do the same work. That is precisely the network you were trying to reach with the job ad.
You lose your own credibility with the ones you keep. Candidates who have been ghosted arrive at the next employer expecting the same, which is a large part of why candidates now ghost employers back, skip confirmed interviews, and accept two offers to see which one turns out to be real. Both sides are defending themselves against a process neither trusts.
You do not owe feedback. You owe an answer
This is the distinction that unlocks most of it. Detailed feedback is optional, sometimes legally awkward, and often not worth the argument it starts. An answer is neither.
- Say the shape of the process before the interview. How many stages, roughly how long, and when they will hear. A date is worth more than a promise to be in touch.
- Send the no, even late. A short message four weeks after the fact is still better received than nothing. Say the role is filled or paused. That is enough.
- Tell people when the role is paused. Candidates find "the budget was pulled" completely reasonable. They find eleven weeks of nothing unreasonable, and cannot tell the two situations apart from the outside.
- Give one team the close-out, in writing. Whoever books the interviews should own the outcome message, and the offer stage should not be considered finished until the other candidates have been told.
- Batch the rejections into the workflow. If closing out a round is a fifteen minute job at a fixed point in the process, it happens. If it is forty individual actions with no deadline, it does not.
- Tell them what happens to their data. How long you keep it, and how to get it removed. It costs a sentence and it is one of the few things candidates actively ask about.
The part we would change further upstream
Post-interview silence is a symptom of a process that produces far more applicants than anyone can talk to properly. A team facing four hundred applications for one warehouse role will not close out every one of them well, no matter how good its intentions are on Monday morning.
The way out is to stop generating the pile. When a requirement is matched against people who already fit it, the number of conversations is small enough to finish properly, and the reasons a person was surfaced are attached to the introduction rather than locked in someone's inbox. That is a different shape of process rather than a better-mannered version of the same one. It is also the only version where telling everyone the outcome is realistic rather than aspirational.
Until then, the standard is low enough to clear easily. Answer the people who showed up.