Interview Questions for a Data Scientist
To interview a data scientist, test statistics, experimentation, and machine learning fundamentals alongside how they translate a business question into a measurable analysis. This set covers hypothesis testing, A/B test design, model selection and validation, bias and overfitting, and how candidates communicate uncertainty to non-technical stakeholders.
Last updated
Run a data scientist interview with a case that starts from a fuzzy business question and ends with a defensible recommendation, plus targeted statistics and modeling probes. Reward rigor about uncertainty and clear communication as much as algorithmic knowledge.
Technical & Role-Specific
What to look for: Defines both correctly, notes a p-value isn't the probability the hypothesis is true, and prefers intervals for communicating effect size.
What to look for: Defines a primary metric, picks a minimum detectable effect, computes sample size and duration, randomizes correctly, and pre-registers the analysis.
What to look for: Connects overfitting to high variance, explains regularization, cross-validation, and the danger of training-test leakage.
What to look for: Knows when decisions require causality, can describe randomized experiments, difference-in-differences, or instrumental variables, and warns about confounders.
What to look for: Class imbalance, the right metric (precision, recall, F1, AUC, calibration), and aligning the metric with the business cost of errors.
What to look for: Distinguishes missing-at-random mechanisms, weighs deletion vs imputation, and acknowledges that naive imputation can bias estimates.
What to look for: Monitors for data and concept drift, compares feature distributions, retrains on a schedule, and investigates upstream data changes.
What to look for: Weighs the cost of errors, regulatory and explainability needs, and stakeholder trust against marginal accuracy gains.
Behavioral
What to look for: Communicates clearly to non-technical audiences, stands behind rigorous findings, and frames uncertainty honestly.
What to look for: Intellectual honesty, willingness to follow the data, and resisting the pressure to confirm a preferred narrative.
What to look for: Scientific integrity, distinguishing exploratory from confirmatory work, and avoiding p-hacking or cherry-picking.
What to look for: Understands that impact requires stakeholder trust and integration, not just accuracy, and reflects on the gap honestly.
Situational / Problem-Solving
What to look for: Segments the metric, checks data quality first, forms hypotheses, isolates causes, and separates signal from noise.
What to look for: Weighs practical significance and cost against statistical significance, considers sample size and multiple-comparison risk.
What to look for: Prioritizes the decision the analysis informs, time-boxes data cleaning, and delivers a defensible answer with caveats rather than perfection.
What to look for: Recognizes Simpson's paradox and heterogeneous effects, digs into subgroups, and avoids a misleading aggregate conclusion.
Data Scientist interview scorecard
Score every candidate on the same criteria, immediately after the interview, using evidence you actually heard rather than an overall impression. Agree the criteria with the panel before the first interview — deciding what counts after you have met people is how the loudest interviewer wins the debrief.
| Criterion | Evidence to record | Score 1-5 |
|---|---|---|
| Technical & Role-Specific | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Behavioral | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Situational / Problem-Solving | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Overall recommendation | Strong no / no / mixed / yes / strong yes, with the single reason that decided it | - |
Want this as a reusable document? Use the interview scorecard template.
Questions to avoid asking a Data Scientist
Exactly which questions are unlawful depends on where you are hiring, and the rules change — so treat this as the list of topics to route through your own employment counsel, not as a legal standard. The practical test that holds everywhere: if the answer could not change how the person does this job, you have no reason to ask it.
Related roles to hire
Choosing your recruiting stack
Frequently asked questions
How many interview rounds for a Data Scientist?
Should a data scientist interview include a take-home case study?
How do I tell a data scientist apart from a data analyst in interviews?
Is coding ability important for data scientists?
Run these interviews structured, and compare candidates fairly
Pitch N Hire is an applicant tracking system with built-in interview scorecards. Load these questions into a scorecard so every interviewer assesses the same criteria and you can compare candidates side by side.
Free for 1 user · No credit card · Talk to a real hiring expert
See how much faster your team could hire
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo Talk to sales View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
