You found the listing four days ago. Right title, right company, salary band that works. You tailored the resume, wrote a real cover letter, hit submit — and then nothing. Not a rejection, not an auto-reply, not even the courtesy of the posting disappearing. It just sits there, still live, still collecting applications, like it has for weeks. There's a decent chance you didn't apply to a real opening. You applied to a ghost job — a listing with no active hiring intent behind it. Not a scam, usually, just a role nobody is actually working to fill right now. The problem isn't that these listings exist. It's that spending real effort on one before you notice costs you time you could've spent on a role that's actually moving.
Why postings go stale in the first place
None of this is about you or your application, which is exactly why it's frustrating — there's no feedback to learn from. A few of the ordinary reasons a listing keeps running with nobody behind it:
- The team is building a pipeline for a role they expect to open later, not now.
- An internal candidate is already the de facto pick, and the posting is a formality required by policy.
- Budget or headcount got frozen after the req went live, and nobody pulled it down.
- The role was filled weeks ago and the posting simply never got closed out.
You can't see any of that from the job description. What you can see is the pattern around the posting — and that pattern is usually enough.
The signals worth checking before you apply
- Posting age. Most boards show "posted X weeks ago." A listing that's been sitting for well over a month without a refresh has usually lost momentum, even if it's technically still open.
- No named contact. A posting that names the hiring manager, links their profile, or at least describes the team you'd join is a stronger signal than one from a generic "Talent Acquisition" account with zero specifics.
- No salary range or closing date. Pay-transparency laws now require ranges in a growing number of states. A posting that dodges this, or has no application deadline at all, often has no real urgency behind it.
- Identical text everywhere, unchanged. A description that's been copy-pasted across five job boards, word for word, for months, usually isn't being actively managed by anyone.
Cross-check the company's own careers page
"If a role isn't on the company's own careers page, the version you found on a job board is either stale or was never really live in the first place."
This is the single best gut check, and it takes thirty seconds. Search the employer's actual site, not just the aggregator you found the listing on. If the role shows up there too, with a matching description and a working apply button, that's meaningfully stronger confirmation than anything else you can check without calling someone. If it's nowhere on the company's own page, treat the board listing with real suspicion.
Don't overcorrect into paranoia
Not every slow-moving listing is a ghost. Large companies with layered approval chains genuinely take a long time to move a req through the system, and some employers post ahead of anticipated need for high-volume roles — retail, seasonal work, support teams that are always hiring somewhat. The point isn't to write off every posting that isn't brand new. It's to stop spending the same amount of energy on all of them. A tailored application to a three-day-old listing with a named hiring manager deserves more of your polish than a fifth attempt at a six-month-old req that's never budged. That's really the same lesson as in our post on response rate versus application count — where you send your effort matters more than how much of it you send.
What to actually do about it
If you have any connection at the company — a former colleague, a referral, a recruiter who reached out — a short, direct message beats guessing indefinitely:
No connection at all? Note the posting date when you save it, and give it a couple of weeks before assuming it's dead. A posting that refreshes, updates its description, or starts naming a hiring manager is coming back to life. One that sits frozen is telling you where not to spend your best effort next.
Let your tracker do the noticing
The pattern that gives a ghost job away is almost never visible in a single moment — it shows up over time, which is exactly what's easy to lose track of once you're juggling more than a handful of applications. If you're logging roles in Findr's job tracker, the posting date you note the day you save a listing becomes useful three weeks later, when you notice a card that's been sitting in "Applied" with zero movement while three others from the same week already converted to interviews. That comparison is much easier to see on a board than to remember, especially once you've applied to more than a handful of roles.
Is it illegal to post a fake job listing?
In most of the U.S., posting a listing with no real intent to fill it isn't illegal on its own, though pay-transparency laws in a growing number of states create real disclosure requirements employers can run afoul of. It's better described as a bad practice than a crime.
How long should I wait before assuming a listing is dead?
There's no fixed number, but if a posting has sat unchanged for well over a month with no update, repost, or hiring-manager detail, treat it as low-priority rather than a lost cause. Deprioritize it, don't delete it.
Should I still apply to an old job listing?
Yes, if it otherwise fits — a stale posting doesn't guarantee a dead role. Just calibrate your effort: spend less polish on a six-month-old generic req than on a specific, freshly posted one with a named hiring manager.
A ghost job isn't a rejection and it isn't your fault — it's just noise you can learn to filter before it costs you a week. Spot the pattern, spend your polish where it's earned, and let the roles that are actually moving get the effort they deserve.