December 10, 2023 ADC Team 5 min read

How to Build an Automation Team

A brilliant automation strategy fails without the team to carry it forward. Recruiting the right profiles, defining clear roles, and creating a quality culture are just as important as the choice of tools.

Key takeaways

5 core roles: QA Automation Engineer, SDET (hybrid dev/QA embedded in product teams), QA Lead, Data QA Engineer, Performance Engineer (k6, Gatling, JMeter)
Prioritise fundamentals over tools: mastery of one programming language, test patterns (POM, DDT), CI/CD experience, and root-cause analysis ability
Quality is a shared responsibility: devs write unit tests, POs define acceptance criteria, DevOps maintains pipeline stability — not QA's job alone
Invest in continuous training: QA certifications, conferences (SeleniumConf, STAREAST), and dedicated platforms like AutomationDataCamp to retain top engineers

Key Roles in a QA Automation Team

QA Automation Engineer: Develops and maintains the test framework. Strong in code (Python/Java/JS), patterns (POM, DDT), and CI/CD
SDET (Software Dev Engineer in Test): Hybrid dev/QA profile. Embedded in product teams, they write tests in parallel with code
QA Lead / Manager: Defines the strategy, prioritises automation, manages test technical debt, interfaces with management
Data QA Engineer: Specialised in validating data pipelines (dbt tests, Great Expectations)
Performance Engineer: Load and stress testing (Gatling, k6, JMeter)

Technical Skills to Look For

Beyond tools (which can be learned), prioritise fundamental skills: mastery of at least one programming language, understanding of test patterns, CI/CD experience, and the ability to analyse root causes of failures.

Organisational Structure

QA Centre of Excellence (CoE): A centralised team that defines standards, maintains the shared framework, and supports product teams. Suited to large organisations
Embedded QA: One or two QA Engineers in each product squad. More agile, but risks divergent standards
Hybrid: CoE for the framework and standards + embedded QA for execution. The best of both worlds from 5+ teams

Creating a Quality Culture

Automation is not the exclusive responsibility of QA. Developers must write unit tests, Product Owners define acceptance criteria, and DevOps maintain pipeline stability. Quality is a shared responsibility.

Training and Upskilling

Invest in continuous training: QA certifications, conferences (SeleniumConf, STAREAST), access to training platforms like AutomationDataCamp. A QA Engineer who progresses stays motivated and delivers more value.

Train Your QA Team

Our enterprise courses are tailored to teams of all sizes. Custom tracks, mentoring, and certification included.