Skip to content

IT services

Accenture

Consulting-style QA: strategy, risk, and tooling choices.

These are our own practice questions for the kind of QA/SDET role this company hires for. They are not the company's real interview questions. Confirm the current process on the company's official careers page.

What they tend to probe

  • Test strategy
  • Risk-based testing
  • Automation tooling
  • Cloud testing
  • Stakeholder communication
  1. Question 1 · Strategy · Medium

    A client wants 100% automation. How do you respond?

    Answer guide

    Reframe to the outcome: fast, trusted feedback. Show a pyramid, what is cheap to automate, what is not worth it, and a coverage-by-risk target. Offer a pilot with measurable results.

  2. Question 2 · Risk · Medium

    Build a quick risk matrix for a new payments feature.

    Answer guide

    Likelihood x impact by area: money movement, auth, reconciliation, third-party outage, regulatory. Map each to depth of testing and automation level. Keep it a living page.

  3. Question 3 · Tooling · Medium

    How would you choose between Playwright, Cypress, and Selenium for a new project?

    Answer guide

    Team skills, browsers needed, app type, parallel and CI needs, ecosystem and support, and cost of change. Decide by a short proof of concept on the hardest screen.

  4. Question 4 · Cloud · Hard

    How do you test a microservice deployed behind a gateway with a message queue?

    Answer guide

    Contract tests per service, component tests with stubs, a few end-to-end flows, queue behaviours (duplicate, delay, poison message), observability to trace a request across services.

  5. Question 5 · Communication · Easy

    Explain to a non-technical sponsor why a release should slip.

    Answer guide

    Lead with user and business impact, the evidence, the options with cost, and your recommendation. No jargon, no blame.

  6. Question 6 · Data · Medium

    How do you manage test data for an environment refreshed monthly?

    Answer guide

    Seed scripts, API-based setup, synthetic and masked data, data owned per test, and a check that runs after refresh to catch broken assumptions.