Razorpay interview questions
and how their rounds actually run
Honest, style-of practice calibrated to Razorpay’s known interview shape. No insider question dumps. CV-tailored mock interviews with 0-100 scoring on the bar a real Razorpay interviewer would set
How Razorpay rounds typically run
Two technical rounds heavy on payments-domain systems thinking, then a behavioural. Expect drilling on production incidents in payment flows
What Razorpay probes hardest
These are the competencies that come up repeatedly in Razorpay engineering rounds. Strong answers reference at least one of them with a specific, named example
- idempotency and reconciliation in payments
- distributed systems under partner-bank SLAs
- regulatory edge cases (RBI, PCI-DSS, tokenization)
- fault tolerance for callback failures
Scale realities to surface in your answers
Razorpay interviewers reward candidates who know the operational realities of their domain. Reference these where natural
- UPI peak QPS
- queue backpressure
- partner-bank webhooks
- settlement windows
What strong answers look like
These are the signals that move you from a 55 to a 78 on Elaior’s rubric — and the same patterns that move you from “maybe” to “hire” in a real Razorpay loop
- named the exact retry/idempotency mechanism
- thought about chargebacks and disputes
- discussed double-spend prevention with metrics
Red flags Razorpay interviewers specifically penalise
Patterns we’ve seen consistently lose candidates points at Razorpay regardless of how strong the rest of the answer was
- hand-wavy 'we used Redis'
- no rollback plan
- treats payments as plain CRUD
Practice questions in Razorpay’s style
These are the shape of questions a Razorpay interviewer might open with. They are not insider questions. Run a CV-tailored mock on Elaior to get versions grounded in your actual projects, then scored against the rubric
- Walk me through how you'd reason about idempotency and reconciliation in payments
- Describe a time you owned a decision involving distributed systems under partner-bank SLAs
- What metric would you watch first if regulatory edge cases (RBI, PCI-DSS, tokenization) broke under load?
- Explain the tradeoff between two approaches to fault tolerance for callback failures