Amazon Qa Automation Engineer Sdet Interview Questions (2026)

1. 1Online Assessment (SDE OA)60 minMedium

   Two timed coding problems plus a workplace-simulation and logic section; the main gate for freshers and India volume hiring.

2. 2Phone screen45 minMedium

   One coding problem plus 1-2 Leadership Principle STAR questions with an SDE.

3. 3Coding loop round60 minMedium

   DSA problem to working code, followed by assigned-LP behavioral questions in STAR format.

4. 4System design loop round60 minHard

   Design an Amazon-scale service with capacity math, plus LPs; low-level/OOD design substitutes for junior candidates.

5. 5Hiring Manager round45 minMedium

   Team fit, project deep dives, and Deliver Results/Bias for Action stories with the manager you would report to.

6. 6Bar Raiser60 minHard

   An interviewer from outside the team stress-tests LP stories and overall bar with the hardest cross-examination of the loop; holds veto.

1. Q1

   How would you test a REST API endpoint for Amazon's subscription billing workflow with authentication, pagination, and error responses?

   MediumAPI/UI automationAPI testingAmazon-specific

   Context: Amazon 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

   How would you integrate automated tests for Amazon's seller onboarding flow into CI/CD without slowing every pull request?

   MediumDebugging and test strategyCI/CD test executionAmazon-specific

   Context: Amazon 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.

3. Q3

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

   MediumAutomation codingCypressAmazon-specific

   Context: Amazon 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.

4. Q4

   Explain Page Object Model for Amazon's login and account recovery flow. When does it help, and when does it become a bad abstraction?

   MediumAutomation codingPage Object ModelAmazon-specific

   Context: Amazon 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.

5. Q5

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

   MediumAutomation codingPlaywrightAmazon-specific

   Context: Amazon 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.

6. Q6

   How would you use Postman/Newman in CI for Amazon's admin approval workflow without making the suite hard to maintain?

   MediumAPI/UI automationPostman/NewmanAmazon-specific

   Context: Amazon 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.

7. Q7

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

   MediumAPI/UI automationREST testingAmazon-specific

   Context: Amazon 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.

8. Q8

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

   MediumAPI/UI automationSQL for testingAmazon-specific

   Context: Amazon 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.

9. Q9

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

   MediumAutomation codingSeleniumAmazon-specific

   Context: Amazon 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.

10. Q10

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

    MediumDebugging and test strategyaccessibility testing basicsAmazon-specific

    Context: Amazon 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.

11. Q11

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

    MediumDebugging and test strategybug reportingAmazon-specific

    Context: Amazon 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.

12. Q12

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

    EasyBehavioral/project discussioncross-functional communicationAmazon-specific

    Context: Amazon 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.

13. Q13

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

    MediumDebugging and test strategydefect lifecycleAmazon-specific

    Context: Amazon 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.

14. Q14

    Design an end-to-end test for Amazon's order tracking workflow. What would you automate, what would you mock, and what would you leave manual?

    MediumAPI/UI automationend-to-end testingAmazon-specific

    Context: Amazon 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.

15. Q15

    A test for Amazon's checkout journey fails only in CI. How would you investigate and fix it?

    HardDebugging and test strategyflaky test debuggingAmazon-specific

    Context: Amazon 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 Amazon Qa Automation Engineer Sdet mock

Prepare 8-12 STAR stories mapped to Leadership Principles; expect a Bar Raiser; quantify impact

Other roles at Amazon

Qa Automation Engineer Sdet interviews at other companies