Checking Greenhouse and Ashby careers pages by hand becomes busywork. An ATS job scraper can turn those public postings into a small hiring-signal watchlist. Begin with named employers and one question: which records differ between two snapshots of the same sample? Keep the scope explicit so the result is a research lead, not a claim about the employer's whole hiring plan.
Build a small, repeatable workflow
Collect a small sample from each selected board, save the export, and repeat with the same inputs. Match successful rows using jobUid and compare title and workplaceType. Label additions as first seen in this sample, then keep the source board beside each finding so you can verify it before acting.
Read the evidence, not just the label
Read title, department, locations and workplaceType together. A missing field means the source did not supply that value, not that it should be filled with a guess. Keep the posting link and collection time so a later observation can be compared without losing the basis for the original record.
Know the source boundary
A supported public board can still be disabled, empty or unreachable. Review errorCode and the run summary before comparing snapshots. Caps, filters and result ordering can also hide a row; absence from a sample is not proof that a role closed. These are observations, not a forecast of the employer's plans.
How to try it on Apify
- Open the Actor using the link below and review its current pricing.
- In the input editor, switch to JSON and paste the example. Replace the example target with your own and keep any sample limits in place.
- Confirm the available run-cost limits before starting. Inspect the result and any errors, then save the input alongside your export so you can repeat the same scope.
A small, explicit input
This is an illustrative, schema-checked input, not a report of a completed run. Replace the documented example target with one you are allowed to collect. Keep the scope small, inspect the first export, and adjust only after you understand which rows and fields the source supplies.
{ "boards": [ "greenhouse:airtable", "ashby:Linear" ], "maxJobsPerBoard": 10, "maxJobsTotal": 20 } Compare two hiring snapshots
Keep two full JSON array exports from runs with identical inputs: before.json and after.json. Save this optional example as compare.py beside them and run python compare.py. It uses only Python's standard library and makes no API calls. It compares title and workplaceType on successful job rows matched by jobUid. First seen means absent from the earlier sample, not newly posted. Missing rows are deliberately not labelled as closed roles: caps, filters, ordering or source failures can hide a posting.
import json from pathlib import Path def load_jobs(filename): rows = json.loads(Path(filename).read_text(encoding="utf-8")) if not isinstance(rows, list) or any(not isinstance(row, dict) for row in rows): raise ValueError("Use a full JSON array export") if any(row.get("ok") is False for row in rows): raise ValueError("Inspect source errors before comparing snapshots") return {row["jobUid"]: row for row in rows if row.get("ok") is True and isinstance(row.get("jobUid"), str) and row["jobUid"]} before = load_jobs("before.json") after = load_jobs("after.json") for job_uid, row in after.items(): if job_uid not in before: print("First seen in sample:", job_uid) elif any(row.get(field) != before[job_uid].get(field) for field in ("title", "workplaceType")): print("Changed in sample:", job_uid) Make the run cost explicit
This Actor has verified paid event pricing. Before starting, check the billing unit, any run-start charge and the run options on the Actor page. Keep the example caps and set a maximum run cost in Apify where supported. The pricing should be checked again before increasing the scope. Using the Apify API requires your own Apify API token; keep it out of public examples.
A useful next step is to save the input, inspect the source fields, and define what the workflow should do when a value is absent or a collection fails. Only then decide whether repeating the same scope on a schedule would answer a real question. We publish this Actor; this guide helps you judge whether it fits your task.
View the Actor, documentation and current pricing: https://apify.com/axiorasolutions/ats-job-scraper
This post was written with assistance from AI.
