When is a job considered new?

A role is new the first time we see its employer requisition id. The same id coming back later is a repost, not a new job.

Where do listing dates come from?

We prefer the employer ATS first-published or created timestamp. Updated-at and relative text such as Posted 30+ Days Ago are not treated as a new post.

Do you scrape LinkedIn or Indeed?

No. We only use public employer career portals and official job APIs.

Methodology

How we source listings, preserve posting dates and keep repeat sightings out of the new feed.

1. Source

Each verified company maps to one public career system (for example Greenhouse, Lever, Ashby, Workday, or a first-party careers API). Apply links are employer job pages, not undocumented API URLs.

2. Identity

A job is keyed by (company, requisition id). That id comes from the employer ATS. Generic tokens that many jobs share are discarded so two roles are not collapsed into one.

3. First posted, not last touched

Career sites often sort by “last updated.” A recruiter saving the same requisition can make an old role look new. We prefer first-published / created timestamps. Relative Workday labels such as “Posted 30+ Days Ago” are converted using the job-page startDate when the employer provides it.

4. Seed vs new

The first time we ingest a company, older or undated requisitions are stored as seed inventory so they never flood the recent feed. After that, a previously unseen requisition can appear in the recent feed only when it has a reliable employer posting date within the selected window.

5. Software-engineering filter

We include software engineering, data science, AI, scientific computing, developer advocacy, architecture and technical leadership. Broad program, project and design titles need software or technical context. Product management, recruiting, unrelated hardware and nontechnical roles are outside our scope.

6. What Google (and you) should trust

We are a tracker, not the hiring company.
We retrieve employer descriptions where supported. The employer’s page is the source for current requirements and availability; some feeds provide incomplete details.
Expired roles are marked not live and are not advertised as open in structured data.
For search engines we assert validThrough 60 days after the employer's original posting date; postings older than that lose job-posting markup. Salary and street-level address fields appear only when the employer's feed provides them — we never invent them.
If we get a date wrong, tell us and we correct it backward—we never move an original posted date forward.