How to Tell If a Job on Indeed Was Reposted Automatically vs. a Fresh Opening (2-Minute Check)

Step 1: Decode the requisition ID (30 seconds)

Most jobs run through an ATS — Greenhouse, Lever, Workday, iCIMS, or a similar system — before they appear on Indeed. Open the listing's "Apply" link and look at the URL on the employer's career page. You'll often see something like gh_jid=4021947005 (Greenhouse), lever/…-d4f2 (Lever), or an explicit req number in Workday links.

Worked example: You find "Senior Data Analyst" on Indeed marked "Posted Today." The apply link goes to a Greenhouse page with gh_jid=4021947005. Search the company's career page or Google for site:greenhouse.io [company name] 4021947005 — if cached results or earlier postings show the same ID from months ago, the req itself is old. Indeed just re-listed it. If the ID is new and appears nowhere else, that's a strong sign of a genuinely fresh opening.

One caveat: req ID conventions vary by ATS vendor and by employer — some companies increment req numbers per office, per batch of hires, or reuse formats — so treat this as a strong heuristic, not a guarantee.

Step 2: Cross-check the employer's own career page (30 seconds)

Go straight to the company's website — or the ATS-hosted page on greenhouse.io, lever.co, or the company's myworkdayjobs.com portal — and find the same role there. Compare:

• Posting date on the employer's page vs. Indeed's "Posted" label
• Number of openings (one req, many locations = one job syndicated many times)
• Whether the description is word-for-word identical (syndicated copy) or freshly written (often a new req)

If the employer's page says "Posted 6 weeks ago" and Indeed says "Posted Today," you have your answer: it was refreshed, not newly opened.

Step 3: Check the history with the Wayback Machine (60 seconds)

Paste the employer's job posting URL into web.archive.org. If snapshots of the same URL exist from weeks or months ago with the same content, the role has been open a long time — or the listing is being recycled. No archive history plus a brand-new req ID leans toward a fresh opening. As a bonus, Google's cached results and LinkedIn posts by the company's recruiters can reveal when the role was first announced.

What the result means for your application?

• Reposted / refreshed: Not necessarily bad. Reposts can mean the first candidate pool didn't pan out — sometimes good news for you. But it can also mean slow hiring, budget limbo, or an internal-favorite search. Tailor your application and temper expectations.
• Genuinely fresh: Apply within the first few days. Early applicants get disproportionately more recruiter attention.

Why job freshness matters more than job boards?

The bigger problem isn't decoding one Indeed listing — it's that by the time a role appears on a major board, hundreds of people have already seen it. The freshest leads often surface first in public communities: a hiring manager posting in r/forhire or r/hiring on Reddit, a founder announcing a role on X/Twitter before it hits any ATS, or a "we're hiring" message dropped in a niche Discord or Slack community.

Stale listings waste your application energy; fresh, less-crowded leads are where response rates live. That's exactly why we built Sidequestboard — it pulls fresh job and gig posts from public communities like Reddit, X/Twitter, and Discord into one calmer feed, so you spot real openings before they've been reposted five times. Try Sidequestboard free and spend your time applying, not archaeology.

Quick recap of the 2-minute check

1. Req ID: Same requisition number as an older posting = refreshed. Brand-new ID = likely fresh (conventions vary by ATS, so hedge accordingly).
2. Career page: Compare the employer's Greenhouse/Lever/Workday posting date against Indeed's label.
3. Wayback Machine: Archive snapshots of the same URL with old dates confirm the role isn't new.

Sources

• U.S. Department of Labor — Termination — Official federal employment reference; state law, contracts, and employer policies may differ.