fine tuning
Applied AI interview questions tagged fine tuning, across every topic.
17 questions · 2 unlocked for you
Concepts behind "fine tuning"
The curriculum that explains the ideas these questions test.
Core
Prompting vs RAG vs Fine-TuningGiven an LLM use case, the senior move is matching the technique to what is missing rather than defaulting to one. Need external or changing knowledge? RAG. Need a specific behavior, format, or skill? Fine-tuning. Need to take actions or use live systems? Tools/agents. Just need better instructions? Prompting. They combine, and you escalate from cheapest (prompting) to most involved (fine-tuning). Applied-AI interviews probe it because choosing wrong wastes months, fine-tuning to inject changing facts is the classic mistake.🧠 Foundations of LLMs & GenAISign in
Core
LoRA and Parameter-Efficient Fine-TuningFull fine-tuning updates all of a model's weights, which is expensive in compute and memory and produces a full-size copy per task. LoRA freezes the base model and trains small low-rank adapter matrices, cutting trainable parameters by orders of magnitude while matching most of full fine-tuning's quality. QLoRA adds 4-bit base quantization to fit huge models on one GPU. Applied-AI interviews probe it because PEFT is how teams actually fine-tune, and because LoRA adapters enable serving hundreds of variants cheaply.🧠 Foundations of LLMs & GenAISign in
Core
DPO and Preference-Optimization VariantsDirect Preference Optimization aligns a model directly on preference pairs with a simple classification-style loss, skipping RLHF's separate reward model and RL loop, which makes alignment far simpler and more stable. A family of variants then relaxes DPO's requirements: SimPO removes the reference model, KTO removes the need for paired data, and ORPO merges SFT and alignment into one step. Applied-AI interviews probe it because DPO is now the common way teams align open models, and the variants show you understand what each requirement buys.🧠 Foundations of LLMs & GenAISign in
Core
Choosing and Adapting Embedding ModelsPicking an embedding model is a decision about retrieval quality, cost, and operational risk on your data, not about who tops a public leaderboard. The hard parts are benchmarking on your own queries, trading dimensionality against storage and latency, deciding whether to fine-tune for your domain, and planning for the re-embedding migration when the model changes. Applied AI interviews probe it because candidates default to the leaderboard winner and ignore the drift and migration costs that bite later.🤖 Retrieval & AgentsSign in
Core
Transfer LearningTransfer learning reuses a model pretrained on a large general corpus as the starting point for a new task, so you inherit learned features instead of training from scratch. The two modes are feature extraction (freeze the backbone, train only a new head) and fine-tuning (unfreeze some layers and keep training), and the choice turns on how much labeled data you have and how far the new domain has drifted. Applied AI interviews probe it because it is the default for vision and NLP when labels are scarce, and because candidates often fine-tune when they should freeze, or vice versa.📊 Evaluation & ML FoundationsSign in
Core
Catastrophic Forgetting and Continual LearningCatastrophic forgetting is when training a neural network on new data erodes capabilities it already had, because gradient updates overwrite the weights that encoded old skills. Applied AI interviews probe it because fine-tuning a model on a narrow task is the most common way teams accidentally break a general model, and knowing the mitigations (data replay, regularization, parameter-efficient methods) separates people who have shipped fine-tunes from people who have only read about them.📊 Evaluation & ML FoundationsSign in
