Accenture Qa Automation Engineer Sdet Interview Questions (2026)

1. 1Cognitive & Technical Assessment60 minMedium

   Timed online MCQs on aptitude, English, pseudocode, networking, and MS Office/cloud fundamentals.

2. 2Coding Assessment45 minMedium

   1-2 straightforward coding problems in a language of choice; correctness over optimization.

3. 3Communication Assessment30 minEasy

   Automated spoken-English evaluation (listening, pronunciation, fluency) that gates client-facing readiness.

4. 4Technical Interview45 minMedium

   Project walk-through, language/skill-track fundamentals, and scenario questions for the assigned practice.

5. 5Managerial / Client-Fit Round45 minMedium

   Delivery manager probes client-handling scenarios, estimation, escalations, and team leadership for experienced hires.

6. 6HR Discussion30 minEasy

   Compensation, location/shift flexibility, relocation, and joining timeline; light behavioral questions.

1. Q1

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

   MediumAPI/UI automationAPI testingAccenture-specific

   Context: Accenture 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 Accenture's seller onboarding flow into CI/CD without slowing every pull request?

   MediumDebugging and test strategyCI/CD test executionAccenture-specific

   Context: Accenture 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 Accenture's checkout journey, and what tradeoffs would you call out?

   MediumAutomation codingCypressAccenture-specific

   Context: Accenture 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 Accenture's login and account recovery flow. When does it help, and when does it become a bad abstraction?

   MediumAutomation codingPage Object ModelAccenture-specific

   Context: Accenture 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 Accenture's notification preference center?

   MediumAutomation codingPlaywrightAccenture-specific

   Context: Accenture 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 Accenture's admin approval workflow without making the suite hard to maintain?

   MediumAPI/UI automationPostman/NewmanAccenture-specific

   Context: Accenture 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 Accenture's seller onboarding flow

   MediumAPI/UI automationREST testingAccenture-specific

   Context: Accenture 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 Accenture's checkout journey?

   MediumAPI/UI automationSQL for testingAccenture-specific

   Context: Accenture 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 Accenture's order tracking workflow?

   MediumAutomation codingSeleniumAccenture-specific

   Context: Accenture 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 Accenture's subscription billing workflow?

    MediumDebugging and test strategyaccessibility testing basicsAccenture-specific

    Context: Accenture 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 Accenture's notification preference center

    MediumDebugging and test strategybug reportingAccenture-specific

    Context: Accenture 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 Accenture's notification preference center?

    EasyBehavioral/project discussioncross-functional communicationAccenture-specific

    Context: Accenture 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 Accenture's order tracking workflow?

    MediumDebugging and test strategydefect lifecycleAccenture-specific

    Context: Accenture 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 Accenture's order tracking workflow. What would you automate, what would you mock, and what would you leave manual?

    MediumAPI/UI automationend-to-end testingAccenture-specific

    Context: Accenture 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 Accenture's checkout journey fails only in CI. How would you investigate and fix it?

    HardDebugging and test strategyflaky test debuggingAccenture-specific

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

Clear aptitude + fundamentals; communicate well; prepare basic technical + HR questions

Other roles at Accenture

Qa Automation Engineer Sdet interviews at other companies