Top 6 Traceability Interview Questions
Browse 6 real-world technical and behavioral interview questions about Traceability. 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.
What goes in a BRD versus an FRD versus a user story, and how do you decide which to produce?
A BRD explains the business objective and sponsor decision, an FRD describes required system behavior, and a user story is a small testable slice with acceptance criteria. Choose the artifact by audience, governance need and delivery granularity.
How do you plan and run UAT, and what happens if the business signs off something that does not meet the original need?
Plan UAT backwards from the business outcome rather than forwards from the specification, and have real users run real work on realistic data. If sign-off lands on the wrong thing, measure the gap against the original objective and raise it as a change with its own business case.
Six months into the build, your requirements documents no longer describe the system. What do you do about it?
Decide which documents deserve to be current before updating anything, because each one is read for a different decision and drift matters in only some of them. Retire what nobody reads, point people at the real record of truth, and cost the maintenance honestly rather than promising to keep everything in step.
Two stakeholders give you directly contradictory requirements. How do you resolve it?
Do not arbitrate between the stated requirements; trace each back to the business objective behind it, because most contradictions dissolve at that level, and escalate the genuine ones as a documented decision for a named owner rather than deciding yourself.