179 questions
No questions match those filters.
Walk through a complete RAG evaluation pipeline, not ju...
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansEvaluation done well operates at four distinct layers, and conflating them is how teams end up unable to diagnose what’s actually wrong. Layer one is pure retrieval quality — hit rate at K (is the right document even in the top results), mean reciprocal rank, and context precision (what fraction of what got retrieved is actually relevant). Layer two is generation quality, typically via RAGAS-style metrics: faithfulness (is the answer grounded in what was retrieved), answer relevancy (does it address the question), and context recall (did retrieval miss anything the ground truth needed).
Layer three is end-to-end evaluation against a golden dataset — several hundred expert-labeled question-answer pairs, run before every deployment, with a hard regression gate: if any metric drops more than a set threshold (5% is a common bar) relative to the current baseline, the deployment is blocked automatically rather than left to human judgment in the moment.
Layer four is what happens after deployment: online monitoring against live traffic, sampling a slice of daily queries for automated evaluation, tracking user thumbs up/down rates, and watching citation accuracy over time. The thing that ties all four layers together into an actual practice rather than a one-time benchmark is treating a quality regression exactly like a broken test — something that blocks a deploy, the same discipline traditional software CI/CD already applies to correctness.