Real, anonymous reports from people who interviewed for Software Engineer at razorpay, newest first and distilled into what to expect across the loop.
I applied and the next day I got a Hackkerrank-style link. The coding round was about 45 minutes and felt medium, though slightly closer to the easy side. After that, the rest of the process moved into structured interviews: a technical follow-up and then an HR round.
My process felt like a straightforward but technical grind. After applying, I moved through three rounds total: two technical rounds and one HR round. The technical interviews leaned heavily into DSA and also pulled in core CS topics—things like object-oriented concepts, operating system fundamentals, computer networks, and database management—and then the rounds also circled back to my resume and the projects I had done.
The interview process typically starts with an online assessment followed by multiple technical rounds and an HR discussion. Candidates noted variations in scheduling and communication, with some experiencing delays and rescheduling that impacted their overall experience.
Candidates faced a mix of machine coding and DSA-focused questions, often requiring them to explain their thought process while solving problems. The difficulty ranged from medium to hard, with a strong emphasis on practical application and core computer science concepts.
Some candidates encountered low-level design (LLD) interviews that required them to create detailed designs for systems or applications, with a focus on clarity and structure in their solutions. This aspect was critical for those aiming for more senior roles.
The HR rounds often involved discussions about candidates' resumes and past projects, with a mix of behavioral questions. Candidates reported varying levels of engagement from interviewers, which affected their ability to convey their experiences effectively.
The overall difficulty of the interviews was perceived as challenging, with some candidates feeling pressure to perform under tight timelines. Many reported that despite strong technical performance, external factors like scheduling issues influenced their final outcomes.
Candidates reflected on the importance of clear communication during technical rounds and wished they had focused more on articulating their thought processes. Some noted that they could have better prepared for the behavioral aspects by aligning their experiences with the role requirements.