What does it mean when a job posting stays up for months?

A posting that has stayed up for months is one of the most familiar puzzles in a job search: you apply, hear nothing, and wonder what a listing that old is telling you. The honest answer is that it tells you how long it has been listed. Why it is still up cannot be read off a careers page.

What can be measured is duration: 16.9% of the 506,652 postings we track have been listed 90 days or longer, and the median has been up 31 days. We publish the duration and stop there, because going from “listed a long time” to a reason would be a guess about an employer, not a measurement.

506,652 live postings1,056 employers we crawl dailyas of September 20, 2026How we measure

Why a months-old posting is hard to read

Applicants notice long-listed postings for a reason: applying to something, hearing nothing, and then seeing the same listing still up weeks later is frustrating, and it invites explanations. People offer many, some ordinary and some less so.

Every one of them is a claim about why an employer did something. We have no access to that, and we are not willing to publish a guess about a named company’s reasons. What we do instead is publish the observable part, with its denominator attached, and let you weigh it.

What the duration data shows

31 days
Median age of the 506,652 live postings we track
16.9%
Listed 90 days or longer (85,647 postings)
1.4%
Listed a year or longer (7,034 postings)

The tail is what people notice. Most postings are recent and behave the way you would expect. A persistent minority does not: at any given moment 85,647 listings have been up for three months or more.

The removal side adds something the age data alone can’t. Of 419,988 postings we watched come down between July 24, 2026 and September 20, 2026; no fleet read on August 23, 2026, August 31, 2026; 4 more days not confirmed complete (see Methodology), 34,464 later went back up under the same listing. A listing that cycles is a real pattern; it still doesn’t say why.

How to use age without over-reading it

Treat posting age the way you would treat any single data point: as one input. A two-week-old posting tells you the employer was doing something recently. A ten-month-old posting tells you the listing has survived ten months, which is worth knowing before you spend an evening on a cover letter — and is not proof of anything.

You can check a specific posting below, see the longest-open postings we track, or read exactly how we date and count them.

How long has that posting been up?

Sign in and paste a job link to find a current public listing and its employer posting date, when available.

What this doesn’t tell you

We cannot tell you why any posting is still up. We measure how long a listing has been live and when it comes down. Nothing in that distinguishes one reason a role stays open from another.

Long-listed postings have ordinary explanations. Specialist roles, roles gated behind a slow approval chain, and requisitions an employer really does hire against continuously all produce long-lived postings for entirely ordinary reasons.

Postings we can identify as continuously-hiring are already excluded. Where a listing is clearly an always-open requisition rather than a specific vacancy, we leave it out of these figures rather than counting it as a stale posting. That exclusion is imperfect and it is applied before the numbers above, not after.

Related questions

Or look up a specific employer: browse the companies we track, see the longest-open postings, or read how these numbers are produced.