--- title: "The QA Career Path: Map Yourself by Scope, Not by Title" author: "Harry" published: 2026-10-31T04:46:53.957Z updated: 2026-10-31T05:06:49.332Z category: "Career & Teams" tags: ["qa-career-path"] canonical: "https://fxblog.dev/posts/qa-career-ladder" --- # The QA Career Path: Map Yourself by Scope, Not by Title ## Key takeaways - The QA ladder has five levels, QA Engineer, Senior QA, QA Lead, QA Manager and Head of QA, and what grows at each step is scope and output, not the amount of testing. - Hands-on time falls from about 90% for a QA Engineer to about 50% for a QA Lead and close to zero for a Head of QA. - Manual and automation testing are specialisations within one ladder; every level has expectations on both sides. - Past Senior QA there is an individual-contributor track, Senior SDET to Staff to Principal Quality Engineer, which is a promotion with no direct reports. - QA job titles vary widely between companies, so compare roles by the scope they own and the people they grow. > **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](https://gitlab.com/agentic-fx/qa-career-path) 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. | Level | You own | Quality of | Hands-on | | ----------- | ----------------- | ---------------- | -------- | | QA Engineer | Assigned stories | a feature | \~90% | | Senior QA | A feature area | an area | \~80% | | QA Lead | A team or project | a release | \~50% | | QA Manager | Teams or products | the product(s) | \~10% | | Head of QA | The organisation | the organisation | \~0% | 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. > **Note** > > A manual tester who can read code and an automation engineer who still explores find more bugs than either purist. At QA Engineer level that means one language and the team's framework on one side, bug reports a stranger can reproduce on the other. ## 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: ```text 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. > **Tip** > > Ask whether your company has a level past Senior that isn't management. If not, notice where its best technical testers end up. ## 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. ![Three job titles read by scope instead of title, and the wrong rung you land on by title alone](https://fxblog.dev/media/01a19047-d354-76d9-9227-23e1e1f1e9e1/1600) _Same title, different job_ 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](https://gitlab.com/agentic-fx/qa-career-path/-/tree/main/roles) 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 ```text Here is my current job description and a job ad I'm looking at: . 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 ```text 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. ``` > **Success** > > You can place yourself on the ladder by scope and tell the two tracks apart. Next: **New QA Engineer? Test the Risk, Not the Ticket**. ## FAQ ### What are the levels of a QA career? The management ladder runs QA Engineer, Senior QA, QA Lead, QA Manager and Head of QA, with scope growing from assigned stories to the whole organisation. A parallel individual-contributor track runs from Senior QA or SDET to Senior SDET, Staff Quality Engineer and Principal Quality Engineer. ### Are manual testing and automation testing separate careers? No. They are specialisations on the same ladder. Every level has manual and automation expectations, and testers who keep a foot in each tend to find more bugs than purists on either side. ### How do I compare a QA job title at another company with mine? Ignore the title. Ask what scope the role owns (stories, a feature area, a release, teams, the organisation) and who it grows, then match those answers to the ladder level with the same scope.