12 Razorpay HR interview questions with sample answers: why HR asks each one and how to answer. From public candidate reports. Free.
At Razorpay the HR round usually comes after you clear the coding assessment, the machine coding or LLD round, and often a hiring manager round. One candidate's 2024 post shows the order as HackerEarth test, machine coding on an in-memory EMI loan calculator, then HM round, with HR calling after to confirm the role level. It is a short conversation, typically 20 to 40 minutes, run by an HR or talent partner, and it is mostly about role fit, expectations, and paperwork rather than code.
What the Razorpay HR round checks:
The first question is always some version of "tell me about yourself". Write your self introduction for the interview (free, no signup).
4 of these 12 questions appear in public Razorpay interview reports; the rest are standard HR questions the company is known to ask.
Why they ask: They want to hear a reason tied to Razorpay's product and scale, not a generic 'good company' answer.
How to answer: Name one or two concrete things about Razorpay: payments and banking products, the scale of transactions, or the fintech problem space. Connect it to something you have actually built or studied. Keep it to two or three sentences and avoid listing perks.
Sample answer: I have been following Razorpay since I built a small payment flow for my [college] fest website. What stuck with me is that you handle payments, banking and lending in one stack, and the engineering problems around reliability and reconciliation are real. I want to work on systems where a failed transaction actually matters to someone's business. That is the kind of ownership I am looking for at this stage of my career.
Why they ask: This is a softer version of the why-us question, checking whether your goals line up with the role you are being hired for.
How to answer: State a short-term goal that matches the role, like growing as a backend or full-stack engineer on payment systems, and a longer-term goal that is realistic. Do not say you want to switch to a different team or role in a year. Tie your motivation to learning from the team and shipping real features.
Sample answer: In the next two years I want to get strong at building and owning backend services at scale, especially around payments where correctness matters. Longer term I want to be someone the team trusts with a critical service end to end. Razorpay gives me that exposure early, and I am motivated by the fact that the work is used by real businesses every day.
Why they ask: This shows up in Razorpay HR interviews and checks whether you can work with others without needing to be managed constantly.
How to answer: Talk about how you actually collaborate: clear ownership, small check-ins, and raising blockers early. Give one example from a project or internship where you coordinated with others. If you are a fresher, use a college team project, not a made-up work story.
Sample answer: In my [college] final year project, four of us built a [project name] and I owned the backend. We agreed on interfaces first, then did short stand-ups twice a week. When one teammate was stuck on the database schema, I paired with him for an hour instead of waiting. We shipped on time because blockers came up early, not at the deadline. That is how I would work in a team here too.
Why they ask: One 2024 candidate reported HR confirming the role was PDE, not SDE, with a different pay structure, so they want to know you understand and accept the level before moving ahead.
How to answer: Ask what the PDE role involves day to day and how it differs from SDE in scope and growth, then answer honestly. If you are fine with it, say so clearly and explain why the work matters more than the title. If you are not, say that too, calmly, and ask if an SDE opening is possible.
Sample answer: I understand PDE and SDE sit in the same team but differ in level and pay. Before I commit, can you tell me what the PDE role owns in the first year and how people typically move up? If the work is real product engineering on payments, I am happy to start there and prove myself. I would rather grow inside the team than hold out for a title.
Why they ask: They need a number to check against the band for the level they have in mind, and they want to see if you are realistic.
How to answer: Give a range, not a single number, and anchor it to the level and location. If you do not know the band, say you are open to the standard range for this role and level. Do not inflate wildly or say 'as per company norms' with no number at all.
Sample answer: I am targeting the standard range for this level in [city], which I understand is around [X to Y] lakhs fixed. I am flexible on the exact number if the role and learning are right. If you can share the band for PDE or SDE at my level, I can tell you where I fit.
Why they ask: Razorpay hires on rolling timelines and needs to plan onboarding, so they check how soon you can start.
How to answer: State your notice period exactly as per your contract and give a realistic earliest date. If you are a fresher, say you can join immediately or after your exams, with the date. Do not promise a date you cannot meet.
Sample answer: My notice period is [30 or 60 or 90] days as per my current contract, so my earliest joining date would be [date]. If the team needs me sooner, I can check with my manager about an early release, but I cannot confirm that until I ask. I will keep you updated within a week.
Why they ask: Razorpay's engineering teams are largely office-based, and they want to know you will actually show up.
How to answer: Answer directly about relocation and office days. If you have constraints, state them now rather than after the offer. Mention any prior experience of living away from home if it helps.
Sample answer: Yes, I am open to relocating to Bangalore. I have lived away from home during my [college or internship] in [city], so it is not a problem for me. I am also fine with working from the office on the days the team needs. If there is any flexibility on location, I would like to know, but relocation is not a blocker.
Why they ask: Payments run 24 by 7, so some teams have on-call rotations or odd hours, and they want no surprises later.
How to answer: Say yes if you mean it, and ask how the rotation works so you understand the load. If you have a genuine constraint, say it plainly. Do not agree to something you will resent in three months.
Sample answer: Yes, I am comfortable with on-call if the team runs a rotation. I would like to understand how often it comes around and how escalations are handled. I have handled late-night debugging during my [internship or project], so I know what it involves. As long as it is shared fairly across the team, I am fine with it.
Why they ask: This is the standard opening, and they use it to check your story matches your resume and the role.
How to answer: Give a two-minute version: education, one or two projects or jobs, the skills that matter for this role, and why you are here. Do not recite your resume line by line. End with why this role is the logical next step.
Sample answer: I did my [degree] from [your college] and spent most of my time on backend projects. My main one was a [project], where I built the API and handled [specific thing]. I also interned at [company] for [duration], working on [task]. That is where I got comfortable with [tech]. I am applying here because the work is payments at scale, and that is the direction I want to build in.
Why they ask: They want to see if you have thought about the role seriously, and it is your chance to clear doubts before an offer.
How to answer: Ask two or three specific questions about the team, the tech stack, the first six months, or the PDE to SDE path if that applies. Avoid asking only about salary and leave in this round. Write your questions down before the call.
Sample answer: Yes, a few. What does the first six months look like for someone at my level, and who would I report to? Which services would I likely work on, and what is the stack? And if I join as PDE, what does the path to SDE look like in terms of review and timeline? I want to know what good performance looks like here.
Why they ask: They are checking maturity and whether you can keep a project moving without drama.
How to answer: Pick a real, small conflict from a project and describe what you did, not what the other person did wrong. Show that you listened, found the actual issue, and moved to a decision. Keep it short and end with the outcome.
Sample answer: In a college project, a teammate wanted to use [tech A] and I wanted [tech B] for the backend. Instead of arguing, we each built a small prototype over a weekend and compared. His was faster to set up, mine handled the queries better, so we went with his for the MVP and mine later. The project shipped, and we stayed on good terms. I learned to test instead of debate.
Why they ask: Standard HR check on self-awareness, and they compare it against how you came across in the technical rounds.
How to answer: Give one strength with a short proof, and one real weakness with what you are doing about it. Do not use a fake weakness like 'I work too hard'. Keep both answers to a few sentences.
Sample answer: My strength is that I finish things. In my [project or internship], I owned the [feature] end to end, including the parts nobody wanted to touch, like tests and error handling. My weakness is that I used to spend too long polishing code before showing it. I have started sharing rough versions early for feedback, which has saved me rework. I am still working on it, but it is better than it was.
Role level. A 2024 candidate reported that HR confirmed the offer was for PDE, not SDE, and that PDE and SDE sit in the same team but have a significant difference in pay structure. Clarify your level and band before you accept.
Interview order. The same candidate reported the process as a HackerEarth assessment with three questions (one DP medium, one DP hard, one SQL query), then a machine coding or LLD round on an in-memory EMI loan calculator, then an HM round, with HR contact after.
Machine coding topic. The reported LLD prompt was an in-memory EMI loan calculator, with bonus requirements and follow-up questions from the interviewer. Expect the HR round only after you clear this.
Common HR questions. AmbitionBox lists Razorpay HR questions such as why you want to join, your aim or motivation for joining, and how you will manage a team and ensure work completion when collaborating.
Office and location. Engineering roles are commonly reported to be office-based in Bangalore, so be ready to answer on relocation and office days. This is a general norm, not a published Razorpay policy in the reports.
Bond or service agreement. candidate reports do not state a bond or service agreement for Razorpay engineering roles. Do not assume one exists; ask HR directly if it matters to you.
Practise the Razorpay HR round in a free 5-minute mock
Candidates report questions such as: Why do you want to join Razorpay; What is your aim or motivation for joining this company; How will you manage the team and ensure work gets completed when collaborating; Are you comfortable with the role being PDE and not SDE. Each one is answered on this page.
At Razorpay the HR round usually comes after you clear the coding assessment, the machine coding or LLD round, and often a hiring manager round. One candidate's 2024 post shows the order as HackerEarth test, machine coding on an in-memory EMI loan calculator, then HM round, with HR calling after to confirm the role level. It is a short conversation, typically 20 to 40 minutes, run by an HR or talent partner, and it is mostly about role fit, expectations, and paperwork rather than code.
Yes. Candidates are rejected in the HR round for unclear answers on relocation, shifts or the package, for contradicting their resume, or for seeming uninterested in Razorpay. Decide your honest answers before the call.
No. They come from public candidate reports and are unofficial. PortLume AI is not affiliated with Razorpay.
Based on 12 public reports: YouTube (5), AmbitionBox (3), Reddit (2), Glassdoor (1), LeetCode Discuss (1), last updated Oct 2026.
Unofficial guide from public candidate reports. PortLume AI is not affiliated with Razorpay. HR questions for other companies · all company interview guides.
PortLume AI
Loading…