Type · coding

Growth · Software Engineer Interview Guide
Sign up to see ATSHeadquartered in IndiaInterview language: English
How to Pass the Razorpay Software Engineer Interview in 2026
The Razorpay DNA (TL;DR)
The Razorpay Interview Loop
Your onsite loop will typically consist of 5 rounds.
- 1
Round 1
Recruiter ScreenMotivation, role fit, logistics. - 2
Round 2
Coding ScreenLeetCode-medium algorithmic problems under time pressure. - 3
Round 3
System DesignDistributed systems, trade-offs at scale, architecture under constraints. - 4
Round 4
Onsite CodingLeetCode-hard, debugging, code clarity, edge cases. - 5
Round 5
Behavioral / LeadershipPast evidence of ownership, influence, resolving conflict.
The Danger Zone: Top Reasons Candidates Fail
Based on our database of Razorpay interview outcomes, avoid these common traps:
- Giving a generic answer that could apply to any tech company.
- Focusing only on personal career growth without mentioning Razorpay's mission or products.
- Not handling edge cases like empty transaction lists or windows spanning across midnight.
- Using a data structure that doesn't allow for efficient window updates or queries.
Test Yourself: Real Razorpay Questions
Three real prompts pulled from our database.
Type · past-experience
Type · algorithmic
+ many more questions, signals, and worked examples
Sign up to unlock the full Razorpay grading rubric
Razorpay Interview Question Bank
A sample from our database, grouped by round. Sign up to see the full set.
9 of 13 questions shown
Recruiter Screen
1- 1
Type · motivation
What interests you about working at Razorpay, and specifically in a software engineering role within the fintech industry?
Coding Screen
3- 2
Type · algorithmic
Given a list of transactions, each with a timestamp and amount, design an algorithm to calculate the total transaction volume within any given rolling 1-hour window. Assume timestamps are in seconds. - 3
Type · algorithmic
Implement a function that takes a list of user IDs and their corresponding payment statuses (success/failure) and returns the top K users who have the highest number of successful payments. Handle ties by prioritizing users with fewer failures. - + 1 more questions in this round (sign up to unlock)
System Design
3- 4
Type · design
Design a system to detect and prevent fraudulent transactions in real-time for a payment gateway like Razorpay. Consider scalability, latency, and accuracy. - 5
Type · design
Design a distributed rate limiter for API requests to protect Razorpay's services. Discuss different algorithms (e.g., token bucket, leaky bucket) and how you would implement it across multiple servers. - + 1 more questions in this round (sign up to unlock)
Onsite Coding
3- 6
Type · algorithmic
Implement a function to find the K most frequent payment methods used by customers in a given time range. Assume you have access to a stream of payment events. - 7
Type · coding
Write a function that simulates the settlement process for a batch of payments. The function should handle potential failures, delays, and ensure that the final settlement amounts are accurate. Consider edge cases like zero-value transactions or invalid bank details. - + 1 more questions in this round (sign up to unlock)
Behavioral / Leadership
3- 8
Type · past-experience
Tell me about a time you had to work with a legacy codebase that was difficult to understand or modify. How did you approach the task, and what was the outcome? - 9
Type · past-experience
Describe a specific instance where you had to choose between prioritizing developer velocity and maintaining strict data consistency for a high-volume financial service. How did you defend your trade-off to stakeholders, and what was the long-term impact on the system reliability? - + 1 more questions in this round (sign up to unlock)
Unlock all 13 Razorpay questions, free
No credit card. Every question with its framework, the grading signals interviewers score against, and a worked answer for each.
Interview tracks at Razorpay
How Razorpay's DNA translates across functions. Pick your role.
Compare Razorpay with similar employers
Same DNA, different bar. Browse the closest companies in our database and see how their loops differ.
Napo
Same tierNapo's 'Builder's Mentality' value drives the interview focus on practical execution and impact. Interviewers look fo...
See Napo interview questions
Aveni
Same tierThe technical assessment at Aveni frequently probes for practical application within Financial Services, especially r...
See Aveni interview questions
Morpho
Same tierMorpho seeks candidates with a strong grasp of DeFi fundamentals, smart contract security, and decentralized governan...
See Morpho interview questions
Practice Razorpay interviews end-to-end
Razorpay Mock Interview
Run a live mock interview with our AI interviewer using Razorpay-style prompts. Get scored on structure, signal, and answer length - exactly how the real loop grades you.
Open
STAR Stories for Razorpay Behavioral Rounds
Build a Story Bank of your past wins, mapped to the leadership signals Razorpay interviewers grade on. Reuse them across every behavioral round.
Open
Razorpay Interview Prep Hub
The frameworks behind every Razorpay round: CIRCLES for product sense, hypothesis-driven debugging for analytical, STAR for behavioral. Learn each one in 10 minutes.
Open
Interview Frameworks
CIRCLES, STAR, AARRR, RICE, MECE. The exact frameworks that make Razorpay interviewers nod instead of frown. Step-by-step playbooks with the moves and the pitfalls.
Open
Sample answers
What a strong answer to these Razorpay interview questions shows.
Write a function that simulates the settlement process for a batch of payments. The function should handle potential failures, delays, and ensure that the final settlement amounts are accurate. Consider edge cases like zero-value transactions or invalid bank details.
A strong answer shows: Well-structured code with clear functions/classes.; Robust error handling and recovery mechanisms.; Accurate simulation of settlement logic, including edge cases.; Testability of the code..
Tell me about a time you had to work with a legacy codebase that was difficult to understand or modify. How did you approach the task, and what was the outcome?
A strong answer shows: Structured approach to understanding the legacy code (e.g., documentation, tests, incremental changes).; Demonstration of technical skills in refactoring or modernization.; Focus on the business impact and successful delivery.; Positive attitude towards challenging technical debt..