Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / Why Ghosting Candidates Destroys Your Employer Brand
Transcript
- Lucas: So there's this data point that has been rattling around in my head ever since I saw it last month. The talent platform Greenhouse ran a survey of about fifteen hundred job seekers in late 2025, and they found that seventy-six percent of candidates who were ghosted by a company after an interview said it made them less likely to ever buy from that company. Luna: Seventy-six percent — that is not a niche annoyance. That is a direct hit to the revenue side of the house. Lucas: Exactly. And it gets worse. Fifty-nine percent of those ghosted candidates said they shared their negative experience on social media or on sites like Glassdoor. So we are not just losing a potential customer — we are broadcasting a story about how we treat people. Luna: Before we go deeper — and I want to go deep on this — I just want to say, this kind of conversation is exactly why we keep this show ad-free. We are not here to sell you an ATS upgrade or a recruiter training course. If these episodes have helped you think differently about hiring, and you want to support that independence, you can find us at buy me a coffee dot com slash fexingo. No pressure, just an option. Lucas: Yeah, and it genuinely makes a difference. Keeps the whole thing sustainable without any sponsor strings attached. Okay, back to ghosting — because I think a lot of hiring managers hear that seventy-six percent number and assume it applies to other companies, not theirs. Luna: Right. There is this cognitive bias where we think our rejection email is somehow different. But the data says the candidate does not distinguish between a impersonal automated rejection and dead silence — both feel like ghosting if the communication is delayed or vague. Lucas: Let me give a concrete example. There was a mid-sized B2B software company — I will call them CloudLogix, not their real name — that was hiring about forty engineers a year. They had a typical process: phone screen, take-home assignment, then a four-hour final round with three separate interviews. And after that final round, they often took two to three weeks to get back to candidates. Sometimes longer. The VP of Talent told me they thought that was just part of the normal cycle. Luna: But the candidate experience of those three weeks is silence. They send a thank-you note, hear nothing. They follow up after a week, crickets. They start telling their friends, 'That company is a black hole.' Lucas: Exactly. So they decided to run a six-month experiment. They implemented what they called the 'forty-eight-hour rule' — every candidate who made it to the final round received a decision within two business days. Even if the decision was 'we need more time,' they sent a note saying exactly that, with a specific date for the next update. It was not a complex technical fix — it was a process discipline. Luna: What happened? Lucas: Their time to hire for engineering roles dropped from an average of forty-five days to thirty-one days. But more interestingly, their offer acceptance rate went up by twelve percent. The VP's theory — which I buy — is that candidates who felt respected during the process were more likely to say yes when the offer came. They had not soured on the company during the waiting period. Luna: That is a really clean signal. And it connects to something I have seen in research from the Society for Human Resource Management: candidates who experience a positive hiring process — even if they are rejected — are eighty percent more likely to reapply for a different role later. Ghosting burns that bridge for good. Lucas: Yeah. And that reapplication pipeline is actually a huge source of high-quality hires. People who have already been through your process, who already know your culture, and who maybe were a close miss the first time. If you ghost them, you lose that entire pool. Luna: So what are the common excuses companies give for ghosting? I imagine bandwidth is high on the list. Lucas: Number one excuse, by a mile: 'We are too busy to send individual rejections.' And I get it — when you have two hundred applicants for a single role, sending a personalized note to each one is not feasible. But there is a middle ground. You can set up automated status updates in your applicant tracking system that trigger at key milestones. Did the candidate complete the phone screen? Send a note saying they will hear back within five days. Did they move to the next round? Send a note with a timeline. The automation does not have to be impersonal — it can say 'We appreciate your patience, we are reviewing all finalists by May 15, and we will update you regardless of outcome.' Luna: That seems so basic, and yet so few companies do it well. I recently applied for a role at a well-known consumer brand — I will not name them — and I got a rejection email five months after I applied. Five months. I had already forgotten I even applied. And that email did not make me feel better, it made me feel like they had no system at all. Lucas: Right. And that is the second excuse: 'Our ATS makes it hard to send timely updates.' I have some sympathy there — some of the legacy systems are clunky. But in 2026, there are dozens of tools that integrate with your ATS and automate candidate communication with templates you can customize in ten minutes. The cost is negligible. The friction is not technical — it is cultural. Someone has to decide that candidate experience is a priority. Luna: And I think there is a third excuse that is less talked about: fear of legal liability. Some hiring managers worry that sending a detailed rejection — especially one that explains why the candidate was not selected — could be used against them in a discrimination claim. Lucas: That is a real concern, and it is why most employment lawyers advise against giving individualized feedback in a rejection letter. But there is a big difference between 'We decided to move forward with another candidate' — which is fine — and complete silence. You do not need to say 'Your presentation skills were weak' or 'You lacked experience in SQL.' You just need to say 'We have filled the position' or 'We are not moving forward at this time.' That is not a legal risk. Silence is not safer — it just feels safer. Luna: So what does best practice look like, practically? Give me the template. Lucas: Okay. For any candidate who has had a live conversation — phone screen or in-person — you should send a rejection within five business days of the decision. The email should have three parts: a thank-you for their time and interest, a clear statement that you are not moving forward, and an invitation to apply for future roles. That is it. Do not apologize profusely, do not over-explain. Just close the loop cleanly. Luna: And for candidates earlier in the funnel — the ones who just submitted a resume? Lucas: That is harder, because volume is high. But you can still set expectations. When they apply, your ATS can auto-reply with a message saying 'We receive a high volume of applications and will review yours within two weeks. If you do not hear from us by that date, we encourage you to apply for future roles.' That is not ghosting — that is setting a clear timeline. If they do not hear back after two weeks, they know the process, and they can move on. Luna: I like that because it puts the onus on the company to manage expectations upfront, rather than leaving the candidate in limbo. Lucas: And there is one more angle I want to bring in. A lot of recruiters I talk to say, 'But we do not ghost — we just take a while.' And I think that is a distinction without a difference from the candidate's perspective. If you take six weeks to get back to someone after a final interview, you might as well have ghosted them. The candidate has already told their network about the negative experience. Luna: So the real enemy is not malice — it is silence. And silence is a choice, just like speaking is. Lucas: Exactly. Let me give you one more data point from that same Greenhouse survey. They asked candidates how long they consider it acceptable to wait after a final interview before hearing a decision. The most common answer was three to five business days. After seven days, the vast majority said they start feeling frustrated. After fourteen days, they consider it ghosting. Luna: That is a really useful benchmark. So if you are a hiring manager listening, you now have a target: five days maximum after the final round. And if you cannot meet that, send a holding note. Lucas: Right. And I want to address one more pushback I hear: 'But what if we are still interviewing other candidates and cannot decide yet?' That is fine — send a note that says 'We are still in the process of interviewing and expect to make a decision by X date. We will update you then.' That is respectful. It is the silence that kills. Luna: So if I am a hiring manager and I want to fix this starting tomorrow, what is the one thing I should do? Lucas: Audit your current rejection email sequence. Or if you do not have one, create one. Go into your ATS, look at what candidates receive after each stage. If there is any point where a candidate could go more than a week without hearing anything, fix that gap. Start with the final interview stage — that is the highest-stakes point — and then work backwards. You do not have to overhaul everything at once. Just close the loop on the most painful silence first. Luna: That is actionable. And I think it is also worth saying: candidate ghosting is not just a hiring problem. It is a brand problem. Every ghosted candidate is a potential customer, a potential referral source, a potential future employee. Treating them with respect is not just polite — it is strategic. Lucas: Yeah. And the cost of a rejection email is essentially zero. The cost of a ghosted candidate, as that survey shows, can be lost revenue and a damaged reputation. It is one of the easiest high-leverage fixes in hiring. You just have to decide that it matters. Luna: Alright, so our takeaway for this episode: set a five-day response deadline for final-round candidates, use automated status updates for earlier stages, and never let silence be your default. Thanks for listening — we will be back next week with another angle on hiring that might change how you think about talent.