Defend

LoRA fine-tuning of LLaMA and Gemma

It’s on LinkedIn but not on your resume, so expect questions designed to test whether you did it hands-on.

On your resume

Implementing PEFT and LoRA fine-tuning strategies for LLaMA and Gemma models to achieve high-precision results in domain-specific financial environments.

Cross-questions

5
A strong answer covers
  • Fine-tune for consistent format, style or domain behavior, or to make a small model do a narrow task cheaply.
  • Use RAG for knowledge that changes or must be cited.
  • State the baseline you beat: the prompted base model versus the tuned model on the same eval set.
Avoid

“Fine-tuning gives better accuracy” with no baseline.

A strong answer covers
  • Freeze the base weights and learn a low-rank update ΔW = B·A of rank r for chosen layers.
  • Alpha scales the update (effective scale alpha/r); r is typically 8 to 64.
  • Target modules: attention projections (q, v) or all linear layers.
  • QLoRA: LoRA on a 4-bit quantized base (NF4), so large models fit on one GPU.
Avoid

Mixing up LoRA with quantization.

A strong answer covers
  • Size, source, cleaning and de-duplication, and the train, validation and test split.
  • A held-out domain test set, with metrics such as exact match, F1 or rubric-based LLM judging.
  • A check that general ability didn’t regress.
Avoid

Evaluating on data that overlaps the training set.

A strong answer covers
  • Merged weights versus serving adapters dynamically (vLLM multi-LoRA).
  • Where it ran (SageMaker, EKS or Vertex), quantization for serving, and the cost compared with an API model.
Avoid

Not knowing how the model reached production.

A strong answer covers
  • Overfitting, forgetting, chat-template mismatches or label noise. Pick the one you actually hit and explain how you fixed it.
Avoid

Saying it all went smoothly.

Your numbers

Interviewers probe numbers first. Write exact values so you never have to improvise.

Next claim