Statistics & Probability interview questions and answers for data analysts and data scientists

Statistics interview questions for data roles cover experimentation, inference, and the reasoning behind an A/B test, the round that separates a data scientist from a dashboard builder. Real questions with worked answers below.

How the Statistics round is run, and what it scores

What the round actually tests

Whether you can reason under uncertainty and say so plainly. Statistics rounds are less about deriving anything than about definitions you can state without hedging, assumptions you volunteer before being asked, and what you would do when an assumption fails. The interviewer is usually checking whether you can be trusted to read an experiment result correctly.

This is the round that most often separates a data scientist from a dashboard builder, and it is scored heavily on explanation. Several large companies ask you to explain a confidence interval or a p-value to a non-technical stakeholder as a question in its own right.

The questions that repeat

What a p-value is, and what it is not. What 95% means in a confidence interval. Type I against Type II error and which is more expensive here. The Central Limit Theorem and why it lets you use a normal approximation on skewed data. Power, and what raises it. Sample size for an A/B test. Multiple comparisons and why twenty metrics produce a winner by accident.

Then the applied half: design an A/B test for this feature, this test ran for three days and the lift is 12%, do you ship it, the treatment group has more users than control, what happened. The applied questions are where the definitions get used, and where memorized answers come apart.

What interviewers score

The definition, then the assumption, then the failure mode. In that order. A candidate who says a p-value is the probability of data this extreme if the null were true, and then adds that it says nothing about effect size, has answered the question and the follow-up at once.

They also score restraint. Reporting an interval rather than a bare p-value, refusing to call a result significant when the interval includes trivial values, and saying a three-day test cannot be read because of novelty and weekly seasonality, all read as judgment rather than caution.

How to prepare, and in what order

Rebuild the core from the questions interviewers ask rather than from a textbook chapter order: p-value, confidence interval, Type I and II error, power, sample size, the CLT, and multiple comparisons. That set covers most of what is asked, and each one has a standard wrong answer you should be able to name.

Then practice the explanations at two levels, one for a fellow analyst and one for a product manager, because you will be asked for the second and graded on it. Say the numbers out loud. Most of the failures in this round are fluency failures, not knowledge failures.

Where candidates lose it

Saying a p-value is the probability the null hypothesis is true, which is the single most common wrong answer in the round. Saying there is a 95% probability the true value lies in this particular interval, which is a credible interval, not a confidence interval. Reading two overlapping confidence intervals as no significant difference. And treating p = 0.06 as no effect rather than as weaker evidence than 0.04.

26 Statistics questions

Probability and distributions

3. Explain Bayes' theorem with a real example.

Posterior is proportional to prior times likelihood. A 99% accurate test for a 1 in 1,000 condition still gives a positive result that is wrong about 90% of the time, because the false positives from the healthy majority outnumber the true positives.

Hypothesis testing and inference

9. Explain statistical power and what increases it.

Power is the probability of detecting an effect that is really there, one minus the Type II error rate. It rises with sample size, effect size and a higher alpha, and falls with variance. 80% is the usual target.

16. How do you correct for multiple comparisons?

Testing twenty metrics at alpha 0.05 gives a 64% chance of at least one false positive. Bonferroni divides alpha by the number of tests and is safe but conservative. Benjamini Hochberg controls the false discovery rate and keeps more real findings.

Experiments and causal inference

Regression and modeling

Practice this for real