Concept guide · Data and features
What is data leakage?
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-017
Start with the idea
In simple terms
This question is asking you to explain What is data leakage 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
Leakage is information entering training or evaluation that will not be available at prediction time, or that would not be available for the specific example in production. It includes future columns, fitting preprocessing before a split, using an outcome-derived aggregate, duplicate entities across train and test, and tuning repeatedly on the test set. The fix is to define the prediction timestamp and rebuild every transformation from information available before it. 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.
Mental model
A safe pipeline splits first, then learns transforms on train and applies them forward.
Say this in the interview
Leakage is information entering training or evaluation that will not be available at prediction time, or that would not be available for the specific example in production. It includes future columns, fitting preprocessing before a split, using an outcome-derived aggregate, duplicate entities across train and test, and tuning repeatedly on the test set. The fix is to define the prediction timestamp and rebuild every transformation from information available before it.
Keep preparing