Ghost jobs backfire hardest on the person who has to read the resumes

According to a 2024 survey of 753 recruiters by MyPerfectResume, 81% admitted their employer posts job ads for roles that either don’t exist or are already filled. Separately, an analysis of 176,268 job listings on Indeed found that about 1 in 7 postings qualify as ghost jobs, rising to roughly 1 in 5 for senior-level roles.

Most coverage of that data blames large companies for stringing candidates along. That story is true as far as it goes, but it skips the version of this that shows up at a much smaller scale. If you’re the owner reading every resume yourself, a ghost job looks less like a corporate trick and more like a role you posted, maybe through one of the free job posting sites employers use to get it live in an afternoon, before deciding whether you were actually set up to review what it would bring in. Now you’re the one holding the pile.

That distinction matters because the cost lands somewhere different depending on who posted the role. A recruiter at a large company can leave a ghost job live for months without personally feeling it. You can’t. Every application that role collects is either read by you or it isn’t, and either way you’re the one who knows it.

Ghost jobs aren’t only a big-company trick

The reasons people give for posting roles they’re not ready to fill are surprisingly ordinary. In that same MyPerfectResume survey, the top reasons recruiters cited were testing how candidates respond to a hard-to-fill role (38%), keeping a presence on job boards while not actively hiring (38%), and evaluating whether a job description is working (36%). Another 26% said they were building a pool of candidates for later.

None of that requires a large HR department. An owner who posts a coordinator role “just to see who’s out there” before payroll is approved is doing the exact same thing, for the exact same reason, as the recruiter in that survey. That instinct is less about dishonesty and more about never testing whether you can actually handle what a live posting invites.

A more deliberate version happens at bigger companies

There’s a related, more deliberate version of this in regulated industries like financial services, where a role gets posted externally purely to satisfy a compliance policy, even though the position was effectively filled internally weeks earlier. That’s a different motive than the small business version. Nobody at a five-person company is posting a role to satisfy a compliance department. But the shared failure mode is the same: a live posting goes up before the actual decision to hire is finished, and someone downstream pays for the gap.

We’ve written before about the mirror version of this problem, where candidates go quiet on employers instead of the other way around. The fix there turns out to hinge on the same thing this does: closing the gap between when something happens and when someone actually reviews it.

What actually happens after you hit publish

The surveys don’t capture what happens next, because they’re written from the recruiter’s chair, not yours. The moment a role goes live, applications start arriving on their own schedule, whether or not you’re ready to read them.

If you’re not set up to screen what comes in, the pile doesn’t disappear. It just sits, growing every day the posting stays up, until it becomes something you feel obligated to deal with even though you never fully decided you were hiring. Anyone who has ended up with more applications than they can read in a week knows how quickly that pile stops being optional. Add in the bot-generated and spam applications that land on any public posting, and a role you weren’t even sure you wanted to fill can generate hours of review you never budgeted for.

A ghost job costs you more than a candidate’s wasted time. It costs you the evening you’ll spend reading resumes for a role you never finished deciding to fill.

The reputation cost lands closer to home than you’d think

There’s a reputation cost too, and it’s sharper for a small business than a large one. A big company’s candidate pool is anonymous and largely one-time. Yours often isn’t. In a single town, a franchise territory, or a niche trade, the same names apply to your postings more than once. A candidate who applied, heard nothing, and later learns the role sat open for months without a real process remembers that the next time you post. So does anyone they mention it to.

The ghost job is usually an unfinished decision

Most writing about ghost jobs treats the problem as dishonesty: employers pretending to hire when they aren’t. For an owner with no recruiter, that framing usually misses what’s actually happening. You’re rarely trying to deceive anyone. You’re testing the market, gauging whether you could even find someone for the role, or leaving a posting live because taking it down feels like giving up on hiring altogether.

Call it sequencing rather than intent. You posted the role before you’d decided whether you were structurally ready to screen what it would bring in. That’s a fixable gap, and the fix looks nothing like “stop posting fake jobs,” which was never really your problem in the first place.

Ask a different question instead: if this role goes live today, do you have a way to review whatever it collects by the time it matters. That’s the question most ghost job advice skips, because it’s aimed at whether you should post at all, not at whether you’re set up to handle it once you do. It’s the same question behind the screening workflow that works when you have no recruiter: not a bigger team, just a way to keep pace with whatever comes in.

A pipeline doesn’t need a live job posting

There’s a real, defensible reason to want a standing supply of good candidates even when you’re not actively hiring, and the survey data backs that up too. Wanting a pipeline is reasonable. Building one with a live, public posting is where it goes wrong.

A live posting is a promise to a real person that a real process is underway. When someone applies, they expect to hear something back, on some kind of timeline. A pipeline doesn’t need that promise. It needs a way to hold onto candidates you already decided were a good fit for your small business, even if the timing wasn’t right, so the next opening doesn’t start from zero.

If you want to keep good people warm between roles, the fix is a system that remembers candidates you’ve already screened and lets you reach back out when a real opening appears, not a job posting that quietly collects strangers’ applications for a role that isn’t actually open yet.

What being screening ready actually takes

Most owners end up choosing between posting now and drowning, or waiting to post until there’s time to babysit an inbox. Those are the only two options when nothing is reviewing the pile as it comes in. The first invites people into a process you can’t keep up with. The second just delays the same problem to a week you don’t have either.

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, and it changes which of those two options you’re stuck choosing between. Resumes get ranked against your own criteria the moment they arrive, so a stack of applications never sits waiting for a night you finally have time. Qualification questions flag who actually meets your must-haves right away, so you’re not spending real attention on the obvious mismatches. If you want a first read on how someone communicates without booking a call, a one-way interview lets a candidate record on their own time, and you can review it in minutes whenever you get to it. Where the role calls for it, a talent assessment adds a signal on judgment or work style, without adding another round of scheduling.

None of that changes whether you’re really ready to hire. What it changes is the excuse for posting before you are. You can go live the day you actually mean to fill the role, because the review already happens as the applications land instead of piling up until you find an evening.

Aim to be screening ready, a bar you can actually hit

Most advice aimed at this problem tells employers to stop posting roles they don’t intend to fill. That’s fine advice for a company with a hiring policy to enforce, and much less useful for an owner who never had a policy in the first place, just a job board account and a role that needed filling eventually.

“Recruiter ready” was never a fair bar when there’s no recruiter to be one. A more useful standard is screening ready: whatever this posting brings in can actually get looked at on a timeline that respects the people applying. That’s a bar you can hit without hiring anyone or building a process from scratch.

Treated that way, honesty about your hiring intentions stops being a rule you have to remember to follow every time you’re tempted to post early. It becomes a side effect of having something in place that reads every application the moment it lands, so there’s never a pile sitting around waiting to become a decision you already made without noticing. The same shift is behind most of what actually speeds up hiring for a small team: less effort spent reading faster, more of the reading happening automatically as it arrives.

Frequently asked questions about ghost jobs

Is it illegal to post a ghost job?

In most of the US, no, not on its own. A few states and cities have proposed salary transparency and posting-accuracy rules that make deceptive listings riskier, but there’s no broad federal law against posting a role you’re not actively filling. That doesn’t make it free. The cost shows up in wasted candidate time and, for a small business, in a local reputation that’s easy to damage and slow to repair.

How can I tell if I’m about to post a ghost job?

Ask whether you could review whatever the role brings in within a week of it arriving. If the honest answer is no, because you haven’t approved the budget, decided on the role’s scope, or built any way to screen the pile it’ll generate, you’re not ready to go live yet, even if the intent to eventually hire is genuine.

What’s the difference between pipeline building and a ghost job?

Pipeline building means keeping candidates you’ve already screened warm for the next opening. A ghost job means inviting strangers to apply to a role that isn’t really open, without any process behind it. The first respects people who already gave you their time. The second collects new applications you have no plan to act on. Most hiring software built for small businesses can hold onto a screened candidate for you. A job board can’t.

Should I take down a role I’m not ready to fill right now?

If you can’t screen new applications on any reasonable timeline, yes. Leaving a stale posting live doesn’t preserve optionality, it just accumulates unreviewed applications and erodes trust with anyone who applies and never hears back. Take it down, and repost when you can actually keep pace with what it brings in.