CrackML by @ml.with.umang
Interview questions / ML Fundamentals
ML Fundamentals interview question

Countering Overfitting

A model has excellent training performance but weak validation performance. How do you diagnose and fix it?

mediumconceptEvidence 34/1001 source reportMeta

The 60-second answer

First rule out leakage or train/validation distribution mismatch; “overfitting” is not always excessive model capacity. Compare learning curves, slices, label quality, and repeated splits before changing the model.

Build the answer in this order

1
Give the core idea

First rule out leakage or train/validation distribution mismatch; “overfitting” is not always excessive model capacity.

2
Explain how it works

Compare learning curves, slices, label quality, and repeated splits before changing the model.

3
Compare alternatives

Remedies include more/better data, augmentation, reduced capacity, early stopping, weight decay/dropout, feature cleanup, and stronger validation protocol.

4
State failure modes + validation

Re-run a simple baseline after each major change so complexity is justified by reproducible validation gain.

A useful interview mental model

This is the shape of a strong answer—not a script to memorize.

01Definition
02Mechanism
03Trade-offs
04Failure modes
05When to use

Senior-level signal

  • Senior answers distinguish variance from leakage, temporal drift, and selection bias before prescribing regularization.
  • Discuss how repeated tuning on one validation set can itself overfit the evaluation process.

What the interviewer is really testing

Mechanistic understanding, assumptions, trade-offs, and whether you can turn a definition into a model decision.

Likely follow-up questions

What assumption makes this approach work?
When would you choose the strongest alternative instead?
What production or data failure mode changes your answer?

Common weak-answer patterns

  • Reciting a definition without mechanism or assumptions.
  • Claiming one technique is always better without a data regime.
  • Stopping before failure modes, validation, or deployment implications.