What questions are asked in Razorpay interviews?

Razorpay interviews commonly cover DSA coding (Design an LRU cache; Implement a rate limiter), core CS (OOPs, DBMS/SQL, OS basics where relevant), project discussion, and topics tied to the business such as payment gateway, webhooks, idempotency. Behavioural questions check ownership, teamwork, and why Razorpay.

How many rounds are there in the Razorpay interview?

Razorpay typically has 4 stages: Online Assessment (90 min), Technical Round 1 (45–60 min), Technical Round 2 (45–60 min), HR / Culture (20–30 min). Some drives skip GD or merge HR with managerial. Always check the mailer for that cycle.

How should I prepare for Razorpay interviews?

For Razorpay, prioritise DSA practice with timed mocks, revise OOPs and SQL, prepare a crisp project narrative, and read up on payment gateway and webhooks. Use STAR for behavioural answers and ask one thoughtful question at the end.

Razorpay Interview Experience 2025–2026 — Real Candidate Stories

Razorpay interview experience

These write-ups reflect how Razorpay fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

Razorpay placement process includes: 1. Online Assessment (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, technical deep dive, 4. Managerial Round (45 minutes) - Behavioral questions,…

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: Razorpay eligibility criteria for freshers (candidate-reported): Minimum 70% or 7.0+ CGPA in 10th, 12th, and graduation. B.Tech/B.E./M.Tech in CS, IT, Electronics, or related fields. Final year students and recent…

Fresher offers (candidate-reported) often land around ers (2025): Software Engineer (SDE-1): ₹18-25 LPA for new graduates, Software Engineer (SDE-2): ₹25-35 LPA (2. Treat numbers as directional — confirm on your offer letter.

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

Experience 1: SDE / Backend Engineer (2025)

Profile: B.Tech CSE, 7.8–8.4 CGPA, tier-2 college, 1 internship, decent DSA practice (150+ problems)

Online / written round

Focus stayed on problem-solving speed and clean code, not trick questions.
Cleared with full or near-full test cases; shortlist mail came in a few days.

Technical rounds

Coding: Design an LRU cache — approach used: HashMap + doubly linked list. Interviewer cared about complexity and edge cases.
Follow-up coding: Implement a rate limiter — sliding window / token bucket.
Domain discussion around payment gateway and webhooks — they wanted practical trade-offs, not buzzwords.
Project deep dive: why you chose the stack, what broke in production/testing, what you would redo.

HR / managerial

Why fintech / payments?
How do you handle production bugs under pressure?
Keep answers short and specific. Name the conflict, what you did, and the result.

Result: Selected What helped: Explaining approach before coding, admitting unknowns early, and linking project work to Razorpay’s domain (payment gateway).

Experience 2: SDE / Backend Engineer (2024–2025)

Profile: B.Tech IT / ECE, 7.2 CGPA, strong projects, average competitive programming

What differed

OA felt tougher on time; one medium-hard problem needed an optimised solution to clear the bar.
Second technical leaned more into idempotency and system design basics (APIs, DB choice, failure modes).
Coding warm-up: Validate overlapping transactions / intervals — sort + sweep line.

Mistakes to avoid

Jumping into code without clarifying constraints
Treating HR as a formality — Razorpay still filters on communication and intent
Memorising system design jargon without a simple capacity / bottleneck story

Result: Selected after a managerial / HR round Takeaway: For Razorpay, consistent DSA plus a clear story on payment gateway beats a perfect CGPA with weak explanation.

Questions that come up often

Coding / technical

Design an LRU cache — typically expects HashMap + doubly linked list
Implement a rate limiter — typically expects sliding window / token bucket
Validate overlapping transactions / intervals — typically expects sort + sweep line
Discussion on payment gateway and webhooks — capacity, failure modes, simple APIs
Project deep dive — architecture, hardest bug, what you would change

HR / behavioural

Why fintech / payments?
How do you handle production bugs under pressure?
Integrity scenario
Notice period / joining date

Practical tips for Razorpay

Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
For domain rounds, be ready to talk about payment gateway in plain language — inputs, outputs, bottlenecks.
Revise OOPs and SQL; many Razorpay panels still open with fundamentals.
Keep HR answers concrete. One story with a clear result beats five buzzwords.
If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

Razorpay HR Interview Questions — common HR questions and how to answer them
Razorpay Preparation Guide — round-wise prep plan
Razorpay Coding Questions — practice problems with approaches
Razorpay Previous Year Papers — past papers and patterns
Razorpay Placement Papers — company overview, eligibility, and process

Last updated: August 2026