How would you set up CI/CD for an LLM application?
Deployment and LLMOps · Pro 1
Short answer
On every pull request run the normal checks (lint, types, unit tests) plus an eval suite: a regression set of prompts with code checks and judge-based scores, compared with the main branch. Block merges that fall below thresholds. Version prompts and model settings in the repository, deploy to staging first, then roll out gradually with monitoring and a quick rollback.
Deeper answer
Evals cost money and time, so run a fast smoke set on every pull request and a fuller set nightly or before release. Cache model responses where inputs are unchanged.
Treat a model version upgrade like a code change: it goes through the same pipeline. Secrets come from the CI system's secret store, never the repository.
What a strong answer covers
- Normal checks: lint, types, unit tests
- Eval suite on every change
- Thresholds block bad merges
- Prompts and model settings versioned
- Staging, gradual rollout and rollback
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- How would you keep eval costs reasonable in CI?
- How would you roll back a bad prompt change?
Common mistakes
- Changing prompts outside version control
- No evals in the pipeline
Learn it
- When would you serve predictions in batch, and when online?
- What is the difference between data parallelism and model parallelism?
- Why does experiment tracking matter, and what do you record?
- 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?