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

Razorpay Engineering Interview Questions India 2026

Razorpay engineering rounds love production scenarios: UPI failure spikes, NPCI rate limits, settlement reconciliation, idempotent payment retries.

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

Questions6
Rounds4
Intense6 of 6
FrameworkReliability-first
Try it · Razorpay question 1 of 6
Intense

We're seeing UPI failure rates spike at 9pm on weekends. How would you debug, and what's your hypothesis?

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

Be specific. Generic 'I'd add caching' answers don't land here; they want to know which cache, what TTL, what happens on cache stampede. The hiring loop runs 4–5 rounds and pays well for the bar it sets: SDE-1 at ₹15–25 LPA with meaningful equity from a pre-IPO company. The culture round is harder to fake than most: interviewers listen for genuine conviction about ownership, not keyword alignment. What distinguishes strong Razorpay candidates is being able to explain a technical choice: say, why you'd design an idempotent API a certain way: in terms of what a merchant actually experiences when a payment fails at checkout.

Practice questions

  1. 01

    We're seeing UPI failure rates spike at 9pm on weekends. How would you debug, and what's your hypothesis?

    IntenseRazorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.
    Practise
  2. 02

    Walk me through how you'd build idempotency into a payment retry system. What happens if the network drops mid-callback?

    Intense
    Practise
  3. 03

    Design Razorpay's settlement system. Money flows from acquirer → aggregator → merchant. Where can it break and how do you reconcile?

    IntenseSettlement = where Razorpay loses real money. Probe expected: T+0 vs T+1, partial captures, refund-of-refund, NPCI mandate edge cases.
    Practise
  4. 04

    Design a payment gateway that routes transactions across multiple banks and handles failures. How do you maximise success rate?

    IntenseRazorpay system-design rounds are payments-native. Strong answers cover smart routing across acquirers, retries, idempotency, and reconciliation.
    Practise
  5. 05

    Design the settlement system that reconciles payments and pays out to merchants on schedule. How do you guarantee no money is lost or double-paid?

    Intense
    Practise
  6. 06

    Design a system to handle UPI payment callbacks and status updates that can arrive late, out of order, or twice. How do you keep state consistent?

    IntenseRazorpay probes UPI-specific realities: asynchronous callbacks, duplicate and delayed notifications, and idempotent state transitions.
    Practise
Prep notes

How to walk in ready.

The typical Razorpay recruitment process has 6 stages: Recruiter screen: background, motivation, and salary expectations (30 min) → Online coding round: 2 DSA problems, 60 minutes (medium-hard difficulty) → Technical round 1: DSA + problem decomposition and code quality review → Technical round 2: System design with payments-specific architecture (SDE-2+ roles primarily) → Culture round: Values alignment and ownership stories; evaluates genuine conviction not keyword alignment → Hiring manager round: Final bar raiser and compensation discussion.

Razorpay typically conducts 4 interview rounds: Online Coding Round (60 min): 2 medium-hard DSA problems. Standard filter; Technical Round 1: DSA + Code Quality (60 min): One harder problem with problem decomposition and code review discussion. Razorpay expects production-readiness thinking: how would this code behave in a payment system?; Technical Round 2: System Design (60 min, SDE-2+): Payments-specific architecture: UPI failure handling, idempotent payment retries, settlement reconciliation, NPCI rate limiting, and smart routing across multiple acquiring banks to maximise transaction success rate. 'I'd add caching' is not a sufficient answer: be specific about which cache, what TTL, and what happens on cache stampede; Culture Round (45 min): Genuine ownership stories evaluated on conviction, not keyword alignment. Can you explain a technical choice in terms of what a merchant experiences when a payment fails at checkout?.

HireStepX recommends the Reliability-first framework for this type of interview: Failure modes first → circuit breakers + idempotency → eventual consistency → reconciliation paths → monitoring.

Razorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.

Settlement = where Razorpay loses real money. Probe expected: T+0 vs T+1, partial captures, refund-of-refund, NPCI mandate edge cases.

Razorpay system-design rounds are payments-native. Strong answers cover smart routing across acquirers, retries, idempotency, and reconciliation.

Razorpay probes UPI-specific realities: asynchronous callbacks, duplicate and delayed notifications, and idempotent state transitions.

Razorpay engineering interview runs 4–5 rounds: a recruiter screen, an online coding round (60 min, 2 DSA problems), Technical Round 1 (DSA + code quality), Technical Round 2 (system design: SDE-2+ roles), and a Culture Round evaluating values alignment and ownership.

Practice

Rehearse the room before you enter it.

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