Razorpay PM Interview — Build a Consumer UPI App

It tests whether you can take an ambiguous build-or-not strategy question and turn it into a clear decision. The interviewer wants you to clarify the goal first, defending merchant volume versus new revenue versus data, then reason inside real Indian payments economics like zero MDR and the PhonePe and Google Pay consumer duopoly. You are evaluated on whether you size the decision with at least one number, weigh the build option against credible alternatives like deepening merchant acquiring or Turbo UPI, and commit to one recommendation you can defend under pushback rather than hedging.

Start by clarifying what success means before you decide anything. State explicitly whether the objective is defending merchant payment volume, opening new revenue, or capturing first-party data, because the answer changes with the goal. Then lay out the realistic options, build a standalone consumer app, deepen merchant acquiring and Turbo UPI, or partner. Evaluate each against the economics and Razorpay's actual capabilities. Close with one decisive recommendation, a success metric with a stated denominator, and the main risks. Avoid reciting a framework name; use payment-domain facts instead.

The biggest one is jumping straight to build it or do not build it without clarifying the objective. Another is discussing a consumer app without ever naming zero MDR, so the revenue logic never closes. Many candidates treat consumer UPI as a greenfield even though PhonePe and Google Pay already hold most of the volume. Others quote a success metric with no denominator, evaluate only the build option, or hedge to the very end without committing. Reciting textbook frameworks instead of using Razorpay-specific facts also reads as weak.

It behaves like a real mid-level Razorpay product leader, but it is consistent and never tires. It probes every claim, asks for the number behind a headline, and raises the same objections a real interviewer would about economics, distribution, and the B2C gap. It will not give you mid-interview praise or tell you how you are doing. It interrupts rambling to pull you back to the decision. Unlike a human, it gives every candidate the same depth of probing and produces a transcript-backed scorecard afterwards.

Scoring is derived from observable behaviour in the transcript, not delivery style or accent. The dimensions reward clarifying the objective before solving, reasoning in real Indian payments economics, sizing the decision with a number, comparing the build option against credible alternatives, committing to a recommendation under pushback, and defending it without hedging. Each dimension has anchored bands from critical failure to exceptional. You receive a written report that names the specific moment your business case stopped closing and what would have strengthened it.

Do not start solving. Spend the first two minutes pinning down what the decision is really for. Ask whether the goal is to defend the merchant volume flowing through Razorpay, to open a new revenue line, or to capture consumer data, and confirm the time horizon leadership cares about. Surface the obvious constraint early, that UPI has no transaction fee, so a consumer app cannot pay for itself through payments. Setting the goal and the economic frame early is exactly what separates strong candidates from those who get screened out.

Acknowledge it directly rather than arguing. PhonePe and Google Pay genuinely hold most consumer UPI volume, so do not pretend entry is open. Reframe the question around what Razorpay is actually trying to protect, which is merchant payment volume, not consumer wallet share. Then argue from Razorpay's real asset, its merchant base and surfaces like Turbo UPI, and show how defending merchants might not require owning a consumer app at all. The interviewer is testing whether you can hold a decisive line while absorbing a hard fact.

A strong answer opens by clarifying the goal and the horizon, then states the economic reality of zero MDR and the consumer duopoly without being prompted. It sizes the decision with at least one rough number, such as the share of Razorpay merchant volume genuinely at risk. It compares building a consumer app against deepening merchant acquiring, doubling down on Turbo UPI, and partnering. It ends with one clear recommendation, a success metric with a denominator, and the top two risks, and it holds that recommendation when the interviewer pushes back.

Either recommendation can score well. The round does not have a single correct answer; it tests the quality of the reasoning and the decisiveness behind it. Recommending not to build, and instead defending merchant volume through Turbo UPI and deeper acquiring, is often the stronger answer because it respects the zero-MDR economics and the B2C gap. But a build recommendation can also score well if you justify the capital, the distribution path, and the metric. What fails is refusing to commit to either.

You need working fluency, not encyclopaedic depth. You should know that UPI is zero MDR, that PhonePe and Google Pay dominate consumer volume, that Razorpay is a business-to-business payment aggregator and TPAP on the merchant side, and that Turbo UPI is its in-app checkout lever. You should understand that consumer apps monetise adjacent products like lending rather than the transfer. Beyond that, the interviewer cares more about how you reason with these facts than about reciting NPCI circulars verbatim.