lora
AI, ML & GenAI interview questions tagged lora, across every topic.
10 questions · 0 unlocked for you
Concepts behind "lora"
The curriculum that explains the ideas these questions test.
Core
LoRA and Parameter-Efficient Fine-TuningFull fine-tuning updates all of a model's weights, costly in compute and memory and leaving a full-size copy per task. LoRA freezes the base model and trains small low-rank adapter matrices, dropping trainable parameters by orders of magnitude while matching most of full fine-tuning's quality. QLoRA layers on 4-bit base quantization to fit huge models on one GPU. AI, ML, and GenAI interviews probe it because PEFT is how teams actually fine-tune, and because LoRA adapters make serving hundreds of variants cheap.🧠 Foundations of LLMs & GenAISign in
Core
Fine-Tuning Hyperparameters and OverfittingChoosing to fine-tune is the easy part. The run succeeds or fails on a short list of dials: learning rate, epochs, effective batch size, LoRA rank and alpha, which modules you target, and max sequence length. Overfitting is the default outcome when those dials are set by copying a blog post, and its signature is a train loss that keeps falling while eval loss turns up. AI, ML, and GenAI interviews probe this because it separates people who have actually run a fine-tune from people who have only read about one.🧠 Foundations of LLMs & GenAISign 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. AI, ML, and GenAI engineer 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 those who have only read about them.📊 Evaluation & ML FoundationsSign in
Core
Multi-LoRA ServingLoRA adapters are tiny weight deltas layered on a shared base model, so you can serve hundreds of fine-tuned variants from one set of base weights rather than one full model per tenant. The serving challenge is batching requests that use different adapters in the same forward pass, moving adapters in and out of GPU memory on demand, and reusing the base model's KV cache machinery. AI, ML, and GenAI engineer interviews probe it because it is the economics behind per-tenant and per-task customization and the serving-side complement to LoRA training.🖥️ ML Infrastructure & ServingSign in
