Hiring Signal Monitor

Find evidence-backed hiring changes in your target accounts: new openings, confirmed removals, first observed functions and hiring surges.

Public Beta. Monitor a saved list of target accounts and review meaningful changes each day. No custom company-check or signal fee is configured during this Beta; normal Apify platform usage applies. Posting a job is evidence of hiring intent, not proof that someone was hired or that the company will buy your product.

Quick start

1. Run the default demo to inspect eight clearly labeled synthetic signals. It does not check real companies. Normal platform usage still applies.
2. Switch to monitor, supply companies and explicit Greenhouse, Lever or Ashby career URLs, and save a stable baselineKey.
3. The first live run establishes a baseline and returns zero change events. Read Run summary to see coverage and current matches.
4. Save the input as an Apify Task and schedule it daily in your chosen timezone. Reuse the same baseline key.
5. Read the run summary first, then the event Dataset. Use eventId to deduplicate downstream recovery deliveries.

{
  "mode": "monitor",
  "companies": [{"domain": "linear.app", "careerUrl": "https://jobs.ashbyhq.com/linear", "externalId": "crm-account-001"}],
  "baselineKey": "my-sales-targets",
  "rules": [{"id": "security", "includeTitles": ["security engineer", "head of security", "ciso"]}],
  "windowDays": 7,
  "minNewRoles": 3,
  "onlyActionable": true,
  "maxEvents": 20
}

Signals and limits

Signal	Meaning
NEW_ROLE	A posting ID appeared after the first baseline.
CLOSED_ROLE	A posting was absent in two complete checks at least 24 hours apart.
FIRST_FUNCTION_OBSERVED	A function appeared for the first time during this monitoring history.
HIRING_SURGE	At least the configured number of distinct new posting IDs appeared in a full observation window.

Coverage gaps over 36 hours and collection failures restart aggregate-signal warm-up. Rule or source changes rebase the comparison. Repeated unchanged runs emit no events. Surge alerts for the same rule are suppressed for seven days unless a later eligible window has fresh evidence.

Supported sources: public Greenhouse, Lever (including EU), and listed Ashby postings. Domain-only source discovery is best effort; ambiguous or unsupported sources require an explicit career URL. No LinkedIn, candidate data, contact enrichment or automated outreach.

maxEvents limits the preview, not the Dataset. Use limit/offset to read remaining rows. Quiet and seed runs have empty Datasets by design; the summary remains available in OUTPUT.

MCP

Connect the official server at https://mcp.apify.com?tools=matdavis/hiring-signal-monitor,get-actor-run,get-key-value-store-record,get-dataset-items. Authenticate with your own Apify account using the client's Apify connection. Never put tokens into prompts or example inputs.

After the Actor tool returns its run information, read the default key-value store's OUTPUT record with get-key-value-store-record. Read all signal rows with get-dataset-items using limit/offset. Empty Datasets are normal for baseline and quiet runs; the monitoring summary is still essential.

Example prompt: “Check this saved account watchlist for new security roles and seven-day hiring surges. Read the monitoring summary first. Return evidence and a suggested account-review action. Show at most 20 events.”

State, recovery and cost

Your named storage is isolated under your Apify account. Reuse the same baseline key. Overlapping runs of that key fail with BASELINE_BUSY. Set the run timeout to 600 seconds or less; unlimited runs are rejected. After an abrupt crash, the lock expires shortly after that run's deadline.

Results are saved before the baseline is advanced. After an interrupted run, retry with the same input and baseline key so pending work can finish. Use eventId to avoid creating duplicate downstream tasks when replaying results.

This Beta does not charge custom PPE events. billing.chargedUsd: 0 refers to custom event fees and does not mean compute, storage or transfer usage is free. Review the Pricing tab and your Apify limits before enabling a recurring schedule. Commercial pricing and paid recovery behavior are still being validated.

Pause monitoring by disabling its Schedule. Export or delete your named hsm-v1-* storage through Apify Storage when you no longer need the watchlist. Raw job descriptions are not stored; minimal snapshots and signal evidence are retained in your storage until deleted.

Beta status and feedback

The current release passed 36 automated tests, three same-day checks of 50 verified ATS boards, a 25-company cloud baseline/repeat check, and a real MCP call with result retrieval. These checks do not establish human signal accuracy, multi-day reliability or customer retention. A separate-account end-to-end test remains pending; account isolation follows Apify's Limited permissions model.

Start with 10–25 companies and review signals before acting. Slack/CRM integration requires your own n8n workflow and credentials; notifications are not enabled automatically. Report an unsupported board, incorrect signal or installation issue in this Actor's Issues tab. Include the source URL and what you expected, without credentials or private customer data.