Skip to content
DXP Team Structure

QA Engineer

Layer: Operational

Scope: Account/Project

Track: qa

Mission

Section titled “Mission”

Own test strategy and quality assurance — functional, performance and accessibility — across each CMS solution.

Responsibilities

Section titled “Responsibilities”
  • Define and execute test plans/strategy per project.
  • Build and maintain automated test suites (unit, end-to-end, accessibility, performance).
  • Track and report quality metrics and regressions.
  • Collaborate with Frontend and Backend on testability and bug triage.
  • Apply the team’s shared QA tooling and standards.

Objectives by level

Section titled “Objectives by level”
LevelWhat success looks like
OperationalTest coverage and quality gates meet the bar and ship on time.

Reporting & management

Section titled “Reporting & management”
  • Reports to: Tech Leader
  • Manages: No direct reports.

Decides vs. escalates

Section titled “Decides vs. escalates”
  • Decides: Implementation details within assigned QA tasks and the agreed design.
  • Escalates: Design ambiguities, blockers, and scope or estimate risks.

Requirements

Section titled “Requirements”

Must have

Section titled “Must have”
  • Test strategy and planning
  • Playwright (end-to-end)
  • Lighthouse CI (performance)
  • axe (accessibility)

Nice to have

Section titled “Nice to have”
  • Not specified in the source material yet.

By CMS

Section titled “By CMS”
  • aem-traditional: JUnit, Mockito, AEM Mocks (wcm.io) for AEM-specific unit test mocking.
  • aem-eds: Lighthouse CI as a primary metric — core to EDS’s performance value proposition.
  • optimizely-cloud: xUnit/NUnit for backend unit testing.
  • contentful: Jest/Vitest + Testing Library for component/unit testing.
Section titled “Related documents”