Razorpay Qa Automation Engineer Sdet Interview Questions (2026)
30 real Qa Automation Engineer Sdet interview questions compiled for Razorpay, 30 of them tailored to Razorpay's actual interview flavor. Below: the interview process, the questions with answer outlines, the topics tested, and how to prepare.
Developer-first fintech hiring: coding rounds plus practical LLD/HLD grounded in payment-gateway problems, a hiring-manager round, and an explicit culture-fit conversation; the bar emphasizes API design quality and correctness because merchants integrate Razorpay's APIs directly.
Questions
30
30 company-tailored
Difficulty
Medium
from our question mix
Rounds
6
typical loop
Razorpay rating
3.35/5
Top 100% in FinTech
Razorpay's interview process
- 1Coding Screen45 minMedium
Practical coding problems of medium difficulty, sometimes closer to building a small utility than pure algorithm puzzles.
- 2Technical Round 255 minMedium
Deeper coding plus engineering fundamentals: concurrency, databases, and API behavior with follow-ups from your stack.
- 3Design Round (LLD/HLD)60 minHard
Design a gateway subsystem — webhook delivery with retries, payment routing across processors, or a settlement engine — with idempotency and audit trails.
- 4Hiring Manager Round50 minMedium
Project deep dive with emphasis on ownership, incidents affecting money movement, and cross-functional execution.
- 5Culture Fit Round40 minMedium
Conversation with a leader outside the hiring team on motivation, collaboration style, and alignment with Razorpay's customer-and-craft ethos.
- 6HR Round25 minEasy
Compensation, ESOPs, and offer logistics.
Qa Automation Engineer Sdet interview questions asked at Razorpay
- Q1
How would you test a REST API endpoint for Razorpay's subscription billing workflow with authentication, pagination, and error responses?
MediumAPI/UI automationAPI testingRazorpay-specificContext: Razorpay subscription billing workflow
How to answer: Cover contract checks, status codes, auth failures, paging boundaries, and schema validation. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q2
How would you integrate automated tests for Razorpay's seller onboarding flow into CI/CD without slowing every pull request?
MediumDebugging and test strategyCI/CD test executionRazorpay-specificContext: Razorpay seller onboarding flow
How to answer: Use suite tiers, parallelism, ownership, quarantines, and release-blocking criteria. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q3
When would you choose Cypress over Playwright or Selenium for Razorpay's checkout journey, and what tradeoffs would you call out?
MediumAutomation codingCypressRazorpay-specificContext: Razorpay checkout journey
How to answer: Compare browser coverage, debugging, network control, speed, and CI behavior. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q4
Explain Page Object Model for Razorpay's login and account recovery flow. When does it help, and when does it become a bad abstraction?
MediumAutomation codingPage Object ModelRazorpay-specificContext: Razorpay login and account recovery flow
How to answer: Keep page APIs user-intent oriented and avoid hiding assertions or business rules. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q5
How would you debug a flaky Playwright test in Razorpay's notification preference center?
MediumAutomation codingPlaywrightRazorpay-specificContext: Razorpay notification preference center
How to answer: Discuss locators, waits, traces, retries, isolation, network timing, and deterministic assertions. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q6
How would you use Postman/Newman in CI for Razorpay's admin approval workflow without making the suite hard to maintain?
MediumAPI/UI automationPostman/NewmanRazorpay-specificContext: Razorpay admin approval workflow
How to answer: Use environments, data files, assertions, secret handling, and useful reports. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q7
Design REST API tests for create, update, and delete operations in Razorpay's seller onboarding flow
MediumAPI/UI automationREST testingRazorpay-specificContext: Razorpay seller onboarding flow
How to answer: Check idempotency, validation, permissions, response shape, and audit events. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q8
Which SQL checks would you write to validate data created by Razorpay's checkout journey?
MediumAPI/UI automationSQL for testingRazorpay-specificContext: Razorpay checkout journey
How to answer: Check records, joins, statuses, timestamps, aggregates, and reconciliation with UI/API results. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q9
How would you handle dynamic elements in Selenium or Playwright for Razorpay's order tracking workflow?
MediumAutomation codingSeleniumRazorpay-specificContext: Razorpay order tracking workflow
How to answer: Prefer stable locators, explicit waits, app test IDs, and avoiding brittle sleeps. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q10
What accessibility checks would you include for Razorpay's subscription billing workflow?
MediumDebugging and test strategyaccessibility testing basicsRazorpay-specificContext: Razorpay subscription billing workflow
How to answer: Cover keyboard navigation, labels, focus order, contrast, screen-reader basics, and automated plus manual checks. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q11
Write the structure of a high-quality bug report for a failure in Razorpay's notification preference center
MediumDebugging and test strategybug reportingRazorpay-specificContext: Razorpay notification preference center
How to answer: Include environment, steps, expected versus actual, evidence, severity, and business impact. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q12
How would you work with developers when automation exposes recurring defects in Razorpay's notification preference center?
EasyBehavioral/project discussioncross-functional communicationRazorpay-specificContext: Razorpay notification preference center
How to answer: Focus on shared ownership, actionable reports, root cause, and prevention. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q13
How should a QA automation engineer handle a defect from discovery through closure for Razorpay's order tracking workflow?
MediumDebugging and test strategydefect lifecycleRazorpay-specificContext: Razorpay order tracking workflow
How to answer: Cover triage, reproduction, ownership, retest, regression coverage, and communication. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q14
Design an end-to-end test for Razorpay's order tracking workflow. What would you automate, what would you mock, and what would you leave manual?
MediumAPI/UI automationend-to-end testingRazorpay-specificContext: Razorpay order tracking workflow
How to answer: Focus on a few critical journeys, stable data, and readable failure output. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
- Q15
A test for Razorpay's checkout journey fails only in CI. How would you investigate and fix it?
HardDebugging and test strategyflaky test debuggingRazorpay-specificContext: Razorpay checkout journey
How to answer: Compare local versus CI state, browser versions, timing, data, parallelism, and logs. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.
Practice these with instant AI feedback in a live mock interview → Start a Razorpay Qa Automation Engineer Sdet mock
Topics tested most
How to prepare for the Razorpay Qa Automation Engineer Sdet interview
Strong coding + machine-coding and system design; understand reliability/scale in fintech
Frequently asked questions
How hard is the Razorpay Qa Automation Engineer Sdet interview?
Based on our bank of 30 Qa Automation Engineer Sdet questions asked at Razorpay, the overall difficulty is medium (Razorpay's process is generally rated elevated). Expect around 6 rounds spanning API testing, CI/CD test execution, Cypress.
How many interview rounds does Razorpay have for a Qa Automation Engineer Sdet?
Razorpay typically runs about 6 rounds for Qa Automation Engineer Sdet candidates: Coding Screen → Technical Round 2 → Design Round (LLD/HLD) → Hiring Manager Round → Culture Fit Round.
What is the interview process at Razorpay?
The Razorpay interview process typically runs: Online assessment -> machine coding/technical rounds -> system design -> hiring manager & culture. Prepare for each round in order rather than only the first — the later stages usually carry the most weight.
How hard is the Razorpay interview?
Razorpay interviews are rated high difficulty. The bar is highest on dsa — go deep there and practise explaining your reasoning out loud.
What does Razorpay look for in candidates?
Razorpay focuses on DSA, machine coding, system design, fintech reliability. Culturally, it values Customer first, ownership, transparency, frugality. Line up your examples to hit both the technical bar and these values.
Explore more
Compiled by PrepNPlaced from 30+ interview reports and question banks for the Razorpay Qa Automation Engineer Sdet loop, cross-referenced with 738 employee reviews. Data refreshed 2026-07-12. Updated 2026.