Scrape SimplyHired Job Listings Without a Public API

What a SimplyHired Record Contains

A delivered row merges what the results card shows with what only the detail page carries. Native SimplyHired labels are kept, so the output maps back to what you see on screen.

• Job key - the base64 string taken from the /job/ path, used as the primary key in every run and every delta file.
• Job title, Company and Location (City, State), plus the Remote or Hybrid marker where a listing carries one.
• Company rating - the star figure printed next to the employer name, which SimplyHired draws from Indeed reviews.
• Salary - free text in mixed shapes such as "$70,000 - $146,000 a year" or "From $65,000 a year", alongside hourly rates. We parse minimum, maximum, period and currency, and flag the open-ended forms. A large share of listings show no pay at all, and that absence is recorded rather than guessed.
• Job Type - Full-time, Contract, Temporary, Part-time or Internship - together with Shift and schedule strings such as "8 hour shift".
• Date posted - cards show relative strings like "17h", "1d", "4d" or "13d", and many show nothing. We resolve these into absolute timestamps anchored to the capture moment and mark rows where the site supplied no date.
• Job Details, Qualifications and Benefits - the structured blocks that sit above the description body.
• Full Job Description - the complete employer text extracted in full, delivered as plain text or with the original markup preserved.
• Quick Apply or the outbound apply destination, including Indeed Apply targets and third-party recruiting systems.
• Sponsored - whether the placement was paid at the moment of capture.
• Crawl metadata - the source query, the location value, the page index and the exact URL each row came from.

What Only a Scheduled Crawl Reveals

A single export tells you what SimplyHired displayed on one afternoon. The signals worth paying for appear when the same searches are walked again on a schedule.

Freshness has to be measured rather than read. The only sitemap declared in robots.txt is the viewjob sitemap index, and its child sitemaps carry a location element and nothing else - no lastmod, no changefreq, no priority. Nothing in those files says when a listing appeared or last changed, so first-seen and last-seen dates exist only if someone crawled and compared.

Disappearance carries meaning. When a job key stops resolving, or drops out of the searches that used to return it, the role was filled, paused or expired. The span between first-seen and last-seen is the closest available proxy for time to fill, and it is only available to whoever was watching.

Reposts are the other half of the picture. Employers relist the same vacancy and SimplyHired issues a fresh key, so the URL alone will never tell you it is the same job. We match on employer, title, location and description body to link repost chains, and keep both the original key and the chain identifier so you can count either way.

Salary edits, changes of job type, and the rotation of Sponsored placements all show up as diffs between runs. Every delivery can carry the full snapshot plus a change file of new, updated and vanished keys.