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

When would you prefer gradient descent to the normal equation?

mediumconceptEvidence 75/1001 source reportAmazon

The 60-second answer

Gradient descent updates parameters in the direction opposite the loss gradient; SGD estimates that gradient from a mini-batch. Adam adds adaptive first- and second-moment estimates, often giving fast initial optimization, while SGD can generalize well with careful schedules.

Build the answer in this order

1
Give the core idea

Gradient descent updates parameters in the direction opposite the loss gradient; SGD estimates that gradient from a mini-batch.

2
Explain how it works

Adam adds adaptive first- and second-moment estimates, often giving fast initial optimization, while SGD can generalize well with careful schedules.

3
Compare alternatives

Learning rate is usually the most important optimizer hyperparameter; warmup, decay, or plateau schedules can stabilize training.

4
State failure modes + validation

Diagnose divergence, plateaus, exploding gradients, and noisy updates using loss/gradient statistics.

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 optimizer-state memory and distributed-training communication, not only convergence speed.
  • For large models, connect schedule/optimizer choices to batch size and effective token budget.

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.