ORIGINAL COMPANY-CONTEXT PRACTICE
Unify entity records while keeping uncertain links reversible
Original practice scenario: A hypothetical operational data platform combines supplier records from several systems. Names and addresses disagree, and incorrectly merging two suppliers would affect downstream work. Design entity resolution.
Written for independent practice using company context; this is not a verified question from a company interview.
A REASONED APPROACH
Model answer.
Keep source records immutable and make entity links versioned decisions with evidence. A unified identifier should not erase the distinctions needed to audit or reverse a mistaken merge.
Work through it
- Normalize selected comparison fields while preserving originals, using strong identifiers where available and marking weaker similarity-based candidate links as uncertain.
- Build an entity view from approved links, recording the matching method, confidence evidence and reviewer decisions without presenting a similarity score as certainty.
- Support splits and corrected links, tracking downstream dependencies so reports and operational actions can be re-evaluated under the new resolution version.
Tradeoffs to discuss
- Aggressive linking improves connected coverage but increases false merges; conservative linking leaves duplicates while protecting distinctions.
Common pitfalls
- Do not train and evaluate matching rules on the same reviewed candidate pairs.
- A shared address or parent organization may be a relationship rather than evidence of identical entity identity.