~learn.
Fintech · Bengaluru

Razorpay.

Payment gateway, subscriptions, payouts and business banking APIs for Indian businesses.

its questions lean on
  • machine coding with extensible OOP
  • recurring payments
  • notifications and webhooks
  • pub-sub and scheduling
  • rate limiting

The rounds, as candidates describe them

  1. Machine coding90 minutes to design and build a working in-memory module in a local IDE, run against test cases; some loops now allow AI tools and judge how they are used.source ↗
  2. High-level system designA product design on top of Razorpay's payment flow, with requirements, estimates, database and HLD diagram.source ↗
  3. Hiring managerDeep dive into a current project, its flaws and how you would redesign it.source ↗

Reported by candidates

From public interview write-ups; each links its source.

Likely, from what they build

Our pick, not a report: questions that fit Razorpay's products.

Study path

An ordered path through the course for Razorpay, and why each step is there.

  1. 01W02 · DAY 02Idempotency in Practicecharge exactly once, whatever the retries
  2. 02W02 · DAY 04Webhook Delivery Systemdelivering payment events to merchants reliably
  3. 03W02 · DAY 01Timeout Helltimeouts and retries against banks
  4. 04W05 · DAY 02Distributed Transactions — The Saga Patternmulti-step money movement without 2PC
  5. 05W05 · DAY 01Consistency Modelswhich reads must be strongly consistent
  6. 06W03 · DAY 02Transactional Outboxnever lose an event after a DB commit
  7. 07W03 · DAY 05Audit Log Systemtamper-evident records regulators ask for
  8. 08SQ-01India's UPIhow UPI moves money end to end
  9. 09IP-20Design a Payment Systemthe classic payment-system interview question

Company names and logos are trademarks of their owners, shown only to identify each company. This course isn't affiliated with or endorsed by any of them.