Deloitte Qa Automation Engineer Sdet Interview Questions (2026)

1. 1Online Assessment60 minMedium

   Timed aptitude, technical MCQs, and English proficiency sections that gate the interview shortlist.

2. 2JAM / Group Discussion25 minEasy

   Speak for a minute on a surprise topic or debate in a group; screens articulation and composure.

3. 3Technical Interview45 minMedium

   Projects, core fundamentals (SQL, OOP, or domain), and applied scenario questions for the service line.

4. 4Senior / Manager Round45 minMedium

   Manager runs a case-let or client scenario plus deep project probing to judge consulting readiness.

5. 5HR Discussion30 minEasy

   Values-fit conversation, compensation, location, and background verification expectations.

1. Q1

   How would you test a REST API endpoint for Deloitte's seller onboarding flow with authentication, pagination, and error responses?

   MediumAPI/UI automationAPI testingDeloitte-specific

   Context: Deloitte seller onboarding flow

   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 Deloitte's admin approval workflow into CI/CD without slowing every pull request?

   MediumDebugging and test strategyCI/CD test executionDeloitte-specific

   Context: Deloitte admin approval workflow

   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 Deloitte's login and account recovery flow, and what tradeoffs would you call out?

   MediumAutomation codingCypressDeloitte-specific

   Context: Deloitte login and account recovery flow

   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 Deloitte's search and filtering experience. When does it help, and when does it become a bad abstraction?

   MediumAutomation codingPage Object ModelDeloitte-specific

   Context: Deloitte search and filtering experience

   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 Deloitte's order tracking workflow?

   MediumAutomation codingPlaywrightDeloitte-specific

   Context: Deloitte order tracking workflow

   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 Deloitte's notification preference center without making the suite hard to maintain?

   MediumAPI/UI automationPostman/NewmanDeloitte-specific

   Context: Deloitte notification preference center

   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 Deloitte's admin approval workflow

   MediumAPI/UI automationREST testingDeloitte-specific

   Context: Deloitte admin approval workflow

   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 Deloitte's login and account recovery flow?

   MediumAPI/UI automationSQL for testingDeloitte-specific

   Context: Deloitte login and account recovery flow

   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 Deloitte's checkout journey?

   MediumAutomation codingSeleniumDeloitte-specific

   Context: Deloitte checkout journey

   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 Deloitte's seller onboarding flow?

    MediumDebugging and test strategyaccessibility testing basicsDeloitte-specific

    Context: Deloitte seller onboarding flow

    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 Deloitte's order tracking workflow

    MediumDebugging and test strategybug reportingDeloitte-specific

    Context: Deloitte order tracking workflow

    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 Deloitte's order tracking workflow?

    EasyBehavioral/project discussioncross-functional communicationDeloitte-specific

    Context: Deloitte order tracking workflow

    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 Deloitte's checkout journey?

    MediumDebugging and test strategydefect lifecycleDeloitte-specific

    Context: Deloitte checkout journey

    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 Deloitte's checkout journey. What would you automate, what would you mock, and what would you leave manual?

    MediumAPI/UI automationend-to-end testingDeloitte-specific

    Context: Deloitte checkout journey

    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 Deloitte's login and account recovery flow fails only in CI. How would you investigate and fix it?

    HardDebugging and test strategyflaky test debuggingDeloitte-specific

    Context: Deloitte login and account recovery flow

    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 Deloitte Qa Automation Engineer Sdet mock

Prepare aptitude, case/technical and behavioral; communicate structured thinking

Other roles at Deloitte

Qa Automation Engineer Sdet interviews at other companies