PhonePe PM Interview — UPI Transactions Per Day

It tests whether you can size an unknown number structurally while someone challenges you. The prompt is to estimate UPI transactions processed across India on a typical weekday. The interviewer is not grading the final number. They are watching whether you clarify scope first, state assumptions with reasons attached, build a decomposition they can inspect segment by segment, use round numbers on purpose, and reconcile the result against something you already know. Recovery under interruption is weighted heavily, because the round is designed to interrupt you mid-calculation and see whether your structure survives.

Start by pinning the scope out loud: what counts as a transaction, India only, a typical weekday rather than a salary day or weekend. Then choose a path from a population or from a known anchor, and break it into segments that do not overlap and leave nothing out. Compute with round numbers and say you are rounding on purpose. State each assumption with one sentence of reasoning, not just a figure. At the end, reconcile against a second route or a number you know. Narrate every step so your logic can be inspected.

The biggest one is multiplying numbers before defining what a transaction even is or which day you mean. Close behind: going silent for several seconds when interrupted, then stacking more decimal precision instead of re-checking the business question. Others give one aggregate guess with no structure to inspect, produce a final number and stop with no sanity check, or defend a clearly-off assumption rigidly after being given a chance to revise. Using unrounded numbers like 365 and compounding small errors silently also reads poorly.

It behaves like a real payments product lead: it interrupts deliberately, challenges shaky assumptions, and refuses to praise mid-round. The difference is consistency and feedback. It probes every assumption with the same rigor every time, never reacts to delivery style or accent, and produces a transcript-backed scorecard afterward that names the exact assumption you could not ground and the moment your structure broke. A real interviewer gives you a yes or no weeks later with no detail; this gives you the specific failure point immediately.

Your transcript is scored on observable behaviours, not on the closeness of your final number. The scorecard looks at whether you scoped the question before computing, whether your segmentation can be inspected without overlaps or gaps, whether your assumptions carry stated reasoning, how you recovered when an assumption was challenged, and whether you reconciled the answer against a known anchor. Each dimension has its own score and the report quotes the exact moments that moved it. Process and recovery outweigh arithmetic precision throughout.

Do not start multiplying. Spend the first minute defining the question aloud: confirm India only, confirm a typical weekday rather than a salary day or festival, and state what you are counting as a single transaction, including whether failed payments or autopay mandates count. Then say which route you will take and why before you write a single number. This early scoping is the first thing the interviewer listens for, and candidates who skip it rarely recover the impression later in the round.

Treat the interruption as the actual test. Do not freeze and do not defend rigidly. Acknowledge the specific assumption being challenged in one sentence, say whether you will hold or revise it and why, adjust that one number, and explicitly return to where you were in your structure so the thread is not lost. The interviewer is watching whether your decomposition survives a shock. Calm revision that keeps the structure intact scores far higher than either silence or stubborn defense of a weak number.

It ends with a reconciliation, not just a number. A strong candidate says something like: my bottom-up route gives roughly this many transactions a day, and as a check, NPCI's published monthly volume divided by about thirty days lands in the same order of magnitude, or PhonePe alone is around 46 percent of volume so the national figure should be roughly double PhonePe's known number. They flag if the two routes diverge by more than two or three times and explain which assumption is the likely culprit, rather than presenting one figure with false confidence.

Because at PhonePe a payments PM constantly makes calls on incomplete data, and the round is a proxy for that. The interviewer is described by past candidates as fixed on hearing structured reasoning and willing to push hard on assumptions. Defending a number means giving the reasoning behind it, not repeating it louder. Each challenge is a chance to show you can separate a defensible assumption from a weak one and revise the weak ones without losing the overall logic, which is exactly the on-the-job behaviour they are screening for.

No. You can pass entirely on structure and reasoning without memorising figures. That said, knowing a rough anchor helps your sanity check land: UPI runs well over 700 million transactions a day nationally, NPCI publishes the official monthly volume, and PhonePe plus Google Pay are roughly 80 to 85 percent of all UPI volume. Use such an anchor only as a reconciliation at the end, never as a substitute for building your own estimate. An answer that quotes a memorised number without a derivation behind it scores worse than a well-reasoned estimate.