Ghost Jobs
How to Spot a Ghost Job Before You Apply
Some job postings were never meant to be filled - they are pipeline-building, compliance theater, or growth signaling dressed up as an open role. Here is how to tell before you spend an hour tailoring a resume for one.
A ghost job is a job posting for a role the company has no real intention of filling - not now, and in some cases not ever. The posting is real in the sense that someone wrote it and put it online. The job behind it isn't.
The important thing to understand: most ghost jobs aren't scams. Nobody's trying to steal your identity. They're something more mundane - a posting serving some purpose other than hiring you.
Why companies post jobs they don't intend to fill
Pipeline building. "We're always hiring great engineers" is a talent-pool strategy. The company collects resumes continuously so that when a real opening appears, they already have candidates. Your application isn't wasted exactly - it's filed. It just isn't being read for the role you think you're applying to.
Signaling. A careers page with forty open roles tells a story - to investors, to competitors, to current employees - about a company that's growing. Some of those roles are aspirational headcount: approved in theory, frozen in practice, posted anyway.
Compliance theater. The role is already filled - often by an internal candidate - but policy or regulation requires it to be posted publicly for some window of time. The posting exists so the company can say the search was conducted. It was. The outcome was predetermined.
Parked headcount. The req was approved last quarter, the budget got murky this quarter, and nobody took the posting down because taking it down requires someone to own that decision. It sits there, getting re-listed on a schedule, collecting applications nobody reads.
None of these are aimed at you personally. That's what makes them so annoying - there's no villain, just a system where your effort evaporates.
The seven tells
It's been reposted for months
Same title, same description, fresh date - again. A real opening that's been live for four months with no hire is either impossibly picky or not actually hiring. Search the exact job title in quotes; if the same text has been circulating since spring, that's your answer.
It's vague about the actual team
Real postings say things like "you'll join the checkout team of six" or name the hiring manager. Ghost jobs describe the role in company-level abstractions - "join our world-class team," "work on exciting initiatives" - because there is no specific team waiting for this person.
Evergreen language
"We're always looking for talented individuals to join our growing team." That's not a job posting, that's a mailing list signup with extra steps. Legitimate evergreen postings exist (high-turnover roles like sales or support), but for a specialized role, evergreen means pipeline.
The application goes into a void
No confirmation email. No ATS status page. Or an ATS that accepts your application and then shows the same "under review" status until the heat death of the universe. One of these alone is just a bad process; combined with the other tells, it's a pattern.
The comp range is absurdly wide or missing entirely
A $70k-$180k range for a single role usually means the req was written to cover multiple levels - or multiple hypothetical futures. It can also just be sloppy writing. Weigh it with everything else.
The company's laying people off in that function
Hiring freezes are rarely announced with the same enthusiasm as funding rounds. If the news says the company cut 15% of engineering last quarter and the careers page still shows twelve open engineering roles, some of those roles are decorative.
The description reads like three jobs stitched together
"5+ years of backend experience, plus frontend, plus DevOps, plus technical writing, plus mentoring interns." A real hiring manager writes a req for the person they need. A req written by committee for a role nobody's urgently filling accumulates everyone's wishlist.
What to do with a suspected ghost job
Don't delete it - deprioritize it. The rational move is to sort your effort, not to boycott:
- Fresh posting, named team, real comp range: worth the tailored resume and the hour.
- Suspected ghost job: apply only if it's cheap - one-click apply, no cover letter, five minutes max. Treat it as a lottery ticket, not an investment.
- Confirmed pattern (three or more tells): skip it. Your hour is better spent finding the next real posting.
And check the date before you do anything. Sorting by "most recent" and ignoring anything older than two to three weeks filters out an enormous amount of ghost inventory with zero analysis required.
How Scoura helps here
This is one of the specific things Scoura's Ghost & Scam Detection flags. When you paste a posting in, ghost-job signals - stale repost patterns, evergreen language, missing team specifics, comp vagueness - get surfaced as part of the fit score, before you've spent any effort on it. It's the same pattern-matching above, run automatically, on every listing.
FAQ
Ghost jobs, answered.
Are ghost jobs illegal?
Mostly no, with narrow exceptions. Some jurisdictions have started requiring that postings reflect a genuine hiring intent - pay transparency laws in several US states touch the edges of this - but enforcement is thin and the definitions are loose. Don't count on the law; count on the tells.
How long before a posting counts as “stale”?
There's no bright line, but two to three weeks without movement is where skepticism becomes reasonable for most roles. Niche senior roles can legitimately stay open for months. A generic posting sitting for a quarter is a different story.
Should I still apply if I suspect it's a ghost job?
If the application costs you five minutes, sure - the downside is negligible. What you shouldn't do is spend an hour tailoring materials for it. Save the real effort for postings that pass the checks above.
What's the difference between a ghost job and just getting ghosted?
A ghost job was never going to hire anyone. Getting ghosted means there was a real process and the company stopped communicating - its own problem, and a different one from a posting that was never real to begin with.
Keep Reading