Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Case Study · Razorpay

Razorpay Product Manager Interview Questions India 2026

Razorpay PM interviews skew operational.

By the HireStepX editorial team · How we source and label this

Questions4
Rounds4
Intense1 of 4
FrameworkPricing-first PM
Try it · Razorpay question 1 of 4
Standard

How would you price a new pricing tier targeted at D2C brands doing ₹50L–5Cr annual GMV?

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect questions about pricing for new merchant tiers, expansion to D2C brands, or feature priority for scale. Indian fintech context matters: knowing UPI vs cards economics is implicitly assumed. The Razorpay PM loop runs 4–5 rounds covering product thinking, case study, technical literacy, and a behavioral culture round. Candidates who treat it like a standard product company PM interview routinely underperform: Razorpay wants PMs who understand merchant economics and payment flows, not just user experience frameworks. The culture round tests merchant empathy the same way the engineering culture round does: can you explain a feature decision in terms of what a merchant actually experiences when a payment fails?

Practice questions

  1. 01

    How would you price a new pricing tier targeted at D2C brands doing ₹50L–5Cr annual GMV?

    Standard
    Practise
  2. 02

    Design an onboarding flow that gets a small-business owner from sign-up to accepting their first payment as fast as possible. What do you cut, and what do you keep?

    IntenseRazorpay design rounds test B2B/fintech onboarding: reducing time-to-value, compliance friction (KYC), and trust for SMB users.
    Practise
  3. 03

    How do you design a complex dashboard (payments, refunds, settlements, disputes) so a non-technical merchant can understand it at a glance?

    StandardRazorpay probes information design for dense financial data: hierarchy, progressive disclosure, and clarity for non-experts.
    Practise
  4. 04

    Walk me through how you'd approach designing for error and edge cases in a payment flow, where failures directly affect trust and money.

    StandardRazorpay tests error-state and edge-case design in a high-stakes money context: clear recovery, reassurance, and never losing the user.
    Practise
Prep notes

How to walk in ready.

The typical Razorpay recruitment process has 5 stages: Recruiter screen: background, product sense, and fintech context (30 min) → Product case round: pricing for new merchant tiers, D2C expansion, or feature prioritization → Technical literacy round: system design familiarity, API understanding, and data analysis → Culture round: merchant empathy, ownership stories, speed-vs-correctness trade-offs → Hiring manager: compensation, role expectations, and product roadmap discussion.

Razorpay typically conducts 4 interview rounds: Product Case Round (45–60 min): Pricing for new merchant tiers, D2C expansion, or feature prioritisation. Indian fintech context (UPI vs cards economics, merchant working capital) is implicitly assumed: candidates who treat it as a standard consumer PM interview underperform; Technical Literacy Round (45 min): System design familiarity (how does an API idempotency key work?), data analysis, and payment-flow understanding at a conceptual level; Culture Round (30 min): Merchant empathy + ownership. The evaluative question is whether you can explain a feature decision in terms of what a merchant experiences when a payment fails; Hiring Manager Round (30 min): Role expectations, product roadmap alignment, compensation discussion.

HireStepX recommends the Pricing-first PM framework for this type of interview: Customer segment → willingness-to-pay → competitor anchor → price ladder → roll-out.

Razorpay design rounds test B2B/fintech onboarding: reducing time-to-value, compliance friction (KYC), and trust for SMB users.

Razorpay probes information design for dense financial data: hierarchy, progressive disclosure, and clarity for non-experts.

Razorpay tests error-state and edge-case design in a high-stakes money context: clear recovery, reassurance, and never losing the user.

The Razorpay PM loop typically runs 4–5 rounds: Recruiter screen (background, product sense, fintech context), Product case round (pricing for new merchant tiers, D2C expansion, or feature prioritisation), Technical literacy round (system design familiarity, API understanding, data analysis), Culture round (merchant empathy, ownership stories, speed-vs-correctness trade-offs), and Hiring manager round (compensation, role expectations, product roadmap).

Razorpay PM interviews skew operational, not just product-strategic. Indian fintech context matters: knowing UPI vs. cards economics is implicitly assumed. Candidates who treat it like a standard consumer PM interview routinely underperform. The culture round tests merchant empathy: can you explain a feature decision in terms of what a merchant actually experiences when a payment fails?

Practice

Rehearse the room before you enter it.

Run a mock Razorpay interview and get scored feedback on every answer.