
Razorpay software engineer candidates report an online assessment, a machine coding round, design or fundamentals discussions, and a hiring manager conversation. Here is what to prepare for in each round.
$48K
Avg. Base Comp
$73K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Razorpay software engineer candidates frequently point to the machine coding round as the most demanding part of the loop. Reported problems include a load balancer with HTTP endpoints and round-robin distribution, a pub-sub queue-style system, and a dictionary-like system for adding words across datasets and searching them efficiently. One candidate got the load balancer working for command-line input but ran out of time before finishing the HTTP endpoints. Another focused on modular, extensible code that passed all test cases. Practice getting a clean working version first, then extending it.
Design rounds are the second pattern, especially for senior roles. Reports mention high-level design with pushback on scalability, availability, consistency and failure points, low-level design with code writing mixed in, and a self-service system for developers to request Cassandra instances. One senior candidate says interviewers evaluated them against a level above the one they applied for, so be ready to defend every trade-off.
Campus candidates describe a different shape. It starts with an online assessment of DSA problems, then a DSA interview with problems such as LeetCode 665 and 84, then a hiring manager conversation on projects, operating systems and networks. Another early-career candidate reports OOPS, DBMS and sharding questions. Across levels, interviewers dig into resume projects, so be ready to explain why you made your technical decisions, not only what you built. Some candidates also mention slow scheduling and feedback, so follow up proactively.
Synthesized from 27 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Razorpay process.
The process had three stages. The first was an online assessment with 20 MCQs and 2 coding questions. The MCQs were the bulk of it, and the coding questions were the part that actually decided how the assessment went for me. The second round was the AI-assisted coding interview, which was the most unusual part. It runs about 60 minutes and is a practical assessment, not a trivia quiz or an algorithm recitation. The interviewers wanted to see how I planned the work, broke the problem down, and executed while working alongside autonomous AI tools. If you go in expecting a whiteboard exam, you'll be thrown off. The final stage was the technical managerial round, which was the last step before a decision. I received a no offer after that round, and I wasn't given detailed feedback on why, so I can't say which stage carried the most weight.
Prep tip from this candidate
Practice short coding tasks while using an AI assistant, focusing on how you plan the steps, check the AI's output, and course-correct, since the AI-assisted round is judged on process rather than memorized algorithms. Also drill the 2 coding questions in the online assessment under time pressure, because the MCQ section takes up most of the time.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Razorpay
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Production Rollout Challenges | |
| Unified Event Pipeline | |
| Length Of Longest Palindrome | |
| Reddit-like Notifications | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Top 3 Users | |
| Subscription Overlap | |
| Top 5 Turnover Risk | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| Duplicate Rows | |
| Scrambled Tickets | |
| Size of Joins | |
| Find Bigrams | |
| Last Transaction | |
| Upsell Transactions | |
| Longest Streak Users | |
| Payments Received | |
| String Shift | |
| Minimum Change | |
| Customer Orders | |
| Find the Missing Number | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
Campus and early-career candidates report an online assessment with three DSA problems, in one case alongside ten multiple-choice questions. One reported a 1.5-hour limit. One experienced candidate instead describes a resume-driven screening that moved into frontend fundamentals.
Candidates report a timed machine coding problem, such as a load balancer with HTTP endpoints, a pub-sub queue-style system, or a dictionary-like system with optimized search. Build a working end-to-end solution first and keep the code modular and extensible. One candidate ran out of time before finishing the HTTP endpoint part.
Senior candidates report HLD discussions covering scalability, availability, consistency and failure points, plus LLD with code writing mixed in. Interviewers may push back hard on your choices, so practice defending trade-offs. Another candidate describes designing a Cassandra self-service system.
Some candidates report DSA interviews with problems such as Non-decreasing Array and Largest Rectangle in Histogram. Others report questions on OOPS, DBMS, OS, networks, sharding, or frontend topics like CSRF, CORS and web vitals. Interviewers commonly dig into resume projects, so be prepared to justify your technology choices.
Candidates describe a hiring manager round covering past projects, background and fit, sometimes with additional design or behavioral discussion. One also mentions a combined technical and HR round. Scheduling and feedback were slow in some reports, so follow up with your recruiter rather than waiting.