Company Hiring Signals (Greenhouse, Lever, Ashby, Recruitee)

A company that's hiring is growing, has budget and is changing how it works: the best time to reach it. Give this actor a list of company websites and get back, for each one:

• Which job board it uses: Greenhouse, Lever, Ashby or Recruitee (the only boards supported)
• How many roles are open, and the newest posting date
• Hiring flags: sales, marketing, engineering, product/design, customer, operations/finance, people/HR, leadership
• Every role: title, department (not available from Greenhouse boards), location, link and posting date
• Top hiring locations

Ideas

• Sales teams: sell recruitment, onboarding, HR, or tools for the team that's growing ("hiring 5 SDRs" = buying sales tools).
• Agencies: companies hiring their first marketer often need outside help in the meantime.
• Recruiters: track open roles across your target accounts every week.
• Investors: watch headcount growth across a portfolio or market.

Tick Only return companies with open roles to get a clean list of hiring companies. You're only charged for rows returned.

How it finds the jobs

It reads the website you give and looks for a link to the company's job board. If there isn't one on that page, it opens up to 3 careers pages linked from it, but only where that site's robots.txt allows it. It then reads the board's public job feed, the same feed the company's own careers page uses. EU-hosted Lever boards are read from Lever's EU feed (api.eu.lever.co). EU-hosted Greenhouse boards (job-boards.eu.greenhouse.io/<board>) are served by the same Greenhouse Job Board API as every other Greenhouse board (boards-api.greenhouse.io); atsRegion shows eu when the link pointed to an EU board.

When the website hides the link, it can try the board named after the domain (e.g. stripe.com → Greenhouse board stripe). Those rows say so in matchedBy ("board named after the domain"), because a board with that name could belong to a different company: check them before relying on them.

Output fields

website, ats, atsBoard, atsRegion, openRoles, hiringFunctions, hiringSales, hiringMarketing, hiringEngineering, newestPostingAt, locations, roles (each with title, department (null for Greenhouse, where hiring flags come from the job title), location, url, postedAt, and for Greenhouse also updatedAt), careersPage, matchedBy, error.

postedAt is the date the job was first published (Greenhouse first_published, Lever createdAt, Ashby publishedAt, Recruitee published_at), as the board gives it. newestPostingAt is the latest of these, compared as real dates across time zones and returned in ISO 8601 UTC (for example 2026-10-01T14:00:00Z).

Data source and licence

Rows come only from public job feeds that each job board provides for public, automated use, plus the company websites you supply:

• Greenhouse Job Board API: https://developers.greenhouse.io/job-board.html (boards-api.greenhouse.io, which also serves EU-hosted boards)
• Lever Postings API: https://github.com/lever/postings-api (api.lever.co, api.eu.lever.co)
• Ashby public Job Posting API: https://developers.ashbyhq.com/docs/public-job-posting-api (api.ashbyhq.com)
• Recruitee Careers Site API: https://docs.recruitee.com/reference/intro-to-careers-site-api (<company>.recruitee.com/api/offers/)

The job listings belong to the companies that published them. The actor returns facts about open roles (title, team, location, link, date), not full job descriptions.

Responsible use

• The actor identifies itself honestly with the User-Agent Mozilla/5.0 (compatible; HiringSignalsBot/1.0; +https://apify.com/velveteen_driver/hiring-signals).
• It follows robots.txt for every page and feed beyond the website you give (including Crawl-delay, so api.lever.co gets at most 1 request a second), waits at least 1 second between requests to the same host, and backs off when a server says it's busy.
• It never logs in, never reads LinkedIn, Indeed, Glassdoor or other sites whose terms forbid automated access, and collects no personal data.
• Use the results lawfully, for example under UK GDPR and PECR when you contact businesses, and within Apify's terms.