What is the base-rate fallacy, and how does it show up in classification metrics?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
The base-rate fallacy ignores prior prevalence when translating a sensitive test into a posterior.
WHY — Probability instead of guessing?
Why interviewers care about Probability:
who only read docs from people who shipped.
and tied to Data Science work.
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:
- 1The base-rate fallacy ignores
prior prevalence when translating a sensitive test into a posterior.
- 2A fraud model with
99 percent recall can still have poor precision if fraud is one in a thousand.
- 3Report precision, recall, and
predicted rates against the actual base rate, not just AUC.
- 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
The base-rate fallacy ignores prior prevalence when translating a sensitive test into a posterior. A fraud model with 99 percent recall can still have poor precision if fraud is one in a thousand.