Razorpay's system-design rounds are payments-native and India-specific.
In 2026 expect prompts on a payment gateway that routes transactions across multiple banks to maximise success rate, a settlement system that reconciles and pays out to merchants without losing or double-paying money, and handling UPI callbacks that arrive late, out of order, or twice. Interviewers probe smart routing across acquirers, idempotency, reconciliation, and consistent state transitions under asynchronous, unreliable notifications. Candidates who understand UPI's real-world messiness and design idempotent, reconcilable flows stand out from generic web-scale answers.
About Razorpay
Indian fintech offering payment gateway, payouts, business banking (RazorpayX), and POS rails for merchants.
Recruiter or online assessment screen
Technical coding round on DSA
System-design round on a payments service
Hiring-manager round, then offer
Round 1 (60 min)
coding round on data structures and algorithms.
Round 2 (60 min)
system-design round on gateways, settlement, or UPI flows.
Round 3 (45-60 min)
design deep-dive on correctness and reconciliation plus behavioral.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
The typical Razorpay recruitment process has 4 stages: Recruiter or online assessment screen → Technical coding round on DSA → System-design round on a payments service → Hiring-manager round, then offer.
Razorpay typically conducts 3 interview rounds: Round 1 (60 min): coding round on data structures and algorithms.; Round 2 (60 min): system-design round on gateways, settlement, or UPI flows.; Round 3 (45-60 min): design deep-dive on correctness and reconciliation plus behavioral..
HireStepX recommends the Route-Reconcile-Idempotent framework for this type of interview: Route across acquirers to maximise success, make every state transition idempotent, and build reconciliation to guarantee no money is lost or double-paid under async UPI callbacks
To answer this question well, HireStepX recommends the Route-Reconcile-Idempotent approach: Route across acquirers to maximise success, make every state transition idempotent, and build reconciliation to guarantee no money is lost or double-paid under async UPI callbacks Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Route-Reconcile-Idempotent approach: Route across acquirers to maximise success, make every state transition idempotent, and build reconciliation to guarantee no money is lost or double-paid under async UPI callbacks Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Route-Reconcile-Idempotent approach: Route across acquirers to maximise success, make every state transition idempotent, and build reconciliation to guarantee no money is lost or double-paid under async UPI callbacks Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Route-Reconcile-Idempotent approach: Route across acquirers to maximise success, make every state transition idempotent, and build reconciliation to guarantee no money is lost or double-paid under async UPI callbacks Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Route-Reconcile-Idempotent approach: Route across acquirers to maximise success, make every state transition idempotent, and build reconciliation to guarantee no money is lost or double-paid under async UPI callbacks Ground your answer in a specific real example from your own experience.