What changed at each company, as dated events_
New leaders, hiring surges, tech switches and companies opening new countries, each one an event with a date, the company and the people involved. Built for scoring models, triggers and research.
- New leaders by function and level, with the month they started
- Hiring surges and first roles in a new country
- Tools added and dropped, with where we saw them
- One event per row, joined to company and person
What is in the files
3 files, joined on the company domain. Pick one to see its fields and a sample record.
A person started a new role.
event_idStable idstartedMonth the new role startedseen_atWhen we detected itnameFull nametitleNew title as writtenfunctionNormalized functionlevelNormalized levellinkedin_urlPublic profileprevious_companyWhere they were before, if knowntypeNew company or promotioncompanyNested company record: domain, name, size, country, offering{
"event_id": "jc_51a90e",
"type": "new_company",
"started": "2026-09",
"seen_at": "2026-10-03",
"person": {
"name": "Dana Whitfield",
"title": "VP of Sales",
"function": "sales",
"level": "vp"
},
"previous_company": "routivo.de",
"company": { "domain": "shipvane.io", "employees": "51-200" }
}On your schedule, in your stack
Parquet, CSV or JSONL
Parquet for warehouses, CSV for everything else, JSONL for pipelines and language models.
Your bucket or a link
Files land in your S3 or GCS bucket, or arrive as a signed download link.
Daily event files
Full history file on request. Webhooks for the same events on Growth and Scale.
Pick a scope
Countries, segments, functions, or a list of domains.
Check a sample
A sample file for your scope, before you commit.
We set up delivery
Format, destination and schedule.
Files land
On schedule, with a manifest per drop.
Built so you do not have to clean it
Dated
Every event has the date it happened and the date we saw it, so you can measure lag.
Deduplicated
One move is one event, however many sources mention it.
Promotions marked
A new title at the same company is labelled, not mixed in with new hires.
Joined
Each event carries the company record and, for people, function and level.
Teams that build on this data
Scoring models
Events as features: new leader, surge, switch.
Sales tools
Trigger feeds inside your product.
Agencies
Signal-based campaigns for many clients at once.
Research
Leadership turnover and hiring by sector.
Not ready for bulk? Use it live
The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.
Plays on the same data
A new sales leader is hiring a team
A VP or Head of Sales started in the last 90 days and sales roles are open.
A past champion lands somewhere new
Someone who bought or used your product starts at a new company.
They just moved to a tool you plug into
The site or job ads started naming a new CRM or platform in the last 60 days.
Signals dataset: questions
How do you detect a job change?
From public profiles and company pages. We compare the current role with what we saw before and record the month the new role started.
Why is the start date a month, not a day?
Public profiles show months only. We keep the month and add the day we first saw the change.
Can I get only certain roles?
Yes: scope by function, level, country or company list.
Is this the same as the webhooks?
The same events. Webhooks push them one by one; the dataset delivers them as daily files with full history.
Other datasets
Jobs dataset
Every open role, read from company career systems, normalized and joined to the company.
View dataset →DatasetCompany and People dataset
41.5M companies read from their own sites, with normalized decision makers.
View dataset →AllCompare datasets
What is in each one, side by side.
All datasets →Get a sample of
the signals data
Tell us your scope and we send a sample file. Or query the same data over the API with 1,000 free records.