Dataset

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.

Signals datasetWhat you getBulk
  • 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
84knew leaders a quarter
10M+open roles watched
Monthlystart dates
Dailyevent files
01 — Schema

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
event_idStable id
startedMonth the new role started
seen_atWhen we detected it
Person
nameFull name
titleNew title as written
functionNormalized function
levelNormalized level
linkedin_urlPublic profile
Move
previous_companyWhere they were before, if known
typeNew company or promotion
Company
companyNested company record: domain, name, size, country, offering
Sample record · illustrative
{
  "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" }
}
02 — Delivery

On your schedule, in your stack

Formats

Parquet, CSV or JSONL

Parquet for warehouses, CSV for everything else, JSONL for pipelines and language models.

Destinations

Your bucket or a link

Files land in your S3 or GCS bucket, or arrive as a signed download link.

Refresh

Daily event files

Full history file on request. Webhooks for the same events on Growth and Scale.

01

Pick a scope

Countries, segments, functions, or a list of domains.

02

Check a sample

A sample file for your scope, before you commit.

03

We set up delivery

Format, destination and schedule.

04

Files land

On schedule, with a manifest per drop.

03 — Quality

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.

04 — Who uses it

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.

Job changes

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

Plays on the same data

05 — FAQ

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.

More datasets

Other 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.

  1. 01Sign up, no card
  2. 02Connect Claude, ChatGPT or an API key
  3. 03Ask for your market, 1,000 records free