The boilr Agent is live Read now
Guides

The Re-Posted Job Signal: When a Client's Own Req Won't Die, It's Your Opening

A role that keeps getting refreshed past 30-45 days is not noise, it is proof that direct and internal hiring already failed. Here is how to read the job reposting signal and turn it into a faster-converting BD call than any fresh posting.

TB Team Boilr
· September 11, 2026 · 15 min read
Abstract dark liquid-metal waves looping back on themselves, representing a job requisition that keeps re-circulating instead of closing

TL;DR

A fresh job posting means a client has a need. A job posting that gets refreshed or re-posted for the third, fourth or fifth time past the 30-45 day mark means something more useful: their own process already tried and failed [1][6]. That is not a weaker signal than a brand-new listing, it is a stronger one, because it comes pre-qualified with proof of pain, a named role, and a client who is already primed to hear that outside help would move faster. Median non-executive time-to-fill sits at 39-44 days in 2026 [1][2], and an open requisition is flagged "at risk" once it passes roughly 1.5x a company's own target time-to-fill [6]. A role still live and re-circulating well past that line has crossed from "hiring" into "struggling to hire" in a way a first-day posting cannot prove. boilr.ai tracks posting age, edit history and repeat-repost velocity as part of its Signals engine, so a re-posted req reaches a consultant's task queue scored and timestamped, not buried in a job board search.

Why a Job That Won't Die Is a Different Signal Than a Fresh Posting

Every recruitment BD consultant is trained to watch job boards for new postings. Fewer are trained to watch what happens to a posting after it does not disappear. That second behaviour is where the real information lives.

  • A fresh posting proves intent. A company wants to hire. That is all it proves. It says nothing about whether their pipeline is working.
  • A re-posted, still-live req proves failure of the current approach. Whatever they were doing, internal sourcing, an ATS auto-apply funnel, an agency already on the account, was not enough to close it inside a normal cycle.
  • Reposting is not free or accidental past a point. A single auto-renewal from an ATS or job board on a 30-60 day cycle is routine housekeeping [4][5]. A role manually refreshed two, three or more times, with edited copy, a widened salary band or a dropped requirement, is a client actively trying to fix something that is not working.
  • It arrives with zero discovery cost. You already know the title, the seniority, the likely budget band and how long they have been stuck. A cold, fresh-posting call still has to establish all of that.

Every recruitment agency already half-knows this instinctively, "that role has been up forever" is a phrase every desk has said out loud. The gap is that almost nobody tracks it systematically as a scored, dated signal the way they track funding rounds or exec moves [7]. It sits in plain sight on LinkedIn, Indeed and the client's own careers page, and most agencies walk past it every day.

How Reposting Actually Works, Mechanically

Not every "still up" listing is the same kind of signal. Reading it correctly means understanding the plumbing behind it:

  • Free/organic postings: Many boards deactivate a listing after a fixed window (commonly 30 days) unless the employer manually republishes it [5].
  • Promoted/paid postings: These run in renewal cycles, typically 14-30 days, and a renewal at expiry counts as a repost even when nothing about the role has changed [5].
  • ATS auto-renewal: Some applicant tracking systems refresh a live req on a schedule (commonly 30-60 days) without any human action, purely to keep search visibility up [4].
  • Manual repost with edits: A human went back into the listing and changed something, title, salary, requirements, and pushed it live again. This is the strongest version of the signal.
  • The "Reposted" badge: On LinkedIn specifically, a manually refreshed listing is marked "Reposted X days ago" and the algorithm treats it as new content, boosting its search ranking again [5]. That badge, combined with an original post date weeks or months earlier, is one of the cleanest public tells of a stuck search.

The practical filter: an automated 30-day renewal on its own is weak signal. Two or more manual reposts, an edited description, or a role still open 45+ days after the first sighting is a real BD trigger.

What 30-45+ Days of Reposting Actually Proves

The claim only works because it is measurable against real benchmarks, not gut feel. Here is what the data says about what "still open" means at different points in the calendar:

  • 39 days: Median 2026 time-to-fill for non-executive roles [1]. A role past this line is already running longer than half of all comparable hires.
  • 44 days: The broader 2026 US average time-to-fill across roles, up from 33 days in 2021, a 33% increase over three years [2].
  • 45 days: Median time-to-fill for executive roles [1]. Past this for a senior mandate, the client's own search is running at or beyond typical duration with no result.
  • 1.5x target time-to-fill: The point most talent acquisition teams use internally to flag a requisition as "aging" and formally at risk, triggering a strategy review [6]. If a client's internal target is 30 days and the role is still live at 45+, it has already crossed their own escalation line, whether or not anyone told you that.
  • 60-90 days without progress: Widely used as the trigger point where a stalled posting should force a mandatory review of the hiring approach [3]. A req this old, still recirculating, is a role in genuine trouble.

One honest caveat: not every long-lived listing is a live signal. Roughly 1 in 7 postings show ghost-job characteristics (climbing to roughly 1 in 5 for senior and executive roles), where there may be no real, immediate intent to hire at all [3]. Reposting alone does not separate a stuck-but-real search from a ghost listing, which is exactly why it should never be the only qualifying signal, verify against company size, other concurrent postings and any other hiring activity before you invest outreach time.

Fresh-Posting Signal vs Re-Posted Job Signal

The two signals look similar on a job board and convert completely differently as a BD trigger:

Dimension Fresh Job Posting Re-Posted / Refreshed Req (30-45+ days)
What it proves Intent to hire, nothing else Intent to hire AND that the current approach has already failed
Agency competition Everyone sees it day one, one of 50 agencies calling in [7] Most agencies never look twice at an "old" listing, far fewer live competitors
Discovery needed on the call High, you are establishing the role exists and is a real need Low, role, seniority and struggle duration are already known
Client receptiveness Untested, may still believe direct/internal hiring will work Primed, they have already watched their own process not work for weeks
Best pitch angle "We heard you're hiring for X" "We noticed this role has been open since [date] and re-posted [n] times, want a second channel running alongside your own search?"
Typical outcome if ignored Role gets filled or dies quietly, no further signal Role keeps re-appearing on your radar every re-post, an escalating, self-refreshing trigger

The BD Playbook: Turning a Won't-Die Req Into a Warm Call

Six steps to go from "I noticed that role is still up" to a booked conversation:

  1. Confirm it is a real repost, not routine renewal. Check for edited copy, a changed salary band, a dropped requirement, or a second/third "Reposted X days ago" badge, not just a single 30-day auto-refresh [4][5].
  2. Establish the timeline. First-seen date, number of reposts, days elapsed. This becomes the evidence in your opening line, specific dates beat vague "I saw you're hiring".
  3. Cross-check for a ghost listing. Look for corroborating activity, other roles opening at the same company, headcount growth, a funding or expansion signal, before you spend outreach time [3].
  4. Identify who owns the pain. The hiring manager for the role, not just a generic talent acquisition inbox. A repeatedly reposted req usually means the hiring manager, not just HR, is frustrated.
  5. Lead with the observation, not a pitch. "I noticed the [Role] req has been live since [date] and re-posted [n] times" is a market-intelligence opener, not a cold sales line. It signals you are watching their business, not blasting a list.
  6. Offer a parallel-track, not a replacement. Position external help as running alongside their own search, not criticising it. "Would a second channel running in parallel help close this faster?" is a lower-friction ask than "let us take this over".

The 7 KPIs to Track for Reposted-Job Signal BD

Metric What It Tells You Target
Reposted signals detected weekly Volume of qualifying roles entering your pipeline 10-30, ICP-dependent
Days since first posting How stuck the role actually is >39 days (non-exec), >45 (exec) [1]
Repost count Strength of the failure signal 2+ manual reposts
Ghost-listing filter pass rate % of flagged reposts confirmed as real, active searches 80%+ after corroboration [3]
Time from detection to first contact How fast you act once flagged <24 hours
Response rate, reposted-signal outreach Conversion vs generic cold outreach Track and compare to fresh-posting baseline
Reposted-signal-to-mandate conversion The number that justifies the effort Track trend monthly

How boilr Detects and Scores the Reposted-Job Signal

Manually checking whether a listing has been reposted means revisiting the same job board pages over and over, remembering what a posting looked like weeks ago, and noticing small edits by eye. That does not scale past a handful of watched accounts. boilr automates the parts that require memory and monitoring, and keeps the parts that need judgement with the consultant:

  • Signals: Continuously monitors watched accounts' job postings, including posting age, repost events and edit history, alongside funding, exec-move and expansion signals, so a re-posted req is caught automatically instead of relying on a consultant remembering to check back.
  • ICP scoring: Filters reposted-job signals against your agency's defined ICP, so the queue surfaces roles that match your desk's specialism, not every stale listing on the internet.
  • Companies: Enriches the account behind the req, size, funding stage, other open roles, so a consultant can cross-check for ghost-listing risk before reaching out.
  • Candidates: Surfaces a relevant candidate pool for the role already in motion, so the opening conversation can come with a shortlist idea attached, not just an observation.
  • Company Brain: Remembers which reposted-signal accounts an agency has already engaged, and what worked, so the pattern survives consultant turnover instead of living in one person's head.
  • Tasks: Delivers a drafted outreach angle referencing the specific timeline (first-seen date, repost count) for the consultant to verify and send, human judgement stays on the actual message and the call.

Keep human, always:

  • Deciding whether a specific stuck req is worth pursuing given relationship history
  • The actual outreach call and relationship-building
  • Negotiating terms and closing the mandate
  • Judging tone when a client's own process has visibly struggled, this needs tact, not automation

5 Mistakes Recruiters Make With the Reposted-Job Signal

Mistake #1: Treating Any Old Listing as Qualified

Why it fails: A single auto-renewed posting on a routine 30-day cycle is not evidence of anything [4]. Pitching every "old" job you see wastes calls on roles that were never actually stuck.

Fix: Require at least one manual, edited repost or 45+ days without change before treating a listing as a qualified signal.

Mistake #2: Skipping the Ghost-Job Check

Why it fails: Roughly 1 in 7 postings, climbing to 1 in 5 for senior roles, show ghost-job characteristics with no real intent to hire [3]. Chasing one wastes a call and can damage credibility with the client.

Fix: Cross-check for corroborating signals, other open roles, headcount growth, funding, before committing outreach time to any single re-posted req.

Mistake #3: Leading With Criticism Instead of Intelligence

Why it fails: "Your job posting has been up forever and clearly isn't working" reads as an insult, not an insight, and puts the hiring manager on the defensive.

Fix: Lead with the observation as market intelligence, "we track hiring signals across [sector] and noticed this role", and offer help running alongside, not replacing, their existing effort.

Mistake #4: Waiting for the Client to Escalate First

Why it fails: By the time a client actively decides to bring in an agency, several competitors may already be in front of them, especially once the role is visibly stuck and other desks have noticed too.

Fix: Treat crossing the 1.5x target time-to-fill or 39-45 day median as your own internal trigger to reach out, do not wait for an inbound brief [1][6].

Mistake #5: Not Tracking the Signal Systematically

Why it fails: Relying on a consultant to notice "hey, that role's been up for ages" while scrolling a job board is inconsistent and does not scale beyond a handful of accounts a person happens to remember.

Fix: Track posting age and repost events as a scored signal across all watched accounts, the same way you would track a funding round or exec hire, so nothing depends on memory.

Build This Into Your BD Motion in 14 Days

Days Action
1-2 List your top 20-30 watched or target accounts and their currently open roles across LinkedIn, Indeed and their careers page
3-4 Note first-seen date for each posting; flag anything already past 30-39 days
5-7 Re-check the list every 2-3 days; log repost events and any edits (title, salary, requirements)
8-9 Cross-check flagged roles for ghost-job risk, other open roles, growth signals, funding activity
10-11 Draft your opening line template referencing first-seen date and repost count; personalise per account
12-13 Run outreach on your first 10 qualified reposted-signal accounts; track response rate
14 Review results against your fresh-posting outreach baseline; decide whether to automate the monitoring step

Want reposted-job signals scored and delivered to your desk automatically instead of hunting for them manually? Try boilr.ai free and see the reposted-signal queue fill itself.

Frequently Asked Questions

What is the "reposted job signal" in recruitment BD?

It is the practice of treating a job posting that has been manually refreshed, edited, or kept live well past a company's typical time-to-fill (39-45+ days) as a business development trigger. Unlike a fresh posting, which only proves a company wants to hire, a reposted, still-open req proves the client's current approach, internal, direct-hire, or an existing agency, has already struggled to close it, making it a warmer, more informed opening for outreach.

How is a reposted job different from a fresh job posting as a signal?

A fresh posting only confirms intent to hire and attracts the most competition, commonly cited as roughly one of 50 agencies calling in on a newly posted role [7]. A reposted req past 30-45 days confirms intent AND process failure, has far fewer agencies actively watching it, requires much less discovery on the call, and gives you a specific, verifiable timeline to open the conversation with.

How many days should a job be open before I treat it as a reposted signal?

Use industry time-to-fill benchmarks as your baseline: 39 days median for non-executive roles and 45 days for executive roles in 2026 [1]. Many talent acquisition teams internally flag a requisition as "at risk" once it passes roughly 1.5x their own target time-to-fill [6]. Combine the day count with at least one manual repost or an edited job description before treating it as a qualified signal, a single automated 30-day renewal on its own is not enough.

Could a reposted job just be a ghost job with no real hiring intent?

Yes, and this is the most important caveat. Roughly 1 in 7 postings show ghost-job characteristics, rising to roughly 1 in 5 for senior and executive roles [3]. Reposting alone does not distinguish a genuinely stuck search from a listing kept live with no real intent to hire. Always cross-check for corroborating activity, other open roles at the company, headcount growth, funding or expansion signals, before investing outreach time.

How do I open a call or email based on a reposted job signal without sounding critical?

Lead with the observation framed as market intelligence, not judgement: reference the specific first-seen date and repost count, then position your offer as a parallel channel rather than a replacement, for example asking whether a second search running alongside their own would help close the role faster. This avoids sounding like you are criticising their process while still demonstrating you are genuinely watching their hiring activity.

Does a single automated repost count as a strong signal?

Generally no. Many job boards and applicant tracking systems auto-renew a live listing on a routine 14-60 day cycle purely to maintain search visibility, with no human decision involved [4] [5]. The strongest version of the signal is a manual repost with an edited description, changed salary band, or dropped requirement, or two or more repost events on the same role.

What is the cost of an aging, unfilled requisition to my client?

Cost per hire for non-executive roles runs around $4,800 on average, rising to $10,000-$28,000 for specialist and senior roles once agency fees and vetting are included [6]. Every extra week a role stays open also compounds lost productivity and team strain, which is part of why a role that has crossed the 1.5x target time-to-fill threshold is a genuinely urgent, not just theoretical, opening for outside help [6].

How does boilr help with the reposted-job signal specifically?

boilr's Signals engine monitors watched accounts' job postings continuously, tracking posting age, repost events and edit history alongside other buying signals like funding rounds and executive moves. Reposted-job signals are scored against your agency's ICP and delivered to a consultant's task queue with a drafted outreach angle referencing the specific timeline, ready to verify and send, rather than requiring a consultant to manually revisit job board listings to notice the pattern themselves.

Sources

Information sourced from public industry reports and research publications as of September 2026.

  1. Noon.ai - Time-to-Hire Benchmarks 2026
  2. Pin - Recruitment Statistics 2026: 50 Data Points Recruiters Need
  3. Glider AI - Ghost Jobs in 2026: Why Companies Post Roles They Never Intend to Fill
  4. Resume Worded - Why the Job You Interviewed For Was Reposted: The Complete 2026 Guide
  5. LeadCRM - Does LinkedIn Automatically Repost Jobs?
  6. Manatal - Talent Acquisition Metrics: Formulas, Benchmarks, ROI
  7. boilr - Why Hiring Signals Outperform Cold Calling for Recruitment BD in 2026

Hire your AI sales employee today.

One employee per consultant that researches companies, sources candidates and drafts outreach, while you verify and send. Live in a day.