Greenhouse
career-ops hits Greenhouse's public boards API directly. No HTML scraping, no rate-limit risk, no AI tokens consumed during the scan itself.
What it does
The greenhouse provider in providers/greenhouse.mjs makes HTTP requests to boards-api.greenhouse.io/v1/boards/{slug}/jobs and parses the JSON response into the career-ops listing format. The slug is the company's Greenhouse board identifier (e.g. 'anthropic' for Anthropic).
When to use it
Use Greenhouse scanning when your target companies use Greenhouse as their ATS. Most US tech companies in the 50–10,000-employee range do. templates/portals.example.yml ships with pre-configured Greenhouse boards you can enable.
Example
- name: Anthropic
careers_url: https://job-boards.greenhouse.io/anthropic
enabled: trueThe next scan then picks up all open Anthropic roles.
What the scanner does
The scanner reads your enabled Greenhouse slugs from portals.yml, calls the public boards API for each one, and adds new, title-matching roles to your pipeline with no scraping and zero LLM tokens spent on the fetch. A single node scan.mjs run handles your Greenhouse, Ashby, and Lever boards in one pass, then filters the results by your configured title keywords.
node scan.mjsCompanies scanned: 12
Total jobs found: 58
Filtered by title: 49 removed
Duplicates: 6 skipped
New offers added: 3
New offers:
+ Anthropic | Applied AI Engineer | San Francisco, CA
+ Intercom | AI Product Engineer | Dublin, Ireland
+ Vercel | Forward Deployed Engineer | RemoteHow career-ops talks to Greenhouse
career-ops requests boards-api.greenhouse.io/v1/boards/{slug}/jobs?content=true and reads the jobs array from the JSON, taking each role's title, its absolute_url, its location and its full description, which arrives in the same response, so there is no request per role. When a board gives a role's location only as a work model, such as Remote, career-ops makes one more request to the board's offices list to add the office names. The scan itself is a plain HTTPS GET against a public endpoint, which is why it stays inside rate limits and spends no model tokens. 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
Because every posting arrives with its full description, the content filters in portals.yml (content_filter, visa_filter and country eligibility) read the whole job text on Greenhouse boards, not just the title. A large board makes one large response rather than many small ones.
Related
Portals
Three of the applicant tracking systems career-ops scans, covered in depth: Greenhouse, Ashby and Lever. No AI tokens are consumed during the scan itself.
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.