Top 4 Genealogy Interview Questions
Browse 4 real-world technical and behavioral interview questions about Genealogy. Review scenarios, edge cases, and architectural best practices.
Explain batch and serial genealogy, how it supports a recall, and what statistical process control gives you that a threshold alarm does not.
Genealogy is the recorded graph linking consumed lots, equipment and process settings to what was produced, and it makes a recall narrow instead of total. SPC monitors a process against its own variation, so it detects drift before anything breaches a specification limit. Use this traceability answer to show the decision, trade-off, and evidence rather than a memorised definition.
A customer returns three failed units built in different weeks. You have one shift to say what else is affected. How do you bound it?
Intersect the lineage of the three units to find what they share, then forward-trace from every shared factor you cannot yet exclude. Containment starts as the union of those populations, because narrowing later is cheap and widening later is the thing that destroys credibility.
The MES is unreachable for four hours and the line keeps producing. What happens to the production record, and how do you reconcile afterwards?
The line survives on cached work orders and locally queued events, so the difficulty is the merge, not the outage. Reconciliation has to be idempotent, ordered by source timestamp rather than arrival, and honest about units that passed a gate nobody could evaluate. It also connects degraded mode to the point an interviewer is testing.
A finished unit fails test, is stripped, gets a replacement component and passes on the second attempt. What has to happen to its genealogy record?
The record is an append-only history, so the replacement adds an install event and a removal event rather than editing the bill of material, and both test results survive. The part that comes out needs a traceable destination, because a component with no exit event is the hole a recall falls through.