How would you decide between continual fine-tuning and retrieval for a new knowledge domain?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
If facts churn, require citations, or are tenant-specific, retrieve.
WHY — Tokens instead of words?
LLMs use tokens (not full words) because it helps them:
question about Fine-tuning vs RAG.
trade-offs, and what you would actually do on a GenAI / LLM project - not buzzwords.
Each piece maps to a number the network can learn.
Fixed pieces are what transformers expect as input.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1If facts churn, require
citations, or are tenant-specific, retrieve.
- 2If the domain needs
new skills, jargon fluency, or a stable procedure, fine-tune or use adapters.
- 3Run a bake-off on
the same eval set with cost and stale-document tests included.
- 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
If facts churn, require citations, or are tenant-specific, retrieve. If the domain needs new skills, jargon fluency, or a stable procedure, fine-tune or use adapters.