The 60 probability questions interviewers actually ask, with direct answers, Bayes examples, diagrams, videos, Python snippets, and data science tips.
60 questions with answersKey Takeaways
Probability is the math of uncertainty. It assigns a number between 0 and 1 to how likely an event is, then gives rules for combining, conditioning, and updating those chances. In interviews, probability questions test whether you can define the sample space, count outcomes correctly, handle conditional information, and reason about expected value. A strong answer is slow and structured: The event, The known information, choose the rule, then compute or explain the result.
Watch: Lecture 1: Probability and Counting
Video: Lecture 1: Probability and Counting (Harvard University, YouTube)
Test yourself and earn a certificate
6 quick questions. Score 70%+ to download your Probability certificate.
Start here. These are the definitions and first-principle checks that open most rounds.
Probability measures the chance that an event happens, from 0 to 1.
Always define the event before giving the number.
probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: Lecture 1: Probability and Counting (Harvard University, YouTube)
The sample space is the set of all possible outcomes in an experiment.
A wrong sample space leads to a wrong answer even if the formula is right.
sample space changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
An event is a subset of the sample space.
For a die roll, rolling an even number is the event {2, 4, 6}.
event changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
The complement of an event is everything in the sample space where that event does not happen.
Use P(not A) = 1 - P(A).
complement changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
| Answer part | What to say | Evidence to mention |
|---|---|---|
| Definition | complement in one direct sentence. | Official docs or course material |
| Use case | The work where it changes a decision. | Dataset, model, query, dashboard, or pipeline |
| Risk | What breaks when it is misunderstood. | Metric, log, test result, or review note |
The union of two events means A or B or both happen.
Use the addition rule and subtract overlap.
union changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: Probability Models and Axioms (MIT OpenCourseWare, YouTube)
The intersection of two events means A and B both happen.
Use multiplication carefully, depending on independence or conditioning.
intersection changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Mutually exclusive events cannot happen at the same time.
Their intersection is zero.
mutually exclusive events changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Independent events do not change each other's probabilities.
If A and B are independent, P(A and B) = P(A)P(B).
independent events changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Dependent events change each other's probabilities.
Drawing cards without replacement is a common example.
dependent events changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Conditional probability is the chance of an event given that another event has happened.
Write P(A given B) and be clear which event is the condition.
conditional probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Bayes theorem updates a probability after new evidence.
It connects prior probability, likelihood, and posterior probability.
Bayes theorem changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Key point: the key signal is the base rate. Missing the prior is the usual Bayes mistake.
A prior probability is the belief or base rate before seeing new evidence.
Ignoring base rates is a common interview mistake.
prior probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
The law of total probability breaks an event into cases and adds the weighted probabilities across those cases.
It is often the denominator in Bayes theorem.
law of total probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: Conditional Probability (Harvard University, YouTube)
A random variable assigns a numeric value to each outcome of a random process.
It can be discrete or continuous.
random variable changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Expected value is the long-run average outcome weighted by probabilities.
It is not always the outcome you expect to see once.
expected value changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Variance measures how spread out a random variable is around its expected value.
Risk often depends on variance, not just average.
variance changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
A Bernoulli distribution models one trial with two outcomes: success or failure.
It has one parameter, the success probability.
Bernoulli distribution changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
A binomial distribution models the number of successes in a fixed number of independent Bernoulli trials.
Use it for repeated yes/no trials with the same probability.
binomial distribution changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
A Poisson distribution models event counts in a fixed interval, while an exponential distribution models waiting time between events.
Both are useful when events occur at a stable average rate.
Poisson and exponential distributions changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
A normal distribution is bell-shaped around a mean, while a uniform distribution gives equal probability across a range.
Know when each shape fits before using formulas.
normal and uniform distributions changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
These questions test whether you can apply the topic to real data, real code, and messy constraints.
Write the sample space, event, known condition, and rule before calculating.
This prevents most interview mistakes.
solving a probability question changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Probability solution flow
For A or B, use P(A) + P(B) - P(A and B).
Subtract overlap so you do not double-count.
using the addition rule changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
For A and B, use P(A) times P(B given A).
Only simplify to P(A)P(B) when A and B are independent.
using the multiplication rule changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Check whether P(A given B) equals P(A), or whether P(A and B) equals P(A)P(B).
Do not assume independence because events sound unrelated.
checking independence changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Restrict the sample space to the condition first, then count favorable outcomes inside that reduced space.
This is often easier than using formulas blindly.
solving conditional probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: Story Proofs and Axioms of Probability (Harvard University, YouTube)
Use Bayes when you know P(evidence given cause) but need P(cause given evidence).
Medical tests, spam filters, and fraud detection are common examples.
applying Bayes theorem changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
prior = 0.01
sensitivity = 0.95
false_positive = 0.05
posterior = sensitivity * prior / (sensitivity * prior + false_positive * (1 - prior))
print(round(posterior, 4))Multiply each outcome by its probability and add the results.
Use it for long-run average payoff, cost, or risk.
using expected value changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Compare expected value and spread, not only the average.
Two options can have the same expected value and very different risk.
comparing risk changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Match the distribution to the data-generating process: Bernoulli for one yes/no trial, binomial for repeated trials, Poisson for counts over time.
the key signal is why the distribution fits.
choosing a distribution changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use binomial when trials are fixed, independent, and have the same success probability.
If probability changes between trials, binomial may not fit.
using binomial probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use Poisson for event counts in a fixed interval when an average rate is known.
It assumes events occur independently at a stable rate.
using Poisson probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Update probabilities after each draw because the sample space changes.
This is a dependent-event problem.
handling without replacement changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Keep probabilities the same after each draw because the item returns to the pool.
This often creates independent trials.
handling with replacement changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use combinations when order does not matter.
A team of three people is the same team regardless of selection order.
counting combinations changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use permutations when order matters.
A ranking of three people changes when order changes.
counting permutations changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Draw branches for each event and multiply along paths, then add paths that match the target event.
Trees make conditional sequences easier to see.
using probability trees changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use simulation when exact calculation is hard, then compare the result with intuition.
Simulation is not a substitute for understanding, but it checks reasoning.
simulating probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
import random
random.seed(42)
wins = 0
trials = 10000
for _ in range(trials):
rolls = [random.randint(1, 6) for _ in range(2)]
wins += sum(rolls) == 7
print(wins / trials)Confirm the final probability is between 0 and 1 and makes sense against the base rate.
If it is outside the range, the setup is wrong.
checking answer range changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
The prior frequency of the event before reacting to evidence.
Base-rate neglect is a common Bayes mistake.
explaining base rates changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
probability connects to uncertainty, class scores, calibration, loss functions, and decision thresholds.
Classification scores need calibration before they can be treated as probabilities.
using probability in ML changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Advanced rounds test trade-offs, failure modes, and whether the decision can hold up under production pressure.
Use Bayes theorem and include the base rate, sensitivity, and false positive rate.
The posterior can be much lower than people expect when the condition is rare.
positive medical test changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Update the sample space after each draw.
Without replacement makes events dependent.
card drawn without replacement changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Multiply probabilities only if the failures are truly independent.
Shared data, infrastructure, or assumptions can make failures correlated.
two independent model failures changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: Bayes Theorem (3Blue1Brown, YouTube)
Use base rates and precision-recall thinking, not raw accuracy.
Rare events make false positives a serious issue.
fraud probability with rare events changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Compute expected value and mention variance or risk before recommending play.
A positive expected value can still be risky for one player.
expected payout game changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Condition on observed user behavior and check calibration before acting on a score.
A model score is only useful if it maps well to real probability.
customer churn probability changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use inclusion-exclusion so overlapping cases are not counted twice.
This is the main trap in A or B questions.
multiple events with overlap changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use the complement: one minus probability of none.
This is often faster and less error-prone.
at least one event changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Consider a Poisson model when events are independent and occur at a stable average rate.
Call out if the rate changes over time.
rare event count changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Translate the sentence into P(A given B) notation.
The order of words matters.
conditional wording confusion changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Check calibration before treating the score as probability.
A score can rank well but still be poorly calibrated.
model confidence score changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Update the prior as population, channel, or time period changes.
A prior from last year may not fit today.
Bayes with changing prior changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Probability calculations must reflect the actual sampling process.
If the process is biased, equal-outcome assumptions fail.
sampling with biased process changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use many trials, set a random seed for repeatability, and report uncertainty in the simulation estimate.
Simulation estimates have sampling error too.
Monte Carlo estimate changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Separate probability model assumptions from observed experiment results.
Do not mix Bayesian and frequentist language casually.
probability in A/B tests changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Pick a threshold by weighing expected cost of false positives and false negatives.
The best threshold is rarely 0.5 by default.
decision threshold changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Use symmetry only after proving outcomes are equally likely.
Not every visible option has equal probability.
probability puzzle with symmetry changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
The event, condition, rule, base rate, and reasonableness check.
This structure works better than memorizing puzzle answers.
senior probability answer changes Probability decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Probability starts with assumptions and reasons about possible data. Statistics starts with observed data and reasons about unknown assumptions. Knowing that direction helps you avoid mixing the two in interviews.
| Area | Starting point | Question it answers | Example |
|---|---|---|---|
| Probability | Known model or assumptions | What outcomes are likely? | Chance of two heads in two coin flips |
| Statistics | Observed data | What model or population value is plausible? | Estimate conversion rate from a sample |
| Conditional probability | New information | How does the chance change? | Chance of churn given low usage |
| Expected value | Outcome values and probabilities | What is the long-run average result? | Expected payout of a game |
Probability interview focus
Most mistakes come from wrong sample space or wrong conditioning.
Scale: Hyring editorial score for interview preparation, not an external benchmark.
Prepare by solving slowly. Probability interviews reward clean setup more than fast arithmetic, especially when conditional information is involved.
The typical Probability interview flow
Most rounds reward clear reasoning more than memorized phrasing.
Probability interview answers are judged by setup more than speed. A good answer defines the sample space, names the event, states what information is already known, picks the right rule, and checks whether the result makes sense. This avoids the most common failure: using the right formula on the wrong event.
For cards, dice, medical tests, churn, or ranking problems, say what outcome counts as success. Then say whether events overlap, whether order matters, and whether sampling happens with or without replacement. That setup often solves half the problem before arithmetic starts.
Drawing with replacement and drawing without replacement create different probabilities after the first draw. Say the assumption explicitly for cards, samples, candidates, retries, and inventory questions. This small sentence prevents a large class of wrong answers.
Phrases like given, at least one, known to be, or after observing change the probability space. Strong candidates restate the condition before computing. This is especially important in Bayes theorem, where base rates and evidence are easy to reverse.
Many at least one questions are cleaner as one minus none. This is not a shortcut for its own sake. It reduces counting errors and lets you explain the answer faster. Interviewers like candidates who choose a simpler equivalent path and still state why it is valid.
Independent events do not affect each other's chances. Mutually exclusive events cannot happen together. These are different ideas, and mixing them is a common interview mistake. Use a simple example to prove the distinction before writing any formula.
A binomial distribution fits fixed yes-or-no trials. Poisson fits counts over time or space when events are rare and roughly independent. Normal often appears through aggregation and approximation. Exponential describes waiting time under a constant event rate. Say the assumption, not only the distribution name.
Expected value is not the outcome you must see next. It is the average result over many repetitions under the same setup. That wording matters in product and risk interviews because one rare outcome can dominate the expected value even when it almost never happens.
When outcomes happen in sequence, a probability tree keeps the branches honest. This works for interviews about cards, funnels, screening tests, retries, and ranking. Label each branch with the conditional probability at that step, then multiply along paths and add matching paths.
A probability must sit between 0 and 1. An expected value carries the unit of the outcome, such as dollars, minutes, or users. If an answer gives a probability above 1 or an expected value with no unit, it signals a setup error even if the algebra looked clean.
A prior is the belief or base rate before seeing the new evidence. In a medical-test style question, disease prevalence is the prior. In a churn question, the historical churn rate can be the prior. Saying it this way makes Bayes theorem easier to follow.
Some interview problems allow a normal or Poisson approximation to avoid messy exact counting. Say why the approximation fits, what assumption it uses, and how you would check the answer if exact precision mattered.
For complex dependency or ranking questions, a short simulation can verify intuition. In an interview, you can describe the simulation even without coding it fully: generate many trials, count the event, divide by trials, and compare the estimate with your analytic answer.
In data science and ML interviews, probability usually supports a decision: thresholding a classifier, estimating risk, ranking candidates, or sizing an experiment. End by saying how the result changes action and what extra data would reduce uncertainty.
6 questions, about 4 minutes. Score 70% or higher to earn a shareable certificate.
Hyring's AI Coding Interviewer scores how candidates reason through uncertainty, code, and trade-offs. Use this page before probability-heavy data science or ML screens.
See Hyring AI Coding Interviewer