Concept guide · Data and features
How do you detect 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-018
Start with the idea
In simple terms
This question is asking you to explain How do you detect 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
Look for an implausibly strong score, a feature whose timestamp is after the target, a large train-to-production drop without a similar validation drop, and transformations that were fitted outside the training fold. Recreate features using an as-of timestamp, inspect the top features, compare performance with deliberately removed suspicious columns, and audit whether duplicates or groups cross the split. A high score is a reason to investigate, not automatically a reason to celebrate. 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.
Say this in the interview
Look for an implausibly strong score, a feature whose timestamp is after the target, a large train-to-production drop without a similar validation drop, and transformations that were fitted outside the training fold. Recreate features using an as-of timestamp, inspect the top features, compare performance with deliberately removed suspicious columns, and audit whether duplicates or groups cross the split. A high score is a reason to investigate, not automatically a reason to celebrate.
Keep preparing