There's a word candidates use for the 2026 market: "ghost jobs" — postings that are up but aren't really hiring.

Candidates treat it like a scam. But on your side of the desk, most ghost jobs aren't on purpose.

It's a req you opened three months ago. The hiring manager went quiet. Headcount may have been frozen. But the posting keeps running, résumés keep landing, and nobody ever officially closed it.

400 people applied. No one read them.

You don't have a shortage of CVs. You have no idea which of your jobs is still alive.

Why do jobs stay open with nobody accountable?

Opening a req is easy. Closing one is a decision nobody wants to make.

Opening a job is a reflex. Closing it is a choice.

When a team might need someone, a job goes up.

When they stop hiring, nobody sends the "please close this" message.

So the job just keeps living. Like a browser tab you forgot to close last month.

You're managing CVs, not jobs

Most of your stack is built to collect résumés in one place.

None of it answers the question that actually matters:

• Is this job still hiring?
• Who owns it?
• When was the last CV even opened?

You have a pile of CVs. You don't have a picture of your jobs.

A scenario every recruiter knows

July: the team needs a Senior Frontend. The job goes live on LinkedIn, Indeed, your careers page.

August: the project slips. Nobody tells you.

October: you open your dashboard — 240 CVs, three "open" roles, and only one that's actually real.

You can't tell which CVs belong to a job that still exists.

The person who applied last week is still waiting for your email. It's not coming.

Candidates remember. You don't.

In 2026, ghost jobs became something applicants talk about openly — on LinkedIn, in community threads, in whole guides on "how to spot a job that isn't real."

Every job you leave open and forget is a person who applied and never heard back.

They don't know headcount got frozen. They don't know the project slipped. They know one thing: your company posted, they applied, and then silence.

Your employer brand pays for something you don't even remember doing.

Opening a job = easy. Closing a job = nobody's task. The candidate = still waiting.

An open job with no one managing it isn't a pipeline. It's a graveyard with the lights left on.

How to manage jobs so none of them turn into ghost jobs

You don't need more CVs. You need every job to carry a clear status.

I call it the O.W.N. framework — every job has to be owned, not left to drift.

The O.W.N. Framework — one owner, one window, one next move

O is for Owner

Every open job gets exactly one name attached.

Not "the recruiting team." One person.

No owner? That job should default to closed.

An unowned job is the single most reliable way to grow a graveyard.

W is for Window

Every job gets a "close by" date.

There's no such thing as an evergreen req.

Hit the date without a hire? Someone decides to extend — actively, not by neglect.

A window isn't a deadline you punish people for missing. It's a forcing function that makes someone look at the job again.

N is for Next move

Every candidate in a job has a defined next step: read, interview, reject, or keep warm.

If a CV has no next move in 7 days, that's your signal the job is dying.

A healthy job is one where every CV knows where it stands.

Silence isn't neutral. For the person on the other end, no next move reads exactly like a rejection — just a slower, colder one.

You can run O.W.N. in a three-column Google Sheet. Really.

The problem was never the tool. It's that nobody treated job status as something you manage — on the same level as reading CVs or booking interviews.

When you start managing jobs the way you manage a live project, something strange happens: your count of "open" roles drops. Not because you hired more, but because you stopped pretending the dead ones were alive.

The Knoot Angle

An open job is a promise to the people who apply — that someone, somewhere, is actually reading them. When you let a job drift, you don't just lose control of your pipeline. You break that promise.

That's why Knoot's Job Management module treats a job as a living process, not a posting you leave running. You create and manage every job in one place, set scoring criteria per role, and track the full application flow for each one — who just applied, who's waiting, which roles are genuinely still open. You control what candidates see, too, so no job quietly runs on behind your back.

When every job carries a clear status, ghost jobs have nowhere to hide — and the people who applied get the one thing they're owed: an answer.

An open job is a promise. Keep it, or close it.