Asked in: ML breadth at every level. The classic warm-up question.
Explain bias and variance, then use the distinction to reason about a model’s generalization behavior.
Problem
Context. A predictor is fitted on sampled training data and evaluated on new examples from a specified population. Its predictions can be systematically wrong and can change when the training sample changes.
Task. Define bias, variance, and irreducible noise under squared loss, then relate them to model capacity and diagnostic experiments. Explain what additional evidence would justify changing data volume, regularization, or architecture.
Constraints. State assumptions behind the classical decomposition and distinguish repeated-sample expectations from one train-validation split. A generalization gap alone does not directly measure every term or establish a universal capacity trade-off.
What an L4 answer sounds like
“Total error decomposes into bias squared + variance + irreducible noise. High-bias models like linear regression underfit; high-variance models like deep trees overfit. You want to find the sweet spot in the middle.”
Correct. Memorable. Insufficient at any level above L4.
The interviewer now knows: you read the textbook. You don’t yet know if you’ve ever used the concept.
What an L5 answer sounds like
“For squared-error prediction at a fixed input, compare the fitted predictor across draws of training data and fitting randomness. Bias is its expected prediction minus the population regression function; variance measures its fluctuation around that expectation. With finite moments and fresh conditionally zero-mean observation noise, expected squared error decomposes into squared bias, predictor variance, and noise variance. This is not a universal decomposition of every classification loss. The expectation and variance lesson supplies the underlying identities.
High training and validation error suggest checks for optimization, features, labels, and model restrictions. A large gap suggests checks for overfitting, split mismatch, leakage, or shift. Two observed errors do not uniquely identify the decomposition’s terms; use controlled learning curves and data audits to distinguish causes.
More data can change both the fitted predictor and the best regularization or capacity choice. A variance rate needs a specified estimator and assumptions; it is not a universal scaling law for deep networks.”
This is L5. You’ve connected the formula to a debugging procedure and to scaling. You’ve also implicitly named the failure modes you’d diagnose in production.
What an L6 answer sounds like
The L6 answer is the L5 answer plus the things the textbook is wrong about:
“…the squared-loss identity does not stop being valid for an overparameterized model. What can fail is the assumption that test error must trace one U-shaped curve as capacity increases.
In the classical regime, increasing model complexity raises variance and lowers bias, with a U-shaped test-error curve. But for deep networks past the interpolation threshold, where they can fit any training set including random labels, you see double descent: test error rises, then falls again as you keep adding parameters. So the practical advice ‘pick a model complexity below the U’s bottom’ is dangerous for deep nets; you may be in the wrong regime entirely.
Compare capacity, regularization, optimization, and data choices under matched budgets and valid held-out evaluation. A second descent is a possible empirical regime, not permission to choose the largest model and assume SGD handles generalization.
One more nuance: in real systems, your training distribution and test distribution differ. Some of what looks like ‘variance’ is actually distribution shift. You won’t fix that by collecting more iid data; you need to inspect what’s drifted.”
This shows: you know the textbook, you know its limits, and you know what changes in practice.
Learning objective: recognize the classical U-shaped curve as one region of a larger capacity axis, with a possible second descent after the model first fits the training set.
Capacity regimes
Two perfect training fits disagree between observed points
Derivation
Do the three observed pins determine the prediction halfway between them?
The tells that get you a strong-hire vote
- You name double descent (or the modern overparameterization regime) without being prompted.
- You mention distribution shift as a confound for variance.
- You connect the decomposition to a debugging procedure (“if I see X I’d do Y”), not just a formula.
- You define noise relative to the available information and target loss, rather than assuming it always dominates.
The tells that get you down-leveled
- You give an estimator definition without identifying its population, sampling randomness, loss, or observable diagnostic checks.
- You say “use cross-validation to find the sweet spot” as the answer to everything. Cross-validation is one tool; with deep nets it’s often impractical and beside the point.
- You can’t give a concrete example: a project where the bias-variance distinction informed an actual decision.
What the interviewer is actually checking
The bias-variance question has high information value because:
- The L4 answer is fast and clean, so finishing it gives you ~3 minutes of remaining time before the interviewer moves on. They will use that time to ask “anything else?” and watch what you fill the silence with.
- Senior candidates fill it with the practical implications; junior candidates fill it with restatements.
The right move when asked this question: give the textbook decomposition in 30 seconds, then immediately pivot to the practical use without waiting for the follow-up. “…and the way I actually use this in practice is…” That single transition often does more for your level signal than the rest of the answer combined.
Related: regularization.