Workforce Intelligence
Job Change Signals
Published Updated
Know when a contact starts a new job or gets promoted.
Detect when contacts join new companies. Each signal includes the new role, previous role and company, both job locations, event date, and founded-new-company detection across 4M+ monitored contacts, refreshed weekly.
- Contacts Monitored
- 4M+
- Detection Types
- New Role, Promotion, Founded
- Refresh Cadence
- Weekly
- Delivery
- REST API, GCS Push, Generate Insights API, Flat File
- Format
- JSONL or Parquet
- Bucket
- gs://autobound-work-milestones-v2/
What Are Job Change Signals?
3 subtypes
Job changes are one of the highest-intent signals in B2B sales: a contact moves to a new company and brings their technology preferences, vendor relationships, and buying authority with them. A VP of Sales who used your CRM at their last company will likely evaluate it at the new one within 90 days.
Autobound monitors LinkedIn profile changes across 4M+ contacts weekly, comparing current employment against historical snapshots. Each signal carries the new title and company, previous title and company, role descriptions, locations on both sides, the event date, months since the move, a founded-new-company flag, and a confidence score. New executives make roughly 70% of vendor evaluation decisions in their first 100 days, so detection within days of the move matters.
Example subtypes
Job changejobChange
Example from the signal catalog
Alex Rivera joined Ironwood Insurance as VP of Operations in March after five years at a competitor.
From a job change to your next move
What we detect, what you get, and what you do with it. Pick the path that fits your team.
Sales, marketing and RevOps: Slack, CRM fields and plays.
Sales, marketing and RevOps: Slack, CRM fields and plays.
0103
Contacts move to new companies
When a contact changes jobs, we record the new role, the old role and company, and when the move happened.
- Profile change
- We detectProfile change
- You getSignal record
- You actSlack, CRM or agent
Profile changeJul 14, 2026- Previous title
- Director of Enterprise Sales
- Previous company
- Brex
- New title
- VP of Sales
- Date
- May 15, 2026
ExtractedRampramp.comcompanyMarcus ChencontactJob changesignal_subtype0203
You get one clean record
Each record names the person, their title and company, labels the event, and links back to the source.
- Signal record
- We detectProfile change
- You getSignal record
- You actSlack, CRM or agent
Signal recordRamp
ramp.com
Marcus ChenVP of Sales
Job changejobChangeMarcus Chen joins Ramp as VP of Sales, from Brex
- From
- Brex
- Date
- May 15, 2026
- Detected
- Jul 14, 2026
signal_id 5c2f8e1a…
0303
Act on it where you work
Send it to Slack, write it to your CRM, or give it to an AI agent.
- When
- A champion's
previous_company_domainis a closed-won account - Do
- Congrats email plus an intro offer to the new team
- Your team acts
- We detectProfile change
- You getSignal record
- You actSlack, CRM or agent
or your own code#account-signalsSignal alert from your workflow
Marcus Chen, Ramp· Job change
Marcus Chen joins Ramp as VP of Sales, from Brex
Play: Congrats email plus an intro offer to the new team
Start the playOpen the sourceIllustration. The record fields are real.
0103
Contacts move to new companies
When a contact changes jobs, we record the new role, the old role and company, and when the move happened.
0203
It lands in your stack
Land weekly JSONL from your GCS bucket. Join on
contact.linkedin_url; update title and employer.0303
Ship it in your product
Offer a 'Changed jobs' filter and a record-update feed.
- Profile change
- We detectProfile change
- You getSignal record
- You actSlack, CRM or agent
- Previous title
- Director of Enterprise Sales
- Previous company
- Brex
- New title
- VP of Sales
- Date
- May 15, 2026
Step 1 of 3: Contacts move to new companies
Try it on your own accounts
1,000 free credits. Query workMilestone in the Signal API or from Claude.
How we build this signal
How we build each job change signal
We detect job changes from full work histories, with fixed rules and no language model.
- Max event age
- 6 months
- Language models used
- None
- 01
Source
Each month a large contact-data delivery with full work histories loads into our warehouse. For an extra contact list we also pull current public profiles, to cover people the delivery misses or has stale.
- 02
Role cleanup
Non-operational roles such as advisor, board member or investor are removed from each history first, so a new board seat does not read as a job change. An advisor title that also names a founder or CEO role is kept.
- 03
Change detection
Adjacent history entries are compared. A different company is a job change, and the record describes the company joined, not the one left. Fields we cannot resolve for the new company stay empty.
- 04
Freshness and sanity gates
Only events from the last 6 months ship. A pair with the same old and new title is dropped as a stale record, not a milestone.
- 05
Dedup and delivery
Each signal is keyed on the person's LinkedIn URL, the subtype, the event date and the company domain. A key that already shipped is not delivered again.
Job Change Signal Schema
Job change signals include complete transition context: new and previous job titles with descriptions, current and previous company details, job locations, event timing, and founded-new-company detection.
{
"signal_id": "5c2f8e1a-9b47-4d36-a2c8-7e91d4f0b263",
"signal_type": "workMilestone",
"signal_subtype": "jobChange",
"detected_at": "2026-07-14T13:22:44Z",
"association": "contact",
"contact": {
"name": "Marcus Chen",
"linkedin_url": "linkedin.com/in/marcus-chen-sf", // match on LinkedIn URL
"title": "VP of Sales"
},
"company": {
"name": "Ramp",
"domain": "ramp.com", // or match on domain
"linkedin_url": "linkedin.com/company/ramp"
},
"data": {
"event_date": "2026-05-15",
"months_since_event": 2,
"new_job_title": "VP of Sales",
"new_job_description": "Leads the North American sales organization at Ramp, overseeing mid-market and enterprise revenue teams.",
"previous_job_title": "Director of Enterprise Sales",
"previous_job_description": "Built and led the enterprise sales motion for corporate card and spend management at Brex.",
"company_name": "Ramp",
"company_domain": "ramp.com",
"previous_company_name": "Brex",
"previous_company_domain": "brex.com",
"new_job_location": "New York, New York, United States",
"previous_job_location": "San Francisco, California, United States",
"founded_new_company": false,
"work_anniversary_year": null, // always null for job changes
"confidence": 0.9
}
}Bulk data
Need this signal for 10,000+ companies?
Get a free sample file or a bulk feed (API, GCS push, flat file). The sample is real Work Milestones records, as a CSV.
Measured coverage
What's inside Job Change Signals
A dated snapshot counted in our production database, not a live count. Minimums, not ceilings.
Top subtypes
3 totalSeniority
full breakdown →Departments
full breakdown →Join keys
fill rateSee for yourself
Check out sample data: real Job Change records with the same fields the API returns.
“Autobound's triggers keep us current with news and job openings, making personalization effortless.”