53% of job seekers reported being ghosted by an employer in the past year, a three-year high. The larger problem sits on the employer side of the funnel, where slow decisions, weak follow-up, and opaque screening leave candidates waiting without a clear outcome.
That framing matters because “ghosting” is often treated as a story about unreliable applicants. The available evidence points to a more complicated hiring-practice problem. Candidates disappear, but employers also decide when a process has effectively ended without telling the person still inside it. The silence can begin after an application, an interview, a skills test, or even an accepted offer.
Table of Contents
- The Three-Year High in Hiring Silence
- Hiring Practices and Candidate Experience, Defined
- How Quickly Companies Respond
- Where in the Funnel Communication Breaks
- Why Employer Silence Keeps Getting Worse
- Algorithmic Screening and Invisible Rejection
- Reading Outcome Data Before You Apply
- What to Check and Track on Your Next Search
The Three-Year High in Hiring Silence
The 53% figure comes from recent reporting on job seekers who said an employer ghosted them during the previous year, described as the highest level in three years. The same reporting recorded a rise from 38% in 2024 to 48% in 2025, before reaching the newer benchmark, which suggests that communication has deteriorated across the hiring funnel rather than at one isolated checkpoint. (Fortune's reporting on employer ghosting)
The usual headline calls this “candidate ghosting,” but that label depends on who gets to define silence. A candidate may be marked as unresponsive after missing a recruiter's message, while an employer can leave an application, interview, or assessment without a final answer and still treat the process as administratively closed. The conduct is different, but both outcomes are often compressed into the same word.
Employer-side evidence makes the issue harder to dismiss as a candidate complaint. 83% of employers across the US, UK, and Canada said candidates had ghosted them, while 69% said the problem had begun within the previous two years, according to the same reporting. Those figures show that both sides experience drop-off, but they don't establish that the causes are equally distributed at every stage.
Silence is a process outcome
An independent U.S. worker survey found that 45% of respondents said employers ghost candidates more often than candidates ghost employers, and 48% said they wouldn't apply to the same company again after being ghosted. (HR Reporter's coverage of candidate ghosting)
That second number changes the commercial meaning of silence. An unanswered application isn't merely an unpleasant interaction. It can remove a candidate from the company's future pipeline, even if the person was qualified for another role or might have recommended the employer to someone else.
The central question, then, isn't whether candidates sometimes vanish. They do. The more useful question is how company hiring practices create conditions where employers can stop communicating without a visible closure event, and how much of the apparent candidate unreliability is a reaction to a process that has already become slow or ambiguous.
Hiring Practices and Candidate Experience, Defined
Company hiring practices include the employer's decisions about how it advertises roles, collects applications, screens resumes, schedules interviews, evaluates work, makes offers, and closes rejected applications. A candidate doesn't see most of those internal decisions. They see the consequences through a smaller set of observable signals.
Candidate experience is the practical record of those signals. It includes whether the employer acknowledges an application, how long the first response takes, whether the next step is explained, and whether the company communicates a final decision. “Candidate-centric” can describe a useful operating principle, but it doesn't tell a job seeker what will happen after pressing Apply.
The terms candidates can measure
Four measures make the process easier to assess:
- Response rate means the share of applications that receive a meaningful employer response rather than remaining unresolved.
- Time to first response measures the interval between applying and the first employer contact.
- Funnel stage identifies where the candidate is, such as application review, interview, assessment, or offer.
- Closure means the company communicates that the process is continuing, paused, rejected, or complete.
Those terms matter because a company can appear responsive at one stage and silent at another. A quick scheduling email doesn't tell you whether the employer sends decisions after interviews. A polished careers page doesn't prove that applications are acknowledged.
GhostedBy uses a 21-day window as an operational point at which silence after the last relevant contact can count as ghosting. That doesn't mean every unanswered message becomes a universal fact about the company. It provides a consistent rule for turning an individual experience into a comparable outcome record.
Practical rule: Record the last meaningful contact, not the date you started feeling uncertain. The distinction helps separate a delayed process from a documented period of silence.
The vocabulary also prevents a common analytical mistake. “Talent pipeline” describes an employer's internal pool, while “candidate experience” describes what the applicant can verify. A company may say it is keeping someone warm, but unless the candidate receives an update, that intention remains invisible.
How Quickly Companies Respond
Candidates set a short clock for application communication. 75% expect to hear back within two weeks, 58% expect a response within one week, and the median expected response time is 6.7 days, according to PIN's candidate ghosting benchmarks. Employer-side outcomes point in the opposite direction: one source reports an average response time of 23 days, while 79% of candidates receive no follow-up after applying. (Worldmetrics' candidate experience data)
| Metric | Candidate expectation | Measured employer outcome |
|---|---|---|
| Initial response window | 75% expect a response within two weeks | 23-day average response time |
| One-week expectation | 58% expect a response within one week | 79% receive no follow-up after applying |
| Median benchmark | 6.7 days | 23-day average response time |
The comparison is imperfect because the sources measure different sides of the process, but the direction is clear. Candidates often judge silence against a one-week or two-week expectation, while employer contact can arrive much later or not at all. That gap makes an active requisition look closed from the applicant's perspective.
The mismatch does not prove that every recruiting team is careless. Application queues, applicant tracking systems, hiring-manager delays, and changing role priorities can stretch the interval before someone replies. These remain company hiring practices because the employer decides whether its process sends an acknowledgement, a status update, or a closure message while an internal decision is pending.
Expectations also vary by location. A separate benchmark reports that 77% of candidates in the US, 79% in Ireland, and 88% in the UK expect a response within two weeks. (CueCoPilot's candidate ghosting statistics) Candidates therefore do not need to identify the internal cause of a delay to assess its effect. They experience the waiting period directly, and the silence reflects process design as much as candidate behavior.
After an interview, the relevant clock starts with the last meaningful contact. Candidates can use this guide on how long to wait after being ghosted after an interview to distinguish a delayed decision from a longer period without communication.
Where in the Funnel Communication Breaks
A hiring process can appear orderly while losing contact at each handoff. The candidate applies, waits for screening, speaks with a recruiter, completes an assessment, meets a panel, provides references, and can still receive no clear outcome. That sequence makes employer process design visible. Silence is produced not only by candidate withdrawal, but also by queues, ownership gaps, and delayed decisions.
The stage data shows why “ghosted or not” is too blunt a label. In one U.S. survey, 19% were ghosted after an initial email, text, or phone call; 22% after one or more interviews; 12% after a skills test; and 13% after being told an offer was coming. (HR Reporter's stage-by-stage findings) The same survey places silence at several distinct points, rather than at one final outcome.
Seven observable checkpoints
- Application received: An automated confirmation indicates receipt, not that a person reviewed the submission.
- Resume screening: Silence may reflect a queue, an internal referral receiving priority, or a role that has effectively paused.
- Phone or video interview: The first human conversation raises the expectation of follow-up. The survey's 19% early-contact figure captures silence before a substantial interview process begins.
- Skills test or take-home: The candidate has invested additional time, while 12% reported being ghosted after a skills test.
- Panel or onsite: Multiple interviewers create feedback that someone must consolidate. Without a named owner, the process can stall between evaluation and communication.
- Reference check: Silence here is difficult to interpret because the candidate may assume the employer is completing a final validation step.
- Offer: 13% reported being ghosted after being told an offer was coming, so verbal momentum does not guarantee written closure.
Interviews show the largest reported concentration in this dataset, with another meaningful break after candidates were told an offer was likely. The pattern is consistent with feedback consolidation and decision delays, although the survey does not establish which internal mechanism caused each silence event.
Silence can continue after acceptance. A study published in the Global Journal of Management and Business Research, using an archival dataset of 157,154 accepted offers at a large telecommunications company, found that 4.1% of accepted offers resulted in ghosting before the start date, with staffing disruptions costing over $6.9 million annually. It also found higher risk when the offer-to-start delay was longer and for customer-facing roles. (Global Journal of Management and Business Research study)
The accompanying video illustrates how a hiring funnel narrows across these stages and where communication handoffs can fail, supporting the stage-by-stage reading above.
Why Employer Silence Keeps Getting Worse
A systematic review found that 93% of surveyed organizations documented ghosting incidents. The same review linked the problem most often to slow hiring processes at 50% and poor recruiter communication at 48.6%. (Systematic review of candidate ghosting literature)
These findings shift attention from candidate temperament to employer process design. Companies control the application queue, internal handoffs, and update schedule. Candidates can withdraw, but employers decide whether a process has a named owner and whether an update is sent when a decision stalls.
| Driver Category | Examples | Relative Weight in Review |
|---|---|---|
| Process speed | Long hiring cycles and stalled approvals | 50% for slow hiring processes (the same review) |
| Recruiter communication | Missing updates, unclear ownership, delayed replies | 48.6% for poor recruiter communication (the same review) |
| Decision-stage drop-off | Silence after interviews or likely offers | Reported most often after interview rounds and post-offer acceptance (the same review) |
Workload explains part of the pattern
Lean recruiting teams may struggle to update every applicant while hiring managers delay debriefs or reconsider a role. Internal referrals may receive attention first, leaving outside applicants in a queue with no visible status. These conditions help explain how silence can spread across multiple roles without requiring each recruiter to deliberately ignore candidates. They do not remove the employer's ability to assign ownership, set response deadlines, or close inactive applications.
The employer-side narrative points in another direction. Industry aggregation reported that 89% of employers called candidate drop-out or day-one no-shows a problem, but that figure is not presented here as a primary survey finding. (Glozo's candidate ghosting statistics) The concern is understandable when a company has reserved capacity for someone who does not arrive. It does not erase the imbalance in visibility: employers can confirm availability, communicate delays, and record decisions, while candidates usually cannot tell whether a role remains active or whether review has stopped.
Silence therefore creates a process cost that may remain invisible inside the hiring team. The immediate work of closing applications is deferred, while later effects can include lower reapplication, weaker referrals, and candidates abandoning future roles. For a closer examination of employer-side causes, see why recruiters ghost candidates.
Algorithmic Screening and Invisible Rejection
Automation changes the problem because a candidate may never know whether a person saw the application. A resume-ranking model can score applications, place them in an order, and filter people below an internal threshold before a recruiter opens the file. The applicant experiences silence, but no individual recruiter necessarily made a visible decision.
A 2026 independent study reported by Fortune found clear racial disparities in AI hiring algorithms. More than one in four applications from Black job seekers were routed to positions where the algorithm produced outcomes that trigger federal discrimination scrutiny, according to the reporting. (Fortune's coverage of the AI hiring algorithm study)
That finding doesn't prove that every automated screening system produces the same outcome. It does show why generic claims about efficiency are insufficient. A company hiring practice that uses automation needs to answer a harder question, namely whether candidates from different groups receive comparable visibility, review, and communication.
Silence without a human checkpoint
Algorithmic rejection can create an invisible loop. The company receives an application, the software routes it away, and the candidate receives no explanation beyond the absence of contact. Calling that “ghosting” captures the candidate's experience, but it hides the governance problem. There may be no accountable person assigned to explain the outcome or test whether the filter is excluding qualified applicants.
Candidates can't audit a model from a confirmation email. They can, however, ask what screening tools are used, whether a human reviews applications, and when the employer closes the process. Employers that can't answer those questions make it harder to distinguish a normal rejection from an automated exclusion.
The employer-brand consequence also differs from a simple delayed reply. A candidate who knows a human reviewed the application can understand a rejection, even without detailed feedback. A candidate who suspects the application disappeared into an opaque system may conclude that the company's hiring practices are arbitrary, especially if repeated applications produce no visible response.
Reading Outcome Data Before You Apply
Aggregated outcome data can turn isolated complaints into a testable pattern, but it still requires careful reading. The trajectory introduced earlier shows that employer silence has become more common. A separate finding is more useful here: 48% of workers wouldn't apply to the same company again after being ghosted. That result, reported in Glozo's reporting on candidate ghosting outcomes, connects a communication failure with a later decision to withdraw from the employer's talent pool.
The two outcomes describe different stages of the relationship. A no-response measure records what happened during an application. A no-reapply measure records what happened afterward, when the candidate decides whether the employer deserves another application. Together, they show why silence is a process-design issue, not only a candidate complaint. Slow review, unclear ownership, and automated filtering can reduce future interest even when the employer's immediate hiring need remains unchanged.
Read the record, then read its limits
| Metric | What It Measures | Why It Matters to Candidates |
|---|---|---|
| No-response rate | The share of reported applications without an employer reply | Indicates whether silence appears repeatedly in the application experience |
| No-reapply rate | The share of workers unwilling to apply again after ghosting | Shows whether poor communication deters future interest |
| Response latency | How long candidates wait before receiving contact | Helps compare the employer's pace with the candidate's own search timeline |
| Outcome count | The number of eligible reports behind a company record | Indicates how much weight to place on a percentage |
A single report may describe one failed interaction. Repeated outcomes across roles and candidates provide stronger evidence of a company-level pattern, especially when the record separates applications, interviews, offers, and other stages. GhostedBy's public company records use verified email contributors, keep individual applications private, and wait for at least five eligible outcomes before displaying a percentage, while counts remain available for context. Candidates can inspect an example through the Sourcegraph company page.
That threshold does not make the record a scientific sample. Self-selected reporting may overrepresent unusually good or bad experiences. Public data may not account for job level, geography, role type, hiring volume, or a paused position. The available sources also lack a universal method for normalizing results across industries.
Use outcome data as a screening signal, not a verdict. A recurring pattern can justify sharper questions or a decision to apply elsewhere, but it cannot reveal every internal reason for an individual delay.
The strongest interpretation combines outcome counts with process details candidates can verify. Check whether recent reports cluster after applications, interviews, or offers. Compare the observed response pattern with the employer's stated timeline. Then weigh it alongside direct communication, public employee discussions, and the clarity of the job posting.
What to Check and Track on Your Next Search
Candidates don't need a complex research project to evaluate company hiring practices. A small record of dates, contacts, and outcomes is enough to distinguish a normal delay from a repeated communication failure.
Before applying
Start with the job post. Vague responsibilities, contradictory requirements, or a title that doesn't match the requested skills can indicate that the employer hasn't settled the role. A salary range that falls below what comparable roles offer may also change the likelihood that the process reaches a serious offer stage, though the posting alone can't prove how the company communicates.
Check the employer's aggregated outcome record where one exists. Read Glassdoor and LinkedIn comments for context, but separate descriptions of workplace culture from direct evidence about applications, interviews, and follow-up. Ask whether the posts describe a specific stage and timeline, or whether they're broad impressions.
- Record the source: Save the job-post URL and the date you applied.
- Note the contact route: Keep the recruiter name, email address, referral, or application channel.
- Save the stated timeline: Copy any language about review dates, interviews, or decisions.
During the process
Send a short confirmation question when the application channel gives you no receipt. At each interview, ask who will follow up, when you should expect an update, and whether the role is still active. A clear answer gives you a benchmark. An evasive answer is still information.
Use a simple 14, 21, and 30-day rhythm. Follow up when the stated timeframe passes or around the two-week point when no timeline was given. At 21 days without a response after the last relevant contact, GhostedBy's operating rule treats the silence as a possible ghosting outcome. By 30 days, decide whether another message is worth your time or whether you should close your own record and move on.
- Log each interaction: Add the date, channel, person, and promised next step.
- Track stage changes: Mark whether you applied, screened, interviewed, tested, or reached an offer discussion.
- Keep moving: Don't pause the rest of your search while one employer remains vague.
After interviews
Send a concise thank-you note if you want to confirm interest, then ask for the decision timeline in writing. If the employer rejects you, request feedback politely, but don't treat a refusal to provide it as evidence about your performance. Record whether the company closed the process, left you waiting, or invited you to reapply.
The practical value of tracking isn't perfect prediction. It gives you enough evidence to decide where to spend another hour, whether to follow up once more, and when an employer's silence has become part of the outcome.
GhostedBy lets candidates check aggregated company response and ghosting outcomes, track applications privately, and report what happened after applying or interviewing. Visit GhostedBy before your next application, then use the record to compare an employer's communication pattern with the timeline you were given.
Authored using the Outrank app