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

ReLU vs Sigmoid

Compare ReLU and sigmoid activations and explain where each is appropriate.

easyconceptEvidence 34/1001 source reportPinterest

The 60-second answer

Sigmoid maps values to (0,1) and is natural for binary probabilities at an output layer, but saturates and can produce small gradients in deep hidden layers. ReLU is cheap and non-saturating on the positive side, making it a common hidden activation, though units can become permanently inactive.

Build the answer in this order

1
Give the core idea

Sigmoid maps values to (0,1) and is natural for binary probabilities at an output layer, but saturates and can produce small gradients in deep hidden layers.

2
Explain how it works

ReLU is cheap and non-saturating on the positive side, making it a common hidden activation, though units can become permanently inactive.

3
Compare alternatives

Mention alternatives such as GELU/SiLU/leaky ReLU when smoothness or dead-unit behavior matters.

4
State failure modes + validation

Choose output activation from the probabilistic objective and hidden activation from optimization/architecture evidence.

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 separate activation choice from loss semantics: sigmoid plus BCE is different from using sigmoid everywhere.
  • Discuss mixed precision and fused kernels only when system constraints make them relevant.

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.