Razorpay Qa Automation Engineer Sdet Interview Questions (2026)

1. 1Coding Screen45 minMedium

   Practical coding problems of medium difficulty, sometimes closer to building a small utility than pure algorithm puzzles.

2. 2Technical Round 255 minMedium

   Deeper coding plus engineering fundamentals: concurrency, databases, and API behavior with follow-ups from your stack.

3. 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.

4. 4Hiring Manager Round50 minMedium

   Project deep dive with emphasis on ownership, incidents affecting money movement, and cross-functional execution.

5. 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.

6. 6HR Round25 minEasy

   Compensation, ESOPs, and offer logistics.

1. 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-specific

   Context:

   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.

2. Q2

   When would you choose Cypress over Playwright or Selenium for Razorpay's checkout journey, and what tradeoffs would you call out?

   MediumAutomation codingCypressRazorpay-specific

   Context:

   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.

3. Q3

   Design REST API tests for create, update, and delete operations in Razorpay's seller onboarding flow

   MediumAPI/UI automationREST testingRazorpay-specific

   Context:

   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.

4. Q4

   Write the structure of a high-quality bug report for a failure in Razorpay's notification preference center

   MediumDebugging and test strategybug reportingRazorpay-specific

   Context:

   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.

5. Q5

   What basic performance tests would you run for Razorpay's search and filtering experience before a large release?

   HardDebugging and test strategyperformance testing basicsRazorpay-specific

   Context:

   Razorpay search and filtering experience

   How to answer:

   Discuss realistic load, response-time goals, bottleneck evidence, and production-safe thresholds. 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.

6. Q6

   How would you decide the regression suite for Razorpay's seller onboarding flow after a major refactor?

   MediumTesting fundamentalsregression testingRazorpay-specific

   Context:

   Razorpay seller onboarding flow

   How to answer:

   Separate smoke, sanity, targeted regression, and full regression. 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.

7. Q7

   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-specific

   Context:

   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.

8. Q8

   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-specific

   Context:

   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.

9. Q9

   How would you debug a flaky Playwright test in Razorpay's notification preference center?

   MediumAutomation codingPlaywrightRazorpay-specific

   Context:

   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.

10. Q10

    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-specific

    Context:

    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.

11. Q11

    Which SQL checks would you write to validate data created by Razorpay's checkout journey?

    MediumAPI/UI automationSQL for testingRazorpay-specific

    Context:

    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.

12. Q12

    How would you handle dynamic elements in Selenium or Playwright for Razorpay's order tracking workflow?

    MediumAutomation codingSeleniumRazorpay-specific

    Context:

    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.

13. Q13

    What accessibility checks would you include for Razorpay's subscription billing workflow?

    MediumDebugging and test strategyaccessibility testing basicsRazorpay-specific

    Context:

    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.

14. Q14

    How would you work with developers when automation exposes recurring defects in Razorpay's notification preference center?

    EasyBehavioral/project discussioncross-functional communicationRazorpay-specific

    Context:

    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.

15. Q15

    How should a QA automation engineer handle a defect from discovery through closure for Razorpay's order tracking workflow?

    MediumDebugging and test strategydefect lifecycleRazorpay-specific

    Context:

    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.

Practice these with instant AI feedback in a live mock interview → Start a Razorpay Qa Automation Engineer Sdet mock

Strong coding + machine-coding and system design; understand reliability/scale in fintech

Qa Automation Engineer Sdet interviews at other companies