Razorpay Interview Questions 2026: SDE Hiring Process & Complete Guide

Razorpay powers payments for over 10 million businesses in India. From startups to enterprises, if you have paid online in India, there is a good chance Razorpay processed that transaction. As India's leading full-stack payments infrastructure company, Razorpay offers engineers the chance to build systems that handle billions of rupees daily.

This guide breaks down the Razorpay SDE interview process for 2026 - what to expect in each round, real questions from recent interviews, system design focus areas, and compensation details.

Company Overview#

Razorpay's engineering culture emphasizes ownership, velocity, and reliability. Their systems process payments across 100+ payment methods with 99.99% uptime targets.

Razorpay Hiring Process#

The Razorpay hiring process has 4-5 rounds and typically takes 2-3 weeks.

Round 1: Online Assessment

• Platform: HackerEarth or CoderPad
• Duration: 75-90 minutes
• Questions: 2-3 coding problems
• Difficulty: Medium to Hard
• Focus: Data structures, algorithms, and one problem often involves a real-world payments scenario

A score of 70%+ on the OA usually gets you to the next round.

Round 2: Technical Interview 1 (DSA Deep Dive)

• Duration: 60 minutes
• 2 algorithmic problems solved on a shared editor
• You must explain your approach before writing code
• Optimization is important - brute force alone will not clear this round
• The interviewer may ask follow-up questions to test depth (e.g., "What if the input is 100x larger?")

Round 3: Technical Interview 2 (DSA + System Design)

• Duration: 60-75 minutes
• For SDE-1: 1 hard DSA + 1 low-level design problem
• For SDE-2+: 1 medium DSA + 1 high-level system design problem
• Razorpay interviewers value practical thinking - they want to see how you handle real constraints like network failures, retries, and data consistency

Round 4: System Design / Architecture (SDE-2 and above)

• Duration: 60 minutes
• Full system design discussion
• Payments-specific scenarios are common
• You are expected to make architectural decisions and defend them
• They care about fault tolerance, idempotency, and observability

Round 5: Hiring Manager + Culture Fit

• 30-45 minutes
• Discussion about your past work, impact metrics, and why Razorpay
• Behavioral questions about handling pressure, disagreements, and production incidents
• Razorpay explicitly screens for "builder mindset" - they want people who ship fast

10 Technical Questions Asked at Razorpay#

These are sourced from verified candidate experiences in 2025-2026.

DSA Questions

1. Implement a payment retry mechanism with exponential backoff and jitter. (Design + coding - tests understanding of distributed systems patterns)

2. Given a list of transactions with timestamps, find the maximum transaction amount in every sliding window of K minutes. (Monotonic deque / sliding window maximum)

3. Design a function to validate and parse IFSC codes from a large dataset. (Trie-based approach or hashing with regex validation)

4. Find all pairs of transactions that sum to a target settlement amount. (Two-sum variation with handling for duplicates and negative amounts)

5. Implement a thread-safe counter that tracks transactions per second. (Concurrency - mutex/atomic operations, sliding window counter)

6. Given a DAG representing dependencies between payment steps, find the minimum time to complete all steps. (Topological sort + longest path in DAG)

7. Serialize and deserialize a nested JSON payment payload efficiently. (Recursive approach with type handling - tests real-world data processing)

8. Implement a consistent hashing ring for distributing payment processing load across servers. (Hash ring with virtual nodes)

9. Find the longest consecutive sequence of successful transactions from a log. (HashSet-based O(n) approach)

10. Design a priority queue for processing refunds where older refunds and higher amounts get priority. (Custom comparator with min-heap)

What Sets Razorpay Interviews Apart

• They often frame DSA problems in a payments context - same algorithm, but wrapped in a business scenario
• Code quality matters. They will comment on variable names, error handling, and modularity
• You may be asked to write unit tests for your solution

5 System Design Questions Asked at Razorpay#

1. Design a Payment Gateway. The signature Razorpay question. Covers: Order creation, payment method selection, bank integration, status callbacks, webhook delivery, idempotency keys, PCI-DSS compliance considerations, retry logic for failed bank calls, reconciliation pipeline.

2. Design a Retry Mechanism for Failed Payments. Covers: Exponential backoff with jitter, dead letter queues, max retry limits, state machine for payment status (created → processing → success/failed), alerting on repeated failures, circuit breaker pattern for unresponsive banks.

3. Design a Subscription Billing System. Covers: Plan management, billing cycles, proration, dunning (failed payment recovery), invoice generation, webhook notifications for subscription events, handling plan upgrades/downgrades mid-cycle.

4. Design a Real-Time Settlement and Reconciliation System. Covers: Double-entry ledger, T+1/T+2 settlement cycles, bank file parsing (NACH, NEFT), discrepancy detection, auto-reconciliation rules, manual review queue, audit trail.

5. Design a Multi-Tenant API Rate Limiter. Covers: Token bucket vs sliding window, per-merchant limits, burst handling, distributed rate limiting across multiple servers, graceful degradation, rate limit headers in API responses.

System Design Expectations

• Razorpay interviewers expect you to think about money - every design choice has financial implications
• Discuss PCI-DSS compliance awareness (you do not need to be an expert, but awareness matters)
• Idempotency is non-negotiable - if you do not bring it up, they will ask about it
• Talk about observability: logging, metrics, distributed tracing
• Mention specific trade-offs: strong consistency vs availability for payment operations

Salary at Razorpay (2026)#

• Razorpay offers competitive ESOPs, especially at SDE-2+
• Performance bonuses: 10-20% of base salary
• Benefits include health insurance, learning budget (₹1 lakh/year), and wellness stipend
• Hybrid work model: 3 days in office (Bengaluru)

How to Prepare#

1. DSA Preparation (4-6 weeks)

Top topics by frequency at Razorpay:

• Hashing and HashMaps (most frequently tested)
• Graphs (BFS, DFS, topological sort, shortest paths)
• Sliding Window and Two Pointers
• Dynamic Programming (medium difficulty)
• Trees (BST operations, serialization)
• Concurrency basics (for SDE-2+)

Target: 150+ Leetcode problems. Focus on medium difficulty with some hard problems.

2. Payments Domain Knowledge (1-2 weeks)

• Understand the payment gateway flow: order → authorize → capture → settle
• Learn about payment methods in India: UPI, cards, netbanking, wallets, NACH
• Read about PCI-DSS basics and tokenization
• Understand webhooks and callback mechanisms
• Study idempotency patterns in payment APIs

3. Study Razorpay's Products

• Read Razorpay's API documentation (it is public and well-written)
• Understand the difference between Payment Gateway, Razorpay X, and Capital
• Follow Razorpay's engineering blog for architecture insights
• Look at their open-source contributions on GitHub

4. Practice System Design with a Payments Lens

• Every system design answer should consider: What happens if a payment is processed twice? What happens if the bank is down? How do you handle partial failures?
• Draw clear architecture diagrams with data flow arrows
• Practice explaining your design in 35-40 minutes (leave time for questions)

5. Behavioral Preparation

Razorpay values:

• Speed of execution (shipping fast without breaking payments)
• Ownership (you own your service end-to-end)
• Customer obsession (merchants depend on Razorpay for revenue)

Prepare 3-4 STAR stories that demonstrate these traits.

Common Mistakes to Avoid#

• Treating payment systems like generic CRUD applications - money requires special handling
• Forgetting about concurrent access issues (two requests trying to capture the same payment)
• Not discussing failure scenarios in system design - Razorpay interviewers will specifically probe "What if X fails?"
• Writing code without handling edge cases (null amounts, negative values, currency precision)
• Not knowing Razorpay's products - at minimum, understand what their payment gateway does

Final Thoughts#

Razorpay interviews reward practical thinking. They want engineers who understand that the code they write moves real money for real businesses. If a bug in your code causes double-charges or missed settlements, merchants lose trust and revenue.

The DSA rounds are standard but wrapped in payments context. The system design rounds are where Razorpay truly differentiates - they test whether you can build reliable financial infrastructure, not just scalable web apps.

Prepare thoroughly, understand the payments domain, and always think about failure modes. That mindset alone sets you apart from most candidates.

Ready to apply? Check your resume's ATS score before submitting - 75% of resumes get auto-rejected.