What raises your odds
- Working code with tests in machine coding round — partial-but-clean beats complete-but-messy
- Payment-domain familiarity (idempotency, eventual consistency, retries)
- Asking about scale + failure modes in system design upfront
Razorpay · Interview process
Razorpay interview process — 2026
Razorpay's engineering loop is 4 rounds: 1 phone screen, 1 take-home coding assignment (optional for senior), 2-3 onsite rounds (machine coding / system design / behavioural). Strong bias toward production-quality code in a working environment, not whiteboard puzzles. Decision usually within 7-10 days.
Editorial. Based on publicly-shared candidate experiences, engineering blogs, and patterns ProdMatch sees across the loop. Not an authoritative reproduction of any company's internal process.
Overview
Razorpay's interview process emphasises practical engineering: live machine-coding rounds where you build a small system in 90 minutes (often a stripped-down payment gateway, a rate limiter, or an idempotent transaction processor) and discuss your design choices live. System-design rounds focus heavily on payment-domain scenarios. The bar is high but explainable: production-quality code, clean abstractions, working tests.
Typical Backend / SDE-2 loop
Total time across rounds: ~5 hours, typically spread across 1-2 weeks.
- 1
Recruiter call
30 min
20-30 min call with the recruiter. Discusses your background, target role, comp band, and Razorpay's interview rubric.
- 2
Phone DSA screen
45 min
One medium DSA problem on CoderPad. Focus on correctness + code style — not exotic optimisations.
- 3
Machine coding (the big one)
90 min
90-min live build of a small system end-to-end. Recent examples: a payment-link generator with idempotency, a transaction-history service with pagination, a webhook delivery retry queue. Bring your own IDE; commit at intervals.
- Practice building small services from scratch in 90 min
- Idempotency patterns
- Clean Java/Go/Node idioms
- 4
System design
60 min
Open-ended payment-domain scenario — design a UPI flow, design a refund workflow, design a recurring-subscription service.
- 5
Hiring manager + culture
45 min
Behavioural + culture fit. Razorpay values ownership; expect questions on bias-to-action, technical leadership, and conflict resolution.
Common rejection reasons
- Machine coding without tests or clean abstractions
- Missing idempotency / retry semantics in design rounds
- Behavioural answers that don't show ownership of outcomes
Frequently asked
- What is the interview process at Razorpay?
- Razorpay's engineering loop is 4 rounds: 1 phone screen, 1 take-home coding assignment (optional for senior), 2-3 onsite rounds (machine coding / system design / behavioural). Strong bias toward production-quality code in a working environment, not whiteboard puzzles. Decision usually within 7-10 days.
- How many rounds does Razorpay have?
- 5 rounds in the typical typical backend / sde-2 loop: Recruiter call, Phone DSA screen, Machine coding (the big one), System design, Hiring manager + culture.
- What should I prepare for the Razorpay interview?
- Working code with tests in machine coding round — partial-but-clean beats complete-but-messy Payment-domain familiarity (idempotency, eventual consistency, retries) Asking about scale + failure modes in system design upfront
- Why do candidates get rejected at Razorpay?
- Common reasons: Machine coding without tests or clean abstractions; Missing idempotency / retry semantics in design rounds; Behavioural answers that don't show ownership of outcomes.