Build a Consumer UPI App round·Product Management·Medium·20 min

Razorpay PM Interview — Build a Consumer UPI App

20 min · 1 credit · scorecard at the end

Take this on a laptop or desktop — not your phone. The live interview needs a full screen and keyboard (including a sketch whiteboard on coding rounds). You can buy now, but start it from a computer.

ZeroPitch Research Desk

Updated 2026-05-16 · Newly added · be among the first to take it

Field: Product Management
Company: Razorpay
Role: Product Manager
Duration: 20 min
Difficulty: Medium
Completions: New
Updated: 2026-05-16

How to prepare

What this round tests, what strong and weak answers sound like, and the traps to sidestep.

What this round is about

Topic focus. You decide whether Razorpay should build its own consumer UPI app, the kind people use to pay a friend or scan a shop QR, specifically to defend the merchant payment volume that flows through Razorpay today.
Conversation dynamic. A senior Razorpay product leader runs this as a working strategy discussion, not a quiz, and will interrupt to pull a rambling answer back to the decision.
What gets tested. Whether you clarify the goal before solving, reason inside real Indian payments economics, and commit to one recommendation you can defend.
Round format. A single twenty-minute spoken case with a warm-up, a core decision, a pressure phase, and a short reflection.

What strong answers look like

Goal before solution. You state explicitly whether the objective is defending merchant volume, opening new revenue, or capturing data, before you choose build or not build.
Economics named unprompted. You bring up zero MDR yourself and reason about why a consumer app cannot pay for itself through the transfer.
Sized, not just argued. You attach at least one number, such as the share of Razorpay merchant volume genuinely at risk, even if it is rough.
Decisive under pushback. You commit to one recommendation with a success metric and a denominator, and you hold it when challenged.

What weak answers look like (and how to avoid them)

Solving before scoping. Jumping to build or not build without clarifying the objective. Fix it by asking what the decision is for in your first response.
Revenue logic that never closes. Discussing a consumer app while ignoring that UPI has no fee. Fix it by naming zero MDR and routing monetisation through adjacent products or merchant retention.
Greenfield illusion. Treating consumer UPI as open when PhonePe and Google Pay already hold most volume. Fix it by acknowledging the duopoly and reframing around merchants.
Endless hedging. Refusing to commit to either recommendation. Fix it by stating one call and defending it.

Pre-interview checklist (2 minutes before you start)

Recall the economics. Have it ready that UPI is zero MDR and a consumer app earns nothing on the transfer.
Identify the real asset. Remember Razorpay's strength is its merchant base and Turbo UPI, not consumer reach.
Think of the alternatives. Have deepening merchant acquiring, Turbo UPI, and partnering ready as options against building.
Pull up a sizing handle. Be ready to put one rough number on how much merchant volume is actually at risk.
Re-read the goal question. Plan to ask whether the aim is merchant defence, revenue, or data before you decide.

How the AI behaves

Probes every claim. It asks for the number behind a headline and the denominator behind a metric, not the slogan.
No mid-interview praise. It will not say great answer or tell you how you are doing; it acknowledges content and pushes.
Interrupts on hand-waving. It pulls a generic or rambling answer back to the specific decision.
Raises real objections. It challenges the revenue model, the distribution path, and the B2C gap the way a real Razorpay leader would.

Common traps in this type of round

Framework recitation. Naming a strategy framework instead of using Razorpay-specific payment facts.
Metric with no denominator. Quoting a success number without saying what it is measured against.
Single-option reasoning. Evaluating only build and never weighing acquiring, Turbo UPI, or partnership.
B2C as solved. Assuming consumer growth and support are easy because the tech exists.
Ignoring the ceiling. Forgetting the discussed per-app volume cap that limits any new entrant's upside.
Goal drift. Answering a revenue question when the goal was merchant defence, because the objective was never pinned.

How to use the canvas in this round

Two-by-two grid at the top. Map consumer-app attractiveness against Razorpay fit, place the build path inside it, and ring the chosen quadrant so the call is visible before you argue it.
Competitive landscape map. Place PhonePe, Google Pay, Paytm and Razorpay as anchors on a separate area of the surface, with arrows showing where merchant volume is at risk and where consumer habit already sits.
Options scoring matrix. Lay the four candidate paths (build a consumer app, deepen Turbo UPI, expand merchant acquiring, partner) as rows with cost and merchant-defence pace written beside each, and the kept row ringed.
Sequencing strip across four quarters. Lay out the four-quarter horizon as a strip with the milestone at each phase, so the timing of the merchant-defence bet is visible to leadership at a glance.
Capital allocation panel on the right. Split the spend across build, Turbo UPI, acquiring and partner pilots in plain numbers, with the killed option struck through so the chosen trade-off is unambiguous.

Reference

The full breakdown

How you're scored, the questions candidates ask most, and the research this interview is built on. Skim it — or just start the interview.

Interview framework

You will be scored on these 7 dimensions. The full rubric with definitions is below.

Objective Framing Before Solving

Whether you pin what the decision is actually for, defending merchants versus revenue versus data, before you argue build or not build.

17%

Indian Payments Economics Reasoning

Whether you reason in real UPI economics, especially zero MDR and the consumer duopoly, rather than generic product-strategy talk.

19%

Decision Sizing Discipline

Whether you attach at least one number or denominator to the decision and any success metric, instead of staying purely qualitative.

14%

Alternative Option Evaluation

Whether you weigh the build option against credible alternatives like deeper acquiring, Turbo UPI, or partnering, not single-option reasoning.

15%

Decisiveness Under Pushback

Whether you commit to one recommendation and hold it while absorbing hard objections, instead of hedging to the end.

13%

Recommendation Self-awareness

Whether you can name the weakest part of your own call and what evidence would change it.

Canvas Options Matrix Visualization

Whether you externalize the call onto the board as a two-by-two, an options scoring grid with the pick ringed, a competitor map and a capital allocation panel, instead of arguing it verbally.

15%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

Common questions

What does the Razorpay PM product-strategy round actually test?

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.

How should I structure my answer in this round?

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.

What are the most common mistakes candidates make here?

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.

How is this AI interviewer different from a real Razorpay interviewer?

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.

How is my performance scored in this mock interview?

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.

What should I do in the first two minutes of this round?

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.

How do I handle it if the interviewer says the consumer UPI market is already won?

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.

What does a strong answer in this round sound like?

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.

Do I need to recommend building the app, or is not building also acceptable?

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.

How much payments domain knowledge do I need for this Razorpay round?

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.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.