Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Technical · Razorpay

Razorpay Technical Interview Questions 2026

Razorpay's coding rounds anchor data-structures and algorithms to real payments scenarios: idempotent retries, NPCI rate limits, and settlement reconciliation.

By the HireStepX editorial team · How we source and label this

Questions4
Rounds3
Intense3 of 4
FrameworkPayments-Aware DSA
Try it · Razorpay question 1 of 4
Intense

Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect medium-to-hard problems where the interviewer wants your reasoning stated aloud, a clean implementation, and an awareness that the code would sit in a payments backend where correctness and concurrency matter. Pure algorithmic answers that ignore edge cases like duplicate callbacks or partial failures tend to lose points; framing your solution around production reality is the Razorpay differentiator.

Practice questions

  1. 01

    Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?

    IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
    Practise
  2. 02

    We see UPI failure rates spike at 9pm on weekends. How would you debug and what's your hypothesis?

    StandardReal Razorpay scenario. Expected: bank-side downtime (most likely), peak load + thread-pool exhaustion, NPCI rate limits.
    Practise
  3. 03

    On Black Friday, p99 checkout latency jumped from 200ms to 4s for 30 minutes. We have full traces. Walk me through your war-room playbook.

    IntenseRazorpay ops-incident war-room probe. Tests: triage discipline (flame-graph first, narrow scope), upstream-vs-self attribution, comms cadence (every 15 min), post-incident artifacts (timeline, MTR review, runbook update).
    Practise
  4. 04

    Walk me through an architecture migration you led across 30+ engineers. What was the rollback plan and when did you nearly need it?

    IntenseTech-leadership probe (not pure IC). Wants migration scope + organisational coordination + actual rollback trigger criteria. 'We didn't need the rollback' fails, interviewer wants the *moment you almost pulled the trigger*.
    Practise
Prep notes

How to walk in ready.

The typical Razorpay recruitment process has 4 stages: Online coding assessment or resume screen → Technical coding round one on DSA → Technical coding round two on harder problems and system framing → Hiring-manager round, then offer.

Razorpay typically conducts 3 interview rounds: Round 1 (60-90 min): online assessment with DSA problems; Round 2 (60 min): live coding on arrays, strings, hashing, or trees; Round 3 (60 min): harder coding round with complexity analysis and payments-context follow-ups.

HireStepX recommends the Payments-Aware DSA framework for this type of interview: Solve the algorithm cleanly with a stated complexity, then name the production edge case (idempotency, concurrency, partial failure) the code must survive.

Razorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.

Real Razorpay scenario. Expected: bank-side downtime (most likely), peak load + thread-pool exhaustion, NPCI rate limits.

Razorpay ops-incident war-room probe. Tests: triage discipline (flame-graph first, narrow scope), upstream-vs-self attribution, comms cadence (every 15 min), post-incident artifacts (timeline, MTR review, runbook update).

Tech-leadership probe (not pure IC). Wants migration scope + organisational coordination + actual rollback trigger criteria. 'We didn't need the rollback' fails, interviewer wants the *moment you almost pulled the trigger*.

Arrays, strings, hashing, heaps, trees, and graphs, frequently framed around payments scenarios like retries, rate limiting, and reconciliation rather than abstract puzzles.

Practice

Rehearse the room before you enter it.

Run a mock Razorpay interview and get scored feedback on every answer.