Why must medical or user data be split by patient or user, not by row?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
Multiple rows from one person share physiology, devices, and labeling quirks.
WHY — Train/Val/Test instead of guessing?
Why interviewers care about Train/Val/Test:
on Train/Val/Test.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Multiple rows from one
person share physiology, devices, and labeling quirks.
- 2A row-wise split puts
the same person in train and test, so scores look like generalization when they are memorization.
- 3Grouped splits and GroupKFold
are the honest design.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Multiple rows from one person share physiology, devices, and labeling quirks. A row-wise split puts the same person in train and test, so scores look like generalization when they are memorization.