Career Site Jobs Scraper

Career Site Jobs Scraper: open roles from a company careers page, no account needed

Paste a careers page, a bare domain, a job-board URL or just a company name. You get one row per open job, with the title, location, department, posted date, the apply link, and the salary where the board publishes one.

The catch to know before you buy: it reads ten applicant tracking systems. A company running on anything else comes back as an uncharged diagnostic row saying so, not as data.

🔎 What Career Site Jobs Scraper does

Most careers pages are a thin front end over an applicant tracking system, and those systems publish the open roles as plain JSON so the company page has something to draw. That feed is what this reads. Ten families are covered: Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, Personio, Teamtailor, Breezy HR and Workday.

The work it saves you is the detection. Knowing in advance that Figma hires through Greenhouse under the token figma and that Ramp uses Ashby is fine for three companies and hopeless for three hundred. Paste whatever you happen to have, and every row comes back stamped with the ats and the boardToken it resolved to, so your first run also builds that mapping for you.

You can narrow the rows too: words in the title or the location, the system, remote only, jobs that show a salary, or an employment type. Jobs a filter leaves out are not charged.

📥 What you give it

Every field is optional. Run it with the input empty and you get one labelled sample row so you can see the shape first.

{
  "companies": [
    "https://www.figma.com/careers",
    "https://jobs.ashbyhq.com/ramp",
    "notion.com",
    "Databricks"
  ],
  "maxItems": 100,
  "titleIncludes": ["engineer", "engineering"],
  "titleExcludes": ["intern"]
}

A board URL is the most reliable input, a domain is next, a bare name is loosest. Workday always needs a full URL, because its addresses carry a tenant and a site name nothing can guess.

Filters run on what each board sends, so a strict one can return fewer jobs than maxItems. On Lever, SmartRecruiters and Workday, which send boards in pages, a filtered run reads at most 1,000 jobs per company, or the company's share of maxItems if larger. A company no filter could pass, say a Greenhouse board when you ask for a salary, gets one free row saying it was skipped.

📤 What you get back

A real row, from run VwcL7Y48Jfl3CxOKL:

{
  "ok": true,
  "charged": true,
  "recordType": "job",
  "inputUrl": "https://www.figma.com/careers",
  "company": "figma",
  "ats": "greenhouse",
  "atsName": "Greenhouse",
  "boardToken": "figma",
  "title": "Distribution Partner Manager",
  "location": "San Francisco, CA • New York, NY • United States",
  "remote": null,
  "department": "Business Development",
  "employmentType": null,
  "postedAt": "2026-02-28T00:00:43.000Z",
  "applyUrl": "https://boards.greenhouse.io/figma/jobs/5813967004?gh_jid=5813967004",
  "jobUrl": "https://boards.greenhouse.io/figma/jobs/5813967004?gh_jid=5813967004",
  "jobId": "5813967004",
  "salary": null,
  "detectedVia": "token",
  "scrapedAt": "2026-09-21T01:23:09.209Z"
}

Three nulls on that row, and none of them are guesses: Greenhouse publishes no employment type, salary or remote flag in its listing feed.

🧾 Reading the output

Three kinds of row, and they are easy to separate.

Filter on recordType == "job" and you have your jobs. The charged field is written when the row is built, a moment before the charge goes out, so read it as "this is a real row" rather than as a receipt. If a charge ever fails, the run adds a CHARGE_ERROR diagnostic at the end saying so.

Each diagnostic carries the inputUrl it belongs to and an errorCode:

▶️ How to run it

1. Open Career Site Jobs Scraper and click Try for free. 2. Put your companies in Career page URLs or company names, one per line. 3. Set Maximum jobs. Keep it small on the first run. 4. Tick Include the full job description only if you need the job text. 5. Click Start, then download the dataset as JSON, CSV or Excel, or read it from the Apify API.

💰 How much does it cost?

$0.55 per 1,000 jobs. The same rate on every Apify plan, with no volume tiers.

One charge per job row written to your dataset. Duplicate postings inside a company and jobs your filters leave out are dropped before anything is billed, and neither the sample row nor any diagnostic row is charged. Working out which system a company uses is not billed either: you pay for jobs, not for lookups.

💡 What people use it for

• Watching a named list of companies and diffing on jobId to see what opened this week.
• Building an ATS map for a portfolio or a market, since every row names the system and the token.
• Pulling the full open board of a company before a sales or recruiting push.
• Checking how a role is actually titled across twenty companies before writing a job ad.

🚧 What it does not do

• Ten systems, not all of them. A company on any other software returns a diagnostic row, not

data.

• Filters read the board's own words. A remote job the board never flags, or pay written only

inside the job text, is left out by remoteOnly or hasSalary.

• A company only resolves if its board id can be derived from its domain or name, or is sitting

on its careers page, or you supplied the board URL yourself.

• Posted dates are not universal. Ashby carries them only with full details on, and Personio

never does.

• Department, employment type and salary depend on the board, and most boards never publish a

salary.

• Open roles only. No history, no closed-job archive.
• Job text is off by default and is flattened to plain text when you turn it on.
• A list that starts with dead entries gives up early and returns TIME_BUDGET rows for the

rest rather than grinding through all fifty. Board URLs avoid it entirely.

🧭 Which jobs scraper do you need?

❓ Questions people ask

What exactly do I paste in? Whatever you have. figma.com, https://www.figma.com/careers or just Figma all reach the same board, and the more specific the input, the fewer lookups.

Why did I get fewer jobs than I asked for? Because the budget is split evenly between companies and some boards are small, because a company returned nothing, or because your filters left most of a board out. Either way you are billed for the rows you got.

Will one broken company kill the run? No. It becomes an uncharged diagnostic row and the run carries on through the rest of your list.

Is scraping job boards legal? These are public feeds companies publish so their own careers pages can render. Apify's write-up on scraping and the law is a fair starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the run ID and the exact entry from companies that misbehaved. The diagnostic row's errorCode and inputUrl usually explain it on their own.