Why the same job appears on five job boards

Short answer: it is one job. One requisition, one application form, one recruiter - copied outward by software. Somebody ticked a box in the company's applicant tracking system, the system pushed that post to every job board it has an integration with, and search engines and scrapers took whatever was left. Five listings is five front doors on one building.

That matters for two decisions you have to make in the next ten minutes: which door to walk through, and whether the duplicate you are looking at is evidence of a busy employer or evidence of nothing at all.

What you are actually looking at

Every copy of a job post has a lineage, and the lineage tells you how much to trust the copy. There is a record inside the employer's applicant tracking system - the requisition - and then there are the representations of it that got sent, crawled or copied outward. The further from the record, the more likely the copy is stale, trimmed, or still standing after the job closed.

Only the last row is ever a different job, and only sometimes. Everything above it is the same requisition wearing a different hat.

The checkbox that puts one job on thirteen sites

Here is the mechanism, from the vendor's own documentation. When a recruiter creates a job post in Greenhouse, there is a "publish to free job boards" section. Greenhouse lists thirteen free job board partners it will push to: Appcast, Arbeitnow, Blind, Indeed, Levels.fyi, LinkedIn, Monster, Nexxt, OfferUp, Ramped, Secret Tel Aviv, X, and ZipRecruiter. Greenhouse says it "can take up to 48 hours for new job posts to appear on all free job board sites" (help centre, updated 14 May 2025).

So take a Sales Development Representative role at a 300-person software company. One person spends four minutes writing the post, ticks the boxes, and inside those two days the job is on Indeed, LinkedIn, ZipRecruiter, Monster and Levels.fyi. Nobody at that company "posted to five boards". They posted once. The five is a side effect of a form.

This is worth internalising because the intuition it replaces is a bad one. Seeing a role everywhere feels like urgency - a company hiring hard, spending money, casting wide. It is not a signal of anything. It is the default setting.

The other half of the mechanism is what happens on the way back. Whichever of those thirteen sites you came in through, your application lands against the same job in the same system, and the board you came in through is recorded as a source on your candidate record - Greenhouse documents this for Indeed Apply, where candidates arrive with "a source of Indeed" - and nothing more than that. It does not open a second pipeline, it does not reach a different recruiter, and it does not change where you sit in the list. The board decides how you found the job. It does not decide anything after that.

Why one remote role shows up five times in five cities

Remote postings multiply differently, and this is the version that confuses people most.

Greenhouse lets an employer add up to seven searchable locations to a remote job post so that candidates searching by region can find it. Its documentation then says the quiet part plainly: "some third-party job boards may display those as separate job posts by location" (updated 15 May 2026).

That is why one remote Sales Development Representative opening becomes "SDR - Austin", "SDR - Denver", "SDR - Chicago", "SDR - Remote (US)" and "SDR - New York" in your saved search. Same requisition. Same form. Same recruiter reading the same pipeline. If you apply to three of them, you have not applied three times - you have created one candidate record and confused your own tracker.

The copies nobody at the company chose

Two more sources of duplicates, neither of which involves a recruiter deciding anything.

The first is Google. Greenhouse "adds metadata about job posts into the source code of job boards so Google web scrapers can parse our posts more easily" (updated 2 March 2026). Nobody submits a job to Google for Jobs; the markup sits in the page and Google collects it. The second is company structure: Greenhouse tells customers that "there is no limit to the total number of external job boards your organization can create" (updated 30 January 2026), which is common for groups that own several brands. A duplicated post on a second brand's board looks like a second job and is one job filed twice.

Then there are the sites nobody authorised at all - aggregators that re-list a posting they crawled somewhere else. A crawled copy has no live connection to the record it came from, which is the practical problem: when the employer edits the salary band, pauses the requisition or closes it, the copy does not know. It sits there, indexed and apparently current, until the crawler comes back.

Here is what the data does not show: no ATS vendor publishes how many of the copies a job seeker sees were pushed deliberately versus scraped, and there is no public count of duplicate listings anywhere. The distribution mechanics are documented. The scale of the resulting duplication is not.

Which of the five should you apply on?

Five listings, one requisition - what changes between them

The row that changes your outcome is the last one: an aggregator is the only listing where you cannot tell in advance whose form you will end up filling in.

	What the employer receives	How fresh the copy is
Company careers page	The employer's own form, every custom question	Live
ATS-hosted board (job-boards.greenhouse.io)	The same form, same questions	Live
Indeed, via Indeed Apply	A candidate record sourced to Indeed	Up to 48 hours behind
LinkedIn free listing	Depends where Apply lands - check the final URL	Up to 48 hours behind
Aggregator you have not heard of	Unknown - often a redirect chain	Unknown

Apply on the employer's own board, not on the aggregator, even when the aggregator's form is shorter. That is a position, so here is the argument. Indeed Apply genuinely works - Greenhouse states that candidates who use it "automatically sync to Greenhouse Recruiting with a source of Indeed," so the application does arrive, tagged and intact. Delivery is not the problem. The problem is that every copy except the employer's own is a snapshot: Greenhouse's Indeed page says "it can take up to 48 hours for new job posts or updates to appear on Indeed" (updated 15 May 2026), and the general free-posts page extends the same window to all thirteen partners. Apply to a two-day-old snapshot of a Sales Development Representative post and you may be answering a requirement the employer rewrote on Monday, or filling in a form for a requisition that was paused on Tuesday.

There is a second and stranger reason to treat the Indeed copy as the incomplete one. Greenhouse tells its customers that as of 1 April 2023, "Indeed no longer allows job post questions that seek personally identifiable information (PII) like full birthdates, driver's license numbers, or social security numbers from applicants," and that if a post contains one, "the job post will be removed from Indeed, and your Indeed account may experience restricted functionality" (updated 2 March 2026). Read that from your side of the form. A role that is missing from Indeed has not necessarily closed - it may have been pulled over a single custom question, while the requisition sits open and collecting applications on the company's own board. Absence from the largest board is not evidence of anything.

The LinkedIn row is the one people misread in the opposite direction. A free listing that hands you off to the employer's own application form has not cost you a step: you end up in exactly the form you would have reached from the careers page, and all LinkedIn did was help you find it. Which is why the useful habit is to follow the Apply button and watch where it lands, rather than ranking the five listings by whose logo is at the top of the page. The final URL, not the board you started on, tells you whose form you are about to fill in.

If you applied last month and the job is back

This is the case where duplicates genuinely matter, because two of the explanations point in opposite directions.

One: the requisition never closed and you are looking at a copy that was re-crawled, or at a second external board belonging to the same parent company. Nothing has changed and re-applying achieves nothing. Two: the employer closed the post, then opened a new one - a new record, a new ID, a fresh pipeline, and your old application sitting in the closed job where nobody will look at it again.

The requisition ID separates the two, which is why it is worth writing down when you apply rather than reconstructing later. Same ID, do not re-apply. New ID for the same Sales Development Representative role, apply again and treat it as a first application, because to the system it is one.

If the five listings show five different dates

Ignore the dates. Each board stamps its own when the feed arrives, and Greenhouse is explicit that "LinkedIn and Indeed limit organizations from refreshing or 'bumping' the job post through Greenhouse Recruiting" (updated 2 March 2026). An employer cannot make a stale post look new on those two sites even if they want to.

So a Sales Development Representative opening reading "Posted 3 days ago" on one board and "30+ days ago" on another is one requisition that reached the two boards at different moments, or was edited once. It is not two hiring rounds. And if you are sorting a saved search by recency to decide what to apply to first, you are ranking by an artefact of the feed rather than by anything the employer did.

If one of the five is not a real job

Some of them are not. Greenhouse warns its customers that Google removes posts for "collecting candidate applications for jobs where your organization is not actively hiring" - talent-community pages and evergreen "General Application" posts are the usual offenders - and adds that "Google will not send an alert to the customer" when that happens (updated 2 March 2026).

The tell for a job seeker is a listing that survives everywhere except the company's own board. If the Sales Development Representative post is live on three aggregators and returns a 404 on the employer's careers page, the requisition is closed and the copies have outlived it. Check the source before you spend twenty minutes on the form.

How many openings are actually out there

U.S. labour turnover, July 2026

7.3MJob openings, July 2026

4.4%Job openings rate

5.1MHires in the month

3.1MQuits in the month

The Bureau of Labor Statistics counted 7.3 million job openings in July 2026, a rate of 4.4 percent, with 5.1 million hires and 3.1 million quits in the same month. Note what that survey counts: an opening at an establishment, on the last business day of the month. It does not count advertisements. One opening can generate no public listing at all, or thirteen. There is no official statistic anywhere that tells you how many distinct job ads exist in the United States, which is precisely why duplicate-heavy search results feel like a bigger market than there is.

For the role in question, the closest occupation code is O*NET's 41-3091.00, Sales Representatives of Services, with a median wage of $69,990 a year (2025) and 123,000 projected annual openings over 2024–2034. O*NET does not list "Sales Development Representative" among its reported job titles for that code - a reminder that the title you search for and the title the statistics use are frequently not the same word.

How to tell whether two listings are one job

Four checks, about ninety seconds

1. 1
   Follow the Apply button

   Watch the final URL. Two listings that both land on job-boards.greenhouse.io/company/jobs/1234567 are one posting with one ID.

2. 2
   Compare the requisition ID

   Many posts carry an ID in the URL or the footer. Identical ID, identical job - regardless of how different the titles look.

3. 3
   Read the location line

   Same description, same team, different city, marked remote: this is one post with searchable locations, not several roles.

4. 4
   Open the employer's own careers page

   If the role is not there, the copies are outliving the requisition. Do not apply to the copy.

Those four checks resolve most duplicates. The one they will not resolve is a staffing agency listing, which is a different employer advertising someone else's role - that is a genuinely separate application, and the recruiter on the other end is not the hiring company's.

The one thing to get right

Apply once, on the employer's own board, and record the requisition ID rather than the board you found it on. Everything else in this post follows from that single habit: you stop double-applying to the same Sales Development Representative role in three cities, you stop reading a board's posting date as news, and you stop treating "it is everywhere" as a reason to hurry.

If tracking which of the five you already used is the part that keeps slipping, the platform fills in the employer's own form, answers the screening questions from your resume, and tracks every application in one dashboard.