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

How should dropout behave at test time?

How should dropout behave at test time? Structure your response as you would in a top-tier ML/AI engineering interview.

mediumconceptEvidence 82/1002 source reportsAmazon

The 60-second answer

During training, dropout randomly zeros activations to reduce co-adaptation and acts as regularization. With inverted dropout, surviving activations are scaled during training so inference is deterministic without extra rescaling.

Build the answer in this order

1
Give the core idea

During training, dropout randomly zeros activations to reduce co-adaptation and acts as regularization.

2
Explain how it works

With inverted dropout, surviving activations are scaled during training so inference is deterministic without extra rescaling.

3
Compare alternatives

Tune dropout against the train-validation gap; excessive dropout increases bias and slows optimization.

4
State failure modes + validation

Switch the model to evaluation mode at inference and test deterministic behavior.

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

  • Discuss interactions with normalization and why modern Transformer configurations may use dropout differently from older MLP/CNN recipes.
  • Treat train/eval-mode mistakes as correctness bugs because they silently shift output distributions.

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.