Concept guide · Data and features
When should you scale features?
A slower explanation for when the short interview answer is not enough. Start with the intuition, then connect it to the technical idea and the way an interviewer expects you to reason about it.
ML area
Data and features → Core interview concept
Interview format
Core
Question
ML-015
Start with the idea
In simple terms
This question is asking you to explain When should you scale features in a way that connects the idea to a real machine-learning decision. Start with the role this concept plays, then explain what changes when the data, target, or deployment situation changes.
Build the answer
How to reason about it
- 1Define the concept before naming algorithms or implementation details.
- 2Connect it to the data, target, decision, or failure mode in the question.
- 3State the assumption or evaluation check that would make the explanation trustworthy.
Go one level deeper
The technical explanation
Scale features when the algorithm uses distances, dot products, gradients, or a weight penalty whose effect should be comparable across columns. It matters for k-nearest neighbours, k-means, support-vector machines, and many linear or neural models. It is usually less important for tree splits. Fit the scaler on training data only, then apply the frozen transform to validation, test, and production. The safest way to understand this topic is to connect the definition to assumptions, data available at prediction time, the decision it supports, and how you would evaluate whether the result is useful.
Common mistake
Fitting the scaler on the full dataset before splitting.
Say this in the interview
Scale features when the algorithm uses distances, dot products, gradients, or a weight penalty whose effect should be comparable across columns. It matters for k-nearest neighbours, k-means, support-vector machines, and many linear or neural models. It is usually less important for tree splits. Fit the scaler on training data only, then apply the frozen transform to validation, test, and production.
Keep preparing