The QA Career Path: Map Yourself by Scope, Not by Title

TL;DR QA job titles are noisy, so if you measure yourself by title you aim at the wrong rung and polish the wrong skills. The QA career path is five levels plus an individual-contributor track, and what grows at each step is scope and output, not "more testing". Place yourself by scope, then choose a level and a track.

Do this: Write one line on what you own today, find the row in the table below that matches it, and read the row above it. That is your next step, whatever your title says.

One company's QA Lead is another's Senior QA. A startup's Head of QA may manage three people. A QA Manager in a 20-person company often does every job on the ladder at once.

So "I want to be a Lead" tells you almost nothing about what to do on Monday.

QA Career Path, in seven parts:

1. The QA Career Path: Map Yourself by Scope, Not by Title (you are here): the map.
2. New QA Engineer? Test the Risk, Not the Ticket: the first job.
3. Manual to Automation Testing in Six Months: Skip the Tutorial Loop: the first PR.
4. Senior QA: Depth Everywhere Is Depth Nowhere: risk.
5. After Senior QA: Lead the Release or Own the Platform?: the fork.
6. QA Manager to Head of QA: The Escape Bill That Wins Budget: money.
7. Will AI Replace Testers? Make Your Judgment the Evidence: AI and your next move.

Every part follows FieldFlow, the fictional case study in the QA Career Path repo this series is built on: a field-service product with a web back office, an offline mobile app and a public API used by about 50 partners. Its QA team is 8 testers, 2 of whom automate, across 6 squads and 40 developers.

What grows at each rung is scope

Each step up widens what you are responsible for, from a feature to an organisation, and changes what you produce: executed tests, then risk calls, coordinated releases, and finally decisions, plans and people.

One word per step: doing, owning, coordinating, enabling, directing. If your days are "doing" and your target is "coordinating", more testing won't close the gap.

Manual and automation are one ladder

Manual and automation are specialisations, not separate ladders. Every level has expectations on both sides.

Past Senior, the road forks

Not everyone should manage. Many organisations run a parallel individual-contributor (IC) track, often through SDET (software development engineer in test) titles, with no direct reports:

Senior QA / SDET → Senior SDET   → Staff Quality Engineer    → Principal Quality Engineer
(owns an area)     (owns a system) (owns a cross-team problem) (owns a direction for the org)

If triage, 1:1s and status reports drain you but hard testing problems energise you, this track is a promotion, not a consolation prize. Most people find out which way they lean as a QA Lead. Part 5 is that choice.

Read a job ad by scope, not by title

To compare yourself with a job ad or a colleague elsewhere, ask what scope the role owns and who it grows, then match the answers to the table above.

1. Cross out the title.
2. Find the scope in the bullets: stories, an area, a release, a team, the organisation.
3. Find who the role grows: only you, juniors informally, testers, managers.
4. Read that level's promotion checklist in the role pages and mark what you already have evidence for.

I kept tools and test-design technique out of this series; the companion QA Skills Path covers them. Salaries stay out too: pay varies too much by country, company and sector to trust a number in a blog post.

Try it

Here is my current job description and a job ad I'm looking at: <paste both>.
Map each one to a level on this ladder by scope, not title:
QA Engineer (stories), Senior QA (a feature area), QA Lead (a release),
QA Manager (teams/products), Head of QA (the organisation).
Then list three things the second role does that I have never done.

Say the table puts you at QA Engineer at FieldFlow, owning assigned stories. Release R25 brings one: a new "round to nearest 5 minutes" billing option, and you cannot test every duration a field engineer might log. Which tests count, and what are your first three months for? Part 2, New QA Engineer? Test the Risk, Not the Ticket, answers both.

Read this with your AI

Read the post "The QA Career Path: Map Yourself by Scope, Not by Title".
1. Summarise it in 5 bullets for a tester deciding their next step.
2. Ask me 3 questions to check I understood; wait, then correct me.
3. Ask me what I own today, then tell me which level that is and why.