HR interview questions
Common Razorpay HR questions, sample answer frames, and STAR tips.
Razorpay Interview Experiences
How Razorpay fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
sment (90 minutes) - 2-3 coding problems on arrays, strings, dynamic programming, graphs, 2. Technical Interview Round 1 (45 minutes) - Data structures and algorithms coding problems, 3. Technical Interview Round 2 (45 minutes) - System design for payment systems, distributed systems, detailed technical discussion, 4. Managerial Round (45 minutes) - Behavioral questions, problem-solving, impact discussion, 5. HR Round (30 minutes) - General discussion, compensation, role expectations. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 7.0+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): SDE-1: ₹18-25 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90 min | Coding (DSA) + sometimes MCQs |
| Technical Round 1 | 45-60 min | DSA + backend / payments concepts |
| Technical Round 2 | 45-60 min | System design (payments / ledger) |
| HR / Culture | 20-30 min | Motivation, integrity, relocation |
Real interview experiences
Section titled “Real interview experiences”These are condensed from public candidate write-ups. Two things stand out across them: the DSA bar is genuinely high (medium-hard DP and constant-space tricks, not warm-ups), and the shortlist ratios are brutal - Razorpay takes very few people per campus.
Experience 1: SDE, on-campus 2022 (GeeksforGeeks write-up)
Section titled “Experience 1: SDE, on-campus 2022 (GeeksforGeeks write-up)”Reported background: a student from a non-CS branch who had switched into software.
Round 1 - Online assessment (90 min)
- 15 MCQs across OS, DBMS, OOPS and DSA, with different questions carrying different point values.
- Three coding problems: a subarray-sum check, a helicopter-rescue optimisation solved with two pointers, and an array manipulation using a doubly linked list.
- 12 candidates advanced.
Round 2 - Technical (45 min, with a Senior Software Engineer)
- One problem, close to “find the next palindrome larger than a given number”.
- The interviewer wanted the brute force stated first, then the optimisation, then the code, then the complexity. 11 candidates cleared.
Round 3 - Hiring manager (60 min, with a Senior Engineering Manager)
- System design for UPI transactions.
- OS, networking and database fundamentals.
- Deep follow-ups on the candidate’s project and tech stack choices.
- Behavioural: why this career path, how you handle conflict, where you are headed. Some candidates got puzzles instead.
Outcome: Selected - 3 students in total from the drive.
Experience 2: SDE internship, on-campus (GeeksforGeeks write-up)
Section titled “Experience 2: SDE internship, on-campus (GeeksforGeeks write-up)”Structure: one coding round, two technical rounds, one managerial round.
- Coding round: 15-20 MCQs on CSE core subjects (DBMS, OS) plus 3 coding questions. Only candidates who finished all three were shortlisted.
- Technical 1: 10-15 minutes on resume and projects, then a dynamic programming problem the candidate described as a harder variant of Regular Expression Matching.
- Technical 2: again resume-first, then find the MEX of an array in O(N) time without extra space.
- Managerial: behavioural questions and puzzles.
Funnel as reported: 8 shortlisted for interviews, 5 to the second technical, all 5 to the managerial round, and 1 offer. That candidate later converted the internship into a PPO.
What both accounts share: every interview opens on your resume and projects before the algorithm question, so have a crisp 3-minute project narrative ready. The differentiator is not finishing the problem - it is stating brute force, optimisation and complexity out loud in that order.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Design an LRU cache. Usually expects HashMap + doubly linked list
- Implement a rate limiter. Usually expects sliding window / token bucket
- Merge overlapping time intervals. Usually expects sort + sweep
- Discussion on payment gateway and webhooks, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why fintech / payments?
- A production bug or outage you helped with
- An integrity / pressure scenario
- Joining timeline
Practical tips for Razorpay
Section titled “Practical tips for Razorpay”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain payment gateway in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Razorpay panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, Razorpay usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.