openroles

Every open role, straight from the employer's own careers system. Greenhouse, Lever, Ashby and Workday, in one shape, from the same public JSON their own careers pages read. No API key, no account, no scraping service, and nothing but the Python standard library.

$ pip install openroles
$ openroles figma --query data --limit 3
2026-09-23  Data Engineer Intern (2027)      San Francisco, CA • New York, NY          https://boards.greenhouse.io/figma/jobs/6178851004?gh_jid=6178851004
2026-09-21  Data Platform Engineer           San Francisco, CA • New York, NY • Unite  https://boards.greenhouse.io/figma/jobs/6201407004?gh_jid=6201407004
2026-09-21  PhD Intern, Data Science (2027)  San Francisco, CA • New York, NY          https://boards.greenhouse.io/figma/jobs/6200626004?gh_jid=6200626004

3 open role(s)

Give it a company name, a careers page, a board URL or ats:token. It finds the board, reads every open role, and gives you the same fields whichever system the employer uses.

Why

Job sites miss roles, show them late, and repost them stale. The employer's own board is the source: it is complete, current, and carries the real apply link. Every major applicant tracking system publishes that board as JSON for its own careers page. openroles reads it the same way, politely, and puts the four biggest systems behind one function.

Related MCP server: io.github.groundtruthtools/ats-jobs-mcp

Install

pip install openroles          # or: uvx openroles <company>

Python 3.9 or newer. No dependencies.

Command line

openroles linear                                   # every open role at Linear
openroles https://jobs.ashbyhq.com/linear          # the same, from the board URL
openroles lever:zoox --query "data" --since 14     # title words, posted in the last 14 days
openroles figma --location "New York"              # filter by place (--remote for remote only)
openroles https://adobe.wd5.myworkdayjobs.com/external_experienced \
          --query "data scientist" --details       # Workday, with each posting's description
openroles detect "Figma"                           # which ATS, and the board's token
openroles linear --json > roles.json               # JSON (the default when piped), or --jsonl

Python

import openroles

openroles.detect("Figma")
# [Board(ats='greenhouse', token='figma'), Board(ats='ashby', token='figma')]

jobs = openroles.fetch("greenhouse:figma", query="data", location="New York")
for job in jobs:
    print(job.posted, job.title, job.location, job.url)

job.to_dict()   # plain JSON-ready dict

fetch() raises openroles.BoardError when a board cannot be read (a wrong token, no answer), and openroles.RobotsDisallowed when the host's robots.txt says no.

For AI agents (MCP)

openroles mcp is a Model Context Protocol server over stdio, so Claude, Cursor and other agents can look up any employer's open roles themselves. Two tools: find_job_board and list_open_roles (descriptions left out unless asked for, to keep answers short).

Claude Code:

claude mcp add openroles -- uvx openroles mcp

Claude Desktop, Cursor and other clients (mcpServers in their config):

{
  "mcpServers": {
    "openroles": { "command": "uvx", "args": ["openroles", "mcp"] }
  }
}

There is also llms.txt, a short brief for a model that has to use the library or the CLI.

What you get

Every role, from every system, has the same fields:

Supported systems

detect finds a board from a company name (Greenhouse, Lever and Ashby, by trying the names an employer is likely to use), from any board URL, and from a careers page that links to or embeds one. A Workday board cannot be guessed from a name: give its URL.

Not supported, because none publishes an open board this way: SuccessFactors, Oracle, iCIMS and custom careers sites. SmartRecruiters publishes one, but its robots.txt closes it to every crawler except LinkedIn's, so openroles does not read it.

Polite by design

• robots.txt is read first for Ashby, Workday and any careers page, and a refusal is honoured, never worked around. For Workday the careers site's own rules count too.

• At most two requests in flight per host, a timeout on every call, and an honest User-Agent naming this project.

• A Workday board that answers 429 or 503 is left alone for the rest of the run.

Is this allowed?

Greenhouse, Lever and Ashby document these endpoints as public job board APIs, for exactly this purpose: showing an employer's open roles somewhere else. Workday's is the endpoint its own careers pages call; it is not documented, it can change without notice, and openroles only reads it where robots.txt allows. Use it the way the boards are meant to be used: to find roles and apply to them, at a human pace. It is not a tool for hammering a site or republishing someone's board wholesale.

Where it came from

openroles is the employer-board reader from last-job-search, a job search that Claude runs end to end, extracted so anyone can use it.

Contributing

Contributions are welcome, and the most useful one is a reader for another ATS (Workable, Recruitee, Personio, Teamtailor and more are wanted). CONTRIBUTING.md has the set-up, the few rules that keep the library small and polite, and a checklist for adding a system. Bugs and requests go in Issues.

pip install -e . pytest ruff
pytest && ruff check .        # offline: every answer comes from tests/fixtures/

Licence

MIT. See LICENSE.