Why does experiment tracking matter, and what do you record?
Deployment and LLMOps · Intermediate 3
Short answer
Without tracking you cannot reproduce or compare results, and you forget which run produced the model in production. Record the code version, data version, parameters, metrics, the environment and the model artefact for every run, in a tool such as MLflow or Weights and Biases.
Deeper answer
Tracking turns 'I think the second run was better' into a table you can sort. It also answers audit questions later: which data trained this model, and who approved it.
Good habits: log automatically from the training script, tag runs with the question they answer, keep the evaluation set fixed so scores are comparable, and register the chosen model in a model registry with its run linked. For LLM work the same applies to prompts and model versions.
What a strong answer covers
- Reproducing and comparing results
- Records code and data versions
- Records parameters and metrics
- Stores the model artefact and environment
- Names a tool such as MLflow
Answer it out loud in the mock interview about 1 min
Follow-ups to expect
- How would you make a run fully reproducible?
- What is a model registry for?
Common mistakes
- Tracking metrics but not data or code versions
- Comparing runs evaluated on different data
Learn it
Experiment tracking and model registry
- When would you serve predictions in batch, and when online?
- How would you set up CI/CD for an LLM application?
- What is the difference between data parallelism and model parallelism?
- Your model scored well offline but performed badly after launch. What could explain it?
- Explain Kubernetes pods, deployments and services, and why you would use Kubernetes for AI apps.
- What is the KV cache, and why can it cause out-of-memory errors when serving an LLM?
- How would you load test an LLM feature and set a latency budget?
- Your model provider has an outage during peak hours. What should already be in place?
- How do you manage API keys and secrets across environments?
- How do you detect and handle model drift in production?
- A bank wants your AI system but says no data may leave its network. What are the options?
- Why does an LLM reply have a wait before the first word and then a different speed after it?
- What is quantisation, and what are the trade-offs?
- When would you use a semantic cache for an LLM app, and what can go wrong?
- How would you serve an LLM feature as an API for a web app?
- How would you serve a model that is too big for one GPU, and how would you scale it to more users?
- How would you add single sign-on to an enterprise AI assistant?
- How do you version prompts and models so you can roll back safely?
- What would you capture in traces for an LLM application?
- Why use Docker for an AI application?
- What does an LLM gateway do, and when do you need one?
- Why use vLLM to serve an open-weight model instead of a simple Hugging Face script?