What is an MLflow run?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
A run is one execution of training or evaluation, with its own ID, parameters, metrics, tags, and stored files.
WHY — MLflow instead of guessing?
Why interviewers care about MLflow:
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:
- 1A run is one
execution of training or evaluation, with its own ID, parameters, metrics, tags, and stored files.
- 2Comparing runs is how
you pick a candidate without scrolling Slack screenshots.
- 3Nested runs can track
child steps like CV folds.
- 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
A run is one execution of training or evaluation, with its own ID, parameters, metrics, tags, and stored files. Comparing runs is how you pick a candidate without scrolling Slack screenshots.