A listing appears on a Tuesday. Senior analyst, hybrid, competitive salary, apply now. It’s still there in October, then December, quietly recycled with a new post date and a slightly different title. No one gets an interview. No one gets a rejection. The posting simply persists, doing whatever job it was actually hired to do — which, increasingly, has nothing to do with hiring.
Recruiters have a name for this now: the ghost job. Not a scam exactly, not always malicious, but a listing kept alive for reasons that have little to do with an open seat. Surveys from staffing platforms and career sites over the past two years have put the share of postings that aren’t tied to an active, fillable role somewhere in the range of a third to nearly half, depending on how the question is asked and who’s answering. The exact figure moves around. The pattern underneath it doesn’t.
Why a Company Would Post a Job It Doesn’t Plan to Fill
The reasons tend to cluster into a handful of familiar motives, and most of them make a certain internal sense to whoever approved the posting, even if they land badly on the applicant side.
Some postings exist to build a pipeline for a role that might open up later — a kind of talent warehousing, where a resume database gets stocked in advance of need rather than in response to it. Some exist because a manager lost a headcount fight but wants the listing up anyway, in case the budget line reappears next quarter. Some are there to signal growth to investors, customers, or competitors: a company with forty open roles reads as a company that’s expanding, regardless of whether those forty roles are moving toward anyone’s desk.
Others serve an internal audience entirely. A posting can function as pressure on an overworked team — proof that management is “trying” to hire, even if the requisition is stuck in approval limbo indefinitely. And a fair number are simply administrative debris: a role got filled or cancelled, and nobody remembered, or bothered, to take the listing down. Job boards don’t always prune themselves, and companies don’t always check.
What almost none of these motives involve is deception aimed squarely at the applicant. That’s part of what makes ghost jobs hard to regulate or even name cleanly — the harm is diffuse, the intent is usually not fraud, and the person filling out the application has no way to distinguish a live req from a warehoused one.
The Cost Lands on One Side of the Table
The asymmetry is the real story. A company that posts a role it isn’t actively filling loses almost nothing — maybe some inbox clutter, maybe a mildly annoyed recruiter who has to file rejections. An applicant who spends an evening tailoring a resume, writing a cover letter, and preparing for a phone screen that will never come loses time that doesn’t get refunded. Multiply that across a job search that already involves dozens of applications, and the ghost-job problem starts to look less like a quirky HR habit and more like a quiet transfer of labor from employer to jobseeker, with no corresponding obligation flowing back.
There’s a rough parallel to how risk gets distributed in other corners of the economy. On public construction jobs, a surety bond system exists precisely because promises made on paper aren’t self-enforcing — someone has to be financially on the hook if the contractor doesn’t show up and do the work they said they would. Hiring has no equivalent backstop. A posting is a kind of promise — there is a role, it is open, applying is worth the effort — and there’s no bond behind it, no penalty if the promise turns out to be decorative.
What a Jobseeker Can Actually Do With This
There’s no reliable way to spot a ghost listing with certainty from the outside, but a few signals correlate with low odds of a real process on the other end. A posting that’s been live for more than sixty or ninety days, especially with a repost date that keeps resetting, is worth some skepticism. Listings with unusually vague requirements — broad enough to fit almost any candidate — sometimes indicate a pipeline-building posting rather than a specific need. So does a title that’s oddly generic for a company’s actual org chart, or a role that’s been posted, taken down, and reposted within a short window.
Applicant volume is another rough tell, though not a perfect one. A listing with several hundred applicants and radio silence for weeks doesn’t prove it’s fake, but it does lower the expected value of applying compared with a fresher, more targeted posting.
None of this is a reason to stop applying broadly — plenty of legitimate roles sit on job boards for exactly the reasons legitimate hiring is slow: budget approvals, internal reorganizations, a hiring manager on leave. The more useful shift is in where energy gets concentrated. Referrals and direct outreach to a hiring manager or team lead tend to route around the ghost-job problem entirely, because they attach a real person to the inquiry rather than a listing that may or may not be attached to anything.
Some career sites and browser extensions have started trying to flag likely-stale postings using repost frequency and listing age, with mixed but improving reliability. Job boards themselves have faced enough pressure on this that a few now surface “actively reviewing applications” labels, though the label is self-reported by the employer and carries no independent verification.
The deeper fix would require employers to treat a posting as a commitment rather than a placeholder — closing listings promptly, disclosing pipeline-building postings as such, giving some kind of status update to applicants instead of silence. Nothing currently requires that, and nothing obviously will soon. Until it does, the posting on the screen is best read the way a promise from a stranger usually should be: plausible, worth a reasonable effort, but not something to build a week’s hopes around.
