You spent forty minutes on that application. You reworked the bullet points, wrote a cover letter that didn't sound like a cover letter, answered the same questions the resume already answered, and hit submit into what felt like a promising opening.
There's a real chance no human was ever going to read it, because the company was never going to hire anyone.
These are ghost jobs, postings with no live role behind them, and they are not a conspiracy theory. The Congressional Research Service wrote a brief about them, which is roughly the moment a job market problem stops being an internet grievance and becomes a documented phenomenon. How common are they? Honestly, nobody knows with rigor, and the CRS brief says so directly. There are no official statistics, only commercial studies with varying methods. One analysis of LinkedIn listings put the ghost share at more than a quarter, other estimates run lower, and in Resume Genius's 2026 survey of a thousand job seekers, 67% said they'd encountered postings they suspected were fake, misleading, or never meant to be filled. Treat every number in this paragraph as an estimate of a thing companies have no reason to measure honestly. The phenomenon is real. Its exact size is not knowable.
The suspicion is not paranoia. Employers admit it themselves.
Companies Told On Themselves
When Clarify Capital surveyed over a thousand hiring managers, the reasons they gave for posting jobs they weren't filling were disarmingly casual. Half said the company is "always open to new people." A third said they keep postings up in case an irresistible candidate wanders by. In a follow-up survey, a quarter of companies said they had no plans to fill posted positions for at least three months.
Notice what none of those reasons involve. You. Your time, your forty minutes, your carefully calibrated hope when the confirmation email lands. A ghost posting costs the company nothing and costs you something real, which is why the practice persists.
There are other motives, and they're worth knowing because they change how you read a listing. A posting can exist to make a company look like it's growing to investors. It can exist to signal to overworked employees that help is theoretically coming. It can exist to collect salary expectations and resumes as market intelligence. In each case the posting is doing its actual job perfectly. Its actual job just isn't hiring you.
How to Smell One
No single tell is definitive, but the tells stack.
The posting is old, or keeps coming back. A role posted more than a month ago that never closes, or one you swear you've seen reposted three times this year, is behaving like furniture, not like a vacancy. Real openings have urgency behind them because someone's work isn't getting done.
No salary, in a state that requires one. Colorado, California, Washington, New York, and a growing list of others legally require salary ranges on postings. A company ignoring that law for a role in those states is telling you how much operational reality sits behind the listing.
The description is a mission statement. Real openings are specific because a real manager wrote down a real problem. Vague responsibilities, no team context, and no hint of who you'd report to suggest the posting was written by nobody, for nobody.
The company is filing layoff notices while "hiring." This one is context, not proof, and worth reading carefully. Big companies genuinely do cut one function while hiring another, so a WARN filing doesn't make their postings fake. What it does is tell you the posting deserves the skeptical read, especially when the "opening" sits in the same org that just got cut. Our company pages exist for exactly this kind of cross-reference.
The recruiter can't answer basic questions. When is the team looking to have someone start? Who does the role report to? How many people are in the process? A recruiter working a live role knows these cold. A recruiter tending a pipeline gets vague.
What This Means for Your Applications
The wrong lesson is to apply to everything with even less care, on the theory that it's all noise anyway. The volume game is exactly how you end up spending months feeding forms that go nowhere, and ghosting after applying is already the top frustration job seekers report.
The better lesson is to treat posting freshness as a ranking signal. A role posted this week, with a salary range, a named team, and specifics in the description deserves your forty minutes. A ninety-day-old posting with boilerplate responsibilities deserves a fast application or none at all.
And the old advice about going around the front door earns its keep twice against ghosts. A referral, a direct message to a hiring manager, or a warm contact from your network improves your odds on real jobs and filters out fake ones entirely, because a human either confirms the role exists or goes quiet, and either answer saves you the forty minutes.
One more thing, because the two problems hunt together. A posting that doesn't exist wastes your time. A recruiter who doesn't exist takes your money or your identity, and we've written about how those scams target the newly laid off specifically. The verification habits are the same. Confirm the role on the company's own careers page, confirm the human on LinkedIn, and treat urgency as a warning rather than an invitation.
It Was Never About Your Resume
If you take one thing from this, make it the reframe. When your response rate is dismal, the natural conclusion is that something is wrong with you, your resume, your age, your last title. That conclusion feeds the exact spiral that makes a hard search harder, and we've written about protecting your head during a long one.
But you cannot be rejected by a job that was never real. Nobody can tell you what share of your silence came from empty rooms, and anyone quoting you a precise number is selling something. What the evidence does support is that the share isn't zero and isn't trivial, which means some of the rejection you've been absorbing as a verdict on you was never about you at all.
Spend your hours where a human is actually waiting on the other side.
