What Is the Razorpay Interview Process Like? (Round by Round)

Candidates report four to six rounds at Razorpay, and the number depends on the level. A recruiter call comes first, and it is followed by an online assessment that contains coding problems and multiple choice questions. After that assessment, candidates report a machine coding round, which is a live session where you write working code for a small system in one sitting.

Senior candidates report a separate high level design round as well, and the last two steps are a hiring manager round and a short HR conversation. Most reports describe about two to three weeks from the first call to the decision, although several candidates report much longer waits at the end.

Quick Overview

Stage 1: Recruiter Call

The recruiter asks about your background, your current role, and your interest in payments. Expect a question about your notice period, because Indian recruiters want the likely joining date early. Prepare the motivation question before this call, and the answer on why Razorpay gives a structure for it.

Stage 2: Online Assessment

Campus candidates report a ninety minute test with fifteen multiple choice questions and three coding problems. The multiple choice questions come from operating systems, databases, object-oriented programming, and data structures. Experienced candidates report a longer coding test, and one report describes a three hour test built around a single hard problem.

Reports name HackerEarth and HackerRank most often, and some describe an in-house Razorpay platform, so confirm the tool with your recruiter. If this format is new to you, read what an online technical assessment involves before you start practicing.

Stage 3: The Machine Coding Round

Candidates describe this as the round that is hardest to prepare for. A machine coding round is a live session where you build a small working program from an open question, and Razorpay reports describe sessions of roughly one to two hours. The code must compile and run by the end of the session.

The most frequently reported problem is an in-memory relational database with tables, primary keys, indexes, and column constraints. Other reported problems are an in-memory search engine, a notification system, and a logger that writes each level to a different destination. Interviewers commonly add a new requirement partway through the session, so the class structure decides much of the result.

Stage 4: High Level Design Round

Senior candidates report a design discussion of about an hour, and one reported question asks for a notification service that sends email, SMS, and push messages at large volume. The reported topics are listed in the Razorpay system design interview.

Stage 5: Hiring Manager Round

Candidates report forty to sixty minutes with the hiring manager, who examines your projects, the technical decisions you made, and the reasons behind them. One report notes that the interviewer cared about the logic rather than the language or the stack. Expect behavioral questions about ownership, conflict, and failure in the same round.

Stage 6: HR Round

A short final conversation covers values, team fit, and joining details. Razorpay publishes its values, which are Customer First, Autonomy and Ownership, Agility with Integrity, Transparency, and Challenging the status quo. Expect a question that asks you for an example of one of these values in your own work.

How the Campus Path Differs

On-campus candidates report a stricter first filter, and the reported eligibility rules ask for sixty percent or a 6.5 CGPA in tenth, twelfth, and graduation, with no active backlogs. The campus path tests data structures more heavily and machine coding less. Freshers report two technical rounds, then a managerial round, then a short HR round.

Timeline and Decision

Reports describe the technical rounds inside about two to three weeks, and some candidates report the whole process finished within a few days. Others report weeks of silence after the final round while the offer is approved internally. The reported waits vary widely, so plan for both outcomes. The full picture is in how long it takes to hear back after a Razorpay interview.

Questions to Ask Them

Every round includes time for your questions. Ask how the team handles failed payments and retries, and ask how on-call works for a system that moves money. Ask which parts of the product the team owns from start to finish. Questions like these show that you understand what Razorpay actually builds.

How to Prepare

• Practice machine coding under a timer. Build a small system in ninety minutes without references, then extend it with a new requirement.
• Learn design in code, not diagrams. Grokking the Object Oriented Design Interview teaches the class structure this round grades.
• Practice data structures every week. Grokking the Coding Interview covers the patterns that the online assessment uses.
• Prepare one deep project story. The hiring manager round examines the decisions you made, the alternatives you rejected, and the results you measured.