Skip to content

100 Job Strategies · 5 of 100

Repost Archaeology

A job posted three times is a job someone is desperate to fill.

3 viewsLow effortPays off in 2-4 weeksExperienced candidatesAnyone screened out on years of experienceCareer switchers
Share

In short

When the same role is posted repeatedly over several months, the hiring pipeline has failed — candidates fell through, the offer was rejected, or the requirements were unrealistic. Those managers negotiate on requirements, move faster and screen more generously than they did the first time. Finding reposted roles takes minutes and changes which jobs are actually winnable.

The situation

Two jobs, same title, same city, both live today.

The first went up eleven days ago. It has 300 applicants and a manager who is still optimistic.

The second has been posted, expired and reposted three times since March. The manager has interviewed nine people, lost their preferred candidate to a counter-offer, and has been covering the work personally for five months.

Your resume is identical in both piles. Your odds are not remotely the same.

Why this works

A repost is a public record of a failed hiring process, and failed processes change how managers behave.

By the third posting, several things have shifted. The manager has learned their original requirements were unrealistic, because the market told them so. The team has been absorbing the missing person's work for months and is vocally tired. The budget is at risk of being reallocated if the seat stays empty. And the manager's own credibility is bound up in closing the role.

All of that makes them flexible in ways they were not in month one. The "8+ years required" that screened you out in March is negotiable in July. The interview loop that ran five rounds gets compressed. The response time drops from three weeks to three days.

There is also far less competition, for a slightly perverse reason: candidates who saw the role in March and did not apply assume it is stale or already filled, and candidates seeing it now cannot tell it has been up before. The signal is invisible unless you deliberately look for it.

How to run it

  1. 1

    Search the exact title in quotes

    Put the job title in quotation marks alongside the company name. Exact-match searching surfaces the same role across multiple postings instead of a hundred similar-sounding ones.

  2. 2

    Filter to older date ranges deliberately

    Set the date filter to earlier windows rather than the last week. You are looking for the same role appearing in several different months — which is the opposite of what job boards optimise for showing you.

  3. 3

    Check the company's own careers page history

    Some ATS pages keep a stable URL or job ID across reposts. A job ID that is months old on a listing marked "posted 2 days ago" is the clearest possible signal.

  4. 4

    Read the versions against each other

    Requirements usually soften between postings — years of experience drop, "required" becomes "preferred", a salary band appears. Those edits tell you exactly where the manager has already conceded.

  5. 5

    Apply, then contact the manager directly

    Apply through the system so you exist in the ATS, then reach the hiring manager separately. A reposted role means the normal funnel has already failed them once.

  6. 6

    Address the gap, not the job description

    Do not recite the posting back at them. Say what you would take off their plate in the first month. They have been short-staffed for a long time and relief is what they are buying.

What to say

Copy, then make it yours
Hi Alex, I've just applied for the Data Engineer role through your careers page. I noticed it's been open for a while, which usually means the work has been landing on someone's desk in the meantime. I've built and maintained pipelines on the exact stack in your listing, and I'm comfortable taking ownership of an existing messy one rather than needing a clean start — which I realise is often the real requirement. If it's useful, I'm happy to talk through how I'd approach the first month specifically. And if the shape of the role has shifted since it first went up, I'd rather hear the current version than the posted one. — Rohan

When it does not work

  • The ghost job. Some reposted roles are never filled on purpose — kept live to build a pipeline, satisfy a policy, or advertise growth. Repeated posting over a very long period with no movement is a warning as often as an opportunity.
  • There is a real reason nobody took it. Occasionally the role is genuinely unpleasant: an impossible manager, a doomed project, a broken team. Ask directly in interviews why the role has been open so long and listen carefully to the answer.
  • Salary that is simply too low. If the band is well below market, the repost is a pricing problem and no amount of positioning fixes it. Check whether the posted band moved between versions.
  • Assuming they will take anyone. Desperation makes managers flexible on requirements, not on competence. The bar for doing the job is unchanged.
  • Mentioning the reposts smugly. Referring to the failed search as evidence they should settle for you reads badly. Acknowledge the length of the search once, sympathetically, then move to what you would do.
The takeaway

The freshest job is the most contested. The job that keeps coming back is the one where a tired manager will actually negotiate.

Questions

How can I tell whether a job has been reposted?

Search the exact job title in quotation marks alongside the company name and deliberately widen the date range backwards, since job boards default to showing you only recent listings. Check the company's own careers page, where some applicant tracking systems keep a stable job ID or URL across reposts — an old ID on a listing labelled as posted this week is conclusive. Comparing the wording of two versions also helps: softened requirements are a strong signal that the same role has been re-advertised.

Is a repeatedly posted job a red flag rather than an opportunity?

It can be either, and the distinction matters. A role reposted two or three times over several months usually reflects a failed search, which favours you. A role posted continuously for a year with no apparent progress is more likely a ghost listing or a genuinely broken job. The way to tell them apart is to ask directly during the conversation why the search has taken so long, then judge whether the answer is specific and credible or evasive.

Should I mention that I noticed the role was reposted?

Lightly and sympathetically, once. Acknowledging that the role has been open a while lets you pivot naturally to offering relief, which is what the manager actually wants. What does not work is treating the failed search as leverage or implying they should lower their standards. The tone should be "that sounds like a long stretch of covering the work" rather than "clearly nobody else wanted this".

Does this work for entry-level roles?

Less often, because entry-level positions rarely fail to attract candidates and so rarely get reposted for lack of applicants. Where it does work is specialised junior roles with an unusual skill combination, or roles in locations with a thin local talent pool. For most early-career searches the higher-yield version of this strategy is watching for softened requirements on mid-level roles you were previously screened out of.

Find verified jobs from 100,000+ companies
Share

More from 100 Job Strategies

See all 25 in this series