Ghost Jobs, Explained: Fake Posting vs. Impossible Req (and How to Stop Wasting Applications)

You found the perfect role. Right title, right stack, right city. You spent an hour tailoring the resume, wrote something halfway human in the application box, hit submit, and then nothing. No rejection, no acknowledgment, not even an automated "we'll be in touch." Three weeks later the listing is still up. So you do what everybody does now. You decide the job was never real.

Maybe it wasn't real, though plenty of the time it was and you just talked yourself out of a job that existed. The honest answer is that "ghost job" has become a single word doing four jobs, and the four things it describes need four different reactions from you. Lump them together and you get the version of job hunting that breaks people: every silence reads as proof the whole system is rigged, so you either rage-apply to 1,300 listings or stop trying. Pull them apart and the picture gets less conspiratorial and a lot more useful.

This is a guide to that sorting. What actually counts as a fake posting, what's just a pipeline play, what's a job that's real but impossible, and how to stop burning your limited application energy on the ones that can't convert no matter what you write.

What people mean when they say "ghost job"

Start with a working definition, because the loose one is where the trouble begins. A recruiter put it cleanly in a long r/recruitinghell thread: if everyone who applies has a zero percent chance of getting the role, it's a fake job. That's the strict bar. By that standard a posting isn't a ghost job just because it took four months to fill, or because you didn't get a callback, or because someone internal got it. It's a ghost job when there is no path from "apply" to "hired" for anyone.

Hold onto that, because it cuts the category down fast. Candidates tend to use "ghost job" to mean "any posting that didn't work out for me." Recruiters tend to use it to mean "a listing with no req behind it at all." Both are talking past each other, and the truth sits in the gap. Genuinely fake postings exist. They're also a minority of what frustrated applicants are tagging as fake. Once you accept both halves of that sentence, you can actually do something about it.

The four things hiding under one label

Here's the taxonomy that does the heavy lifting. Four buckets, plus a couple of edge cases.

1. The genuinely fake posting. No live, funded role behind it. The company is collecting resumes, padding its growth story, or keeping a listing up out of habit. This is the one everyone pictures, and it's real, just rarer than the panic suggests.

2. The evergreen, or pipeline, requisition. A posting a company keeps open on purpose to build a candidate pool for a role it hires for constantly. There is genuine intent to hire, just not a single seat waiting on you today. To a candidate this is indistinguishable from a fake job from the outside, which is exactly why it gets miscounted.

3. The unicorn req. A real, budgeted role that stays open for months because the description asks for the combined skills of five people at one person's salary. Nobody's lying, but nobody can match it either.

4. The compliance or internal-candidate post. A real job that's already going to a specific person, usually someone inside the company, posted publicly because law or policy demands an open call. Government roles run this way by default.

The two edge cases worth knowing: the budget-limbo req, where a manager will fund the seat only if a good enough candidate walks through the door, and the stale-but-filled post that's just left up after someone got hired. Neither is a scam. Both feel like ghosting from where you sit.

Walk through them one at a time, because the spotting signs and the right move are different for each.

The pipeline req: real intent, no open seat

This is the type most often misfiled as fake, so it goes first. An evergreen requisition is a recruiting tool, not a trick. The role has no end date and stays posted continuously so the company can keep a steady flow of applicants for a job it fills over and over. Call centers run on these. So do retail chains, hospitals, warehouses, and any team with predictable turnover or hard-to-find skills. The major applicant tracking systems even build it in. Workday and SAP SuccessFactors both have an "evergreen" flag you can set on a req precisely so it never auto-closes.

The logic is boring and legitimate. If you hire fifteen medical coders a year, opening and closing a fresh posting each time is slow and wasteful, so you keep one open and pull from the pool when a seat actually frees up. A recruiter described doing exactly this in an r/recruiting thread, and the part worth stealing is how they handled it: they told candidates up front that it was a pipeline role, and yes, sometimes the need never materialized and the posting led nowhere. That's the honest version. The dishonest version is the same mechanic with no disclosure, which is how a perfectly normal pipeline req earns the "ghost job" label it half-deserves.

What it looks like from your chair: a posting that's been live for ages, often for a high-volume role, sometimes reposted or "refreshed" so it keeps surfacing at the top of search. Applying isn't pointless. It just isn't the same as applying to a role with a funded seat and a hiring manager who needs someone by month's end. Treat it as putting your name in a hat, not as the focused shot you tailor your whole week around.

The unicorn req: real job, impossible bar

Then there's the listing that's completely real and still a waste of your time, which is its own special insult. You've read these. Seven years of an SDK that's existed for four. A "rockstar" who is also a "guru" and also somehow a "ninja," fluent in six tools, willing to own three job functions, for a salary that tops out where one of those functions should start. The line that's been quoted to death because it's accurate: companies wanting Tony Stark and paying Burger King wages.

How do reqs get like this? Usually not malice. A manager who doesn't quite understand the role writes down everything they see their current team doing and turns it into one person's job description, not realizing that "their current team" is four people with overlapping skills. Sometimes a slack labor market makes employers greedy. They figure if hundreds are applying, the unicorn might actually show up, so why settle. The req sits open for a quarter while they wait for a candidate who doesn't exist.

From a strategy standpoint, a unicorn req and a fake job have the same expected value for you, which is close to zero, so the practical response is identical: don't pour effort into it. The tell is in the description itself. When the requirements read like three roles stapled together and the comp doesn't match, you're looking at a posting that will stay open until either the market shifts or the company gives up. Neither outcome involves you.

The compliance post: the job already has a name on it

A big slice of "why was this posted if it was never open to me" comes down to rules you can't see. Plenty of employers, and nearly all government bodies, are required to post a role publicly even when they already know who's getting it. A public-sector worker described it bluntly: they're obligated to put the offer online for anyone to apply, even when they know one hundred percent who's taking the seat, because the government requires a public call for applicants.

That sounds damning until you hear the other public-sector voice in the same conversation, which is the part that keeps this honest. Another government employee said they have the identical posting requirement and still run the competition for real, hiring the most qualified applicant rather than the internal favorite. So a compliance post is not automatically rigged. Sometimes the internal candidate genuinely is the best fit and would have won anyway. Sometimes an outsider walks in and takes it. And sometimes, yes, the external applicants are a formality so a pre-chosen person clears a box.

You usually can't tell which from the listing. What you can do is read the signal in the process. If an internal title is referenced, if the description is oddly specific to one person's exact background, or if the role appears and gets filled suspiciously fast, you may be furniture in someone else's competition. None of that is fraud, and none of it is aimed at you personally. You've just walked into a game where another player started on third base.

The genuinely fake posting: where the panic is actually warranted

Now the real thing, because pretending it doesn't exist is its own kind of gaslighting. Companies do post roles they have no intention of filling, and they've said why in surveys with their own names on them.

The most-cited number is from a ResumeBuilder.com survey of 1,641 hiring managers fielded in May 2024: 40% said their company had posted a fake listing in the past year, and about three in ten had one live at the moment they were asked. The reasons the managers gave are the uncomfortable part. Sixty-seven percent posted to look open to external talent, sixty-six to look like they were growing, sixty-three to make existing staff feel that relief was coming, and sixty-two, read that one twice, to make employees feel replaceable. Fifty-nine percent kept the resumes on file for later.

A separate motive comes up constantly and is worth flagging as a claim rather than a proven fact: optics for investors. The theory goes that a wall of open reqs signals growth to shareholders, so companies post phantom roles to look healthy. It's plausible and people in hiring repeat it, but it has a hole. A recruiter pointed out that fake postings actually wreck the internal metrics recruiters get judged on, like interview-to-hire ratio, so the incentive runs the other way for the recruiter doing the posting even if it flatters the company's story. File the investor-optics motive under "commonly alleged, partly contested."

One category deserves its own line: the always-be-collecting pile. A worker on Reddit asked their HR why three openings had sat up for eight months with no real staffing need, and HR called them "proactive" pipeline postings. The sharpest reply in the thread aged the strategy in one sentence: does HR really think someone who applied eight months ago is still available, and won't the same HR then ask that person to explain the eight-month gap in their employment? Collecting resumes you let rot is its own small absurdity.

Where it stops being a ghost job and becomes a scam

One important fork. There's a difference between an employer posting a role it won't fill and a criminal posting a "role" to rob you. The second isn't a ghost job, it's fraud, and it deserves a different reflex.

The pattern surfacing most often in 2025 and 2026 looks like a clean, well-written remote listing, frequently for a data or crypto-adjacent role at a company you've never heard of, that moves fast to a "technical step" asking you to run some code or install something on your machine. One applicant who fell for a "remote data analyst" gig got walked into running a script; the top reply was a security warning that these attacks typically drop infostealer malware that hoovers up every saved password in your browser. Other variants exist only to harvest your personal data through a fake application form.

The rule of thumb is simple. A real employer, even one running a cynical pipeline, never needs you to run code, pay a fee, install a "screening app," or hand over bank details before an offer. If a posting pushes you toward any of those, close the tab. That's not a job you're missing out on.

How to read a posting before you spend an hour on it

So how do you sort a listing in the ninety seconds before you commit? No single sign is proof, but a stack of them tells you where to put your effort. The patterns that hold up across both candidate and recruiter accounts:

It's been up forever, or it keeps coming back. A posting that's been live for many months, or one that reappears at the top of search every week after you've already applied, is either evergreen or stale. Job seekers track this manually, some with spreadsheets, some with browser extensions that gray out companies they've already applied to. On LinkedIn you can mute a serial reposter by adding a NOT operator with the company name to a saved search, which is a genuinely useful five-second fix.

The same role is posted in a dozen cities at once. One common tech title filling five pages of search results under a single company name is the signature of a pipeline or volume play, not a dozen real openings waiting for you specifically.

No named company, thin description, all buzzwords. Generic agency postings with no real employer attached and a vague write-up are the ones experienced applicants quietly stop answering. If the listing can't be bothered to tell you who you'd work for, match its energy.

The requirements read like three jobs. That's the unicorn tell, a real role at long odds.

It's still live weeks after you were rejected. Either evergreen or nobody took it down. Not worth a second application.

And the single best move, if you get far enough to talk to a human: ask. A candidate in an interview asked how long the company expected the role to take to fill and got the quiet part out loud, that they'd "consider allocating a budget" if the right person showed up, meaning there was no funded seat at all. "Is the headcount approved, and what's your timeline to fill it?" is a fair, normal question. A crisp answer is a good sign, and a vague non-answer tells you plenty too.

Why the void feels bigger than the data says

Here's the uncomfortable middle ground. Even if only a slice of postings are truly fake, the experience of applying feels like shouting into a void almost regardless, and that's not your imagination. The funnel is just brutally crowded now.

A single posting can pull hundreds to over a thousand applications in its first days, a lot of them fired off by auto-apply bots and AI tools. Greenhouse reported recruiter workload jumping by a chunk in a single quarter as AI-assisted mass applying spread, and that more than nine in ten workers found the market hard going into 2025. When a recruiter is staring at eight hundred applications, the difference between a real job and a fake one barely registers from your side, because either way you're not getting a personal reply. So the silence you read as proof of a ghost job is often just proof of volume. That distinction matters, because the fixes are different: you can't beat a fake job, but you can absolutely beat the volume problem by being more targeted than the bots.

The push to make them illegal, and why it's harder than it sounds

The anger has started turning into legislation, which is new. In 2026, New York's legislature passed a bill, S8877, aimed squarely at ghost postings. As of June 2026 it's sitting with Governor Hochul awaiting a signature, so treat what follows as a proposal, not settled law. The bill would require larger employers and third-party job sites to be upfront about hiring intent: state the expected timeframe if they plan to fill within ninety days, say so plainly if there's no current opening, disclose when the only goal is collecting resumes, and pull listings within two weeks of a hire. The penalty floated is $2,500 per violation, doubling every thirty days a bad posting stays up. Similar bills have been floated in New Jersey, California, Kentucky, and Pennsylvania, and a frustrated tech worker spent 2025 pushing for a federal version.

Worth wanting. Also worth a dose of realism about enforcement, which is the part the angriest threads actually get right. Proving a posting was fake means proving intent, and a company has easy outs: no qualified applicants, candidate didn't interview well, budget got pulled, still reviewing. Any of those can be true, and all of them are hard to disprove from the outside. A disclosure law might clean up the laziest offenders and force evergreen reqs to label themselves, which would genuinely help. It won't make the unicorn req or the slow-rolling hiring manager illegal. Don't wait on a law to fix your job search.

What to actually do with this

The point of the taxonomy isn't to win an argument about whether ghost jobs are "real." It's to spend your effort where it can pay off. A few concrete shifts.

Cap your investment on low-signal postings. If a listing trips the ghost-job tells, you can still apply, but do it in two minutes, not sixty. Save the hour of real tailoring and keyword-matching for roles with a named company, a specific description, and a recent post date. Quality of targeting beats volume here, and it beats the bots, because a recruiter drowning in eight hundred auto-applications notices the one that obviously read the job.

Mute the repeat offenders so they stop eating your attention. Build the LinkedIn NOT filter, keep a short list of companies you've watched repost the same role for months, and stop re-applying to them on reflex.

Get off the apply button when you can. The roles least likely to be ghosts are the ones you reach through a person, so put weight on referrals, direct messages to people on the team, and a networking email that actually gets opened rather than a fortieth Easy Apply. When you do apply cold, a short, well-timed follow-up on the application a week later both nudges real roles and quietly outs the dead ones.

And fix the variables that are genuinely yours, because the posting being a ghost is the one thing you can't touch. Everything else, you can. Does your resume mirror the language in the job description? Does it clear the parsing and keyword screens people imagine the ATS uses? Does it read like a person wrote it and not a template? Tighten that. Sharpen the header so the basics parse cleanly on the first pass. Keep your LinkedIn profile searchable enough that a recruiter with a real opening surfaces you in a Boolean search before you ever apply. Ghost jobs are a real tax on your time. That's a lousy reason to stop sharpening the things that decide the real ones.