How the three certifications fit together
The ISTQB certification structure has a clear rule: Foundation Level comes before everything else. It is the prerequisite for both Test Automation Engineering and Test Automation Strategy. Once you hold Foundation Level, you can take the two automation exams in whichever order suits your current role or learning goals.
The three certifications cover complementary territory. Foundation Level gives you the testing vocabulary and principles that make the automation-specific content meaningful. Test Automation Engineering covers the hands-on technical work. Test Automation Strategy covers the organizational, financial, and methodological decisions that determine whether automation succeeds at scale. Without all three, the picture is incomplete.
ISTQB Foundation Level
Foundation Level is the entry point to the entire ISTQB certification structure. It establishes the core vocabulary and principles of software testing: what testing is and is not, why it exists, how testers design tests, how they manage test activities, and how defects are tracked and reported.
For the Test Automation Pro™ path, Foundation Level is not just a prerequisite checkbox. It provides the testing fundamentals that give the automation-specific certifications their context. Understanding risk-based testing, for example, is essential for making sound decisions about what to automate. Understanding test design techniques shapes how you build automated test suites that actually cover the right conditions.
If you have already passed Foundation Level, you can move directly to either automation exam. If you have not, it is your first step regardless of how much practical testing experience you already have.
ISTQB Test Automation Engineering
Test Automation Engineering is the technical certification in the path. It covers how to design and build automation that is maintainable over time, how to select and evaluate automation frameworks and tools, how to implement automation across different levels of the test stack, and how to integrate automated testing into a continuous delivery pipeline.
The syllabus addresses automation architecture decisions, keyword-driven and data-driven approaches, test script maintainability, automation infrastructure, and reporting. It is the certification that maps most directly to the day-to-day work of an automation engineer or a tester who writes and maintains automated tests.
Most candidates with a hands-on automation background find this exam the most natural starting point after Foundation Level. The content validates and structures what they have already been doing in practice, while also filling in gaps around architecture and maintainability that are easy to overlook when you learn automation on the job.
ISTQB Test Automation Strategy
Test Automation Strategy addresses the decisions that determine whether an automation program succeeds at the organizational level. It covers how to evaluate the costs and risks of automation, how to calculate and communicate return on investment, how to define roles and responsibilities within an automation program, and how automation fits into different development models including Agile, DevOps, waterfall, shift-left, and shift-right approaches.
This certification is particularly relevant for test leads, QA managers, and anyone who has to justify automation investments to stakeholders, staff automation programs, or advise teams on what to automate and when. It is also valuable for automation engineers who want to move from purely technical work into broader program-level responsibilities.
ASTQB does not require you to take this before Test Automation Engineering. Candidates who lead teams or make strategic automation decisions often prefer to take it sooner; those who want to build the technical foundation first take it second. Both sequences are valid.
Which order should you take them in?
Foundation Level is fixed as the first step. After that, the decision between Test Automation Engineering and Test Automation Strategy usually comes down to your current role.
If you are primarily doing hands-on automation work, writing or maintaining test scripts, working with frameworks, or integrating tests into a CI pipeline, Test Automation Engineering is the more immediately applicable certification and most candidates start there.
If you are in a lead or management role, advising teams on automation decisions, or need to justify an automation program to stakeholders, Test Automation Strategy is more directly relevant to your day-to-day work.
If neither description fits cleanly, Test Automation Engineering is the more common starting point. The technical layer tends to inform the strategic one, and many candidates find the strategy content easier to absorb once they have the engineering foundations in place.
The next step after understanding the certifications is the path guide, which covers the sequence from first exam to requesting the designation. Or, if you are ready to register, the exams page covers format, pricing, scheduling, and current offers.