career-ops

Lever

Lever is the established ATS for mid-market and growth-stage companies. career-ops hits Lever's public postings API directly.

What it does

The lever provider in providers/lever.mjs makes HTTP requests to api.lever.co/v0/postings/{slug} and parses the JSON response. The slug is the company's Lever postings identifier (e.g. 'mistral' for Mistral AI).

When to use it

Use Lever scanning when your target companies post their roles on Lever. Mistral AI, Palantir and Spotify are among the Lever boards pre-configured in templates/portals.example.yml.

Example

portals.yml
- name: Mistral AI
  careers_url: https://jobs.lever.co/mistral
  enabled: true

The next scan then picks up active Mistral AI roles.

What the scanner does

The scanner reads your enabled Lever slugs from portals.yml, calls Lever's public postings API for each one, and merges new, title-matching roles into your pipeline with no browser session and zero LLM tokens spent on the fetch. The same node scan.mjs run also covers your Greenhouse and Ashby boards, then filters everything by your configured title keywords.

Terminal
node scan.mjs
Output
Companies scanned:     12
Total jobs found:      33
Filtered by title:     28 removed
Duplicates:            2 skipped
New offers added:      3

New offers:
  + Mistral AI | Applied AI Engineer | Paris, France
  + Palantir | Forward Deployed Engineer | London, UK
  + Spotify | ML Engineer, Search | Stockholm, Sweden

How career-ops talks to Lever

career-ops requests api.lever.co/v0/postings/{slug}, or the api.eu.lever.co host for EU boards, and reads the JSON array of postings. For each role it takes the text field as the title, the hostedUrl as the link, the location, the creation date, and the full description. Because Lever returns the whole board in one structured response, the scan is a single public HTTPS GET per company that stays inside rate limits and spends no model tokens. Token cost only begins later, when you evaluate a role you want to pursue. 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

Lever's API exposes the full JD in the postings response: the intro, every list section (such as requirements and responsibilities) and the closing text. The content filters in portals.yml (content_filter and visa_filter) read all of it, so a phrase that appears only in a Lever role's requirements list still matches.

On this page