Razorpay

Razorpay's process is structured and mostly virtual, with three to five evaluated conversations depending on the role and level. Expect two to four weeks from first call to offer.

1. Application and recruiter screen

Apply on the Razorpay careers page, through a referral, campus placement or a job portal such as Jobaaj. A recruiter calls to confirm your experience, current role, notice period and expectations, and explains the rounds for the specific team.

2. Online coding or functional assessment

Engineering candidates take a timed online coding test on a standard platform with two or three problems. Product, analytics and risk roles may receive a take-home case or a short assignment instead. Sales roles skip this step and go straight to interviews.

3. Technical or functional interviews

Two rounds with engineers or functional leads: a problem-solving and coding round, followed by a design or domain round. For business roles these become a role-play or case discussion around merchant acquisition, payments products or risk scenarios.

4. Hiring manager round

The manager you would report to discusses your past projects in depth, how you handle ambiguity and ownership, and fit with the team's roadmap. This round often decides the level you are offered.

5. Leadership or culture conversation

For senior roles a founder or function head speaks with you about motivation, values and long-term thinking. For junior roles this is usually folded into the manager round.

6. Offer and background check

HR shares a compensation breakdown covering fixed pay, variable pay and ESOPs where applicable, followed by document verification and a joining date.

The rounds below follow the software engineering track, with notes on how product, risk and sales interviews differ.

Round 1: Online coding assessment

About 90 minutes with two or three problems of easy to medium difficulty. Hidden test cases and code quality both matter, so handle edge cases and write readable code.

• Arrays, strings, hashing and two-pointer techniques
• Trees, graphs and basic dynamic programming
• Time and space complexity of your solution

Round 2: Data structures and problem solving

A 60 minute live coding interview with an engineer in a shared editor. You are expected to talk through your approach before coding and to improve the solution on hints.

• Designing an idempotent payment retry mechanism
• Rate limiting and concurrency-safe counters
• Medium problems on linked lists, heaps and intervals

Round 3: System design or low-level design

Freshers get a low-level design round on object modelling; engineers with three or more years get a high-level design discussion of 60 minutes.

• Design a payment gateway flow with webhooks and reconciliation
• Handling failures, retries and exactly-once settlement
• Database choices, sharding and caching for high write volumes

Round 4: Hiring manager and behavioural

A 45 minute conversation on your projects, decisions you owned and how you work with product and other teams.

• A project you drove end to end and what you would change
• Handling a production incident or a disagreement with a peer
• Why fintech and why Razorpay

Round 5: Functional round for non-engineering roles

Sales, risk and product candidates get a case or role-play of 45 to 60 minutes in place of the coding rounds.

• Pitching Razorpay's products to a mid-sized online business
• Prioritising features for a payouts or subscriptions product
• Spotting fraud patterns in merchant transaction data