Ashby
Ashby is the modern ATS choice for Series A–C startups in the AI and dev-tools space. career-ops hits the public job-board API directly.
What it does
The ashby provider in providers/ashby.mjs makes HTTP requests to api.ashbyhq.com/posting-api/job-board/{slug} and parses the resulting JSON. The slug is the company's Ashby job board identifier (e.g. 'elevenlabs' for ElevenLabs). career-ops picks this provider from the entry's careers_url (https://jobs.ashbyhq.com/<slug>), or from an explicit api: field.
When to use it
Use Ashby scanning when targeting AI labs, infrastructure companies, and modern startups. ElevenLabs, Deepgram, Sierra, Decagon and n8n are among the Ashby boards pre-configured in templates/portals.example.yml.
Example
- name: ElevenLabs
careers_url: https://jobs.ashbyhq.com/elevenlabs
enabled: trueThe next scan then picks up ElevenLabs' active roles.
What the scanner does
The scanner reads your enabled Ashby slugs from portals.yml, calls Ashby's public job-board API for each one, and merges the fresh roles into your pipeline with no browser, no login, and zero LLM tokens spent on the fetch itself. A single node scan.mjs run covers your Ashby, Greenhouse, and Lever boards together, then filters the results by the title keywords you configured.
node scan.mjsCompanies scanned: 12
Total jobs found: 41
Filtered by title: 35 removed
Duplicates: 3 skipped
New offers added: 3
New offers:
+ ElevenLabs | Applied AI Engineer | London, UK
+ Deepgram | Inference Engineer | Remote
+ Sierra | Agent Engineer | San Francisco, CAHow career-ops talks to Ashby
career-ops calls Ashby's public posting API at api.ashbyhq.com/posting-api/job-board/{slug}?includeCompensation=true and reads the jobs list straight from the JSON response. For each job it takes the title, the public jobUrl as the apply link, the location (the primary location plus any secondary ones, with "Remote" added for remote roles), the plain-text description, the publish date, and an annualized salary range when the board publishes one. Because this is a structured API call rather than page scraping, the scan needs no browser and spends no model tokens. Ashby's public API is slow to answer, with a floor of about ten seconds per board, and it rate-limits repeated requests, so career-ops waits up to 30 seconds per board and retries with backoff. Tokens are only spent later, during the evaluate step, when you decide a role is worth a closer look. Re-running the scan is safe: every URL is deduplicated against your scan history, your evaluated applications, and the current pipeline, so a role you have already seen is never added twice.
Gotchas
Ashby's job board API returns full JD text directly, no follow-up request needed. Each board takes around ten seconds to answer, so a scan with many Ashby boards takes a little longer than the same number of Greenhouse or Lever boards.
Some companies turn Ashby's posting API off while their board stays live: the API answers 404 even though the jobs are still published. For one of those, add ashby: { embed: true } to its entry, and career-ops reads the board from the page Ashby serves to embed it on careers sites instead. If the entry's careers_url is the company's own site rather than a jobs.ashbyhq.com address, also name the board with ashby: { board: <slug> }. On that source a posting comes without a description or a publish date, and its pay range stays as display text rather than a parsed salary. It is opt-in because a 404 usually means a closed board or a mistyped slug, which should stay an error.
- name: Example Co
careers_url: https://jobs.ashbyhq.com/exampleco
ashby: { embed: true }
enabled: true