Sample report

Sample data for a fictional student, from a scripted interview. The report was written by the same pipeline that writes yours.

Probability interview

Quant Developer, regular level, five problems, Oct 25, 2026

Hire

If you read nothing else

At the Regular bar in this interview.

  • Strength: You set up and solve recurrences cleanly, and you explicitly check general formulas against small cases (2, 6, 14, then 2^(n+1) - 2).

    The pattern from one and two heads is 2 and 6, each one is double the previous plus two, so three heads is 14.Your words, 3:44
  • Strength: You recover fast from a hint: one prompt on the reroll threshold took you to the correct 4.67 with a proper sanity check.

    I reused the old threshold; the threshold should be the value of continuing, which is now 4.25, not 3.5.Your words, 8:40
  • Gap: Set the threshold to the value of continuing.

    keep 4, 5 or 6 on the first roll, otherwise play the one-reroll gameYour words, 8:22

One moment from your delivery

You hesitated

When asked “Check that against a simpler case. How long until the first single...” (Q1), you hesitated: you took 6.6 s to start (your usual 3.5 s); you sped up to 172 words per minute (your usual 141).

  • Time to start 6.6 s vs your usual 3.5 s
  • Words per minute 172 vs your usual 141
And one over a half is two, so that matches.Your words, 1:54

Try: Start with a one-line headline ('My approach is X because Y') and think aloud from there instead of in silence.

Your next task, 20 min

Set the threshold to the value of continuing

Run the die game with three rerolls and with a one-dollar cost per reroll. Each time, state the value of continuing first, then derive the keep threshold and the game value.

What happened

You worked through five probability problems: coin patterns, optimal stopping with dice, the birthday problem, the two-children puzzle and a piano-tuner estimate. You set up states cleanly, sanity-checked most answers and recovered well when the interviewer pushed back, for example on the reroll threshold and the Tuesday-boy count. The main takeaway: your first instinct is sometimes too quick, but your recovery is strong. The session was complete.

At the bar

At the Regular bar: your setups, approximations and self-checks are already there, and the remaining gap is first-pass accuracy on the trickier variants, where you sometimes answer before counting.

You answered all 5 planned questions.

After that

More ways to practice, in order of impact.

  1. 1

    Check pattern-matched guesses with a quick state count: For 15 minutes, take five short waiting-time problems and before answering, say out loud whether the attempts are independent or overlap. Only then compute.

  2. 2

    Your longest pause, 3.4 seconds, came just before you corrected heads-tails; saying 'let me redo the states' out loud turns that silence into visible method.

Scorecard

Each skill from the rubric, scored 1 to 5, with the moments it was based on.

  • Slow down on the first ten seconds: write the setup and check it against a trivial case before committing to a number. On the reroll question, re-derive the threshold from the value of continuing each time instead of carrying the old one forward.

    A quarter of E0 is 1.5, and E0 is 6.Your words, 1:54
    I reused the old threshold; the threshold should be the value of continuing, which is now 4.25, not 3.5.Your words, 8:40
    The day shouldn't matter, it's independent of everything, so I'd say it's still one third.Your words, 20:34

    What good looks like: You get the first answer right on the variants too: the two-reroll threshold, the Tuesday-boy count and the variance, without needing the interviewer to prompt a recount.

    To reach 5: correct on all, including trickier ones.

    Before answering a variant, ask yourself what changed from the previous case, and only then commit to a number.

  • Your setups are clean when you use them; the misses come from skipping the setup on the first pass. At minimum, state which quantities are random and what the state is before writing any arithmetic.

    Let me use states. E0 is the expected flips from scratch, E1 after one head.Your words, 1:54
    If I use n times n minus one instead of n squared, then 23 times 22 is 506Your words, 15:36

    What good looks like: Same clean setup, plus you state the key insight before the algebra and finish with an explicit check every time, including on the variance question where you stopped at the method.

    To reach 5: clean setup, states the key insight, checks the result.

    On questions you can't finish, still write the two equations for the second moment and say what you'd solve.

  • Keep the estimation habit, but practise producing a defensible rough number where you currently stop at 'I would set it up'. A quick bound on the variance would have been enough.

    So it's about e to the minus n squared over 730. Set that to a halfYour words, 14:36
    A million people, about two and a half per household, so 400,000 households.Your words, 23:32

    What good looks like: This is already at the top anchor: you approximate, bound and chain assumptions quickly and keep the arithmetic in your head.

    To reach 5: fast, comfortable approximating and bounding.

    Keep the same pace, but say the rounding you use out loud so the interviewer can follow the numbers.

  • When you are unsure, say the method out loud as you did on the variance instead of going quiet or guessing quickly; that is what lets the interviewer give you a useful hint.

    Backward induction. At every decision, compare what you have now with the expected value of continuing optimallyYour words, 9:40
    the extra detail changes how many families fit the descriptionYour words, 22:49

    What good looks like: You narrate the whole chain while computing, not just the conclusion, and you flag when a follow-up detail is about to change your answer.

    To reach 5: narrates the reasoning clearly while working.

    When a number surprises you, say 'that feels low, let me check' before moving on, as you did on the tuner count.

Also went well

  • Your estimation is well structured, and you are honest about uncertainty, widening the interval when the errors were correlated rather than cancelling.

Also to improve

  • Stop committing to a first number before checking the framing; the 1/4 = 4 flips and the 1/3 Tuesday answer were both avoidable.
  • Carry the right quantity forward between sub-questions: after the one-reroll game, the value of continuing is 4.25, not 3.5.
  • Finish the parts you start: the variance question ended with a method and no number, and the 99% birthday count ended at '57 or 58'.

Red flags

  • Two answers needed an interviewer hint to correct a wrong number (turns 6 and 26), which suggests the first pass is not being checked.
  • One follow-up (variance for heads-heads) was left without any computed answer.

Question by question

Open a question to see which key points you covered, in your own words, and what a stronger answer sounds like.

  1. Your answer: You first guessed 4 from 1/(1/4), then switched to states E0 and E1 and solved E0 = 6. You extended to n heads with 2^(n+1) - 2 and corrected heads-tails to 4; for variance you described the second-moment method but gave no number.

    Key points

    • States/recursion gave E = 6; checked simpler case (Covered)

      Let me use states. E0 is the expected flips from scratch, E1 after one head.Your words, 1:54
    • Three heads in a row = 14 (Covered)

      The pattern from one and two heads is 2 and 6, each one is double the previous plus two, so three heads is 14.Your words, 3:44
    • General n heads: 2^(n+1) - 2 (Covered)

      So E n plus 2 is two to the n plus one, and E n is two to the n plus one, minus two.Your words, 5:01

    Follow-up questions

    • Check against the single-head case Handled wellYou used 1/(1/2) = 2 and saw that the independent-block shortcut only works for one head.
    • Three heads in a row Handled wellYou extended the pattern to 14 and then justified it with the recursion.
    • Why double plus two Handled wellYou derived E_n = 2E_(n-1) + 2 instead of relying on the pattern.
    • General formula for n heads Handled wellYou rearranged to E_n + 2 and got 2^(n+1) - 2.

    A stronger answer

    I'd set up states rather than assume independent blocks: E0 from scratch and E1 after one head. From scratch one flip takes me to E1 half the time or back to E0 half the time, so E0 = 1 + 0.5E1 + 0.5E0. From E1 a head finishes and a tail restarts, so E1 = 1 + 0.5E0. Solving gives E0 = 6, and the single-head check is 2, so 6 is plausible. For n in a row the recursion is E_n = 2E_(n-1) + 2, giving 2^(n+1) - 2: 14 for three heads. For heads then tails the state does not reset on a second head, so it is 2 + 2 = 4. For variance I'd write the second-moment equations for E0 and E1 and solve them rather than leave it at 'large'.

    Common mistakes on this question

    • Treating the two flips as independent tries and answering 1/(1/4) = 4
    • Leaving the pattern 2, 6, 14 unexplained instead of deriving the recursion

    Hints used: 1

  2. Your answer: You worked backwards from the last roll, kept 4-6 against a 3.5 reroll, and got 4.25. For two rerolls you first reused the 3.5 threshold, then corrected to 4.67 once you used 4.25. You also handled a $1 reroll cost and unlimited paid rerolls.

    Key points

    • Compared with 3.5 reroll value; threshold; 4.25 (Covered)

      So I keep anything above 3.5: keep 4, 5 or 6, and reroll 1, 2 or 3. ... So 2.5 plus 1.75, 4.25 dollars.Your words, 7:48
    • Two rerolls: keep 5 or 6; value 4.67 (Covered)

      So I only keep a 5 or a 6. ... 28 sixths, about 4.67.Your words, 8:40

    Follow-up questions

    • What if you may reroll up to two times? Partly handledYou first reused the 3.5 threshold and got 4.625, then corrected it after the next question.
    • Is a 4 worth keeping when rolling on is worth 4.25? Handled wellYou saw the threshold should be the value of continuing and recomputed 4.67.
    • What if each reroll costs a dollar, one reroll? Handled wellYou set the continuation value to 2.5, kept 3 or more, and got about 3.83.
    • Unlimited rerolls, each costing a dollar Handled wellYou tested keep 5/6, then keep 4+, and found a value of 4 with a 3 indifferent.

    A stronger answer

    I'd work backwards from the last decision: a reroll is worth 3.5, so I keep 4, 5 or 6 and reroll 1, 2 or 3, giving 2.5 + 1.75 = 4.25. With two rerolls the threshold is the value of continuing, which is 4.25, not 3.5, so I keep only 5 or 6: 11/6 + (4/6)(4.25) = 4.67. The principle is backward induction: compare the current roll with the expected value of continuing optimally. If a reroll costs a dollar, continuing is worth 2.5, so I keep 3 or more and the value is about 3.83. With unlimited rerolls at a dollar each, I'd solve V = (sum of kept values)/6 + (fraction rerolled)(V - 1); keeping 4 or more gives V = 4, and a 3 is indifferent. I'd sanity-check that each extra option raises the value but by less each time.

    Common mistakes on this question

    • Reusing the old threshold when the number of rerolls changes
    • Forgetting that a paid reroll lowers the value of continuing

    Hints used: 1

  3. Your answer: You avoided the 183 trap, built the product of different-birthday probabilities, approximated with exp(-n^2/730), and got 23. You checked 22 vs 23 and extended to 99% (about 57 or 58), expected matching pairs, leap years and non-uniform days.

    Key points

    • Product form, exponential approximation, about 23 (Covered)

      The probability that all birthdays are different with n people is 364 over 365, times 363 over 365 ... So 23 people.Your words, 14:36
    • 99% case: about 57 people (Covered)

      ln of 100 is about 4.6. So n squared is 730 times 4.6 ... So about 57 or 58.Your words, 17:29

    Follow-up questions

    • Is the approximation good enough to pick 23 over 22? Handled wellYou checked n(n-1): 23×22 = 506 passes half, 22×21 = 462 does not.
    • Expected number of pairs sharing a birthday with 23 people Handled wellYou computed 253/365 ≈ 0.69 and linked it to ln 2.
    • What if we want 99%? Handled wellYou got about 57 or 58 but could not decide between them exactly.
    • How does the answer change if birthdays are not uniform? Handled wellYou argued matches become more likely and sketched a convexity argument.

    A stronger answer

    I'd first avoid the 183 trap: what matters is pairs, not people. Assuming 365 equally likely days, the chance all n birthdays differ is 364/365 times 363/365 down to (365-n+1)/365. Each factor is about exp(-k/365), so the product is about exp(-n^2/(2*365)) = exp(-n^2/730). Setting that to 0.5 gives n^2 ≈ 730 ln 2 ≈ 504, so n ≈ 22.4, meaning 23 people. Checking n(n-1) instead of n^2, 23×22 = 506 is just over 504 and 22×21 = 462 is under, so 23 is the first to pass half. For 99% I'd set exp(-n^2/730) = 0.01, so n^2 ≈ 730 × 4.6 ≈ 3,358 and n ≈ 57 or 58. With 23 people the expected number of matching pairs is 253/365 ≈ 0.69, and non-uniform birthdays would make a match more likely, not less.

    Common mistakes on this question

    • Answering 183 from 365/2 instead of counting pairs
    • Forgetting that the expected number of matching pairs can be below one even when the chance of a match is above half
  4. Your answer: You enumerated BB, BG, GB, GG and gave 1/3 for at least one boy and 1/2 for the older child being a boy. You explained the selection effect, then counted the Tuesday-boy case as 13/27 after first thinking the day could not matter.

    Key points

    • Conditioned on the four cases; 1/3 and 1/2 (Covered)

      three cases are left, and one of them is boy-boy: one in three. ... only boy-boy and boy-girl are left, so one half.Your words, 18:49

    Common mistakes on this question

    • Answering 1/2 for both parts by treating the remaining child as independent
    • Assuming an independent detail like a weekday cannot change the answer
  5. Your answer: You chained households, piano ownership, tunings per year and tuner capacity to get about 12 full-time tuners. You sanity-checked that as low, allowed for part-time work, and gave 15 to 40 with 25 as a point estimate, plus a range and a market quote.

    Key points

    • Chained demand and capacity assumptions; checked result (Covered)

      A million people, about two and a half per household, so 400,000 households. What fraction has a piano... I'd say one in twenty, so 20,000 pianos in homes.Your words, 23:32

    Follow-up questions

    • How often are pianos tuned? Handled wellYou separated home and institutional pianos and estimated 12,000 tunings a year.
    • Sanity check Handled wellYou called 12 low, allowed for part-time tuners, and gave 15 to 40 with 25 as central.
    • Most uncertain assumption and how to narrow it Handled wellYou named the piano-ownership share and suggested sales data or a directory check.
    • How confident are you in the 25? Handled wellYou gave an 80 percent interval of 12 to 50 and noticed that errors could push the same way.

    A stronger answer

    I'd split demand and supply. A million people at about 2.5 per household gives 400,000 households; if one in twenty has a piano that's 20,000 home pianos, plus maybe 2,000 institutional ones, so about 22,000 pianos. If home pianos are tuned once every two years and institutional ones once a year, that's about 12,000 tunings a year. A tuner can do about four tunings a day, 250 days a year, so 1,000 tunings per full-time tuner, which gives 12 full-time equivalents. That feels low for a city of a million, so I'd allow for part-time tuners and repair work and give a range of 15 to 40 with 25 as a point estimate. The piano-ownership share is the most uncertain input; I'd check it against sales data or a local directory and work backwards. For a city of ten million I'd scale roughly linearly, and I'd quote a wide market like 15 bid, 45 offered because the uncertainty is large.

    Common mistakes on this question

    • Ignoring travel time when estimating how many tunings a tuner can do in a day
    • Letting the chain of assumptions produce a precise-looking number without widening to a range

What this round looked at in detail, with your words for each point, and one thing to practice.

Where the reasoning went off

  • You roll a fair die and are paid the number shown in dollars. You may roll once more and take the second result instead. What is the game worth, and what is your strategy?

    Left the path at: On the two-reroll follow-up you reused the old 3.5 threshold, which gave 4.625 instead of 4.67.

  • A family has two children and at least one is a boy. What is the probability both are boys? Now, what if you are told the older child is a boy?

    Left the path at: On the Tuesday follow-up you first said the day could not matter and kept 1/3, before counting gave 13/27.

Coaching

The few changes that matter most, with a way to practice each one.

  1. 1Correctness

    Set the threshold to the value of continuing

    On the two-reroll dice game you kept the old 3.5 threshold, so you kept a 4 when rolling on was worth 4.25.

    keep 4, 5 or 6 on the first roll, otherwise play the one-reroll gameYour words, 8:22

    How to practice: In 20 minutes, redo the die game with three rerolls, then with each reroll costing a dollar. Before any arithmetic, write the value of continuing and compare every face to it.

  2. 2Correctness

    Check pattern-matched guesses with a quick state count

    Your first answer on heads-heads came straight from 1/(1/4), and you only fixed it after a hint about the simpler case. The same reflex showed up on heads-tails, where you first said 6 before the states gave 4.

    two heads in a row has probability a quarter, so... four flips?Your words, 1:37

    How to practice: For 15 minutes, take five short waiting-time problems and before answering, say out loud whether the attempts are independent or overlap. Only then compute.

  3. 3Structured reasoning

    Turn 'I don't know' into a visible setup

    On the variance question you described the second-moment method but stopped there, so the interviewer saw no equations and no number. You had already solved the same two-state system for the mean minutes earlier.

    I don't know the number offhand and I don't think I can do it cleanly in my head right nowYour words, 6:55

    How to practice: In 15 minutes, write the two equations for E[N^2] from states E0 and E1 for heads-heads, solve them symbolically, and only then plug in numbers.

  • I don't know the number offhand and I don't think I can do it cleanly in my head right nowYour words, 6:55

    I'd set up the second-moment equations for the two states and solve them; I can't finish the arithmetic in my head, but here is the setup and a rough size for the answer.

    Shows the method and gives a bound instead of ending on 'I don't know'.

  • The day shouldn't matter, it's independent of everything, so I'd say it's still one thirdYour words, 20:34

    My instinct is that the day can't matter, so one third, but let me count the cases to check, because the extra detail changes which families qualify.

    Flags the instinct as a guess and verifies it, which is exactly what turned the answer into 13/27.

  1. Day 1Redo the die game with three rerolls; write the value of continuing before each threshold.20 min
  2. Day 2Rest day: no drills, just reread your notes on backward induction.5 min
  3. Day 3Solve five waiting-time problems, stating independence or overlap before computing.20 min
  4. Day 4Write and solve the second-moment equations for heads-heads from both states.20 min
  5. Day 5Rest day: skim the birthday-problem counting argument once.5 min
  6. Day 6Do one fresh estimation chain end to end and state a factor-of-two interval.20 min
  7. Day 7Re-run the Tuesday-boy count from scratch without looking at your notes.15 min

Pace, pauses, fillers and pitch, measured from your voice. Signals, not judgments.

Moments worth a look

  • You hesitated

    When asked “Check that against a simpler case. How long until the first single...” (Q1), you hesitated: you took 6.6 s to start (your usual 3.5 s); you sped up to 172 words per minute (your usual 141).

    • Time to start 6.6 s vs your usual 3.5 s
    • Words per minute 172 vs your usual 141
    And one over a half is two, so that matches.Your words, 1:54

    Try: Start with a one-line headline ('My approach is X because Y') and think aloud from there instead of in silence.

  • You hesitated

    When asked “Is a 4 worth keeping when rolling on is worth 4.25?” (Q2), you hesitated: you took 6.4 s to start (your usual 3.5 s); a 3.1 s pause mid-answer.

    • Time to start 6.4 s vs your usual 3.5 s
    • Longest pause 3.1 s
    I reused the old threshold; the threshold should be the value of continuing, which is now 4.25, notYour words, 8:40

    Try: Start with a one-line headline ('My approach is X because Y') and think aloud from there instead of in silence.

  • You hesitated

    When asked “Try counting it.” (Q4), you hesitated: you took 7.4 s to start (your usual 3.5 s); a 3.3 s pause mid-answer.

    • Time to start 7.4 s vs your usual 3.5 s
    • Longest pause 3.3 s
    Each child is one of 14 types, sex and day, all equally likely.Your words, 20:47

    Try: Start with a one-line headline ('My approach is X because Y') and think aloud from there instead of in silence.

Voice signals

Measured in 48 of 50 answers with audio.

  • Your pitch went up at 19 of 321 measured phrase endings.

2 of 50 answers did not have enough clear audio to measure (background noise, too little speech).

Your longest pause, 3.4 seconds, came just before you corrected heads-tails; saying 'let me redo the states' out loud turns that silence into visible method.

When a detail looks irrelevant, say the instinct and then say you will count, as you did on the Tuesday question; that reads as rigour rather than a guess.

Pace, pauses and fillers

Measured across 50 answers: average speaking rate 144 wpm, 1.0 fillers per speaking minute, average time to start answering 3.7 s, longest mid-answer pause 3.4 s.

Pace
144words/min
Fillers
1.0per min
Longest pause
3.4s
Time to first word
3.7s
Average before you started answering
Speaking time
81%
Share of answer time spent speaking
Hedges
19
Phrases like "I think" or "maybe"

Answer by answer

Pause Strong Hesitation Rushing Trailing off Rambling

The answers with a marked moment. Notes on single answers use typical speaking ranges.

Question 1

  • 0s38s
    Length
    38s
    Pace
    132
    To first word
    6.0s
    Fillers
    1
    Hedges
    2
    Pauses
    1
    • Hesitation (0s to 16s): Start came after 6.0 s, with 1 filler and 2 hedge phrases in the answer.
    • Trailing off (29s to 38s): Voice level over the last 9 s was about 7 dB lower than earlier in the answer.

Question 5

  • 0s37s
    Length
    37s
    Pace
    133
    To first word
    6.5s
    Fillers
    1
    Hedges
    2
    Pauses
    1
    • Hesitation (0s to 17s): Start came after 6.5 s, with 1 filler and 2 hedge phrases in the answer.
  • 0s27s
    Length
    27s
    Pace
    141
    To first word
    4.0s
    Fillers
    0
    Hedges
    4
    Pauses
    0
    • Hesitation (0s to 14s): Start came after 4.0 s, with 0 fillers and 4 hedge phrases in the answer.
    • Strong (0s to 27s): Steady rate (141 wpm), no pauses over 1.5 s and few fillers.
  • 19 steady stretches noted.
  • 3 hesitation episodes noted.
  • 1 trailing-off ending noted.

What Alex wrote down while listening.

  1. GapQuestion 11:37

    First answer 4 from 1/(1/4); wrong.

  2. ClaimQuestion 11:54

    Set up states E0, E1 and solved to 6.

  3. ClaimQuestion 14:02

    Derived E_n = 2E_(n-1) + 2 when asked why the pattern holds; 14 and 2^(n+1) - 2.

  4. ClaimQuestion 15:36

    Youads-tails: first guessed 6, corrected to 4 with states; explained self-overlap.

  5. GapQuestion 16:55

    Could not compute the variance for Youads-Youads; described the method only.

  6. GapQuestion 28:22

    Two rerolls: reused the 3.5 threshold, got 4.625.

  7. ClaimQuestion 28:40

    Corrected to keep 5 or 6 only: 28/6 = 4.67.

  8. ClaimQuestion 210:22

    Reroll costing $1: threshold 2.5, value about 3.83, sanity-checked.

  9. ClaimQuestion 212:43

    Unlimited $1 rerolls: tried keep>=5 (3.5), then keep>=4, value 4, 3 indifferent.

  10. ClaimQuestion 314:36

    Birthday: avoided the 183 trap, exp approximation, 23; checked 22 vs 23.

  11. GapQuestion 420:34

    Tuesday boy: first said the day cannot matter (1/3).

  12. ClaimQuestion 420:47

    Counted 27 cases and 13 favourable: 13/27.

  13. ClaimQuestion 524:56

    Piano tuners: chained households, pianos, tunings, capacity; corrected 8 a day to 4.

  14. ClaimQuestion 525:29

    Sanity-checked 12 as low, adjusted for part-time tuners: 15-40.

101 turns, word for word.

  1. Alex0:02

    Hi, I'm Alex. This is the probability round: about thirty minutes, five problems, no paper needed. Reason out loud; rough numbers are fine, and I care about how you get there as much as the answer. Before we start, what are you working on these days?

  2. You0:19

    Hi. I'm in the last year of a maths degree, with a lot of statistics. My dissertation is on stopping rules for sequential trials, so, um, when you're allowed to stop collecting data and still trust the result. And for fun I'm in a trading-game society at university, the Ravensmoor Trading Club, where we make markets on silly things for fake money, like the number of pigeons in the square at noon.

  3. Alex0:54

    Okay. What have the trading games taught you so far?

  4. You0:58

    Mostly that my first guess is usually too confident. When you quote a tight market on something you know nothing about, the people who trade with you are the ones who know more. So I've learned to quote wide first and narrow as I learn. And to do quick sums without freezing, which I hope helps today.

  5. Alex1:26

    Okay. First problem. You flip a fair coin repeatedly. What is the expected number of flips until you first see heads twice in a row?

  6. You1:37

    Um, two heads in a row has probability a quarter, so... four flips?

  7. Alex1:45

    Check that against a simpler case. How long until the first single head?

  8. You1:54

    Two. And one over a half is two, so that matches. Hmm, but for two in a row the tries overlap, a tail after one head throws away the progress, so it's not independent tries of two flips. The one-over-p formula only works for independent attempts. Let me use states. E0 is the expected flips from scratch, E1 after one head. From scratch I flip once: half the time I get a head and go to E1, half the time a tail and I'm back at E0. So E0 is 1 plus half E1 plus half E0. From E1, I flip once: a head finishes, a tail sends me back to the start. So E1 is 1 plus half times zero plus half E0. Substituting, E0 is 1 plus half of 1 plus a quarter E0 plus half E0, so 1.5 plus three quarters E0. A quarter of E0 is 1.5, and E0 is 6.

  9. Alex3:02

    Sanity check?

  10. You3:04

    It should be more than four, because of the restarts, and six is more than four. Another way: you need a head first, that's two flips on average, then the next flip is a head half the time, and a miss costs you the whole thing again. If I simulate it roughly in my head, it's around six. And for E1, it's 1 plus 3, so 4, which is also bigger than 2. It hangs together.

  11. Alex3:41

    What about three heads in a row?

  12. You3:44

    Same states with one more. The pattern from one and two heads is 2 and 6, each one is double the previous plus two, so three heads is 14.

  13. Alex4:00

    Why double plus two?

  14. You4:02

    Um, to get n in a row, first get n minus one in a row, that's E of n minus one. Then flip once more: half the time it's heads and I'm done, half the time it's tails and I start over from zero, with E n still to go. So E n is E n minus one plus 1 plus half E n. Half E n equals E n minus one plus 1, so E n is two E n minus one plus two. Okay, so it's not just a pattern, it's the recursion. Good, I was a bit uneasy about that.

  15. Alex4:58

    And the general formula for n in a row?

  16. You5:01

    If I add two to both sides, E n plus 2 is two times E n minus one plus 2, so E n plus 2 doubles each time, starting from E0 plus 2, which is 2. So E n plus 2 is two to the n plus one, and E n is two to the n plus one, minus two. For n equal to 2 that's 8 minus 2, 6. For three, 16 minus 2, 14.

  17. Alex5:31

    Now the expected number of flips until you first see heads followed by tails.

  18. You5:36

    Heads then tails. Also two specific flips, so... also 6? Hmm, wait, wait. Let me do the states again. From scratch, flip until I get a head, that's 2 on average. Once I have a head, a tail finishes it, and another head doesn't hurt me, I'm still sitting on a head. So I never go back to the start. From there it's waiting for a tail, another 2. So 4, not 6.

  19. Alex6:21

    Why is it different from heads-heads?

  20. You6:23

    Because with heads-heads, a failure throws away the progress: a tail after a head puts me at zero. With heads-tails, a failure, another head, keeps me where I was. The pattern overlaps with itself for heads-heads and not for heads-tails, I think that's the general idea, the self-overlap is what makes it slower.

  21. Alex6:52

    Variance of the number of flips for heads-heads?

  22. You6:55

    Um. I'd set up the same states for the second moment, E of N squared from each state, and solve the linear equations. I don't know the number offhand and I don't think I can do it cleanly in my head right now. I'd guess it's large, the distribution has a long tail, maybe a standard deviation around the same size as the mean.

  23. Alex7:35

    Next. You roll a fair die and are paid the number shown in dollars. You may roll once more and take the second result instead. What is the game worth, and what is your strategy?

  24. You7:48

    Work backwards from the last decision. If I reroll, I get a fresh roll, worth 3.5 on average. So I keep anything above 3.5: keep 4, 5 or 6, and reroll 1, 2 or 3. Half the time I keep, and the average of 4, 5 and 6 is 5, so that's 2.5. Half the time I reroll and get 3.5 on average, that's 1.75. So 2.5 plus 1.75, 4.25 dollars.

  25. Alex8:17

    What if you may reroll up to two times?

  26. You8:22

    Then I use the same rule again: keep 4, 5 or 6 on the first roll, otherwise play the one-reroll game. That's 2.5 plus half of 4.25, so 4.625.

  27. Alex8:35

    Is a 4 worth keeping when rolling on is worth 4.25?

  28. You8:40

    Oh. No, it isn't. I reused the old threshold; the threshold should be the value of continuing, which is now 4.25, not 3.5. So I only keep a 5 or a 6. That's 5 plus 6 over 6, plus four sixths of 4.25. 11 sixths plus... four times 4.25 is 17, so 17 sixths. 28 sixths, about 4.67.

  29. Alex9:16

    Sanity check?

  30. You9:18

    It has to be more than 4.25, since an extra option can't hurt, and less than 6. And the jump is smaller than from 3.5 to 4.25, which makes sense, each extra roll is worth less. 4.67 fits.

  31. Alex9:37

    What's the general principle behind the threshold?

  32. You9:40

    Backward induction. At every decision, compare what you have now with the expected value of continuing optimally from there, and you can only compute that from the end backwards. Each extra reroll raises the value of continuing, so the threshold goes up. It's the same thing I do in my dissertation, actually, with stopping a trial early, just with dice instead of patients.

  33. Alex10:12

    What if each reroll costs a dollar? One reroll.

  34. You10:22

    Then rolling on is worth 3.5 minus 1, so 2.5. So I keep anything at least 3, and reroll a 1 or a 2. Value: keeping 3, 4, 5, 6 gives 18 over 6, that's 3. Plus two sixths times 2.5, which is, um, 5 sixths, about 0.83. So about 3.83.

  35. Alex10:47

    Check?

  36. You10:49

    Without rerolling the game is worth 3.5, so 3.83 is above that but below the free version, 4.25. And you only reroll the really bad rolls now, which makes sense when it costs something. Fits.

  37. Alex11:08

    How much would you pay to play the original game, once?

  38. You11:12

    If I'm risk neutral, up to 4.25. In practice a bit less, to have an edge, and it's only once, so the variance is large compared to the stake. Maybe 4 dollars. If it were a thousand times I'd pay close to 4.25.

  39. Alex11:36

    Now unlimited rerolls, each costing a dollar. What's it worth?

  40. You11:45

    Okay. Now the game looks the same after every roll, so the value V is the same every time. If I reroll I get V minus 1. So I keep a roll if it's at least V minus 1. Guess a threshold and check it. Keep 5 or 6: V is 11 over 6 plus four sixths of V minus 1. So V minus two thirds V is 11 sixths minus 4 sixths, a third of V is 7 sixths, V is 3.5. Hmm. That's no better than not playing on.

  41. Alex12:41

    What are you thinking?

  42. You12:43

    That keeping only 5 and 6 is too picky, I'm paying too much in rerolls. Try keep 4 and up: V is 15 over 6 plus a half of V minus 1. Half of V is 2.5 minus 0.5, 2, so V is 4. Then continuing is worth V minus 1, which is 3, so a 4 is worth keeping, and a 3 is exactly indifferent. Keep 3 and up gives the same: 18 sixths plus a third of V minus 1, two thirds V is 3 minus a third, V is 4. So it's worth 4, keep anything 4 or above, and it doesn't matter what you do with a 3.

  43. Alex13:49

    Next. How many people do you need in a room so that the chance that two share a birthday exceeds 50%?

  44. You13:57

    My gut says something like 183, half of 365, but I know that's the classic trap, because it's pairs that matter, not people. With n people there are n squared over two pairs. Let me do it properly. I'll assume 365 equally likely days, no leap years, no twins.

  45. Alex14:25

    Go on.

  46. You14:36

    The probability that all birthdays are different with n people is 364 over 365, times 363 over 365, and so on, down to 365 minus n plus 1. Each factor is 1 minus k over 365, which is about e to the minus k over 365 for small k. So the product is e to the minus the sum of k, and the sum is n times n minus 1 over 2, roughly n squared over 2. So it's about e to the minus n squared over 730. Set that to a half: n squared over 730 is ln 2, 0.69. So n squared is about... 730 times 0.69, um, 700 times 0.69 is 483, plus 21, 504. Square root of 504, about 22.4. So 23 people.

  47. Alex15:32

    Is the approximation good enough to pick 23 over 22?

  48. You15:36

    Hmm. It's borderline. If I use n times n minus one instead of n squared, then 23 times 22 is 506, which is just over 504, and 22 times 21 is 462, under. So 23 is the first one past a half. The exponential approximation slightly overestimates each factor, but I don't think it moves it by a whole person. I'd want to check it exactly, but I'm fairly confident.

  49. Alex16:13

    With 23 people, what's the expected number of pairs sharing a birthday?

  50. You16:23

    23 choose 2 pairs, that's 23 times 22 over 2, 253. Each pair matches with probability 1 over 365. 253 over 365 is about 0.69. Oh, that's ln 2 again, which makes sense, it's the same exponent as before. So on average less than one matching pair, even though the chance of at least one is just over half.

  51. Alex16:56

    Does ignoring leap years matter?

  52. You16:58

    Barely. February 29th has about a quarter of a day's weight, so it's like 365.25 days with one tiny day. That makes matches very slightly less likely, but it won't move 23. I'd ignore it.

  53. Alex17:17

    What if we want 99%?

  54. You17:29

    Then e to the minus n squared over 730 is 0.01. ln of 100 is about 4.6. So n squared is 730 times 4.6, um, 730 times 4 is 2,920, plus 730 times 0.6, 438, so 3,358. Square root... 58 squared is 3,364. So about 57 or 58. I can't tell which one without doing it exactly.

  55. Alex17:58

    How does the answer change if birthdays are not uniform?

  56. You18:02

    It goes down. Uneven days make collisions more likely, because people pile up on the popular days. Uniform is the worst case for matching. I can't prove it right now, but I think it's a convexity argument, the chance of a match for a pair is the sum of p squared over days, and that's smallest when all the p are equal.

  57. Alex18:37

    Next. A family has two children and at least one is a boy. What is the probability both are boys? Now, what if you are told the older child is a boy?

  58. You18:49

    Assuming boys and girls are equally likely and independent. The cases are boy-boy, boy-girl, girl-boy, girl-girl, ordered by age, each a quarter. At least one boy removes girl-girl, so three cases are left, and one of them is boy-boy: one in three. If the older one is a boy, only boy-boy and boy-girl are left, so one half.

  59. Alex19:17

    Why does the second piece of information change the answer?

  60. You19:21

    Because it points at one specific child. At least one boy keeps both mixed cases, the older one is a boy keeps only one of them. Once you know which child is the boy, the other one is just a fair coin.

  61. Alex19:43

    What are you assuming about how you learned there's a boy?

  62. You19:48

    Hmm, good point. I'm assuming the information is 'we checked the family and it has at least one boy'. If instead you met one of the children at random and it happened to be a boy, then it's like the older-child case, you've picked out a specific child, and the answer is a half. So the answer depends on how the information was produced, not just what it says.

  63. Alex20:26

    What if you are told at least one is a boy born on a Tuesday?

  64. You20:34

    Hmm. The day shouldn't matter, it's independent of everything, so I'd say it's still one third.

  65. Alex20:43

    Try counting it.

  66. You20:47

    Okay. Each child is one of 14 types, sex and day, all equally likely. Pairs with at least one Tuesday boy: everything minus the pairs with no Tuesday boy, 14 squared minus 13 squared, 196 minus 169, 27. Both boys with at least one Tuesday boy: each is one of 7 boy types, so 7 squared minus 6 squared, 49 minus 36, 13. So 13 over 27. Huh, so it does matter. The Tuesday detail almost picks out one child, so it moves the answer toward one half.

  67. Alex21:41

    And if it were a boy born on the first of January?

  68. You21:53

    Same logic with 365 days instead of 7. That's even more specific, so it's very close to a half. By the same formula: two times 365 minus 1 over four times 365 minus 1, so 729 over 1,459. Just under a half.

  69. Alex22:16

    Does that formula give 13 over 27 for Tuesday?

  70. You22:19

    Two times 7 minus 1 is 13, four times 7 minus 1 is 27. Yes. And with one day it's 1 over 3, which is the original problem. Nice, so it goes from a third to a half as the detail gets more specific.

  71. Alex22:44

    How would you explain the Tuesday result to someone who thinks it's a trick?

  72. You22:49

    I'd say: the extra detail changes how many families fit the description. Families with two boys have two chances to contain a Tuesday boy, families with one boy have only one. So two-boy families are overrepresented among the ones that fit, almost twice as much, and that pushes it toward a half. It's not about Tuesday, it's about how the information was selected.

  73. Alex23:24

    Last one. Estimate how many piano tuners work in a city of one million people. Talk me through your assumptions.

  74. You23:32

    Okay. Demand side first, then supply. A million people, about two and a half per household, so 400,000 households. What fraction has a piano... I'd say one in twenty, so 20,000 pianos in homes. Plus schools, churches, concert halls, music schools, maybe another 2,000. So round it to 22,000 pianos.

  75. Alex24:02

    How often are they tuned?

  76. You24:04

    Officially once or twice a year, but a lot of home pianos are never tuned. Say on average once every two years at home and once a year for the institutional ones. So 10,000 plus 2,000, call it 12,000 tunings a year. Um, institutional ones maybe more, concert pianos get tuned before every concert, but there are very few of them, so I'll ignore that.

  77. You24:37

    Oh, and grands versus uprights, grands are usually tuned more often, and the ones in concert halls are tuned—

  78. Alex24:48

    Keep it to the count.

  79. Alex24:51

    Supply side?

  80. You24:56

    A tuning takes about an hour and a half, plus travel. So maybe eight a day... no, that's too many with travel, that's twelve hours of tuning alone. Four a day is more realistic. 250 working days, so a thousand tunings a year per full-time tuner. 12,000 over 1,000 is 12 tuners.

  81. Alex25:28

    Sanity check?

  82. You25:29

    Hmm. Twelve feels low for a city of a million. Many tuners are part-time, and they also repair and restore pianos and teach, so the headcount would be higher than the full-time equivalent, maybe double. And my one in twenty might be low for an older city. So I'd say somewhere between 15 and 40, with 25 as my point estimate.

  83. Alex26:07

    Which assumption is the most uncertain and how would you narrow it?

  84. You26:12

    The share of households with a piano. It could be one in ten or one in fifty depending on the city, and everything scales linearly with it. I'd narrow it with piano sales or ownership survey data, or just count the tuners listed in a local directory and work backwards to check the whole chain. If the directory says 60, then one of my assumptions is off by a factor of two, probably that one.

  85. Alex26:50

    What changes for a city of ten million?

  86. You26:53

    Roughly linear, so about ten times, 150 to 400. Maybe a bit less per person, big cities have more small flats with no room for a piano, but tuners also travel less between jobs in a dense city, so each one does more tunings. I'd still say roughly ten times.

  87. Alex27:20

    How confident are you in the 25?

  88. You27:22

    Not very. I'd say a factor of two either way is plausible, so maybe an 80 percent interval of 12 to 50. Every step in the chain is a guess, but at least the errors partly cancel: if I overestimated the pianos, I probably also overestimated how often they're tuned... no, that makes it worse, they go in the same direction. So the interval should be wider, not narrower.

  89. Alex28:01

    If you had to make a market on the number, what would you quote?

  90. You28:07

    Given how uncertain the piano share is, wide. Something like 15 bid, 45 offered. And I'd lean higher rather than lower, because the part-time effect only pushes it up.

  91. Alex28:24

    Someone sells to you at 15 straight away. What now?

  92. You28:28

    Then they probably think it's below 15, maybe they've looked it up. I'd lower my market, maybe 10 at 25, and be careful about buying more from them. Unless I think they're just testing me, but the first rule in the club is that the person who trades fast usually knows something.

  93. Alex28:57

    Okay. That's the five. We have a few minutes left. Any questions for me?

  94. You29:02

    Yes. How much of the day-to-day uses this kind of quick probability, versus longer research?

  95. Alex29:11

    It depends a lot on the desk and the role. Quick reasoning like this comes up daily in some seats and rarely in others. The hiring team can tell you about the specific role.

  96. You29:24

    Okay. And, um, is the next round more coding or more of this?

  97. Alex29:32

    That depends on the process for the role. The recruiter will have the schedule.

  98. You29:38

    And, um, how do you usually find out whether someone just memorised these puzzles?

  99. Alex29:46

    Mostly with follow-ups and variations, like the ones today. A memorised answer doesn't extend well.

  100. You29:52

    Fair. Okay, thank you, that's all.

  101. Alex29:58

    Thanks, that's the round. The report will be ready in a few minutes.

Mockich is a practice tool. Scores and delivery signals are guidance for your preparation, not a prediction of a real hiring decision.

Start another interview
Sample report · Mockich