Ghosting
Why Good Candidates Get Ghosted After Applying
Silence after an interview almost never means you did something wrong. It usually means a frozen budget, an internal hire, or a recruiter managing forty open roles at once - none of which have anything to do with you.
Getting ghosted after a promising interview is one of the most demoralizing parts of a job search, mostly because it feels personal even when it almost never is. The silence doesn't come with an explanation, so it's easy to fill that gap with your own worst guess about what went wrong. Here's what's actually happening on the other side, most of the time.
Four reasons companies go silent
The role got frozen, not filled
Hiring freezes and budget cuts don't come with an email blast to every open applicant - the req just quietly stops moving. From your side, that looks identical to being rejected. Internally, it's often nobody's job to close out a role that technically doesn't exist anymore, so it just sits open on the job board for months.
An internal or referred candidate took it
Plenty of postings are legally required to be public even when the company already has someone in mind - a referral, an internal transfer, a candidate from a previous search. You were never really being evaluated against the field; you were competing against a decision that was functionally already made.
The recruiter is managing 40 open reqs, not one
A single recruiter juggling dozens of roles at once will always prioritize the candidates already mid-process over sending rejection notices to everyone who didn't move forward. It's not personal - it's a real capacity problem, and closing the loop on "no" is usually the first thing that gets deprioritized when time runs short.
Legal and liability concerns, not feedback
Many companies have a blanket policy against giving specific rejection reasons at all, out of concern it could be used as evidence in a discrimination claim - even when the actual reason is completely mundane. The safest legal answer, for a lot of companies, is no answer.
What actually helps, and what doesn't
Following up once, politely, two or three weeks past whatever timeline you were given is reasonable and sometimes works - recruiters do sometimes just lose track of a thread in the noise. Following up repeatedly rarely changes the outcome and mostly just costs you time you could spend on a role that's actually still moving. The more useful move is closing the loop yourself: flag the role as ghosted, stop checking it, and put that attention toward the next one.
That's exactly what Scoura's Ghost & Scam Detection is built for - flag a role that's gone quiet with one click, and it's out of your active list for good without you having to keep it open just to remember to give up on it eventually.
What this looks like in practice
Flagging a ghosted role in your Tracker takes one click - here's the actual interaction.
FAQ
Ghosting, answered.
Does getting ghosted mean I did something wrong in the interview?
Usually not - most ghosting happens for reasons that have nothing to do with your performance: a frozen budget, an internal hire, or a recruiter who's simply underwater. It's worth reviewing your interview if you have real doubts, but silence on its own isn't evidence of anything.
How long should I wait before assuming I've been ghosted?
Two to three weeks past whatever timeline you were given is a reasonable point to follow up once, briefly. Past that with no response at all, it's fair to treat the role as dead and move on - chasing further rarely changes the outcome.
Is there a way to know in advance which companies are more likely to ghost?
Not with certainty, but a pattern of it does show up over time - it's exactly what Scourcard is built to surface: real signal from people who actually went through a company's process before you apply.
Keep Reading