Why do companies keep training and serving as separate pipelines?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
Training jobs are bursty, expensive, and allowed to fail and retry, while serving must stay up with tight SLAs.
WHY — Train vs Serve instead of guessing?
Why interviewers care about Train vs Serve:
on Train vs Serve.
the situation, the default choice, and one exception - that reads as experience.
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:
- 1Training jobs are bursty,
expensive, and allowed to fail and retry, while serving must stay up with tight SLAs.
- 2Splitting them lets you
scale GPUs for train and CPUs or small accelerators for inference independently.
- 3It also reduces the
chance that a training library upgrade takes down production traffic.
- 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
Training jobs are bursty, expensive, and allowed to fail and retry, while serving must stay up with tight SLAs. Splitting them lets you scale GPUs for train and CPUs or small accelerators for inference independently.