How to Crack the Razorpay Interview
The Razorpay interview for engineers and product roles, why payment correctness runs through every round, and a live mock interview at the same technical bar.
Sample scorecard
Razorpay loop
What the report tells you to close:
The short version
Why Razorpay interviews is hard
Razorpay sits between merchants and banks, which means it absorbs the unreliability of both. Interviews focus hard on failure: what happens when a bank times out after taking the money, how a retry stays safe, and how the ledger is reconciled the next morning.
What to expect
The rounds you should rehearse
Coding and low-level design of a payment, order or refund model with clear state transitions.
System design
an idempotent payment API, webhook delivery with retries, and settlement reconciliation.
Failure reasoning
the bank charged the customer but never responded, and what your system does about it.
Avoid these
The mistakes that quietly sink candidates
Designing the happy path and treating timeouts as an exception rather than the normal case.
Omitting idempotency keys, which is the single most common reason a payment design fails here.
Talking about money in floating point, or without a ledger that can be audited.
Reading the questions is not practicing them.
Run a live voice mock tuned to Razorpay-style loops. It follows your answers, probes the gaps, and scores you like a senior interviewer would.
FAQ
Questions, answered.
What is the payments question they always ask?▾
How much regulatory knowledge is expected?▾
Walk in knowing exactly what they will ask.
Your first interview is free. No card, no scheduling. Just you and a room that pushes back.
Start your free interview