# A job change leaves two records for one person or keeps their old job

Any one-pick rule that ignores employment serves the employer a person left.

By Ki Moon · 2026-10-05 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/job-change-splits-one-person/

**Symptom:** A person who changed jobs appears twice, or their profile shows the title and company they left.

Two standard rules meet at a job change. Same-name dedup requires a shared account, so two different people with one name stay apart. A stable "one contact per person" pick keeps answers consistent.

A job change fails the shared-account test by definition. The person's new record shares no account with the old one, so dedup correctly refuses to join them and leaves two records for one person.

A stable pick that ignores employment serves the old job. The oldest record, or any fixed key, is deterministic and tends to land on the employer the person left.

Electing the newest contact by created date tends to land on the current employer. Created date is still only a proxy for employment, so check it against a dated source where you can.

In a synthetic test set of 200 people, 60 of them job changers, electing the oldest record pointed all 60 at the employer they left. Electing the newest pointed none there, because in the set every new-employer record is the newer one. The set shows the mechanism, not how common it is.

## Check your setup (read-only)

List the people with more than 1 CRM contact record. Take the 20 whose newest record was created most recently. Compare the account on the record your system picks with the account on their newest record. More than 2 of 20 where the pick points at the older employer means the pick rule ignores employment.

**Passes if:** 18 or more of 20 sampled people with several contact records resolve to the account on their newest record.

**Access needed:** crm-read

## If it fails (changes to make later, not part of the check)

1. Keep same-name dedup scoped to a shared account. Do not loosen the dedup scope to catch job changes.
2. When one person has several contact records, pick the newest by created date, not the oldest or a fixed key.
3. Track the share of picks that land on an account the person has left.
4. Join records across accounts only on a second signal beyond the name.

**Applies if:** A job marks contacts departed or dedupes people across sources by name, and it serves 1 record per person to reps or agents.

**Skip if:** Your contacts carry a person-level id from an identity source that survives job changes.

Tags: identity, crm, matching
