How Long Do Ghost Jobs Stay Posted? What Posting Age Reveals

You apply to a job that's been "posted 3 weeks ago." You apply again a month later and the same listing says "posted 2 days ago." Same title, same company, same weirdly specific requirement about a niche software tool. What happened? Nothing happened — the job was probably never filled, and it might never be.

Posting age is one of the more useful, and more misunderstood, signals in the ghost job problem. Roughly 43% of job postings may be ghost jobs — listings with no real role behind them, or none the employer actually intends to fill (Resume Builder, Clarify Capital, ZipRecruiter, 2024–2025). That's a survey figure based on employers admitting to the practice, not an audit of every posting on every board, but it's a strong signal that "the listing is old" is worth paying attention to.

inteller.ai, an AI-powered career advisor, exists partly to make sense of signals like this one. It's not a resume builder — it reads every job description twice, once for a full assessment and once through an independent second pass, specifically looking for fraud and ghost-job signals before you spend hours tailoring an application.

There's no universal clock. A specialized engineering role at a 200-person startup might reasonably take six to eight weeks to fill. A retail associate position should move faster — often within two to three weeks — because the hiring process has fewer steps. Executive searches can drag on for months for entirely legitimate reasons: internal alignment, competing candidates, or a board sign-off that keeps slipping.

The problem is that none of this tells you much in isolation. A 45-day-old posting for a software engineer isn't necessarily a ghost job. A 45-day-old posting for a warehouse associate role, reposted three times with identical text, starts to look different. Context — sector, role complexity, and repost pattern — is what turns "old" into "suspicious."

To make that context concrete, it helps to see how "normal" posting age varies by role type before you start judging any single listing as stale:

This isn't a precise rulebook — it's a baseline. The point is that "60 days old" means something completely different for a warehouse job than it does for a VP of Engineering search, and treating every posting against the same clock is how people either over-flag legitimate slow hires or under-flag genuine ghost listings.

Here's how this plays out with an actual listing pattern, rather than in the abstract. Imagine a "Senior Data Analyst" role at a mid-size logistics company:

• Week 1: Posted with a fairly standard description — SQL, dashboarding, cross-team reporting.
• Week 4: Still live, unchanged. Not alarming yet; a mid-level analytics role can take a month or more to fill.
• Week 7: Listing disappears, then reappears two days later with the same text but a new posting date, resetting the "days ago" counter to zero.
• Week 10: Same thing happens again. Requirements haven't changed, but a line has been added asking for "5+ years in a tool" that didn't exist five years ago.

Read individually, none of these weeks is damning. A hire that takes seven weeks is normal. A single repost could mean the first candidate fell through. But stacked together — repeated resets, no substantive change in language, and a requirement that's logically impossible to satisfy — the pattern stops looking like a slow, honest search and starts looking like a listing being kept alive for reasons that have nothing to do with actually hiring someone. This is the kind of pattern-over-time read that a single glance at "posted 3 days ago" can never give you, because that glance only shows you the most recent reset, not the history behind it.

There are a few honest reasons a listing lingers well past what feels normal:

• Evergreen pipelines. Sales, nursing, and customer support roles are often kept open permanently so a company always has a bench of pre-screened candidates when someone leaves.
• Budget freezes. A role gets approved, posted, then quietly frozen while leadership works out financing — but nobody takes the listing down.
• Failed searches. The first round of candidates didn't work out, so the company reposts rather than reopening from scratch, which resets the "days ago" counter.
• Compliance requirements. Some companies are required to post externally even when they already have an internal candidate lined up.

None of these are automatically malicious. But they all produce the same visible artifact: a listing that's been up far longer than the role should reasonably take to fill, and that's exactly why posting age alone can't be your only filter.

This is where a lot of job seekers get it wrong, and it's worth being direct about: reposting is not the same thing as ghosting. A repost can mean a genuinely restarted search — the first attempt failed, and the company is trying again in good faith. That's frustrating for candidates but not deceptive.

What's different is a listing that reposts on a tight, repeating cycle with no real change in language, no clear evidence anyone was hired, and requirements so specific or contradictory that almost nobody could plausibly fill them. That pattern — not the repost itself — is the actual ghost signal. The distinction matters because treating every repost as a scam will cause you to skip real opportunities, while treating every old listing as safe will waste your time on nothing.

If you're applying to an evergreen listing, you're not necessarily being scammed — you're being added to a pool. That can still be worth your time if you're early in a search or building relationships in an industry, but it changes your expectations. You should not expect a fast response, and a long silence isn't a rejection so much as the company waiting for a specific opening to match your profile against.

The frustrating part is that companies rarely label a listing as evergreen. You're left guessing based on how long it's been up and how generic the language is. That ambiguity is exactly why silence is such a common complaint: 40% of job seekers say never hearing back is their single biggest frustration in the job search (ZipRecruiter Research, 2026). An evergreen listing and a dead one produce identical silence from the applicant's side, even though the intent behind them is completely different.

Even without a dedicated tool, there are a few manual checks that get you most of the way to a judgment call:

• Search the exact job title plus company name on a second job board. If the same role is posted on three different sites with three different "days ago" counters, you're looking at syndication, not three separate openings.
• Save the listing text. If you revisit it in two weeks and the posting date has reset but the description is byte-for-byte identical, that's a stronger signal than the reset alone.
• Check the company's other listings. A company that reposts one role on a tight cycle while its other roles move normally is a different situation than a company where every listing looks stuck.
• Look at the "easy apply" behavior. Listings that accept applications through a generic portal with no named recruiter are harder to verify and more likely to be low-effort postings kept alive with little oversight.

None of these checks are conclusive on their own, which is the same limitation posting age has by itself. They're most useful stacked together, the same way sector, repost pattern, and requirement specificity are most useful stacked together.

Posting age is one input, not a verdict. On its own it tells you a role has been open a while — it doesn't tell you why. To actually screen for ghost jobs, you'd want to also look at:

• Whether the requirements are unusually vague or, conversely, so narrow they read like they were written for one specific unicorn candidate
• Whether the company has a pattern of near-identical reposts across multiple boards
• Whether the listing description uses generic, copy-paste language that doesn't match the rest of the company's actual job openings
• Whether contact information routes to a general inbox instead of a real recruiter

Doing this manually for every listing you consider applying to isn't realistic, especially if you're applying broadly. This is part of the reason 97%+ of Fortune 500 companies use an applicant tracking system to filter resumes on their end (Jobscan, 2024) — it's an entirely automated process on their side, and it's reasonable for candidates to want automated screening on theirs.

This is where inteller.ai's approach differs from a keyword-matching tool. Every job description gets read twice: once for a full contextual assessment, and once by an independent second reader that ignores tone and only asks what the posting actually requires you to do, without seeing the first reader's conclusion. That two-read structure is protection-first — most resume tools skip this step entirely and go straight to formatting your resume against the listing.

When a posting looks stale or evergreen, inteller.ai doesn't just say "this might be a ghost job" and leave you guessing. It shows you the specific phrase in the listing that triggered the flag — the vague requirement, the contradictory language, or the pattern that raised the concern — so you can judge the reasoning yourself instead of trusting a black-box score.

Beyond ghost-job detection, inteller.ai also runs ATS scoring using a 200+ skill database with weighted categories and skill aliases, so you can see how your resume actually reads against a specific posting's requirements. It gives an honest AI fit assessment too — including telling you when you're not a fit, which is a different posture from tools like Jobscan (built around keyword matching) or Teal (built as a job-search CRM) or Rezi (a resume builder). None of that is a knock on those tools; they solve different problems. inteller.ai's role is specifically the fraud and fit layer before you invest time tailoring anything.

• Don't treat "posted X weeks ago" as proof of anything by itself — check it against the role's sector and typical complexity.
• Be more skeptical of listings that repost on a tight cycle with identical language than of listings that are simply old.
• If a listing feels evergreen, apply with the expectation of a pool, not a fast pipeline — and don't read silence as personal rejection.
• Use a tool that shows its reasoning. A flag is only useful if you can see the exact phrase that triggered it, not just a score.
• Before you spend an evening tailoring a resume, check whether the listing itself is worth the time.

Posting age is a genuinely useful clue, but it's not a verdict. A three-month-old listing might be an evergreen pipeline for a company that hires constantly, a failed search that's since been abandoned, or exactly what it looks like: a ghost job that was never going to be filled. Reposting adds another layer of nuance — restarting a real search looks identical, from the outside, to running out the clock on a listing nobody intends to fill.

What actually helps is being able to see the reasoning behind a flag instead of guessing. Using inteller.ai, you can run a posting through two independent reads and see the exact phrase that triggered a stale or evergreen flag before you commit hours to an application. If you want to try it, inteller.ai has a free tier, and the code GHOSTJOB gets you 40% off.

Sources: Resume Builder (2024–2025), Clarify Capital (2024–2025), ZipRecruiter Research (2026), Jobscan (2024).