Why employers ghost applicants and when a nudge helps

By the Reach team · Updated September 03, 2026

Employers ghost applicants because their hiring pipeline is built to move forward, not to close out. Most ghosting is a side effect of how requisitions get cancelled, filled internally, or simply deprioritized, not a verdict on your candidacy. One polite nudge is worth sending when you have a concrete reason to think the process is still alive; after that, move on.

What actually happens inside an ATS

An applicant tracking system is, at its core, a database with workflow states. Your application enters at "submitted" and is supposed to move through stages like "screening," "phone interview," "onsite," and eventually "hired" or "rejected." The problem is that moving a candidate to "rejected" requires someone to do it manually, and that someone is usually a recruiter with forty other requisitions open.

In our experience, the default behavior of most ATS platforms is to leave candidates sitting in whatever stage they last reached. There is no automatic cascade that sends a rejection email when a req closes. Some platforms can be configured to do this, but many companies never turn it on, or they turn it on for certain job families and not others. So when a req gets cancelled or filled, everyone still in the pipeline just stays there, in limbo, indefinitely.

This is not usually malicious. It is a configuration gap combined with workload pressure. A recruiter who has to choose between reviewing fifty new applications for a role that is actively open and sending rejection emails for a role that was cancelled three weeks ago will almost always choose the former. The cancelled role's candidates are no longer a priority for anyone.

The three most common causes of ghosting

Requisition cancellation

Reqs get cancelled for reasons that have nothing to do with you. A hiring manager leaves the company and the backfill is frozen. Finance pulls the headcount at quarter-end. The team gets reorganized and the role no longer exists in its original form. In these cases, the recruiter often gets a system notification that the req is closed, but there is no corresponding action item to notify candidates. The req just goes inactive, and everyone in the pipeline becomes a ghost story.

Internal hires

Many companies have a stated policy of considering internal candidates first, or at least in parallel. When an internal person gets the job, the external pipeline is often just abandoned. There is sometimes a political reason for this: sending rejection emails to external candidates who were further along in the process than the internal hire can raise questions about why the external search was run at all. Silence is easier than explaining that the external process was a formality.

This is frustrating but common. If you suspect an internal hire happened, you are probably right, and there was likely nothing you could have done differently.

Deprioritization

Sometimes the role is still technically open, but it has dropped down the priority list. A different role became more urgent. The hiring manager got pulled into a fire. The team decided to delay the hire until the next budget cycle. In these cases, the ATS still shows the req as open, and your application is still technically under consideration, but nobody is looking at it. The recruiter may not even remember that you exist.

This is the scenario where a nudge can actually help, because the process is not dead, it is just stalled.

What ghosting does and does not say about your application

Ghosting after an initial application submission tells you almost nothing. Your resume may have been filtered out by the ATS, it may have been briefly reviewed and deprioritized, or it may never have been looked at at all. You cannot distinguish between these outcomes from the outside, and trying to is a waste of energy.

Ghosting after a phone screen or first interview is more informative, but still not a verdict on your qualifications. It usually means one of three things: the recruiter moved another candidate forward and stopped communicating with the rest, the req was cancelled or frozen between your interview and the next step, or the recruiter is simply disorganized and has not updated anyone in the pipeline. None of these are a reflection of your interview performance.

The pattern that does carry some signal is ghosting after a final round. If you did a full onsite loop and then heard nothing for two weeks, that usually means you were not the top choice and the company is waiting to see if their preferred candidate accepts before sending rejections to the rest. This is a common practice, and it is arguably worse than outright ghosting because it is deliberate. But it still does not mean you did badly. It means someone else was ranked slightly higher and the company is hedging.

When a nudge is worth sending

A nudge is worth sending when you have a concrete reason to believe the process is still alive. Here is a rough guide:

The nudge should be short, neutral in tone, and not ask for feedback. You are asking for a status update, not a performance review. Something like: "Hi [name], I wanted to follow up on my interview on [date] for the [role] position. I know things get busy, so I just wanted to check whether there is any update on next steps. Thanks for your time." That is it. No guilt, no pressure, no mention of other offers you may have.

What a nudge will not do

A nudge will not revive a cancelled req. It will not get you reconsidered if an internal hire has been made. It will not make a disorganized recruiter suddenly become responsive. What it can do is surface your application to the top of someone's inbox at a moment when they have a few minutes to respond, and sometimes that is enough to get the process moving again.

In our experience, the response rate to a well-timed nudge is modest but real. You should send it expecting no response, and be pleasantly surprised if you get one. If you send it expecting a response, you will be disappointed most of the time, and that disappointment will color your job search in a way that is not useful.

How to reduce ghosting before it happens

You cannot eliminate ghosting. It is a structural feature of modern hiring, not a bug. But you can reduce how often it happens to you by doing a few things during the interview process.

First, ask about timeline at the end of every conversation. "What are the next steps, and when should I expect to hear back?" This gives you a concrete date to follow up after, and it signals that you are tracking the process. Recruiters are slightly less likely to ghost candidates who have explicitly asked about timeline because they know the candidate is expecting an update.

Second, get a direct email address from whoever you spoke with, not just the generic recruiting inbox. A direct email is more likely to be read and more likely to get a response. If you only have a generic address, your nudge is going into a shared inbox that may or may not be monitored.

Third, pay attention to signals during the process. If the recruiter is slow to respond, reschedules multiple times, or seems vague about the role and its requirements, these are indicators that the process is not well-run. You can expect ghosting from a poorly run process, and you should keep your expectations low and your other options open.

When to stop following up

The rule of thumb is one nudge, one week after the expected update date, and then you are done. If you have a recruiter's email and they do not respond to a polite follow-up within a few days, that is your answer. Following up again will not change the outcome, and it may make you look desperate, which can actually hurt your chances if the role does reopen later.

There is one exception: if you have an offer from another company and a deadline, you can send a more direct message saying you have another offer but would prefer this role, and asking if there is any update. This is a legitimate reason to push for a response, and any reasonable recruiter will understand it. But you should only do this if the other offer is real and you would actually take it. Do not fabricate competing offers as a tactic. Recruitors talk to each other, and this happens more than you might think.

The honest takeaway

Ghosting is not about you. It is about a hiring system that is designed to find and advance the right candidate, not to close out the wrong ones. The energy that would go into closing out a pipeline is almost always better spent on the next open req, and so the pipeline stays open, and you stay in limbo.

Accept that this is how the system works, send one nudge when it is warranted, and put your energy into finding roles where the process is run with more respect for candidates' time. Those companies exist, and they tend to be the ones where the recruiter responds within a day or two at every stage. That responsiveness is itself a signal worth paying attention to, maybe more than any other signal you get during a job search.