Job Board Keyword Signal Scanner GTM Eng Finance Clay-Ready

🔑 What can Job Board Keyword Scanner do?

Give it a company domain and a role category and it tells you whether that company is hiring for those roles right now, across five ATS platforms. One flat row per domain.

Pick from twelve role categories, combine several at once, or pass your own keyword list.

📦 What you get	⚙️ Features and integrations
🎯 hiring_signal, one boolean to gate on 🗂️ Five role categories, or your own keywords 📊 roles_by_category and a signal_strength 🧾 23 flat fields, snake_case, one row per domain	🔍 Five ATS platforms: Greenhouse, Lever, Ashby, Workday, Rippling 🗄️ Pre-indexed fallback when the live cascade misses 🔄 Change detection across runs ⬇️ Export to JSON, CSV, Excel, HTML or XML

Bought by teams whose buying signal is a specific kind of hire: an engineering scale-up, a first CFO, an ops buildout, or a GTM ramp.

🚫 If you only need GTM roles, use GTM Hiring Signal Scraper instead. It is purpose-built for that one category and costs the same per row. This actor exists for everything else, and for combining categories in one call.

💡 Why use Job Board Keyword Scanner?

If you want	Read these fields
A hiring gate for any function	hiring_signal, signal_strength
How much they are hiring	matched_role_count, total_open_roles
Which function is growing	roles_by_category, department_with_most_openings, top_matched_role
Recency	most_recent_posting_date
What changed since last run	new_roles_detected, removed_roles_detected, roles_added_count, change_detected
Whether the data is live or indexed	fallback_used, fallback_source
Where to look	career_page_url, ats_platform, linkedin_company_url

🗂️ The twelve categories

Pass one or more in role_categories:

Category	Covers
GTM	VP Sales, AE, SDR, RevOps, Head of Growth, CMO, CRO
Engineering	VP Engineering, CTO, Software Engineer, Staff Engineer, Engineering Manager
Finance	CFO, VP Finance, Controller, FP&A, Financial Analyst
Operations	COO, VP Operations, Chief of Staff, Business Operations, Strategy and Operations
Executive	CEO, President, Co-Founder, MD, General Manager, VP and above
Marketing	CMO, VP Marketing, Demand Gen, Product Marketing, Brand, Content, SEO
HR	CHRO, Chief People Officer, People Ops, Talent Acquisition, HRBP, Recruiter
CustomerSuccess	Chief Customer Officer, VP CS, CSM, Account Manager, Renewals, Support
Data	Chief Data Officer, VP Data, Data Engineer, ML Engineer, Data Scientist, BI Analyst
Product	CPO, VP Product, Product Manager, Product Owner, Product Ops
Legal	General Counsel, Chief Legal Officer, Corporate Counsel, Compliance, Paralegal
Design	VP Design, Head of UX, Product Designer, UX Researcher, Brand Designer
Custom	Your own list, via custom_keywords

Category names are matched case insensitively and separators are ignored, so customer_success, Customer Success and customerSuccess all reach the same category. sales resolves to GTM, people to HR, analytics to Data.

That is a fix, not a convenience. Until 2026-08-22 the lookup was an exact, case sensitive property read and anything that missed was skipped in silence, so a run asking for marketing matched no roles at all and reported no hiring signal for every company. Seven of the twelve categories above are also new on that date. categories_unresolved on every row now names anything you sent that still matches nothing, so a typo is visible rather than silent.

🗄️ The pre-indexed fallback

When the live cascade finds no ATS match, the actor falls back to a pre-indexed database covering over 175,000 companies and 54 ATS platforms. enable_fallback defaults to true.

fallback_used and fallback_source tell you which path produced the row, which matters because indexed data can be a few days behind live scraping. Set enable_fallback to false for faster runs on large lists where you are confident about ATS coverage.

▶️ Ready-to-run examples

Example	What it does
Find Companies Hiring Software Engineers	Engineering scale-up signal
New CFO Hire Detector	Finance leadership signal
Partnerships and Channel Role Scanner	Channel buildout signal
GTM and Engineering Combined Scan	Two categories in one call
Weekly Hiring Change Tracker	Momentum over time

📋 What data can Job Board Keyword Scanner extract?

23 fields per domain.

Field	What it holds
hiring_signal	The boolean gate
matched_role_count, total_open_roles	Matches, and the whole board
matched_roles_detected, top_matched_role	Which roles matched
roles_by_category	Breakdown across the categories you searched
department_with_most_openings	Where the hiring is concentrated
signal_strength	Triage band
most_recent_posting_date	Freshness
categories_searched	What you asked for, echoed back
ats_platform, career_page_url	Which board answered, and where
company_name, linkedin_company_url	Company identity
new_roles_detected, removed_roles_detected, roles_added_count, change_detected	Delta since your last run
fallback_used, fallback_source	Whether the row came from live scraping or the index
previous_run_date, run_date	Run bookkeeping

⚠️ Custom keywords are all treated as Tier 2 signals. signal_strength weights the built-in category keywords more heavily than anything you supply yourself, so a custom-keyword run will read lower on strength than an equivalent GTM run. Use matched_role_count rather than signal_strength when you are running your own keyword list.

⚠️ false and null mean different things on every row. false is a measurement: the actor looked and the answer was no. null is the absence of one: the actor could not look. When something it needed fails, the row comes back with degraded: true, a plain-language degradation_reason, and every field it could not measure set to null rather than to a confident false or 0. Filter on degraded before you trust a negative.

🛠️ How to find companies hiring for a role category

1. Open the Input tab and put a bare domain in company_domain.
2. Set role_categories, one or several.
3. For anything the categories do not cover, add custom_keywords.
4. Click Start.
5. Filter on hiring_signal, then read roles_by_category to see where the hiring sits.

🧪 Using it in Clay

Add an Apify enrichment column and map your domain column to company_domain. Every field is a top-level key.

Combine categories in one call rather than running the actor twice. roles_by_category keeps them separable in the output.

⏱️ Tracking change over time

Pass previous_roles_detected and previous_run_date from your stored prior-run columns, and the actor returns new_roles_detected, removed_roles_detected and change_detected. Filter on roles_added_count to find companies that just opened positions.

💵 How much does it cost to scan a job board?

You are charged once per domain scanned.

Plan	Per domain	Per 1,000 domains
Free	$0.05	$50.00
Bronze	$0.0475	$47.50
Silver	$0.045	$45.00
Gold	$0.0425	$42.50

There is also an Actor start event at $0.00005, charged once per run per GB of memory.

💳 A domain that matches no ATS is still billed. The actor probed five platforms and, if enabled, the pre-indexed fallback as well, and a row saying so is a real answer. When the free-tier monthly cap is reached the run exits before any scraping or paid fallback call, with an upgrade message and no result row, so it never charges you for a run it did not do.

⌨️ Input

Everything is on the Input tab.

Field	Type	Default	What it does
company_domain	string	required	Bare company domain.
role_categories	array	["GTM"]	One or more of the twelve categories above, plus Custom. Case insensitive.
custom_keywords	array	none	Your own role keywords.
previous_roles_detected	string	none	Prior run's roles, unlocks change detection.
previous_run_date	string	none	Prior run's date.
enable_fallback	boolean	true	Use the pre-indexed database when the live cascade misses.

📤 Output

One flat row per domain, exportable as JSON, CSV, Excel, HTML or XML.

{
  "company_domain": "example.com",
  "company_name": "Example Inc",
  "linkedin_company_url": "https://www.linkedin.com/company/example",
  "hiring_signal": true,
  "ats_platform": "greenhouse",
  "matched_role_count": 5,
  "matched_roles_detected": ["Staff Engineer", "Engineering Manager"],
  "top_matched_role": "VP Engineering",
  "most_recent_posting_date": "2026-08-04",
  "department_with_most_openings": "Engineering",
  "total_open_roles": 18,
  "signal_strength": "high",
  "categories_searched": ["Engineering"],
  "roles_by_category": {"Engineering": 5},
  "career_page_url": "https://boards.greenhouse.io/example",
  "new_roles_detected": ["Staff Engineer"],
  "roles_added_count": 1,
  "change_detected": true,
  "fallback_used": false,
  "fallback_source": null,
  "run_date": "2026-06-18T16:18:12.670Z"
}

💡 Tips

• Combine categories in one call. It costs one row either way and roles_by_category keeps them apart in the output.
• Check fallback_used before treating a posting date as live. Indexed rows can lag by a few days.
• Set enable_fallback to false on large lists where you already know your targets use a supported ATS. It is measurably faster.
• Store matched_roles_detected and run_date each time. Change detection is free once you do.

⚠️ Known limits

Workday and Rippling detection relies on career page scraping, not a clean public API, so slug mismatches can cause false negatives on some Workday domains. Greenhouse, Lever and Ashby use public APIs and are more reliable.

Roles behind authenticated career portals are not visible.

The pre-indexed fallback can be a few days stale compared with live scraping. fallback_used tells you when a row came from it.

Custom keywords are all treated as Tier 2 signals, which lowers signal_strength relative to the built-in categories.

No proxy layer by default. Heavy batch runs against the same ATS domain may get rate limited. Say so on the Issues tab if it becomes a pattern.

A fallback failure is not a run failure. If the fallback sub-call errors or times out it is caught and logged, the run continues, and the row comes back with ats_platform: "none" and fallback_used: false.

❓ FAQ

How is this different from GTM Hiring Signal Scraper?

That one is scoped to GTM roles only and is purpose-built for it. This one lets you pick the category, covers five ATS platforms instead of three, and can combine categories in one call.

What happens when no ATS matches?

The pre-indexed fallback is tried when enable_fallback is true. If that also finds nothing, the row comes back with ats_platform: "none".

Can I use my own keywords?

Yes, via custom_keywords. Note they are weighted as Tier 2 in signal_strength.

Do I need to run it twice for two categories?

No. Pass both in role_categories and read roles_by_category in the output.

Does it need a proxy or an API key?

Neither.

🧩 Want other GTM data?

Mamba Labs builds custom actors for B2B go-to-market teams. The public versions of that work live here on the Store, so our users get the same tooling we build under contract.

🧑‍💼 GTM Hiring Signal Scraper	🧱 Tech Stack Detector
📡 B2B Buying Signals Aggregator	🔗 Domain to LinkedIn URL Resolver
🎯 ICP Fit Scorer	📋 Job Posting Monitor
📬 Domain Deliverability Checker	🏢 Company Firmographic Enricher
🌐 Company Social Presence Mapper	🪪 Company Identity Resolver
💰 Funding and Press Signal Scanner	🔄 Company Change-Event Feed
👤 People Finder and Email Verifier	🚀 Prospect Engine
🤖 AI Tooling Detector	📮 Outbound Stack Detector
📝 Publishing Frequency Tracker	✉️ Work Email Waterfall Finder
⏩ Sequencer Lead Push	🏅 Workplace Program Detector
👥 Team Page People Extractor	🧭 Company Discovery List Builder

Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything.

🛠️ Need something custom built for you or your team? Tell us what you are trying to find and we will build it. Talk to Mamba Labs.

🆘 Support

Found a bug or want a category extended? Open an issue on the Issues tab. Response time is typically within 48 hours.

ℹ️ Sourcing and legal. Roles come from the public job board APIs of Greenhouse, Lever and Ashby and from public career pages on Workday and Rippling, plus a pre-indexed job database when the live cascade finds nothing. No authenticated portal is accessed. The actor returns companies, role counts and role titles, not people. You are responsible for how you use the output.

Built by Mamba Labs.