Razorpay Software Engineer interview typically runs 3-4 rounds: OA, DSA, system design/machine coding, hiring manager, and HR. Timeline is about 2-6 weeks, and the process is practical, resume-driven, and sometimes inconsistent.
$52K
Avg. Base Comp
$84K
Avg. Total Comp
4-7
Typical Rounds
3-6 weeks
Process Length
We’ve seen Razorpay lean hard toward engineers who can turn real product constraints into concrete design choices. Across candidate reports, the strongest signal is not polished theory but how well you defend tradeoffs: scalability, availability, consistency, failure handling, and the edges where a system breaks. One candidate who received an offer noted that the panel kept pushing on failure points in HLD, while others described LLD prompts like notification systems, photo-sharing apps, and even code-versioning-style designs. That pattern suggests they care less about naming patterns and more about whether you can reason through how software behaves under pressure.
A recurring theme is the emphasis on past work as evidence of engineering judgment. Multiple candidates said the conversation kept returning to projects, architecture decisions, and how things were built on previous teams, with one person specifically calling out resume deep-dives and another being asked to walk through a project’s high-level design. We also see a practical bent in the coding rounds: machine coding around load balancers, pub-sub workflows, and end-to-end project flows, plus DSA that still demanded clear explanation under time pressure. Even frontend candidates were pressed on CSRF, CORS, SSR, and web vitals in the context of their resume, which tells us Razorpay wants applied understanding, not memorized definitions.
The non-obvious make-or-break factor here is consistency of communication. Several candidates described abrupt or uneven interviewer behavior, and one experience felt confusing because the interviewer wasn’t fully aligned on the design concepts. That means candidates who do best are the ones who can stay crisp when the discussion gets messy and keep anchoring answers in concrete implementation details. In our view, Razorpay rewards engineers who sound like they’ve actually shipped systems, not just studied them.
Synthetized from 4 candidates 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 most frustrating part for me was that the process felt pretty inconsistent from round to round. I got scheduled through Instahyre, and the first round was actually fine. It was a low-level design style discussion where I had to design a notification management system, and I felt like I was able to explain my approach clearly. After that, though, the second round was much rougher because the interviewer seemed less confident on the system design concepts themselves, so even when I walked through things carefully, there was a lot of confusion on their side and it was hard to get into a real back-and-forth.
In another round, I was asked to design a photo sharing app using any language I wanted, and then to talk through the high-level design of a project I had worked on. That part was more straightforward, but it still leaned heavily on past work and architecture rather than pure coding. I also had a manager round and an HR round, which were mostly normal managerial and basic HR questions. In a separate interview experience, the questions were even more centered on resume deep-dive, system design for a large-scale system, and low-level design for something similar to a code versioning system. One thing that stood out across the process was how much they cared about how things were built in previous teams, especially engineering practices and design decisions. I also heard the interviewers can be quite abrupt and interrupt often, which matched the overall vibe of the process being a bit haphazard. I ended up not getting an offer, so my main takeaway is to be very ready for practical design discussions and to explain past projects in detail, not just generic system design theory.
Prep tip from this candidate
Be ready to design concrete apps like file sharing, photo sharing, and notification management systems, and practice explaining your past project architecture in detail. Also prepare for resume deep-dives and system design follow-ups that stay close to how you actually built things before.
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 | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Customer Orders | |
| String Shift | |
| Comments Histogram | |
| Random SQL Sample | |
| Minimum Change | |
| Prime to N | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Retailer Data Warehouse | |
| First Touch Attribution | |
| Raining in Seattle | |
| Job Recommendation | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically enter the process through a recruiter or campus placement channel such as Instahyre. Scheduling and feedback can be slow, and some candidates reported needing to follow up multiple times to get interviews arranged or updates shared. For some candidates, the process starts with an online assessment containing 3 DSA problems. Speed and correctness both matter, and the test is used to filter for strong problem-solving under time pressure.
This round often focuses on coding and practical fundamentals, including array and stack problems such as Non-decreasing Array and Largest Rectangle in Histogram. In some cases, it begins as a resume-driven screen and moves into frontend or web fundamentals like CSRF, CORS, SSR, and web vitals. Candidates are asked to design practical systems such as a notification management system, photo sharing app, code versioning system, or a self-service Cassandra provisioning system. Interviewers probe scalability, availability, consistency, failure modes, and implementation tradeoffs rather than just high-level architecture.
This round emphasizes building a working solution for a non-conventional, implementation-heavy problem. Examples included designing a load balancer with HTTP endpoints and round-robin distribution, or building workflow and pub-sub style components end to end. The hiring manager interview is conversational and centers on projects, hands-on experience, and core CS fundamentals such as Operating Systems and Computer Networks. Candidates are also expected to explain how they learned over time and how their background fits real-world engineering work.
The final stage is a basic HR discussion covering standard managerial and process-related questions. This round is generally lighter than the technical rounds and comes near the end of the process.