From QA tester to Lead QA: what US data says before you step up

After a few years writing and automating tests, many testers wonder whether to keep going deeper on the tooling or move into a role that sets test strategy, designs the test architecture and runs the team's approach to quality. This article explains what changes, what US labor data can and cannot tell you, and what our Lead QA & Architect specialisation covers.

Tester, lead, architect: three different jobs

Job titles vary from one company to the next, and what follows is our reading of the field, not a standard. A tester designs and runs tests, often with an automation tool, on the scope they are given. A QA lead answers a different question: for this product, with this deadline and this budget, what should we test, at which level, and who does it? A test architect looks after structure: how test code is organised, where data comes from, how tests run in the CI pipeline, and how all of it stays maintainable two years from now.

In a small team one person wears both hats. In a large one, they are two jobs. Either way, the shift is from "I deliver tests" to "I make the team able to deliver good tests".

What actually changes in the work

Test strategy

Strategy starts with risk: identify what could hurt the product, decide what to test first, decide what not to automate, and split the effort between unit, API and end-to-end tests. A good strategy fits on a few pages and can be defended in front of a project manager. It says why, not just what.

Test architecture

An automation project that grows without a plan gets slow and brittle. The architect sets the rules: repository layout, data and environment management, parallel execution, readable reports, and conventions the whole team follows. The goal is simple: a new tester can add a test without breaking the others.

Metrics

Measuring is for deciding, not for decorating a dashboard. A coverage percentage alone does not tell you whether the right risks are covered. A lead picks few indicators, explains what they show and what they hide, and uses them to make trade-offs: where to put effort, when to stop, what to fix in the process.

Leading the team

Sharing out work, reviewing, coaching, pushing back on an unrealistic deadline, presenting a risk to the Product Owner: a growing share of the job happens in conversation. For a tester used to working alone on their scenarios, this is often the biggest change.

What US labor data says

The most solid public source is the Bureau of Labor Statistics (BLS) Occupational Outlook Handbook, which treats "software quality assurance analysts and testers" (SOC 15-1253) as its own occupation alongside software developers. Its page was last modified on August 27, 2026:

• Jobs. About 187,600 software QA analysts and testers in 2025, against about 1,717,800 software developers. By our own division, that is roughly one QA analyst or tester for every nine developers.
• Growth. Projected employment growth from 2025 to 2035 is 6% for QA analysts and testers and 10% for software developers.
• Pay. Median annual pay in May 2025 was $104,300 for QA analysts and testers and $135,980 for software developers.

Two honest limits. First, BLS does not publish figures for QA leads or test architects, so these numbers describe the occupation as a whole, not the step up. Second, a 6% projection is moderate growth, and it says nothing about your own chances of getting a given job.

Our interpretation, which is an opinion and not a statistic: when there are relatively few tester seats per team, broadening your scope towards strategy, architecture and metrics is one way to become harder to replace by a script or an AI assistant. It is not the only way, and it does not suit everyone.

If you are weighing this step, a simple test helps: for a week, note how many of your questions at work are about how to write a test, and how many are about what to test and why. The second kind is the lead's territory.

What about certification?

ISTQB offers advanced levels. The CTAL-TM (Test Management, version 3.0) covers, among other topics, project test strategy, risk-based testing, test metrics, estimation, defect management and stakeholder relationships. It requires the Foundation level (CTFL) and enough practical experience, with the exact criteria set by ISTQB's national member boards. It is not mandatory, and it is not included in our specialisation: any certification or validation for a specialisation is confirmed with an ADC advisor before enrolment.

ADC's Lead QA & Architect specialisation

The track is for an experienced tester who wants to move towards team leadership, test strategy and test architecture. As shown on the specialisation page:

• 399 hours of training over 3 months, 100% online;
• next session announced for January 2027 (confirm the exact date with an advisor);
• one-to-one mentoring, learning platform for 6 months, session replays for 24 months;
• topics: test strategy, team leadership, test architecture, metrics.

On price: the launch price for individuals is €1,750 incl. VAT, payable in 1 to 4 interest-free instalments; for companies, it is €7,500 incl. VAT. Prerequisites are clarified in a conversation with an advisor, since this track is not meant for beginners. One practical point for readers outside France: ADC is a French-language online training provider, so check the teaching language with an advisor before you enrol.

We do not promise a job, a promotion or a salary. The programme gives methods and mentoring; what follows depends on your context.

Who it is for, and who it is not for

• For you if you have tested for several years, already automate, and keep being asked "what should we test?" and "how should we organise testing?".
• Not yet for you if you are starting out: the main QA Automation & AI Tester programme, open without technical prerequisites, is the better starting point.
• For a company that wants a seasoned tester to take ownership of test strategy and architecture.

Frequently asked questions

Written by Oussama Belakhdar with AI assistance. Market figures come from the BLS Occupational Outlook Handbook; role descriptions and the interpretation of the data are our own reading, not statistics.