How do you navigate the latency, cost, quality triangle when choosing an eval approach?
You are designing an eval strategy for a production LLM system. Explain how to navigate the latency, cost, quality triangle when choosing between automated metrics, LLM-as-judge, and human evaluation. What is the recommended layering strategy?
Layer the three eval modes as a cost-ordered cascade: cheap automated checks gate everything, an LLM judge scores a sampled slice, and human review calibrates the cheaper layers on a small holdout.
Imagine inspecting every car leaving a factory. You cannot afford a full crash test on each one, so you use three tiers. First, a quick automated scanner checks the obvious stuff on every car: do the lights work, are the doors attached? It is instant and almost free. Second, an experienced inspector test-drives a small random sample to feel for handling problems a scanner cannot catch. That costs more, so you only do it on a few cars. Third, once in a while you send one car to a full crash-test lab. That is slow and very expensive, but it is the gold standard. You use it rarely, mostly to check that your scanner and your inspector are still judging cars correctly. Each tier is cheaper than the next, and the cheap tiers do most of the work.
Detailed answer & concept explanation~8 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
5 min: place the three modes on the latency cost quality triangle, build the cheap-gate to sampled-judge to human-calibration cascade, then cover sampling rates, judge tiering, stratification, and drift detection.
Real products, models, and research that use this idea.
- LangSmith and Langfuse run automated assertions inline, then schedule LLM-judge evals (Claude Opus 4.7 or GPT-5.5) on a sampled slice of production traces.
- RAGAS computes cheap faithfulness and relevance scores on samples, with teams reserving human spot-checks to validate the judge quarterly.
- Promptfoo gates CI on cheap deterministic assertions first, escalating to LLM-judge comparisons only when the cheap checks pass.
- Braintrust and Arize Phoenix dashboard judge scores against human-labelled holdouts to surface drift between cheap and gold-standard signals.
- OpenAI Evals supports graders you can tier, so a small model triages and a stronger model adjudicates only the ambiguous cases.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you pick the sampling rate for the LLM-judge tier on production traffic?
QHow do you tier the judge itself to cut cost without losing fidelity?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Running an expensive LLM judge or human review on every request. The fix is a cascade where cheap automated checks handle the volume and costly tiers run only on a small sample.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.