Reposted Jobs: How to Tell a Listing Is Just Recycled (2026)

Short answer: a reposted job is a listing that a company takes down and puts back up, or leaves running for months, so it reads as fresh when it is not. Unlike a ghost job, the role is usually real. The problem is that the req has been open long enough that your application lands in a pile that has already been sorted, ignored, or half-filled. Fresh-looking does not mean fresh, and the difference decides whether a human ever opens your resume.

We build software that watches how job listings behave over time, so we score staleness rather than guess at it. This post is the plain-language version of the signals we compute, so you can spot a recycled listing before you spend an hour on its form.

Reposted, ghost, and evergreen are three different problems

A reposted job is a real req that keeps getting re-listed. A ghost job has no hiring intent at all, which we cover separately in how to spot a ghost job. An evergreen posting is a role a large employer keeps permanently open to pool candidates, common in sales, support, and warehouse hiring. All three look like a normal listing on day one. The way to tell them apart is behavior over time, not the words in the post.

The signals we score, and how you can read them by hand

Our posting-intelligence system tracks a handful of behaviors for each listing. You do not need our system to use them. Each one is checkable from the public posting.

Freshness versus first-seen date. A posting can say Posted 2 days ago and still be months old, because many boards reset that stamp every time the listing is edited or re-syndicated. Find the role on the company's own careers page and on an aggregator, and compare. A large gap between the two dates is a recycled listing wearing a fresh timestamp.

Reposting cadence. If the same title at the same company disappears and reappears every few weeks, that is a treadmill. Sometimes it is genuine backfill. Often it is a req that is not being closed, which means low urgency and a long queue ahead of you.

Hiring velocity. How fast does this company actually move roles from open to filled? A team that closes reqs in three weeks and a team that lets them run for six months are different bets, even for the same job title. Public signals include how long the role has been searchable and whether older postings from the same team are still up.

Requisition age. The single most useful number, and the one most often hidden. The longer a specific req has been live, the more your application competes with everything submitted before it, and the more likely the shortlist already exists.

How to check a listing in two minutes

A fast manual pass that catches most recycled listings:

Find the role on the company's own careers page. The ATS-hosted posting (Greenhouse, Lever, Ashby, Workday and the rest) is more honest about age than a re-syndicated aggregator copy.

Compare the posted date across two sources. A mismatch between the careers page and the aggregator is the clearest tell that the timestamp was reset.

Search the exact title in quotes plus the company name. If you find the same role posted repeatedly over past months, you are looking at a treadmill.

Check whether near-identical reqs are open in parallel. Ten copies of the same role across cities is usually a pooling posting, not ten open seats.

Why companies leave the same req open for months

It helps to know the reasons, because they change how you should respond. Most recycled listings come from one of these, and none of them are visible in the post itself.

Backfill that never closes. The team keeps hiring for the same role as people leave, so the req stays open by design. These are worth applying to, because they are genuinely hiring, but the bar tends to be high and steady.

A budget that keeps stalling. The role is approved, then frozen, then approved again. The listing stays up through the freeze because taking it down and reposting is friction. Your application can sit untouched for weeks with nothing wrong on your end.

Candidate pooling. Large employers keep evergreen postings to build a bench for roles they expect to open. You are applying to a pipeline, not a seat, and the response timeline is measured in months.

Compliance and optics. Some roles are posted publicly for policy reasons even when an internal candidate is favored. The listing is real, the process is real, and the outcome was largely decided before you arrived.

Reposted does not always mean walk away

The signals are a filter, not a verdict. A backfill req that reposts every month is still a real job, and a company that hires steadily for a role you fit is a reasonable bet even if the listing is old. What the freshness read changes is your effort allocation, not a simple yes or no. Spend a full tailored application plus a direct outreach on a stale req you genuinely want. Skip the ten-minute form on a stale req you are lukewarm about, because a lukewarm application to a months-old listing is close to a guaranteed non-answer. The signal tells you how hard to push, not whether to exist.

Why a recycled listing quietly kills your response rate

Applying to stale reqs is one of the least visible reasons good applications get no reply. The role is real, so nothing feels wrong, but the shortlist may have been drawn weeks before you arrived. If you have been applying steadily and hearing nothing, the mix of what you are applying to matters as much as how you apply, which is the subject of why you get no response after applying. Freshness is a filter you can apply before you spend the effort, not after.

How fresh is fresh enough?

There is no universal cutoff, because hiring speed varies by team and role, but a few rules of thumb hold up. A req under two weeks old is a normal, live application with the shortlist still forming, and worth a standard tailored effort. A req in the one-to-two month range is a judgment call that depends on how much you want it and how fast that company tends to move. A req that has been continuously live for three months or more, or that you can find reposted repeatedly across the past half year, should never get more than a form-only application unless you pair it with direct outreach. The older the req, the more the form alone is a coin flip, and the more the human contact is what actually moves you forward.

What to do when a job is recycled but you still want it

A stale req is not always a dead end. If the role fits, applying is still cheap insurance, but change your approach. Do not rely on the form alone. Find the hiring manager or a team member and reach out directly, because a recycled req often means the inbound pile stopped being read. A short, specific note can put you in front of a human that the queue would not. Treat the application as the floor of your effort on that role, not the ceiling.

How AI Applyd uses these signals

We compute freshness, reposting cadence, hiring velocity, and requisition age so that stale listings can be flagged rather than blindly applied to. When our agent does apply, it tailors your resume and cover letter to the role, you approve every application before it sends, and it verifies the submission actually landed. The point is not to apply to more listings. It is to spend your applications on roles where a human is still reading. Results vary, and no signal is a guarantee that a given req is being actively worked. AI Applyd is free to start, no card.

FAQ

What is a reposted job? A listing a company takes down and re-lists, or leaves running for months, so it appears freshly posted when it is not. The role is usually real, but the requisition has been open long enough that your application may land after the shortlist is already set.

How can I tell if a job has been reposted? Compare the posted date on the company's own careers page against an aggregator copy, and search the exact title plus company name for older instances. A reset timestamp or the same role appearing repeatedly over past months both point to a recycled listing.

Is a reposted job the same as a ghost job? No. A reposted job is generally a real role that keeps getting re-listed, while a ghost job has no hiring intent at all. An evergreen posting is a third case, a role kept permanently open to pool candidates. They look identical on day one and only diverge in behavior over time.

Why do companies repost the same job over and over? Reasons include genuine backfill, a req that never gets formally closed, budget that keeps stalling, and deliberate candidate pooling. From the outside these look the same, which is why cadence and requisition age matter more than the wording of the post.

Should I still apply to a job that has been reposted for months? Sometimes. If the role fits, applying is cheap, but do not rely on the form alone. Reach out to the hiring manager or a team member directly, because a stale req often means the inbound pile stopped being read.