An auditor asks you to reproduce a model from 11 months ago. What is your checklist?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
Code SHA, config, dataset snapshot, dependency lock, Docker digest, seed, and hardware notes from the tracking run.
WHY — Reproducibility instead of guessing?
Why interviewers care about Reproducibility:
who only read docs from people who shipped.
and tied to MLOps work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Code SHA, config, dataset
snapshot, dependency lock, Docker digest, seed, and hardware notes from the tracking run.
- 2Rebuild the image, pull
DVC data, and compare metrics within recorded tolerance.
- 3If any link is
missing, you say so and retrain a documented approximation rather than faking bitwise identity.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Code SHA, config, dataset snapshot, dependency lock, Docker digest, seed, and hardware notes from the tracking run. Rebuild the image, pull DVC data, and compare metrics within recorded tolerance.