Razorpay's coding rounds anchor data-structures and algorithms to real payments scenarios: idempotent retries, NPCI rate limits, and settlement reconciliation.
Expect medium-to-hard problems where the interviewer wants your reasoning stated aloud, a clean implementation, and an awareness that the code would sit in a payments backend where correctness and concurrency matter. Pure algorithmic answers that ignore edge cases like duplicate callbacks or partial failures tend to lose points; framing your solution around production reality is the Razorpay differentiator.
Recruitment process
Online coding assessment or resume screen
Technical coding round one on DSA
Technical coding round two on harder problems and system framing
Hiring-manager round, then offer
Interview rounds
Round 1 (60-90 min): online assessment with DSA problems
Round 2 (60 min): live coding on arrays, strings, hashing, or trees
Round 3 (60 min): harder coding round with complexity analysis and payments-context follow-ups
Payments-Aware DSA framework
Solve the algorithm cleanly with a stated complexity, then name the production edge case (idempotency, concurrency, partial failure) the code must survive
Practice questions
01
Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?
IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
Walk me through an architecture migration you led across 30+ engineers. What was the rollback plan and when did you nearly need it?
IntenseTech-leadership probe (not pure IC). Wants migration scope + organisational coordination + actual rollback trigger criteria. 'We didn't need the rollback' fails, interviewer wants the *moment you almost pulled the trigger*.
The typical Razorpay recruitment process has 4 stages: Online coding assessment or resume screen → Technical coding round one on DSA → Technical coding round two on harder problems and system framing → Hiring-manager round, then offer.
Razorpay typically conducts 3 interview rounds: Round 1 (60-90 min): online assessment with DSA problems; Round 2 (60 min): live coding on arrays, strings, hashing, or trees; Round 3 (60 min): harder coding round with complexity analysis and payments-context follow-ups.
HireStepX recommends the Payments-Aware DSA framework for this type of interview: Solve the algorithm cleanly with a stated complexity, then name the production edge case (idempotency, concurrency, partial failure) the code must survive.
Razorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
Tech-leadership probe (not pure IC). Wants migration scope + organisational coordination + actual rollback trigger criteria. 'We didn't need the rollback' fails, interviewer wants the *moment you almost pulled the trigger*.
Arrays, strings, hashing, heaps, trees, and graphs, frequently framed around payments scenarios like retries, rate limiting, and reconciliation rather than abstract puzzles.