0 day streak

Razorpay interview rounds

ProductFintech India Machine coding / LLD

Pick your level above: the list shows only your rounds, with what interviewers score at that level.

0%ready
  1. Phone / recruiter screen · 20 min

    An HR screen on stack, experience and compensation.

    At : Usually one medium problem. Explain your idea before coding and test by hand at the end.

    At : One or two problems, a little faster. Some companies mix in a design question.

    At : Often a coding problem plus questions about your past systems; some companies (Uber) use it to set your level.

    At : Frequently a hiring-manager conversation about scope and impact instead of pure coding.

  2. Online assessment · 90 min

    Two or three DSA problems plus MCQs, reportedly including AI and LLM basics.

    At : The main filter for new grads and campus drives. Expect two medium problems, sometimes one hard. Passing all test cases on both usually gets you to the next round.

    At : Used by some companies for experienced hires (Amazon, Uber, Salesforce, Oracle). The bar is the same as for SDE 1 but the time is often shorter.

    At : Rare. Most companies replace it with a live screen for senior candidates.

    At : Almost never used.

  3. Low-level design / machine coding · 90 min

    Machine coding: build a working in-memory system that matches the spec exactly, often the first round for lateral hires.

    At : Object-oriented design with clear classes and responsibilities. Working code matters more than patterns.

    At : The core round at many product companies: working, modular, extensible code with validation, error handling and tests, finished on time.

    At : Same as SDE 2 plus concurrency (two users booking the same seat) and a clean extension story.

    At : Rare as a standalone round; folded into design discussions.

  4. System design (HLD) · 60 min

    Starts from requirements, then goes deep on scalability, availability and consistency per component.

    At : Usually absent, or light design questions inside a coding round.

    At : Present at most companies. A sound end-to-end design with sensible components and basic scaling is enough.

    At : One or two rounds that set your level. Expected to lead, size the system and go deep on two or three hard parts.

    At : Two rounds at many companies. Expected to handle ambiguity, cost, operations and cross-team trade-offs, and to change the design when the interviewer pushes.

  5. Team-specific round · 60 min

    A one-hour technical deep dive on a single past project.

    At : Mostly language and CS fundamentals deep dives (Java internals, databases, OS).

    At : Debugging, integration or code review rounds at product companies.

    At : Project deep dives become central: scope, trade-offs and what you would do differently.

    At : Presentations or deep dives on multi-quarter work that crossed teams.

  6. Hiring manager · 60 min

    Projects, ownership, production incidents, and CS fundamentals for junior roles.

    At : Motivation, learning, a project walk-through and sometimes CS fundamentals.

    At : Ownership of features, handling production issues, working with product and other teams.

    At : Technical leadership, mentoring, and how you choose what to work on.

    At : Strategy, influence without authority and the biggest bets you have made.

What interviewers look for

  • Spec-exact, compilable machine-coding solutions
  • Extensibility when requirements change mid-round
  • Consistency and availability trade-offs in HLD
  • Ownership and handling of production issues
  • Customer-first decisions

Worth knowing

  • Two separate 2025 reports describe the same machine-coding prompt: an in-memory relational store with create, insert, update, delete and index.
  • A 2025 senior candidate was rejected despite a working solution because input handling differed from the problem statement: read the spec twice.
  • A 2025 loop: machine coding, design (notification service), a project deep dive, then manager.

Sources

Written in our own words from public candidate reports and Razorpay's careers pages, checked 2026-11. Company names and logos belong to their owners; AlgoRung is not affiliated with Razorpay.

Questions people ask

How many interview rounds does Razorpay have for SDE 1 (SDE-1)?

About 2 interviews after the screening: phone / recruiter screen, online assessment, low-level design / machine coding, hiring manager. Design is part of the loop at this level.

How many interview rounds does Razorpay have for SDE 2 (SDE-2)?

About 4 interviews after the screening: phone / recruiter screen, online assessment, low-level design / machine coding, system design (hld), team-specific round, hiring manager. Design is part of the loop at this level.

How many interview rounds does Razorpay have for SDE 3 (Senior SDE)?

About 4 interviews after the screening: phone / recruiter screen, low-level design / machine coding, system design (hld), team-specific round, hiring manager. Design is part of the loop at this level.

What coding questions does Razorpay ask?

The most reported are Maximum Profit in Job Scheduling, Two Best Non-Overlapping Events, Longest Substring with At Most K Distinct Characters, House Robber, Target Sum, Merge Intervals. Candidates say Razorpay focuses on greedy, dynamic programming, graphs, trees, sliding window.

What is the Razorpay behavioral interview based on?

Company values: Customer First, Autonomy & ownership, Challenging the status quo, Agility with Integrity, Transparency, Razorpay Grows with Razors. The company blog says interviews are built to check for these values; prepare a story for each.