Razorpay - interview guide

Razorpay interview questions - a complete guide

Razorpay's machine coding round needs code that compiles and runs to the end. Here is how to prepare for it, along with payments concepts and the hiring manager round.

Language:EnglishHinglish

About Razorpay

Razorpay is an Indian payments and business banking company that helps businesses accept payments online. Its engineering involves a lot of work on reliability, security and APIs.

This guide covers 13 Razorpay interview questions with answers - what each question checks and how to answer it - plus the Razorpay interview process, round by round, a 7-day preparation plan for freshers, tips and the mistakes to avoid.

Razorpay hiring process

  1. Step 1: Online screen

    2-3 DSA questions and MCQs.

  2. Step 2: Machine coding

    60-90 minutes live - a functional, modular system from scratch that compiles and runs.

  3. Step 3: Hiring manager and culture

    Projects, tech decisions, how you handled conflict or failure. High-level design is mostly for SDE-2 and above.

Razorpay doesn't publish its process. Reports are mostly for senior roles, so this is indicative for freshers - confirm with the recruiter.

Sources (checked 16 October 2026): Razorpay Careers. Hiring processes change - read the official notice before you apply.

Razorpay interview questions and answers

Machine coding and payments

  1. 1.Machine coding: build a payment links system.

    What they're checking
    Working code tied to the domain.
    How to answer
    PaymentLink (amount, status, expiry), create/pay/expire flows, an in-memory store. A working version first, then validation and edge cases.
  2. 2.What is a webhook?

    What they're checking
    The core of payments integration.
    How to answer
    When an event happens (like a successful payment), one server tells another with an HTTP call. Verifying the signature and handling retries are essential.
  3. 3.Why use exponential backoff for retries?

    What they're checking
    Reliability.
    How to answer
    Retrying again and again immediately after a failure adds load to the server; doubling the wait each time (with some randomness) gives the system room to recover.

DSA

  1. 4.What is the minimum number of rooms needed for a set of meetings?

    What they're checking
    Intervals + a heap.
    How to answer
    Sort by start time; keep end times in a min-heap; a new meeting takes a free room when the top end ≤ its start. The heap's size = the answer.
  2. 5.Check whether a Sudoku board is valid.

    What they're checking
    Hashing.
    How to answer
    Sets for each row, column and 3x3 box; a duplicate means invalid.
  3. 6.Compare two strings where '#' is a backspace.

    What they're checking
    Two pointers.
    How to answer
    Walk from the end, counting '#' and skipping characters. O(1) extra space.

Hiring manager

  1. 7.Tell me about a technical decision that later turned out to be wrong.

    What they're checking
    Ownership and learning.
    How to answer
    What you decided, why, what went wrong, and how you decide now.
  2. 8.How did you resolve a disagreement in the team?

    What they're checking
    Collaboration.
    How to answer
    Talking with data, listening, and deciding together - in STAR.
  3. 9.Why Razorpay?

    What they're checking
    Motivation.
    How to answer
    Payments and fintech for Indian businesses - whatever genuinely appeals to you.

More questions

  1. 10.How do you keep API keys safe?

    What they're checking
    Security.
    How to answer
    Not in the code - in environment variables or a secret manager; rotate them immediately if they leak.
  2. 11.Find the longest substring of a string with k distinct characters.

    What they're checking
    Sliding window.
    How to answer
    A character count map for the window; when there are more than k distinct characters, shrink from the left.
  3. 12.What is settlement in payments?

    What they're checking
    Understanding the domain.
    How to answer
    Sending the money collected from customers (minus fees) to the merchant's bank account - usually on a set schedule.
  4. 13.Tell me about a production bug you fixed.

    What they're checking
    Ownership.
    How to answer
    How you found out, the root cause, the fix, and what you did so it doesn't happen again.

7-day preparation plan for the Razorpay interview

  1. Day 1: Machine coding - a wallet or payment links, 90 minutes.
  2. Day 2: Intervals and heaps.
  3. Day 3: Hashing and two pointers.
  4. Day 4: A second machine coding problem.
  5. Day 5: Webhooks, retries, idempotency.
  6. Day 6: Project decisions and STAR stories.
  7. Day 7: A mock round.

Preparation tips

  • In machine coding, a working solution first - perfection later.
  • Understand payments concepts (webhooks, idempotency, retries).
  • Prepare the reason behind every tech decision in your projects.

Mistakes to avoid

  • Over-engineering in machine coding and running out of time.
  • Code that doesn't compile - working code is required here.
  • Taking the hiring manager round lightly.

Frequently asked questions

What is the Razorpay machine coding round like?

Commonly 60-90 minutes live, building a functional system from scratch - code that compiles and runs.

How many rounds are there at Razorpay?

Commonly 3-4: an online screen, machine coding/DSA, hiring manager and HR.

Does Razorpay ask freshers about system design?

According to reports, high-level design is mostly for SDE-2 and above.

Do AI/LLM topics come up at Razorpay?

Some recent reports mention topics related to AI and LLMs.

Ready for your Razorpay interview?

Practise these questions with Cuelyte AI: add your resume, type a question and get a clear answer in your own words - in English, Hindi or Hinglish. Free to start.