A ghost job is a job posting that stays live even though the employer is not actively trying to fill it. Some ghost jobs are never real openings at all, and others are roles that were quietly filled, paused, or cancelled while the listing kept collecting applications.
Ghost jobs matter because they waste candidate effort, erode trust in your employer brand, and quietly corrupt the recruiting metrics you use to make budget decisions. For talent teams that measure performance seriously, understanding and eliminating ghost jobs is a fast way to clean up both candidate experience and reporting.
What Counts as a Ghost Job?
A posting is usually considered a ghost job when it falls into one of these buckets:
A role that was already filled internally, but the public listing was never taken down. A req kept open to build a pipeline for a future need that has no approved budget. A listing used to gauge the talent market or to signal growth to investors and competitors. An evergreen post that an agency or job board keeps live to collect resumes. A role frozen by a hiring pause where the posting simply lingers.
The common thread is a gap between what the listing implies (we are hiring now) and reality (we are not, or not yet).
How Common Are Ghost Jobs?
Ghost jobs are far more widespread than most candidates assume. In its 2024 analysis of hiring activity, Greenhouse reported that a meaningful share of postings on its platform showed ghost-job characteristics and that a large majority of companies had posted at least one role they were not actively filling during the period studied. Separate survey work by Resume Builder found that a significant portion of hiring managers admitted their company had listed a job it was not truly trying to fill in the prior year.
The takeaway is not a single precise percentage, which varies by source and method, but the direction: a nontrivial slice of the postings candidates see are not live, fillable roles.
Why Do Employers Post Ghost Jobs?
Most ghost jobs are not malicious. They usually come from process gaps and incentives rather than deliberate deception.
Pipelining is the most common reason. Recruiters keep a role open to collect applicants for a position they expect to open later. Slow offboarding of listings is another: once a role is filled, taking the posting down is nobody’s clear job, so it stays up. Some organizations post roles to project growth, and others keep evergreen listings for high-turnover positions where they are always technically hiring but not against a specific req today.
Whatever the motive, the effect on your data is the same.
How Do Ghost Jobs Distort Your Recruiting Metrics?
Ghost jobs pollute the numbers that recruitment teams rely on. When a listing collects applications for a role no one is filling, your apply totals rise while hires do not, which inflates cost per hire and drags down apply-to-hire conversion. Time-to-fill becomes meaningless for a req that will never close. Source-of-hire and channel performance get muddier because spend and clicks flow to postings that cannot produce a hire.
If you advertise those postings through paid channels, the damage compounds: budget is spent driving applicants into a dead end. This is exactly why serious teams tie every dollar to completed applications and hires rather than to clicks. A clean, outcome-based measurement model, like the one described in our guide to recruitment advertising metrics that matter, makes ghost-job distortion obvious instead of invisible.
Ghost Jobs vs Real Openings: A Quick Comparison
| Signal | Real, active opening | Likely ghost job |
|---|---|---|
| Recency | Recently posted or refreshed with a clear date | Stale, reposted repeatedly for months |
| Hiring intent | Tied to an approved, budgeted req | No named hiring manager or start date |
| Responsiveness | Applicants get timely status updates | Silence after applying, no movement |
| Detail | Specific team, scope, and pay range | Vague, generic, or evergreen language |
| Reporting | Feeds real apply-to-hire data | Collects applications with no hires |
How to Reduce Ghost Jobs in Your Own Hiring
The fix is mostly operational. Set an owner and an expiry date for every posting so roles come down when they are filled or paused. Reconcile live listings against approved reqs on a regular cadence. Only put paid spend behind roles you are genuinely trying to fill, and route pipeline-building to a talent community or CRM rather than a public job ad. Finally, optimize campaigns toward hires, not clicks, so postings that never convert stop draining budget.
Programmatic job advertising helps here because spend automatically shifts toward roles and sources that produce applications and hires, and away from listings that do not. You can see how that outcome-based model works in our ultimate guide to programmatic job advertising and our overview of how programmatic job advertising works.
Frequently Asked Questions
Are ghost jobs illegal?
In most places ghost jobs are not illegal, though some jurisdictions have begun exploring pay-transparency and job-posting rules. The bigger risk for employers is reputational: candidates who feel misled lose trust in your brand.
How can candidates spot a ghost job?
Watch for postings that are months old and repeatedly refreshed, listings with vague scope and no pay range, and roles where applicants report total silence after applying. A recently dated, specific posting tied to a real team is a better sign.
Do ghost jobs hurt employers?
Yes. They damage candidate experience and employer brand, and they distort recruiting metrics like cost per hire, time-to-fill, and source-of-hire, which leads to worse budget decisions.
How do ghost jobs affect recruiting data?
They add applications without adding hires, which inflates cost per hire, lowers apply-to-hire conversion, and makes channel performance harder to read. Tying measurement to hires rather than clicks exposes the problem.
How can employers avoid posting ghost jobs?
Assign an owner and expiry date to every listing, reconcile postings against approved reqs regularly, keep paid spend only on active roles, and use a talent community or CRM for pipeline building instead of a live job ad.
