After a few years writing and automating tests, many testers wonder whether to keep going deeper on the tooling or to 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, and what US labor data can and cannot tell you before you step up.
TL;DR
- The role change: a lead decides what to test, how to organise it and how to measure it; an architect designs the technical structure that keeps it sustainable.
- US data: the Bureau of Labor Statistics projects 6% employment growth for software QA analysts and testers from 2025 to 2035, against 10% for software developers.
- The limit: the BLS does not track QA leads or test architects separately, so no official figure exists for those roles.
Tester, lead, architect: three different jobs
Job titles vary from one company to the next, and what follows is my 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 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 simple 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, the 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.
My 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.
A one-week test before you decide
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. If most of your questions already sit there, the step is probably natural. If they do not, that is useful to know too.
If you are already asked "what is our test strategy?" and want an outside view of the answer, ADC offers a QA audit: a risk and coverage map of a team's testing, with a costed action plan.
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 part of the specialisation below.
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 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.
Launch price for individuals: €1,750 incl. VAT, payable in 1 to 4 interest-free instalments; for companies, €7,500 incl. VAT. Prerequisites are clarified with an advisor, since this track is not meant for beginners. ADC is a French-language online training provider, so check the teaching language before you enrol. No certification is promised for this specialisation, and no job, promotion or salary either.
Over to you
If you have made the jump from tester to lead, what was the first thing that surprised you: the strategy work, the metrics, or the conversations? And if you decided to stay hands-on instead, what made you choose that?
Sources: US Bureau of Labor Statistics: Software Developers, Quality Assurance Analysts, and Testers (Occupational Outlook Handbook, page last modified August 27, 2026) · ISTQB: Advanced Level Test Management CTAL-TM v3.0 (page modified August 22, 2026) · ADC: QA specialisation tracks (Lead QA & Architect)
Originally published on AutomationDataCamp. Written with AI assistance. Every figure comes from the sources listed above, as cited in the original article (checked on 19 October 2026).
AutomationDataCamp is an online software testing academy (Playwright, API testing, CI, AI-assisted testing, ISTQB prep). More on our site.
Top comments (0)