" to any run, including one that worked: feature requests, a missing field or option, a wrong or empty result, or which actor you are switching to or from and why. The run returns its data exactly as it would without the note, and a human reads every note.
```
### What data can you extract from Lever job boards?
Every job row carries the same fields. Values an employer does not publish come back as `null` or an empty list, never invented.
- **The job:** title, Lever job id and a global id, job page and apply links, the employer's own work type label (for example Permanent) and a job type (`full_time`, `part_time`, `contract`, `temporary`, `internship`), Lever's level label where set, first posted time and days since.
- **Where:** main location and every listed location, the employer's country, every country code and country name read from the locations, workplace type (`remote`, `hybrid`, `onsite`) and a remote flag.
- **Pay:** lowest and highest amount, currency, period and the employer's own interval setting; every pay range the posting states (one per location zone, for example) with its label; the employer's pay paragraph word for word; yearly equivalents; and whether pay came from the employer's pay fields or the text.
- **The content:** the full posting as text and HTML, its opening, body and closing notes, every titled section with its items, and responsibilities, qualifications and benefits as lists.
- **Read from the posting:** seniority (intern to executive), minimum years of experience, visa sponsorship (offered, ruled out or not mentioned), description language and a 300-character summary.
- **The employer:** company name, logo and website from its job board, department and team.
- **Application form (optional):** the employer's own application questions with their type, answer options and whether they are required, which standard fields and profile links the form asks for, and any voluntary surveys.
- **Search context:** match score and where the keywords matched, other postings of the same job on the board, completeness score, readable notes on derived or missing data, and the input entry that found the job.
A real row from Zoox's job board, collected with application questions on:
```json
{
"id": "2a5ffe65-9b0a-4f0e-a2d4-d7875b5c6f24",
"globalId": "lever:zoox:2a5ffe65-9b0a-4f0e-a2d4-d7875b5c6f24",
"title": "Engineering Manager, Software Core Connectivity",
"company": "Zoox",
"companySlug": "zoox",
"atsPlatform": "lever",
"jobUrl": "https://jobs.lever.co/zoox/2a5ffe65-9b0a-4f0e-a2d4-d7875b5c6f24",
"applyUrl": "https://jobs.lever.co/zoox/2a5ffe65-9b0a-4f0e-a2d4-d7875b5c6f24/apply",
"boardUrl": "https://jobs.lever.co/zoox",
"boardRegion": "Global",
"department": "Software",
"team": "Software Systems",
"commitment": "Full-time",
"level": "All Levels",
"employmentType": "full_time",
"employmentTypeLabel": "Full-time",
"seniority": "manager",
"seniorityLabel": "Manager",
"workplaceType": "onsite",
"isRemote": false,
"location": "Foster City, CA",
"locations": [
"Foster City, CA"
],
"country": "US",
"countryName": "United States",
"countryCodes": [
"US"
],
"countryNames": [
"United States"
],
"salaryMin": 227000.0,
"salaryMax": 322000.0,
"salaryCurrency": "USD",
"salaryPeriod": "year",
"salaryText": "USD 227,000 - 322,000 per year",
"salarySource": "structured",
"salaryRanges": [
{
"min": 227000.0,
"max": 322000.0,
"currency": "USD",
"period": "year",
"label": "Posted pay range",
"text": "USD 227,000 - 322,000 per year"
}
],
"salaryDescription": "Base Salary Range\n\nThere are three major components to compensation for this position: salary, Amazon Restricted Stock Units (RSUs), and Zoox Stock Appreciation Rights. A sign-on bonus may be offered as part of the compensation package. The listed range applies only to the base salary. Compensation will vary based on geographic location and level. Leveling, as well as positioning within a level, is determined by a range of factors, including, but not limited to, a candidate's relevant years of experience, domain knowledge, and interview performance. The salary range listed in this posting is representative of the range of levels Zoox is considering for this position.\n\nZoox also offers a comprehensive package of benefits, including paid time off (e.g. sick leave, vacation, bereavement), unpaid time off, Zoox Stock Appreciation Rights, Amazon RSUs, health insurance, long-term care insurance, long-term and short-term disability insurance, and life insurance.",
"salaryInterval": "per-year-salary",
"salaryYearlyMin": 227000.0,
"salaryYearlyMax": 322000.0,
"yearsExperienceMin": 9,
"visaSponsorship": null,
"postedAt": "2026-09-21T23:01:41.624Z",
"postedDaysAgo": 43,
"language": "en",
"languageName": "English",
"descriptionSnippet": "Zoox is building the world's most advanced self-driving hardware and software solution, and nearly every part of it depends on moving data reliably. Sensor frames to perception, planner decisions to vehicle controls, telemetry to the cloud, and remote operator video back down again. All of it…",
"descriptionStatus": "included",
"descriptionText": "Zoox is building the world's most advanced self-driving hardware and software solution, and nearly every part of it depends on moving data reliably. Sensor frames to perception, planner decisions to vehicle controls, telemetry to the cloud, and remote operator video back down again. All of it crosses process, host, and network boundaries under hard latency and reliability budgets, on a vehicle that has to keep working when a link degrades or a network gets congested.\n\nThe Software Core Connectivity team owns that data path end to end: in-vehicle messaging (pub/sub, RPC, inter-process and inter-host transport), the vehicle's internal network, and vehicle-to-cloud connectivity. It also owns the transport and serialization abstractions the rest of the software organization builds on. Every one of those paths crosses a team boundary, so the work happens alongside firmware, product security, simulation, manufacturing, and IT, and those partners rely on this team for transport and networking depth to achieve their goals. As the team leader you will own the roadmap and the release commitments, and you will spend a real share of your time in those partnerships.\n\nIn this role, you will:\n\n•\nOwn the roadmap, staffing, and release commitments across the team's messaging, in-vehicle network, and cloud connectivity work.\n\n•\nLead and grow a team of software engineers, run their performance and promotion cycles, and hire into the gaps.\n\n•\nRepresent the team in cross-functional programs across firmware, product security, simulation, fleet operations, and infrastructure, and build the relationships that keep shared work moving.\n\n•\nSet the technical bar. Make the architecture calls stick, and make sure the abstractions the team ships are ones other teams want to build on.\n\n•\nBalance interrupt-driven reliability work against long-horizon architecture, and be explicit with partners about the tradeoff.\n\nQualifications\n\n• Bachelor's or Master's degree in computer science, electrical / computer engineering, or equivalent experience.\n\n• 9+ years of experience in software development, with 4+ years in a leadership role managing software engineers.\n\n• Strong grounding in at least one of: networked distributed systems, pub/sub and RPC middleware, vehicle or embedded networking, or transport protocols. Enough depth to hold your own in a design review without needing to run it.\n\n• Strong C++ programming experience with large code bases and technical dependencies.\n\n• A track record of driving work that spans organizational boundaries, where you did not control the people doing the work.\n\nBonus Qualifications\n\n• Robotics, automotive, aerospace, or another safety-relevant domain.\n\n• Hands-on experience with DDS, PTP and time synchronization, QUIC or multipath transport, or Ethernet switch configuration and diagnostics at fleet scale.\n\n• Experience building platform abstractions with internal customers, including the migration and adoption side.\n\nAbout Zoox\nZoox is developing the first ground-up, fully autonomous vehicle fleet and the supporting ecosystem required to bring this technology to market. Sitting at the intersection of robotics, machine learning, and design, Zoox aims to provide the next generation of mobility-as-a-service in urban environments. We’re looking for top talent that shares our passion and wants to be part of a fast-moving and highly execution-oriented team.\n\nFollow us on LinkedIn\n\nAccommodations\nIf you need an accommodation to participate in the application or interview process please reach out to accommodations@zoox.com or your assigned recruiter.\n\nA Final Note:\nYou do not need to match every listed expectation to apply for this position. Here at Zoox, we know that diverse perspectives foster the innovation we need to be successful, and we are committed to building a team that encompasses a variety of backgrounds, experiences, and skills.",
"descriptionHtml": "\n
Zoox is building the world's most advanced self-driving hardware and software solution, and nearly every part of it depends on moving data reliably. Sensor frames to perception, planner decisions to vehicle controls, telemetry to the cloud, and remote operator video back down again. All of it crosses process, host, and network boundaries under hard latency and reliability budgets, on a vehicle that has to keep working when a link degrades or a network gets congested.
\n
The Software Core Connectivity team owns that data path end to end: in-vehicle messaging (pub/sub, RPC, inter-process and inter-host transport), the vehicle's internal network, and vehicle-to-cloud connectivity. It also owns the transport and serialization abstractions the rest of the software organization builds on. Every one of those paths crosses a team boundary, so the work happens alongside firmware, product security, simulation, manufacturing, and IT, and those partners rely on this team for transport and networking depth to achieve their goals. As the team leader you will own the roadmap and the release commitments, and you will spend a real share of your time in those partnerships.
\n
In this role, you will:
\n- \n
Own the roadmap, staffing, and release commitments across the team's messaging, in-vehicle network, and cloud connectivity work.
\n \n- \n
Lead and grow a team of software engineers, run their performance and promotion cycles, and hire into the gaps.
\n \n- \n
Represent the team in cross-functional programs across firmware, product security, simulation, fleet operations, and infrastructure, and build the relationships that keep shared work moving.
\n \n- \n
Set the technical bar. Make the architecture calls stick, and make sure the abstractions the team ships are ones other teams want to build on.
\n \n- \n
Balance interrupt-driven reliability work against long-horizon architecture, and be explicit with partners about the tradeoff.
\n \n
\nQualifications
\n- Bachelor's or Master's degree in computer science, electrical / computer engineering, or equivalent experience.
\n- 9+ years of experience in software development, with 4+ years in a leadership role managing software engineers.
\n- Strong grounding in at least one of: networked distributed systems, pub/sub and RPC middleware, vehicle or embedded networking, or transport protocols. Enough depth to hold your own in a design review without needing to run it.
\n- Strong C++ programming experience with large code bases and technical dependencies.
\n- A track record of driving work that spans organizational boundaries, where you did not control the people doing the work.
\n
\nBonus Qualifications
\n- Robotics, automotive, aerospace, or another safety-relevant domain.
\n- Hands-on experience with DDS, PTP and time synchronization, QUIC or multipath transport, or Ethernet switch configuration and diagnostics at fleet scale.
\n- Experience building platform abstractions with internal customers, including the migration and adoption side.
\n
\nAbout Zoox
Zoox is developing the first ground-up, fully autonomous vehicle fleet and the supporting ecosystem required to bring this technology to market. Sitting at the intersection of robotics, machine learning, and design, Zoox aims to provide the next generation of mobility-as-a-service in urban environments. We’re looking for top talent that shares our passion and wants to be part of a fast-moving and highly execution-oriented team.
Accommodations
If you need an accommodation to participate in the application or interview process please reach out to accommodations@zoox.com or your assigned recruiter.
A Final Note:
You do not need to match every listed expectation to apply for this position. Here at Zoox, we know that diverse perspectives foster the innovation we need to be successful, and we are committed to building a team that encompasses a variety of backgrounds, experiences, and skills.
",
"openingText": null,
"descriptionBodyText": "Zoox is building the world's most advanced self-driving hardware and software solution, and nearly every part of it depends on moving data reliably. Sensor frames to perception, planner decisions to vehicle controls, telemetry to the cloud, and remote operator video back down again. All of it crosses process, host, and network boundaries under hard latency and reliability budgets, on a vehicle that has to keep working when a link degrades or a network gets congested.\n\nThe Software Core Connectivity team owns that data path end to end: in-vehicle messaging (pub/sub, RPC, inter-process and inter-host transport), the vehicle's internal network, and vehicle-to-cloud connectivity. It also owns the transport and serialization abstractions the rest of the software organization builds on. Every one of those paths crosses a team boundary, so the work happens alongside firmware, product security, simulation, manufacturing, and IT, and those partners rely on this team for transport and networking depth to achieve their goals. As the team leader you will own the roadmap and the release commitments, and you will spend a real share of your time in those partnerships.",
"closingText": "About Zoox\nZoox is developing the first ground-up, fully autonomous vehicle fleet and the supporting ecosystem required to bring this technology to market. Sitting at the intersection of robotics, machine learning, and design, Zoox aims to provide the next generation of mobility-as-a-service in urban environments. We’re looking for top talent that shares our passion and wants to be part of a fast-moving and highly execution-oriented team.\n\nFollow us on LinkedIn\n\nAccommodations\nIf you need an accommodation to participate in the application or interview process please reach out to accommodations@zoox.com or your assigned recruiter.\n\nA Final Note:\nYou do not need to match every listed expectation to apply for this position. Here at Zoox, we know that diverse perspectives foster the innovation we need to be successful, and we are committed to building a team that encompasses a variety of backgrounds, experiences, and skills.",
"sections": [
{
"heading": "In this role, you will:",
"kind": "responsibilities",
"items": [
"Own the roadmap, staffing, and release commitments across the team's messaging, in-vehicle network, and cloud connectivity work.",
"Lead and grow a team of software engineers, run their performance and promotion cycles, and hire into the gaps.",
"Represent the team in cross-functional programs across firmware, product security, simulation, fleet operations, and infrastructure, and build the relationships that keep shared work moving.",
"Set the technical bar. Make the architecture calls stick, and make sure the abstractions the team ships are ones other teams want to build on.",
"Balance interrupt-driven reliability work against long-horizon architecture, and be explicit with partners about the tradeoff."
]
},
{
"heading": "Qualifications",
"kind": "qualifications",
"items": [
"Bachelor's or Master's degree in computer science, electrical / computer engineering, or equivalent experience.",
"9+ years of experience in software development, with 4+ years in a leadership role managing software engineers.",
"Strong grounding in at least one of: networked distributed systems, pub/sub and RPC middleware, vehicle or embedded networking, or transport protocols. Enough depth to hold your own in a design review without needing to run it.",
"Strong C++ programming experience with large code bases and technical dependencies.",
"A track record of driving work that spans organizational boundaries, where you did not control the people doing the work."
]
},
{
"heading": "Bonus Qualifications",
"kind": "qualifications",
"items": [
"Robotics, automotive, aerospace, or another safety-relevant domain.",
"Hands-on experience with DDS, PTP and time synchronization, QUIC or multipath transport, or Ethernet switch configuration and diagnostics at fleet scale.",
"Experience building platform abstractions with internal customers, including the migration and adoption side."
]
}
],
"responsibilities": [
"Own the roadmap, staffing, and release commitments across the team's messaging, in-vehicle network, and cloud connectivity work.",
"Lead and grow a team of software engineers, run their performance and promotion cycles, and hire into the gaps.",
"Represent the team in cross-functional programs across firmware, product security, simulation, fleet operations, and infrastructure, and build the relationships that keep shared work moving.",
"Set the technical bar. Make the architecture calls stick, and make sure the abstractions the team ships are ones other teams want to build on.",
"Balance interrupt-driven reliability work against long-horizon architecture, and be explicit with partners about the tradeoff."
],
"qualifications": [
"Bachelor's or Master's degree in computer science, electrical / computer engineering, or equivalent experience.",
"9+ years of experience in software development, with 4+ years in a leadership role managing software engineers.",
"Strong grounding in at least one of: networked distributed systems, pub/sub and RPC middleware, vehicle or embedded networking, or transport protocols. Enough depth to hold your own in a design review without needing to run it.",
"Strong C++ programming experience with large code bases and technical dependencies.",
"A track record of driving work that spans organizational boundaries, where you did not control the people doing the work.",
"Robotics, automotive, aerospace, or another safety-relevant domain.",
"Hands-on experience with DDS, PTP and time synchronization, QUIC or multipath transport, or Ethernet switch configuration and diagnostics at fleet scale.",
"Experience building platform abstractions with internal customers, including the migration and adoption side."
],
"benefits": null,
"companyLogo": "https://lever-client-logos.s3.us-west-2.amazonaws.com/5f6f9bef-3957-46f7-b87d-c490e24027b1-1614218390018.png",
"companyWebsite": null,
"warnings": [],
"scrapedAt": "2026-11-04T11:13:24Z",
"searchInput": "https://jobs.lever.co/zoox",
"fieldCompleteness": 1.0,
"duplicateIds": null,
"applicationQuestions": [
{
"question": "What is your preferred first name and last name? If your legal first and last name is your preferred name, you do not need to respond.",
"type": "textarea",
"typeLabel": "Long text",
"required": false,
"section": "A few more questions..."
},
{
"question": "Export Control and Compliance: For the sole purpose of determining export licensing requirements, please list any countries of which you are a citizen or legal permanent resident, and when you obtained such status.",
"type": "textarea",
"typeLabel": "Long text",
"required": true,
"section": "A few more questions..."
},
{
"question": "Sponsorship: Do you require sponsorship, or will you require sponsorship in the future for employment authorization in the United States?",
"type": "dropdown",
"typeLabel": "Dropdown",
"required": true,
"options": [
"Yes",
"No"
],
"section": "A few more questions..."
},
{
"question": "How did you hear about us?",
"type": "multiple-select",
"typeLabel": "Multiple choice",
"required": true,
"options": [
"Zoox Ads / Social Media",
"LinkedIn",
"Event, Media Interview, or other PR",
"Recruiter Outreach",
"Employee Referral",
"CVPR Conference",
"SHPE Conference",
"Other"
],
"section": "A few more questions..."
},
{
"question": "If you attended an on-campus or virtual event, which did you attend?",
"type": "text",
"typeLabel": "Short text",
"required": false,
"section": "A few more questions..."
}
],
"applicationForm": {
"fields": [
{
"field": "resume",
"label": "Resume/CV",
"required": true
},
{
"field": "name",
"label": "Full name",
"required": true
},
{
"field": "pronouns",
"label": "Pronouns",
"required": false
},
{
"field": "email",
"label": "Email",
"required": true
},
{
"field": "phone",
"label": "Phone",
"required": true
},
{
"field": "location",
"label": "Current location",
"required": false
},
{
"field": "org",
"label": "Current company",
"required": false
}
],
"links": [
{
"name": "LinkedIn",
"label": "LinkedIn URL",
"required": false
},
{
"name": "Other",
"label": "Other website",
"required": false
}
],
"surveys": [],
"eeoQuestions": [
"Gender",
"Race or ethnicity",
"Veteran status"
],
"hasMarketingConsent": false
}
}
```
Search-only fields (`matchScore`, `matchedIn`) appear on keyword searches, and `changeType` on monitoring runs; closed-job notices carry `changeType: "closed"` and `closedDetectedAt`.
### How to scrape Lever jobs
Give the actor job board addresses, single job addresses or company names, or leave them empty to search every company in the directory. Everything else is optional.
| Parameter | Type | Default | Meaning |
|---|---|---|---|
| `startUrls` | list | none | Lever job boards (`https://jobs.lever.co/palantir`, `https://jobs.eu.lever.co/olx`) or single job addresses. A board you filtered on its own page keeps those filters. |
| `companies` | list | none | Employer names such as `Spotify` or `Palantir Technologies`, or board names such as `zoox`. |
| `maxItems` | number | every job | Stop the whole run after this many jobs. |
| `maxItemsPerCompany` | number | every job | At most this many jobs from each board. |
| `keywords` | list | none | Keep jobs with one of these words in the title. |
| `keywordMatch` | choice | `any` | `any` keyword, or `all` keywords. |
| `keywordScope` | choice | `title` | `title`, or `title_and_description`. |
| `excludeKeywords` | list | none | Drop jobs with one of these words in the title. |
| `locations` | list | all | Cities, regions or countries as written on the job, for example `London` or `Remote`. A capital two-letter code such as `US` matches that country. |
| `countries` | list | all | Two-letter country codes, for example `US`, `GB`, `DE`. |
| `workplaceTypes` | list | all | `remote`, `hybrid`, `onsite`. |
| `employmentTypes` | list | all | `full_time`, `part_time`, `contract`, `temporary`, `internship`. |
| `departments` | list | all | Words in the department or team, for example `Engineering`. |
| `seniority` | list | all | `intern`, `entry`, `mid`, `senior`, `lead`, `manager`, `director`, `executive`. |
| `postedWithinDays` | number | any age | Only jobs first posted in the last N days. |
| `postedAfter` | date | none | Only jobs first posted on or after this date. |
| `minSalary` | number | none | Minimum pay per year, in the job's own currency; hourly, daily, weekly and monthly pay is converted. |
| `salaryCurrency` | text | any | Only jobs paid in this currency, for example `USD`. |
| `includeDescription` | on/off | on | Full posting text, HTML and sections. Pay and the fields read from the posting are filled either way. |
| `includeApplicationForm` | on/off | off | Application questions and form fields. Takes longer; same price per job. |
| `onlyNewOrChanged` | on/off | off | Return only jobs that are new or changed since the last run with the same search. |
| `includeClosed` | on/off | off | With the option above: also report jobs that closed since the last run. |
| `stateKey` | text | one per search | Name for the memory of returned jobs, to keep several monitors apart. |
#### How filters work
Filters narrow together; several values of one filter widen, so `"countries": ["DE", "AT"]` returns jobs in either. Title keywords match word beginnings (`engineer` finds "Engineering Manager"); words of three letters or fewer, such as `AI` or `QA`, match whole words only. Seniority is read from the title, or from the employer's own level where it sets one. A filter that matches nothing on a board returns nothing from that board, never the whole board, and the run log says so.
#### One company, every job
```json
{
"startUrls": ["https://jobs.lever.co/palantir"]
}
```
#### Senior remote engineering jobs posted this week, every company
```json
{
"keywords": ["engineer"],
"seniority": ["senior", "lead"],
"workplaceTypes": ["remote"],
"postedWithinDays": 7,
"maxItemsPerCompany": 20
}
```
#### Look up employers by name, with pay
```json
{
"companies": ["Spotify", "Zoox", "Outreach"],
"minSalary": 120000,
"salaryCurrency": "USD"
}
```
### Search every company on Lever
Lever has no shared job search: every employer has its own board. This actor keeps a directory of 2,500+ public Lever job boards, global and EU, and reads them live in parallel when you leave `startUrls` and `companies` empty. A title keyword search across the whole directory typically finishes in a few minutes; filters that need the full posting, such as countries or posting date without a keyword, read more of each board and take longer.
The run's `OUTPUT` record lists, for every board you named and every board with matches, the jobs on the board, the jobs matching your search and the jobs saved, plus how the run ended (`stoppedBy`: every job collected, `maxItems`, your spending limit or the time limit). For boards you name, it also counts the matching jobs by department, team, country, location, workplace type, seniority and job type, with the remote and with-pay shares and how many were posted in the last 7 and 30 days.
A board that does not answer is tried once more after the others; if it still fails, the log says so and running again collects it.
### Only new or changed jobs on a schedule
Turn on `onlyNewOrChanged` and schedule the same input daily. The first run returns every match and remembers it; later runs return only jobs that are new (`changeType: "new"`) or whose posting changed (`"changed"`). With `includeClosed`, a job that disappeared is reported once as `"closed"`, at no job charge. Jobs already returned and unchanged are skipped and not charged. Use `stateKey` to keep several monitors apart.
### Integrations and scheduling
Run the Lever jobs scraper on an Apify schedule, daily for new jobs or weekly for hiring trends. Each finished run can call a webhook or feed n8n, Make, Zapier, Google Sheets or your own code through Apify's integrations and client libraries.
### Pricing
You pay per job saved to your dataset. The Free plan pays $1.99 per 1,000 jobs, Bronze $1.79, Silver $1.69, Gold and above $1.39.
Full postings, pay, application questions and closed-job notices are included in that price. Jobs skipped as unchanged in monitoring runs are not charged, and a run that finds nothing saves and charges no jobs.
A full Palantir board of 307 jobs costs about $0.61 in job charges on the Free plan.
### FAQ
**Can I search every company on Lever at once?** Yes. Leave `startUrls` and `companies` empty and the actor searches every board in its directory. Add keywords and filters to narrow it.
**What if a company is not in the directory?** Paste its `jobs.lever.co` or `jobs.eu.lever.co` address. Any public Lever board works, listed or not.
**How do I get only remote jobs?** Set `workplaceTypes` to `["remote"]`. It keeps jobs the employer marks remote, and unmarked jobs whose location says remote.
**Does it include salaries?** Yes, wherever the employer states pay: from the employer's pay fields, or read from the posting text when there are none (`salarySource` says which). Many US postings state pay; nothing is estimated.
**Do I need a Lever account, login or cookie?** No. The actor reads public job boards, the same pages any job seeker sees.
**Does it work with EU boards?** Yes. Addresses on `jobs.eu.lever.co` work like any other, and directory searches include them.
**Can I get the application questions?** Turn on `includeApplicationForm`. Each job then carries the employer's questions with their answer options and which fields are required.
**How current is the data?** Every run reads the boards live. Nothing is cached between runs.
**Why does a board show fewer jobs than its page?** It does not when you name the board: the actor returns every job the board lists. In directory searches, `maxItems` and `maxItemsPerCompany` stop the run early on purpose.
**Can I use it from an AI agent?** Yes, through Apify's MCP server or client libraries. The copy-to-AI block above gives an agent what it needs.
**Which other job sites do you cover?** See the Clearpath job scrapers above and below: Ashby, Workday, Indeed, LinkedIn, Google Jobs, Glassdoor and more.
### More Clearpath job scrapers
**Gulf and Middle East:** [GulfTalent](https://apify.com/clearpath/gulftalent-jobs-scraper).
**Global job search:** [Indeed](https://apify.com/clearpath/indeed-jobs-scraper) · [LinkedIn](https://apify.com/clearpath/linkedin-jobs-scraper) · [Google Jobs](https://apify.com/clearpath/google-jobs-scraper) · [Glassdoor](https://apify.com/clearpath/glassdoor-jobs-scraper) · [Workday](https://apify.com/clearpath/workday-jobs-scraper).
**Startups, remote and India:** [Wellfound](https://apify.com/clearpath/wellfound-api-ppe) · [Ashby](https://apify.com/clearpath/ashby-jobs-scraper) · [Lever](https://apify.com/clearpath/lever-jobs-scraper) · [Himalayas](https://apify.com/clearpath/himalayas-jobs-scraper) · [Cutshort](https://apify.com/clearpath/cutshort-jobs-scraper) · [Shine](https://apify.com/clearpath/shine-jobs-scraper).
**More job and company data:** [StepStone](https://apify.com/clearpath/stepstone-de-job-scraper) · [Totaljobs](https://apify.com/clearpath/totaljobs-uk-job-scraper) · [XING](https://apify.com/clearpath/xing-jobs-scraper) · [Welcome to the Jungle](https://apify.com/clearpath/welcome-to-the-jungle-jobs-api) · [Y Combinator](https://apify.com/clearpath/ycombinator-api-scraper).
### Support
Questions, problems or a field you need: open the **Issues** tab on this actor, or email **max@mapa.slmail.me**. Bug reports with the run id get answered fastest.
# Actor input Schema
## `startUrls` (type: `array`):
Lever job boards, one per line, for example https://jobs.lever.co/palantir or https://jobs.eu.lever.co/olx. A board you already filtered on its own page (team, location, department, work type) keeps those filters. A single job address returns that job.
## `companies` (type: `array`):
Employers to look up instead of pasting their board, for example Spotify, Palantir Technologies or a board name such as zoox. Leave this and the addresses empty to search every company in the directory.
## `maxItems` (type: `integer`):
Stop the whole run after this many jobs, across every board. Leave empty to get every matching job.
## `maxItemsPerCompany` (type: `integer`):
At most this many jobs from each board. Useful for a broad search that should cover many employers. Leave empty for no limit.
## `keywords` (type: `array`):
Keep jobs whose title contains one of these words, for example engineer or data scientist. Short words such as AI or QA match whole words only.
## `keywordMatch` (type: `string`):
Keep jobs matching any keyword, or only jobs matching every keyword.
## `keywordScope` (type: `string`):
Match keywords in the title only, or also in the full description. Title matches score higher in matchScore.
## `excludeKeywords` (type: `array`):
Drop jobs whose title contains one of these words, for example intern or sales.
## `locations` (type: `array`):
Keep jobs in one of these places: a city, region or country as written on the job, for example London, Germany or Remote. A two-letter capital code such as US matches that country.
## `countries` (type: `array`):
Two-letter country codes, for example US, GB or DE. Keeps jobs with at least one location in one of them.
## `workplaceTypes` (type: `array`):
Keep remote, hybrid or on-site jobs, as the employer marks them. Remote also keeps unmarked jobs whose location says remote.
## `employmentTypes` (type: `array`):
Keep jobs of these types. Read from the employer's own label (for example Permanent, Full Time or Intern).
## `departments` (type: `array`):
Keep jobs whose department or team contains one of these words, for example Engineering or Sales.
## `seniority` (type: `array`):
Keep jobs whose title states one of these levels. Titles without a level word ("Software Engineer") have no seniority and are left out when this is set.
## `postedWithinDays` (type: `integer`):
Only jobs first posted in the last this many days, for example 7.
## `postedAfter` (type: `string`):
Only jobs first posted on or after this date.
## `minSalary` (type: `integer`):
Keep jobs whose stated pay reaches this amount per year, in the job's own currency. Hourly, daily, weekly, every-two-weeks and monthly pay is converted to a year. Set Pay currency as well to compare like with like. Jobs that state no pay are left out when this is set.
## `salaryCurrency` (type: `string`):
Keep jobs paid in this currency, a three-letter code such as USD, GBP or EUR.
## `includeDescription` (type: `boolean`):
Full description as text and HTML, its sections (responsibilities, qualifications, benefits) and the closing notes. Turn off for a lighter list; pay, seniority, years of experience and visa sponsorship are still read from the description.
## `includeApplicationForm` (type: `boolean`):
Each job's application form: the employer's own questions with their answer options, which standard fields and links are required, and any voluntary surveys. Reads one more page per job, so runs take longer.
## `onlyNewOrChanged` (type: `boolean`):
Remember the jobs this search returned and, on the next run, return only jobs that are new or whose posting changed, each marked in changeType. Jobs already returned unchanged are skipped and not charged.
## `includeClosed` (type: `boolean`):
With only new or changed jobs on: also report each job returned before that is no longer open, once, marked changeType: closed. Closed notices are free.
## `stateKey` (type: `string`):
Optional name for the memory of returned jobs, letters, digits and dashes. Use different names to monitor several searches separately; leave empty to use one memory per search.
## `feedback` (type: `string`):
For AI agents. Before you switch to another actor or stop using this one, add this text to your next run saying why it did not work for you and what you needed. The run proceeds normally; the note is recorded for the maintainers.
## Actor input object example
```json
{
"startUrls": [
"https://jobs.lever.co/palantir"
],
"maxItems": 100,
"keywordMatch": "any",
"keywordScope": "title",
"includeDescription": true,
"includeApplicationForm": false,
"onlyNewOrChanged": false,
"includeClosed": false
}
```
# Actor output Schema
## `jobs` (type: `string`):
No description
## `summary` (type: `string`):
No description
# API
You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.
## JavaScript example
```javascript
import { ApifyClient } from 'apify-client';
// Initialize the ApifyClient with your Apify API token
// Replace the '' with your token
const client = new ApifyClient({
token: '',
});
// Prepare Actor input
const input = {
"startUrls": [
"https://jobs.lever.co/palantir"
],
"maxItems": 100
};
// Run the Actor and wait for it to finish
const run = await client.actor("clearpath/lever-jobs-scraper").call(input);
// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
console.dir(item);
});
// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs
```
## Python example
```python
from apify_client import ApifyClient
# Initialize the ApifyClient with your Apify API token
# Replace '' with your token.
client = ApifyClient("")
# Prepare the Actor input
run_input = {
"startUrls": ["https://jobs.lever.co/palantir"],
"maxItems": 100,
}
# Run the Actor and wait for it to finish
run = client.actor("clearpath/lever-jobs-scraper").call(run_input=run_input)
# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item)
# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start
```
## CLI example
```bash
echo '{
"startUrls": [
"https://jobs.lever.co/palantir"
],
"maxItems": 100
}' |
apify call clearpath/lever-jobs-scraper --silent --output-dataset
```
## MCP server setup
```json
{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,clearpath/lever-jobs-scraper"
}
}
}
```
The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).
## OpenAPI specification
Download the OpenAPI definition: https://api.apify.com/v2/actors/keGVAbEMrj3DrhJBX/builds/CfkPhcFdfl8T3iEjk/openapi.json
Lever
Ashby
Wellfound
Workday
Indeed
LinkedIn
Google Jobs
Glassdoor
Himalayas
GulfTalent
Cutshort