Top 4 Auditability Interview Questions
Browse 4 real-world technical and behavioral interview questions about Auditability. Review scenarios, edge cases, and architectural best practices.
A customer disputes their total and asks why. Can your system answer?
Only if it recorded which rules fired, in what order, against which lines, at the moment of the order. Recomputing today gives a different answer because prices and campaigns have moved, so the price becomes unexplainable exactly when someone needs it explained.
Six months after a decision, a regulator asks how your model arrived at it. What must you have logged at the time?
The prediction record must name the model version, the exact feature vector as served with its values, the identifier of the code that computed those features, the decision and any thresholds or overrides applied. Reconstruction after the fact is not possible, because feature pipelines and reference data have moved on.
Your promotions engine lets two discounts stack when it should not. How do you fix it and stop it recurring?
Model eligibility, exclusivity, and priority as explicit promotion data rather than accumulated conditionals, pin a deterministic evaluation order because the same two discounts applied in a different sequence produce a different total, and persist a price trace finance can read months later.
Analysts want yesterday's numbers to still match after a late-arriving correction. What does the warehouse have to record?
Two time axes, not one: when the fact was true in the world, and when this warehouse first learned it. Corrections append a new version with a knowledge timestamp instead of updating in place, so a report becomes a query with an as-of predicate and reproduces for ever - and the figure you published should be snapshotted alongside it rather than reconstructed later.