Test engineer career path: from junior to test manager and head of QA
Each step up the testing ladder, from your first test job to test manager and head of QA: what changes in the job, the gap to close, how to show it on your CV and in interviews, and a realistic plan.
The cvscored team
Contents
The ladder at a glance
| Step | What you are measured on next | Typical time |
|---|---|---|
| Junior test engineer to test engineer | Testing a feature well on your own, including automation | 1 to 2 years |
| Test engineer to senior test engineer | Owning the testing of a product area, end to end | 2 to 3 years |
| Senior test engineer to test lead | A team's test plan, its people and its results | 2 to 3 years |
| Senior test engineer to test architect | The test framework and standards other teams use | 2 to 4 years |
| Test lead to test manager | Several teams' testing, budget and hiring | 2 or more years |
| Test manager to head of QA | Quality across the company, and its strategy | After leading several teams |
The steps up to senior
Junior test engineer to test engineer
What changes: you test a feature from start to finish without help: you read the story, design the tests, run them, write clear bug reports and add the checks that should be automated.
The gap: test designAsked in 43% of test engineer ads (as of 5 Nov 2026).Test design: equivalence classes, boundary values, state changes and exploratory sessions. The core of the job at every level. techniques, a first automationAsked in 34% of test engineer ads (as of 5 Nov 2026).Automated checks that run on every change, are fast, stable and easy to read, and that the team trusts. tool, one language such as PythonAsked in 33% of test engineer ads (as of 5 Nov 2026).Scripting test data, API checks and small tools; pytest for test suites. Readable code, reviewed like product code. or JavaAsked in 8% of test engineer ads (as of 5 Nov 2026).Common in enterprise test automation (JUnit, TestNG, Selenium, REST Assured). Clean, maintainable test code., API testingAsked in 0% of test engineer ads (as of 5 Nov 2026).Test APIs directly: status codes, contracts, error cases, authorisation, and the data a call leaves behind., SQLAsked in 5% of test engineer ads (as of 5 Nov 2026).Check what a test left in the database, build test data, and find the record behind a bug report. for checking data, and GitAsked in 20% of test engineer ads (as of 5 Nov 2026).Branches, pull requests and reviews; test code lives in version control like product code..
On the CV and in interviews: one line per feature you tested, with what you found or prevented. Expect a test design exercise on a simple form or API, and questions on how you write a bug report.
Plan (6 to 12 months, on the job): design the tests for one feature each sprint and ask for review; automate the regression checks of one area; take the ISTQB Foundation exam if your market asks for it; read the bug reports of your senior colleagues.
Test engineer to senior test engineer
What changes: you own the testing of a product area. You choose what is tested at which level, keep the automation fast and stable, and others ask you before they decide.
The gap: a test strategy based on risk, framework design (structure, test data, reports), putting tests into CI/CDAsked in 17% of test engineer ads (as of 5 Nov 2026).Tests run on every change in the pipeline; a failed check stops the release and the team sees why at once. pipelines, fixing flaky tests at the cause, performance and security basics, and reviewing other people's test code.
On the CV and in interviews: an area you owned and a measured result, such as a faster regression run or fewer bugs after release. Expect a question on your test strategy for a new product, and a story about a bug that escaped and what you changed.
Plan (6 to 12 months, on the job): write the test strategy for your area and get it reviewed; cut the pipeline's test time with parallel runs and API checks; mentor a junior colleague; run one exploratory session a week on the riskiest change.
The steps up from senior
Senior test engineer to test lead
What changes: you answer for a team's testing, not only your own. You write the test plan, share out the work, report the risks to the product owner and help testers grow.
The gap: test planning and estimating, reporting risk in plain words, running triage of bugs with the team, coaching, and AgileAsked in 10% of test engineer ads (as of 5 Nov 2026).Testing inside the sprint, not after it: refine stories, agree acceptance criteria, test as code lands. ways of working at team level.
On the CV and in interviews: the team's size and what changed under your lead. Expect questions about a release decision under time pressure, and about a disagreement with development.
Plan (6 to 12 months): act as test lead for one release; write and run its test plan; run the weekly bug triage; agree the exit criteria with the product owner; ask your manager for feedback on your reporting.
Senior test engineer to test architect
What changes: you design how testing works across teams: the shared framework, test environments and data, the pipeline stages and the standards. It is a step up without managing people.
The gap: framework design for several teams, contract testing between services, test environments with DockerAsked in 2% of test engineer ads (as of 5 Nov 2026).Start the app and its database in containers so every test run starts from the same clean state., performance testing, and persuading teams that do not report to you.
On the CV and in interviews: a framework or standard other teams adopted, and how far it reached. Expect a design question: how would you test a system of many services?
Plan (12 months or more): build one shared part, such as the test data service or the pipeline template; write a decision record with the reasons; get two other teams to adopt it and measure the result.
Test lead to test manager
What changes: you lead testing for several teams or a whole product. You own the test strategy, the budget, the tools and the hiring, and you speak for quality to senior management.
The gap: line management (one-to-ones, reviews, hard conversations), hiring, budgets and tool contracts, quality metrics that leadership understands, and LeadershipAsked in 2% of test engineer ads (as of 5 Nov 2026).For leads and managers: planning the team's work, growing testers, and owning quality decisions. across teams.
On the CV and in interviews: the people you led, hired and grew, and results across teams, such as fewer escaped defects with more releases. Expect questions on metrics, on handling poor performance and on a quality strategy for the company.
Plan (9 to 12 months): take on line management for two or three testers; run the hiring for one post; build a quarterly quality report with honest metrics; take a management course or the ISTQB Test Manager exam.
Here this ladder meets the test management ladder. Its steps from test lead to senior test manager and head of QA have a page of their own: the test manager career paths.
Test manager to head of QA
What changes: you own quality across the company: the strategy, the organisation of testers, the tools, and how quality is built into how every team works. You report to engineering or company leadership.
The gap: organisation design (where testers sit, how many, what they own), budgets across departments, quality and risk at board level, audits and the law in regulated industries, and Communication skillsAsked in 20% of test engineer ads (as of 5 Nov 2026).Explaining risk to people who are not testers, and writing bug reports a developer can act on at once. with people outside technology.
On the CV and in interviews: a change you led across the company and its result, the size of the organisation, and the budget. Expect a case: our releases are slow and customers complain about bugs; what do you do in your first ninety days?
Plan (12 months or more): lead one change across several teams, such as moving testers into delivery teams; present quality to leadership every quarter; find a mentor who already leads a department.
Your CV for the next step
A step up shows on a CV as proof of the bigger responsibility, in the words that level's ads use, under a real job. Three rules:
- Add, never rename. Keep your past job titles. Add lines that show the new work.
- Use the next level's words. A senior role wants "test strategy", "framework", "pipeline"; a lead role wants "test plan", "triage", "coached"; a manager role wants "hired", "budget", "quality metrics".
- One result per line. Bugs prevented, time saved, stability, releases, people grown.
| Skill | Weak line | Strong line, with proof |
|---|---|---|
| AutomationAsked in 34% of test engineer ads (as of 5 Nov 2026).Automated checks that run on every change, are fast, stable and easy to read, and that the team trusts. | Worked on automation. | Designed the shared Playwright framework now used by 6 teams; new suites start in a day instead of two weeks. |
| CI/CDAsked in 17% of test engineer ads (as of 5 Nov 2026).Tests run on every change in the pipeline; a failed check stops the release and the team sees why at once. | Improved the pipeline. | Moved slow UI checks to API tests and parallel runs; pipeline time down from 50 to 15 minutes. |
| Test planning | Planned testing. | Wrote and ran the test plan for a 4-team release; shipped on the date with no critical bugs open. |
| LeadershipAsked in 2% of test engineer ads (as of 5 Nov 2026).For leads and managers: planning the team's work, growing testers, and owning quality decisions. | Managed testers. | Hired 4 testers and grew 2 manual testers into automation; escaped defects down by half in a year. |
Key takeaways
- The ladder runs junior, test engineer, senior, test lead or test architect, test manager, head of QA.
- Senior means owning an area's testing end to end; lead means owning a team's.
- Test architect is the step up without managing people; test manager is the step up that does.
- Each step changes what you are measured on; prepare proof of that, not just new knowledge.
- Add proof to your CV in the next level's words, one result per line.
Frequently asked questions
- What comes after senior test engineer?
- Test lead or test architect, then test manager, and from there head of QA.
- How long does it take to become a test manager?
- Often several years of testing and at least one or two years leading a team's testing. What counts is the responsibility you can show, not the years.
- Do I need to manage people to move up?
- No. Test architect is a step up without managing people; test manager and head of QA are the steps that do.
- Which certificates help on the way up?
- ISTQB Foundation early on, and its advanced Test Manager level for management roles, mainly in Europe. Results on your CV count for more.
- What should the CV show for a test manager role?
- The teams you led, the people you hired and grew, and quality results across teams, each with a number.