Career Change Signal Engine

🔑 What can Career Change Signal Engine do?

Career Change Signal Engine reads the people on your watch list and returns only what changed since you last checked: who left, who landed where, who replaced them, and who started after a role closed. Every row says how the person was matched, which source answered, and how old that source is.

• Only changes. Send last run's reading per person (state_source: caller), or let the engine keep state between runs (state_source: actor). A person who has not changed returns no row.
• Your watch list, nothing else. The engine reads only the people you send. A run takes up to 150 people by default and 1,000 at most.
• Leavers and landings. No current role at the company you know: a leaver. A current role somewhere else: a move or a landing, with the new company, title, and start month when a source dates them.
• Replacements. For a leaver, the current holder of the departed title at the old company, ranked, for a person to confirm.
• New hires after a closed posting. Send Account Hiring Watch closed rows and get the people who started in that role.
• Replies and bounces as evidence. "No longer with", "has left Acme", and hard bounces count. Out of office replies do not.
• Ready to use. Segment (landed, replacement, new hire, past champion), a first line draft, and Slack card, HubSpot properties, HeyReach, and Instantly payloads on every row.
• No LinkedIn fetch. Readings come from data you already hold (a HeyReach stored copy, a Proofed LinkedIn reader row, or your own role list), web search, Prospeo, and an email verifier on your own keys, and the company's public team pages.

💡 Why use Career Change Signal Engine?

Champions who change jobs buy again, and the person who replaces a leaver inherits the budget. Most CRMs learn about a move months late. The engine checks the people you care about every two weeks and hands you the change with its evidence, so a person decides in seconds whether to reach out.

🛠️ How to watch contacts for job changes

1. Add the people you watch to people: name, company, title, and a LinkedIn profile URL when you have it.
2. Add your keys in providerKeys (optional): serper or serpapi, prospeo, bounceban, findymail.
3. Run it. Schedule it every 14 days with the same watch_list_id.
4. Read the signals in the dataset, or set webhook_url to receive them signed.

📋 What data does Career Change Signal Engine return?

Field	Example
signal_type	leaver_detected, landed, moved, replacement_proposed, new_hire
segment	landed, replacement, new_hire, past_champion, watching
person_name, profile_url, external_id	Jane Doe, https://www.linkedin.com/in/janedoe, your id
previous_company_name, previous_title, left_month	Acme, Head of Content, 2026-08
current_company_name, current_title, start_month, days_in_role	Contoso, VP Content, 2026-09, 40
leaver_confidence, identity_match, needs_confirmation	likely, profile_url, true
evidence	each signal with its source and source date
first_line_draft	a template line from row fields only
slack_card_json, hubspot_properties_json, heyreach_tags	delivery payloads
source, source_detail, source_date	byod, proofed_linkedin_reader, 2026-10-14

One run_summary row per run carries the counts and is never charged.

💵 How much does it cost?

Pay per event:

Event	Price	When
contact_checked	0.020 USD	once per watched person per run with a usable reading
signal_delivered	0.068 USD	once per change returned

BRONZE, SILVER, and GOLD plans pay 5, 10, and 15 percent less. Suppressed people, people not due, unreadable people, the run summary, and rows held for review cost nothing. max_spend_usd stops a run before it crosses your limit. Calls to your own providers bill your own accounts.

⌨️ Input

Field	Default	Notes
people	required	Your watch list
watch_list_id	default	Names the list and its state
state_source	actor	caller when you keep state and send last_reading
first_run_mode	report	baseline stores state and returns nothing on the first run
max_people_per_run	150	At most 1,000; a longer list fails before any charge
providerKeys	none	Secret; never logged or stored
replies, bounces, posting_changes	none	Optional evidence
suppression	none	Emails, profile URLs, opt outs, client domains
webhook_url, webhook_secret	none	Standard Webhooks signature

⚠️ Known limits

• A logged out profile view gives employment status and company, not titles or dates. Titles and start months come from a HeyReach stored copy, Prospeo, or your own data.
• A person with two open roles reads as still at the company you know.
• A leaver found only from a reply, with no reading, is likely and needs a person to confirm.
• Executive moves from the Company Change Event Feed are not in this version.

❓ FAQ

Does it scrape LinkedIn? No. It requests no linkedin.com page.

Which keys do I need? None for data you already hold. A search key and Prospeo add readings for people without one.

Can I keep state myself? Yes: state_source: caller and send each person's last_reading.

🆘 Support

Open an issue on the actor page.

ℹ️ Sourcing and legal. Readings come from data you supply, from providers you hold keys for, and from public company pages. The actor returns information about the people you send. You are responsible for a lawful basis to process it and for how you use the output.