Talent moves

A worked example

A join requires a stored experience with the exact company name and a usable start month inside the selected window. The previous employer is shown only when a preceding experience identifies one. A role with only a year has no usable move month and is omitted.

How it works

1. Enter the company’s public name and choose a time window.
2. Review the newest reported moves first. Expand a row to inspect the experience timeline and follow its public LinkedIn URL.
3. Filter the loaded rows, copy a link to the inputs or download the sample as CSV.

Limits and interpretation

Employment is self-reported, not verified by the employer. Community and ambassador entries are labelled because they may not represent employment. Exact company-name matching reduces unrelated records but cannot resolve every employer identity or overlapping role.

Dates describe profile experience, not the date Metix independently observed a hire. Missing dates, delayed edits and incomplete profiles can make recent activity absent. The fetched timestamp tells you when this sample was retrieved, not when the employment was verified. No counts here estimate total hiring, attrition or headcount.

Five live runs per network per UTC day; cached samples can be reused for six hours without spending a run. Sorting puts the newest loaded move first but cannot make the upstream sample complete. No result is invented to fill an empty table.