Razorpay Engineering Interview Questions India 2026

Razorpay system design interview FAQ

01What is the recruitment process at Razorpay?

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.

02What are the interview rounds at Razorpay?

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. '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?.

03What framework should I use for Razorpay system design interviews?

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

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

To answer this question well, HireStepX recommends the Reliability-first approach: Failure modes first → circuit breakers + idempotency → eventual consistency → reconciliation paths → monitoring. Ground your answer in a specific real example from your own experience.

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

To answer this question well, HireStepX recommends the Reliability-first approach: Failure modes first → circuit breakers + idempotency → eventual consistency → reconciliation paths → monitoring. Ground your answer in a specific real example from your own experience.

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

To answer this question well, HireStepX recommends the Reliability-first approach: Failure modes first → circuit breakers + idempotency → eventual consistency → reconciliation paths → monitoring. Ground your answer in a specific real example from your own experience.

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

To answer this question well, HireStepX recommends the Reliability-first approach: Failure modes first → circuit breakers + idempotency → eventual consistency → reconciliation paths → monitoring. Ground your answer in a specific real example from your own experience.

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

To answer this question well, HireStepX recommends the Reliability-first approach: Failure modes first → circuit breakers + idempotency → eventual consistency → reconciliation paths → monitoring. Ground your answer in a specific real example from your own experience.