Hiring Signals — Jobs to Sales Intelligence (AI)

Turn any company's public job board into buying-intent signals. Give it a list of companies (Greenhouse, Lever, or Ashby) and get back their open roles plus an AI read of what their hiring says: where they're growing, their likely tech stack, a buying-intent summary, a sales angle, and a personalized outreach opener.

Built-in AI. No OpenAI / OpenRouter API key required.

---

Why hiring is the best buying signal

What a company hires for tells you what it's about to spend on:

• Hiring a Head of RevOps / Sales Ops → investing in sales tooling & data.
• Hiring 5 backend engineers → scaling infrastructure, needs dev tools/cloud.
• Hiring Demand Gen / Content → ramping marketing spend.

Most job scrapers just dump raw listings. This actor reads the public, no-auth job-board APIs (no anti-bot pain) and adds the layer that matters: what it means for you.

	Raw job scrapers	Hiring Signals (AI)
Open roles, departments, locations	✅	✅
Reliable public APIs (no anti-bot)	⚠️	✅
Growth / momentum signal	❌	✅
Inferred tech stack	❌	✅
Buying-intent summary + sales angle	❌	✅
Personalized outreach opener	❌	✅
Works with no API key	—	✅

Pairs perfectly with AI Lead Enricher: find hiring signals here → enrich the company there.

---

Input

Field	Type	Description
companies	array (required)	Board URLs (https://boards.greenhouse.io/gitlab, https://jobs.ashbyhq.com/ramp, https://jobs.lever.co/plaid), provider:token (greenhouse:gitlab), or a bare token to auto-detect.
keywords	array	Keep only jobs whose title contains one of these words (e.g. sales, engineer). Empty = all.
locationFilter	string	Keep only jobs whose location contains this text (e.g. Remote, London).
maxJobsPerCompany	integer (1–200)	How many roles to read per company. Default 50.
aiSignals	boolean	Turn on built-in AI analysis. Default true.
offerDescription	string	What you sell — the AI ties each company's hiring to your offer and writes a personalized opener.
aiLanguage	string	Language for AI text. Default English.
proxyConfiguration	object	Optional. The job-board APIs are public and usually need no proxy.

Example input

{
  "companies": ["greenhouse:gitlab", "ashby:ramp", "https://jobs.lever.co/plaid"],
  "keywords": ["sales", "account executive", "revops"],
  "maxJobsPerCompany": 50,
  "offerDescription": "We sell a sales-engagement platform that automates outbound and books 2x more meetings.",
  "aiLanguage": "English"
}

---

Output

Two record types per company:

company_signal — one AI summary row per company:

{
  "recordType": "company_signal",
  "company": "GitLab",
  "provider": "greenhouse",
  "openRoles": 37,
  "departmentBreakdown": { "Sales": 12, "Engineering": 18, "Marketing": 7 },
  "growthSignal": "Strong commercial expansion — sales hiring outpaces engineering.",
  "topHiringAreas": ["Sales", "Engineering", "Marketing"],
  "techStack": ["Ruby on Rails", "Kubernetes", "PostgreSQL"],
  "hiringSignalSummary": "Heavy AE hiring across regions signals a push to scale outbound revenue.",
  "salesAngle": "Position around faster ramp time for new AEs and pipeline efficiency.",
  "personalizedOpener": "Noticed GitLab is hiring AEs across EMEA — as you scale outbound, teams usually...",
  "aiAnalyzed": true
}

job — one row per open role:

{
  "recordType": "job",
  "company": "GitLab",
  "title": "Account Executive - Italy",
  "department": "Sales",
  "location": "Remote, Italy",
  "remote": true,
  "seniority": "Mid",
  "category": "Sales",
  "url": "https://job-boards.greenhouse.io/gitlab/jobs/8503792002",
  "postedAt": "2026-04-17T05:58:03-04:00"
}

---

How it works

1. Parses each company entry → provider + token (or auto-detects Greenhouse → Ashby → Lever).
2. Reads the provider's public job-board API (no key, no anti-bot).
3. Filters by your keywords / location and computes a department breakdown.
4. Runs one AI call per company to derive growth signals, tech stack, buying-intent summary, sales angle and a personalized opener — and to classify each role's seniority/category.
5. Saves a company-level signal row plus one row per open role.

Companies with an invalid token or empty board are skipped (and logged).

---

Tips

• Monitor target accounts on a schedule to catch new roles (= fresh buying signals) as they appear.
• Add an offerDescription to get openers tailored to your product.
• Use keywords like revops, procurement, data to surface only the roles that signal demand for what you sell.

---

FAQ

Do I need an API key for the AI? No. The AI analysis runs on Apify's built-in model — there's no OpenAI / OpenRouter key to manage. Just toggle aiSignals on.

Which job boards are supported? Greenhouse, Lever, and Ashby — the three most common public, no-auth job-board APIs. Pass a board URL, a provider:token pair, or a bare token to auto-detect.

Will I get blocked or hit anti-bot walls? No. This reads the providers' public job-board APIs, not the rendered website, so there's no anti-bot pain and no proxy needed in most cases.

What if a company isn't on one of these three providers? It's skipped and logged. Most venture-backed and mid-market companies use one of the three, so coverage is high for B2B prospecting.

Can I turn the AI off? Yes. Set aiSignals to false to get just the structured roles + department breakdown with no AI cost.

---

Related Actors — build a full pipeline

This Actor is the "find the signal" step. Pair it with the others to go from intent → enriched contact → outreach:

• Find the signal → enrich the company: Run Hiring Signals (this Actor) to spot companies hiring for what you sell, then feed those companies into the AI Lead Enricher to pull their site profile, emails, socials and a personalized cold-email opener. Önce sinyal bul → sonra enrich et.
• Hiring Signals + AI Lead Enricher = a complete outbound list: who's in buying mode, why, and how to contact them.

Workflow: Hiring Signals (intent) → AI Lead Enricher (contact + opener) → your CRM / sequencer.