Ghost jobs explained. Why companies post them, and how to avoid losing candidate trust

Somewhere in every ATS is a requisition nobody quite remembers approving to stay open. Maybe it was funded and then the budget froze mid-quarter. Maybe a hiring manager asked to “keep the door open” for a role that isn’t coming back this year. Maybe it’s simply still there because closing it required a conversation nobody had time to have. It sits in the pipeline like a low hum in the background of every headcount meeting – not urgent enough to fix, not disposable enough to delete.

Multiply that one requisition across an industry, and you get a labor market where a fifth to a third of all postings, at any given moment, don’t reflect an active hire. That’s not a scandal committed by a handful of bad-faith employers – it’s the accumulated residue of a hundred reasonable-sounding decisions, each made under real pressure, none of them designed with the applicant on the other end fully in view. Ghost jobs exist because they solve real operational problems for employers – pipeline gaps, budget lag, market signaling – and they turn toxic the moment a company starts treating candidate trust as a resource that replenishes itself. That’s the whole argument. What follows is the evidence, the nuance, and a working playbook for staying on the right side of it.

What a ghost job actually is

A ghost job is a public posting that stays live without a genuine, near-term intention to fill it. The company is real. The applicant tracking system is real. The role may even become real eventually. But no one is currently reading your resume with the intent to hire against it. That distinguishes a ghost job from an outright scam listing, which has no legitimate employer behind it at all and exists purely to extract money or data. Ghost jobs are a workforce-planning failure mode wearing a recruiting costume – not fraud, though from the applicant’s chair, it can feel indistinguishable.

Nobody owns a clean, authoritative count of how often this happens. The Congressional Research Service noted in April 2025 that there are no official statistics on the scale of the phenomenon, since federal labor data tracks reported openings, not posting intent. But three independent measurement approaches, using entirely different methods, converge on roughly the same territory:

• Platform data. Greenhouse’s analysis of its own hiring platform found that between 18% and 22% of all postings show no real hiring activity behind them.
• Employer self-reporting. A Clarify Capital survey of 1,045 hiring managers found that while 96% claimed to be actively trying to fill a role quickly, 40% didn’t expect to fill it for another two to three months. A separate 2025 Clarify Capital survey of 1,000 employers found that nearly one in three admitted posting jobs with no current intent to hire at all.
• Outcome gaps. Bureau of Labor Statistics JOLTS data shows a persistent monthly gap between reported openings and actual hires – on the order of 2.1 to 2.2 million nationally through 2025.

Three different questions, three different numbers, one shared shape: a meaningful slice of the market’s “open” roles are not, in any functional sense, open.

The business problems hiding behind the ghost posting

Before passing judgment, it’s worth taking the underlying motives seriously – because most of them are legitimate management problems wearing a job listing as a disguise.

Pipeline building. The most common justification by far. A recruiter keeps a requisition live to accumulate resumes ahead of a role they expect to open eventually – hard-to-fill technical seats, seasonal retail surges, chronically high-turnover functions like support or nursing. It’s less “posting a job” than “keeping a net in the water.” A LiveCareer survey found the practice widespread enough that 45% of HR professionals post ghost jobs regularly and another 48% do so occasionally – 93% engaging with the practice to some degree.

Budget-to-approval lag. Headcount gets approved on paper long before finance releases the funding, or a department head wants a role greenlit “in principle” before an offer can legally exist. The requisition arrives ahead of the money it’s supposed to represent.

Always-open sourcing. Some organizations treat certain roles – sales, engineering, high-turnover frontline positions – as permanently open on the theory that a strong unsolicited candidate is worth a conversation whenever they surface. Clarify Capital’s research found this the single most common reason employers gave for keeping a posting live without real urgency behind it, cited by roughly half of respondents.

Market and competitive intelligence. A posting can function as a listening device – a way to benchmark salary expectations, gauge the depth of a local talent pool, or read what a competitor’s hiring activity is signaling, all without any near-term intention to hire.

Optics. A visible wall of open roles reads as growth to investors, customers, and the market, even when the actual headcount plan is frozen solid. This is the motive most likely to slide from workforce planning into performance – a stage set built to look like momentum.

Operational drift. Sometimes there’s no strategy at all, just entropy: a filled requisition never gets closed in the ATS, or a hiring freeze never made it down to the recruiter still running the campaign.

None of these motives are inherently predatory. What separates a defensible business decision from a trust violation is a single variable: whether the person on the other end of that application ever finds out what’s actually happening.

When ghost postings make business sense

There’s a legitimate version of nearly every motive above, and the legitimate version shares three traits.

1. Evergreen roles, honestly labeled. High-turnover, high-volume functions – retail associates, delivery drivers, call-center staff, seasonal warehouse workers – genuinely never stop hiring. Keeping a standing requisition open for roles like these isn’t deceptive, as long as candidates understand they’re entering a rolling pool rather than applying to one vacancy with a start date attached.

2. Approved headcount with a bounded timeline. If a role has cleared budget approval and is expected to open within a defined window – a quarter, say – posting ahead of the formal opening can be entirely reasonable, provided the posting says so and the window is actually honored.

3. Specialized or senior pipelines with real engagement. For roles where qualified talent is scarce and hiring cycles are long – niche engineering, executive search, rare clinical specialties – building a relationship with strong candidates before a seat opens is standard talent acquisition, not deception, as long as those candidates are engaged as people and not silently filed away as resumes in a folder no one reopens.

The common thread across all three: the organization is honest – either explicitly in the posting or through active recruiter contact – about what stage the role is actually in. That honesty is the entire distance between workforce planning and what candidates experience as bait.

When it stops being strategy and starts being something messier

The same practice curdles under three conditions.

No disclosure, no end date. A posting that sits live for months with no label, no update, and no closing date has stopped being pipeline building. It’s an unmaintained asset generating false hope on autopilot. Clarify Capital’s tracking of posting age found that the share of employer listings staying active more than 30 days fell from 68% in 2022 to roughly a third by 2025 – real improvement, but still describing an enormous volume of stale listings live at any given moment.

Used as leverage instead of logistics. When a posting exists mainly to make an internal team feel replaceable, or to imply an external hire is one interview away in order to pressure current employees, the tool has crossed from workforce planning into something closer to manipulation. Precise figures on how often this happens specifically should be treated cautiously – the self-reported surveys behind some of the more dramatic numbers circulating online have thin, undisclosed methodology. What’s well documented is the downstream effect: candidates and employees alike now default to assuming bad faith, which corrodes the credibility of every posting a company runs – including the honest ones.

Regulatory exposure. This has stopped being a purely reputational risk. Ontario’s Working for Workers Act introduced anti-ghosting and posting-transparency requirements effective January 2026. California passed legislation in 2025 requiring employers who publicly advertise openings to disclose whether a posting reflects a genuine vacancy, with violations treated as unfair competition under state law and enforcement authority held by the state labor commissioner. New Jersey has introduced comparable bills. At the federal level, the FTC’s Consumer Sentinel data showed reports of job and employment scams nearly tripling between 2020 and 2024, prompting the agency to prioritize deceptive job advertising through a dedicated task force in 2025. Ghost jobs and outright scam listings remain legally distinct categories, but regulators are increasingly treating “no disclosure of posting status” as a violation in its own right – meaning the undisclosed version of this practice now carries legal exposure, not just reputational cost, across a growing list of jurisdictions.

The hidden cost: what every undisclosed posting withdraws

Call it the trust ledger. Every job posting is an implicit promise: apply, and a real person will weigh you against a real opening. A disclosed, honestly-labeled pipeline posting makes a small, visible withdrawal – candidates can see it coming and choose whether to accept the terms. A silent ghost posting makes the same withdrawal without telling anyone, and the balance doesn’t reset when the next posting goes up. It compounds – quietly, then all at once – against the employer brand as a whole, the way erosion looks like nothing for years and then a hillside for one season.

The measurable costs fall into four buckets:

• Referral collapse. Employer-brand research links ghosted candidates to sharply reduced willingness to refer other qualified people into the organization – a direct hit to what remains, in most industries, the cheapest and highest-quality hiring channel available.
• Signal degradation on the real postings. Once candidates can no longer distinguish a company’s genuine openings from its pipeline-building ones, they discount all of them – applying with less effort, or skipping roles entirely that would have been a strong mutual fit.
• Public, searchable erosion. Review platforms, forums, and an entire cottage industry of “ghost jobs exposed” coverage now exist to catalog employers by name. Frustration that used to dissipate privately over dinner is now indexed, permanent, and exactly the kind of content increasingly surfaced by the AI-driven answer engines candidates use to research an employer before ever applying.
• Recruiter time, spent twice. Every ghost posting that surfaces real applicants still generates real screening work – resumes to sort, ATS noise to manage, occasionally interviews conducted for a role that was never going to close. Whatever efficiency a standing posting buys the pipeline is partly eaten by processing overhead that never converts into a hire.

None of this shows up cleanly on a quarterly P&L, which is precisely why it persists. The costs are diffuse and delayed; the benefits – a fuller pipeline, tidier optics, a cheap-looking source of resumes – are immediate and easy to point to in a meeting.

Can ghost jobs be done responsibly? A practical framework

Yes – and the mechanism is disclosure, not abstinence. A four-part operating standard:

1. Label pipeline postings as pipeline postings. A single sentence – “This is an ongoing talent pool for future openings; we are not actively interviewing for an immediate start” – converts a deceptive posting into an honest one overnight. Clarify Capital’s research on job-seeker sentiment found that 97% of job seekers believe companies should disclose when a posting exists for pipeline building rather than an immediate vacancy. This is the single highest-leverage fix available, and it costs nothing to implement.

2. Give every posting a time-to-live. Set a default expiration – 30 or 45 days is common – after which a requisition auto-closes or requires active recruiter renewal. This alone kills the “forgotten open req” category and forces a low-effort, periodic audit of what’s actually still true.

3. Build a minimum-viable response SLA. Applicants don’t need a phone call. They need an acknowledgment, and eventually a status update or closure – even an automated one – within a defined window. This single change addresses most of what candidates describe as being “ghosted,” since the bulk of the trust damage comes from silence itself, not from rejection.

4. Separate the market-signal use case from the hiring use case entirely. If leadership wants a visible wall of open roles for investor or competitive optics, that’s a communications decision, not a recruiting one – and it shouldn’t run through the same ATS and candidate-facing channel as real hiring, where it inevitably gets mistaken for one.

External verification infrastructure is emerging too: both LinkedIn and Greenhouse have introduced posting-verification badges meant to signal confirmed, active openings – giving transparent employers a way to visibly differentiate themselves in a market that now treats every listing with suspicion by default.

When workforce planning reads as a broken promise

Here’s the mechanism worth naming outright, because it’s the crux of why well-intentioned organizations mishandle this so often.

Organizational psychology has a term for the implicit set of expectations two parties form around an exchange: the psychological contract. A job posting creates one instantly, on the candidate’s side, whether the employer means it to or not. The candidate’s half of the exchange – hours spent tailoring an application, the small emotional investment of imagining themselves in the role – is offered upfront and in good faith. When the employer’s half of the exchange never arrives – no real evaluation, no real answer – the candidate doesn’t register a neutral, ambiguous outcome. They register a broken promise, because structurally, that is what happened, regardless of whether any individual recruiter meant harm.

This is why “we were just building a pipeline” reads to a candidate as a non-answer, even when it’s a perfectly coherent internal rationale. The company and the candidate were reading from two different documents the whole time: the company’s internal requisition plan, and the candidate’s reasonable interpretation of a public posting as a present-tense statement of intent. Responsible ghost-job practice is, at bottom, the discipline of making sure those two documents say the same thing before a stranger spends an evening writing to either of them.

So what decision should you actually make?

Strip away the research and the regulation, and most HR teams staring at a stale requisition are really asking one narrower question: do I leave this posting up, or not? It’s a smaller decision than it feels like, and it collapses into four honest questions, asked in order.

1. Is there a real, funded intention to fill this role within a defined window – say, the next 90 days? If yes, post it normally. This isn’t a ghost job; it’s ordinary recruiting with a slightly early start date. Move on.

2. If not, is there still a genuine, ongoing need for this type of talent – high turnover, hard-to-source skills, a role that effectively never stops hiring? If yes, keep the posting live, but label it as a pipeline: state plainly that it’s an open talent pool rather than an active vacancy, and set an expiration date so it doesn’t outlive its own honesty. This is the responsible version of the practice – the one 97% of job seekers say they’d accept if told upfront.

3. If neither of the above is true – no funded plan, no ongoing need – is the posting serving a purpose other than hiring: optics, benchmarking, internal signaling? If yes, that purpose still doesn’t belong on your careers page or ATS. Pull the posting. Whatever it’s accomplishing for investors, competitors, or internal morale, it can be accomplished through a channel that doesn’t cost a stranger an evening of unpaid, uncompensated hope.

4. If none of the above applies and the listing is simply still live out of neglect – a closed req nobody remembered to close – close it today. This is the cheapest fix in the entire framework and the one most often skipped. An audit of every posting past 30–45 days, run monthly, catches nearly all of it.

The decision, in other words, is never really “ghost job or not.” It’s “can I put a true sentence next to this listing” – and if the honest answer is no, the posting needs to come down, not stay up hoping nobody asks.

What applicants should know

If you’re on the receiving end of this pattern, a few signals are worth checking before investing hours in an application:

• Posting age. A listing live for 60-plus days with no updates is more likely to be a pipeline posting than a live vacancy.
• Specificity. Vague scope, no named team, no concrete deliverables, and a salary range spanning $40,000 or more often signal a low-urgency requisition rather than an active search.
• Reposting patterns. A role that vanishes and resurfaces under a new requisition number every few weeks is a strong signal it isn’t converting into a hire.
• Verification badges. Where platforms offer them, a verified or “actively hiring” tag is a meaningfully stronger signal than an unverified listing.

None of this means abandoning older or vaguer postings outright – some genuinely are disclosed pipelines that convert later. It means calibrating expectations, and diversifying search effort toward direct outreach, referrals, and recruiters rather than treating any single posting as a near-guaranteed path to an interview.

The bottom line

Ghost jobs aren’t a scandal by default – they’re a workforce-planning tool that a large majority of HR professionals already use in some form. The evidence is consistent across independent methodologies: somewhere between one in five and one in three postings, at any given moment, doesn’t reflect an active, imminent hire. That isn’t going away, and outright bans are unlikely to succeed where disclosure requirements are already proving far more durable.

The organizations that come out ahead won’t be the ones that stop pipeline-building. They’ll be the ones that stop asking candidates to guess which kind of posting they’re looking at.