Razorpay Interview Process 2026 — Rounds, Tips & Questions
Everything about the Razorpay interview process: rounds, what each round tests, difficulty level, and 18 real questions asked by engineers who cleared the loop.
Interview Rounds at Razorpay
- Online test / phone screen
- Technical interview
- Managerial / HR round
Prepare well for the technical interview with questions from Razorpay's previous loops.
Real Questions Asked at Razorpay
How do you write a good user story? Walk through an example for a payments feature.
Design a rate limiter in Node.js that allows 100 requests per user per minute. It must work across multiple Node.js instances without a central Redis lock causing a bottleneck.
A Node.js microservice processes background jobs from a Redis queue. Under load, jobs fail and retry endlessly, creating a death loop that blocks the queue. How do you implement a proper retry strategy with dead letter handling?
Design Razorpay's payment retry system. When a payment fails due to a transient error (bank timeout, network blip), how do you retry safely without double-charging the customer? Cover: idempotency keys, exponential backoff with jitter, dead-letter queues, and reconciliation with bank statements.
You're building a feature flag system in React. Flags come from an API and affect which components render. How do you implement this so: flags load once at startup, components don't re-render when irrelevant flags change, and engineers can easily wrap any component.
Your JWT tokens are being stolen from localStorage and used in attacks. A developer suggests using httpOnly cookies instead. Describe the complete migration, including risks and security tradeoffs.
What is idempotency? Why is it critical for payment APIs and how do you implement it?
Design Razorpay's payout system (RazorpayX). Businesses send bulk payouts to thousands of vendor accounts simultaneously. Cover: batching, bank API rate limits, real-time status tracking, and failure handling.
Your Next.js app fetches user-specific data in getServerSideProps. The page load time is 3.2 seconds. CDN cache hit rate is 0%. Product team asks you to make it faster without losing personalization. What do you do?
How do you implement a distributed ledger for financial transactions? Explain double-entry bookkeeping in code, why you never update a balance directly, and how you use event sourcing to reconstruct the current balance from a transaction log.
Practice these questions with AI feedback
Get instant grading on your answers, identify your weak areas, and generate a personalised 14-day study plan — all free.
Build my study plan →