Razorpay Software Engineer interviews center on a DSA-heavy online assessment, a distinctive time-boxed machine coding round, and system design or LLD/HLD discussions for senior levels, closing with a hiring-manager round on projects and fit.
$67K
Avg. Base Comp
$84K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Razorpay's Software Engineer interviews often start with a coding-heavy online assessment — typically two to three DSA problems at medium-to-hard difficulty, often paired with MCQs on time complexity, OS, or CS fundamentals, delivered inside a one-to-two-hour window. Candidates who clear the OA report moving into one or two technical rounds built around live coding problems (arrays, strings, trees, DP) where interviewers care as much about how you explain your approach and handle edge cases as whether you land the optimal solution.
A distinctive feature of Razorpay's process is the machine coding round, which shows up across levels: building an in-memory database, a load balancer with round-robin routing, a parking lot or notification system, or a UI component like a Tabs widget — always under a tight time limit with an expectation of clean, extensible code rather than a quick hack. For mid-to-senior roles, system design and LLD/HLD discussions go deeper, with several candidates describing pointed pushback on scalability, failure modes, and trade-offs rather than a single sketch-and-move-on conversation.
The process typically closes with a hiring-manager or behavioral round that digs into past projects, architectural decisions, and team fit, sometimes alongside a separate HR conversation. Scheduling and feedback speed vary by candidate — some describe a smooth few-week process with clear updates, while others report rescheduling delays and little closure after rejection, so following up proactively is worth doing rather than assuming silence means nothing is happening.
Synthesized from 23 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.
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 | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| Top 5 Turnover Risk | |
| String Shift | |
| Minimum Change | |
| Customer Orders | |
| Comments Histogram | |
| Raining in Seattle | |
| Scrambled Tickets | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Flight Records | |
| Prime to N | |
| Over 100 Dollars | |
| Upsell Transactions | |
| Retailer Data Warehouse |
Synthesized from candidate reports. Individual experiences may vary.
Multiple candidates report Razorpay's process typically opens with an online assessment of two to three DSA problems (arrays, strings, intervals, trees, jump-game or peak-finding variants) at medium-to-hard difficulty, sometimes paired with multiple-choice questions on time complexity, CPU scheduling, or code-output prediction, usually completed within a one-to-two-hour window.
Candidates commonly move into one or two live technical rounds where interviewers give one or two DSA problems similar in difficulty to the OA and ask candidates to talk through their approach, edge cases, and optimizations out loud; several reports note interviewers seem more interested in reasoning and communication than a flawless first pass.
A recurring stage across levels is a time-boxed machine coding round — candidates describe being asked to implement things like an in-memory database, a load balancer with round-robin routing, a parking lot or notification system, an EMI calculator, or a UI component, typically in 45 to 90 minutes with a stated expectation of clean, extensible code rather than just passing test cases.
For mid-to-senior candidates, a separate high-level or low-level design round appears frequently, covering topics such as scalability, sharding, failure points, or designing services like messaging, booking, or notification systems; several candidates describe interviewers pushing back on trade-offs rather than accepting an initial design without follow-up.
The process typically closes with a hiring-manager round focused on past projects, technical decisions, and culture fit, and in some cases a separate HR conversation covering standard behavioral questions; candidates generally describe this stage as more conversational than the earlier coding and design rounds.
