A job listing disappears from the careers page. Three weeks later, it's back. Same title, maybe a few sentence changes, often the same recruiter. You applied the first time and never heard back. Now you're wondering: is this worth a second application, or are you wasting your time?

The honest answer is "it depends" — but not in the unhelpful way. The pattern that produced the repost tells you what to expect, and the patterns are knowable.

Why jobs get reposted

Reposting isn't one thing. It's at least four different patterns, each with a different implied probability of getting hired. The biggest mistake candidates make is treating all reposts the same way — either "they must be desperate" or "this is a ghost job" — when the right read depends on what's actually happening behind the post.

The most common scenario is a pipeline refresh. An aging requisition has collected hundreds of resumes, most no longer relevant. The recruiter archives the batch and reposts to surface fresh candidates. The role is real. Hiring is active. You weren't necessarily rejected the first time — your application may simply have aged out of the active pool.

A failed loop is the second most common. An offer was extended and declined, or a finalist accepted elsewhere. The team needs to fill the role but is now operating from a more cautious position. They've learned what their candidates expect on salary, scope, or remote flexibility.

A ghost or evergreen post — same JD reposted every 30 days for six months — is closer to a pipeline-building exercise than active hiring. See the longer analysis in ghost-job-postings.

The fourth pattern is a scope rewrite: a repost with meaningful JD changes. Title nudges up or down a level, required years shifts, must-haves move to nice-to-haves. The team has updated its mental model of the role.

How to read which one you're looking at

Two variables do most of the work: how much time passed between the takedown and the repost, and how much the JD itself changed. Plot them, and the four categories above sort themselves into the four cells.

A quick repost with no JD changes usually means a failed search loop. A quick repost with a rewritten JD is one of the strongest signals on the job board — it means the team ran a process, learned something, and is actively retuning. A long gap with no changes is the evergreen pattern. A long gap with a rewrite is effectively a brand-new posting that happens to share a title with an older one.

What about reapplying to the same role?

Most candidates assume that if they applied once and didn't hear back, applying again is pointless. That's only true in the failed-loop and evergreen cases. In a pipeline refresh, the recruiter has effectively cleared the deck — your earlier application is no longer being compared against your current one. Reapplying with an updated resume is reasonable, especially if your background has changed materially or you can credibly tailor to a refreshed JD.

A useful step: run your current resume against the new JD with a job-compatibility check before reapplying. If your match score has moved meaningfully since the first attempt — because your resume is better tailored, or because the JD has changed — you're not sending the same application twice.

The pattern across industries

Repost rates aren't uniform. In engineering, the rate is high because failed searches are common — candidates have leverage and offers fall through. In finance and legal, repost rates skew toward genuine new openings — turnover is lower, but when a role opens, it opens again every cycle.

The corollary: a reposted engineering role is less meaningful than a reposted finance role, all else equal. The base rate matters when interpreting any one observation.

What this isn't

Three clarifications:

• It's not a reason to stop applying to reposts. Some of the highest-conversion applications come from reposts in the pipeline-refresh or scope-rewrite categories. Avoiding all reposts is over-correcting.
• It's not a signal you can read from one observation. "Reposted once" is weak signal. "Reposted four times across six months with no JD changes" is strong signal. Watch the pattern, not the event.
• It's not predictive of how the interview will go. Even reposts in the failed-loop category often hire — the team isn't broken, they just had bad luck. Read the JD, decide if you fit, and apply on the merits.

The shorter summary: when a job reappears, ask two questions before applying. How long did the gap last, and what changed in the JD? The answer points you to one of four scenarios, and three of the four are worth your time.