Razorpay Engineering Manager Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Razorpay.
Razorpay
Engineering Manager
Manager Average Negative experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Group Presentation
Interview formats
Technical System Design Behavioral
The overall interview process initially appeared well-structured and clear. However, as the interviews progressed, issues became apparent. The interviewers seemed disengaged. Surprisingly, junior staff members were assigned to evaluate candidates for roles significantly senior to their own, such as a software engineer assessing a senior engineering manager on system design. These junior interviewers lacked a grasp of the technological scope and showed little interest in probing further, framing questions, or actively listening to responses. This situation reflects the prevailing work culture at the company.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Razorpay
Engineering Manager
Manager Average Negative experience Decline offer 1 round
Interview process
Technical screen
Interview formats
Technical System Design Coding
The interview was pretty boring and just repetitive questions on basic stuff. The person interviewing me didn't seem that into it and just read off a script. Nothing engaging or challenging, just really dull. Felt like they were just ticking boxes rather than actually seeing what I can do.
Confirmed questions5 questions
- Given Uber scaled from 1M to 10M DAU and plans to reach 50M DAU in 3-4 years, you need to rebuild key architecture pieces. As the manager for the driver tracking and ride allocation systems, you're rebuilding from scratch and migrating from monolith to microservices. Assume other services like User, Auth, Notifications, Driver Profiles are available via REST API. Plan the work.
- What milestones would you set, and what's your MVP and subsequent iteration plan?
- What's your execution plan, detailing what Sprint 1, 2, 3, etc., would look like?
Razorpay
Engineering Manager
Manager Average Positive experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
System Design Coding
The interview had two rounds, covering High-Level Design (HLD) and Low-Level Design (LLD). It was a detailed discussion, and I had to write code. The questions were moderately difficult. Overall, it was a positive experience; the interviewers were approachable, supportive, and clearly explained what they were looking for.
Confirmed questions1 question
- Could you identify potential failure points within the High-Level Design?
Razorpay Engineering Manager Interview Questions
Quoted word for word from Razorpay interview reports.
“Write code for the LFU and LLD problems.”
Read reports →“Can you implement an LFU cache?”
Read reports →“For the Driver Tracking system, what features would be included, such as live tracking until the trip ends and ETAs using Google Maps?”
Read reports →“Could you detail the low-level design for a load balancer?”
Read reports →“Can you design a load balancer at a high level?”
Read report →“Given Uber scaled from 1M to 10M DAU and plans to reach 50M DAU in 3-4 years, you need to rebuild key architecture pieces. As the manager for the driver tracking and ride allocation systems, you're rebuilding from scratch and migrating from monolith to microservices. Assume other services like User, Auth, Notifications, Driver Profiles are available via REST API. Plan the work.”
Read report →“Could you identify potential failure points within the High-Level Design?”
Read report →“Can you implement LLD?”
Read report →“What is your approach to designing Google Docs at the LLD level?”
Read report →Formats, difficulty and experience
Across all 8 Razorpay interview reports.