← Interview experiences
Rejected

Senior Software Engineer at RazorPay

Difficulty
Process took
1-2 Weeks
Rounds
4
Format
On site
Applied via
Company Website

How it went

Although I didn’t make it through, the experience was valuable. I realized that system design rounds are often the differentiator between good candidates and exceptional ones.

What they would tell you

Although I didn’t make it through, the experience was valuable. I realized that system design rounds are often the differentiator between good candidates and exceptional ones.

How to prepare

Regularly practice designing end-to-end systems for apps like URL shorteners, ride-sharing platforms, e-commerce checkouts, or collaborative editors. Sketch HLD diagrams, break them into LLD.

Their background

Hey everyone, sharing my Razorpay interview experience, it was one of the most rewarding interview processes I have gone through so far. Applied through the careers portal and got call just 4 days later, which was really fast. I had been preparing for about 3 months, going through system design, DSA problems, and machine coding, so I felt reasonably confident going into it.

Round by round

  1. 1

    System Design Round60 min

    This was my first round, interviewer asked me to design a payment processing pipeline, basically a system that could handle multiple payment sources, validate transactions, process them, and send confirmations.I began by explaining the overall architecture, like how the service would accept requests, queue them, process asynchronously, and handle retries Honestly, this round felt great and the interviewer seemed satisfied

    Verdict: Hire

  2. 2

    Machine Coding Round60 min

    Next up was a machine coding round the problem was to design a transaction logger service with REST APIs.

    • Requirements: adding transactions, querying by user or date, and supporting dynamic configurations. The interviewer wanted a fully working, implementation, so I wrote modular code with proper error handling. I remember being a bit nervous initially, but as I coded, I got into a rhythm. The interviewer gave hints along the way, and it felt like a real collaborative discussion rather than just testing
  3. 3

    Low Level Design Round60 min

    Once the short break ended, I returned to the room and was handed a new challenge, build something like Google Docs, complete with access control. The interviewer was curious to hear my thoughts on storage, database schema, and syncing logic. I described how edits could ripple through the system in real time, how conflicting changes might be resolved, and how permissions would shape user actions.

  4. 4

    HM Round60 min

    Questions about my current role, responsibilities, and career aspirations, and we talked about how I see myself contributing at Razorpay

What came up

Medium HardOn site5+ years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources