QA career paths: manual, automation, SDET, lead, manager

A lot of QA careers happen by accident: you take whatever comes next without a sense of where the roads actually lead. But QA branches into genuinely different directions, each rewarding different strengths, and knowing the map lets you steer toward work you'll be good at and enjoy rather than drifting into a role that fights your grain. This isn't a hierarchy where each step is "better" — they're directions, and the right one depends on what you like doing.

The main paths

Manual / exploratory QA, deepening. Not a phase to "graduate" from — a discipline that gets more valuable with depth. Senior exploratory testers, domain experts, and quality specialists who find what automation can't are rare and prized. The growth here is in judgement, domain mastery, and risk thinking, not in writing more code. If you love investigation and breaking things cleverly, this is a real path, not a waiting room.

Automation QA. Building and maintaining automated suites — frameworks, CI integration, reliable coverage. The skill ceiling is high: flake control, architecture, speed, trust in the suite. This is often where people head after manual-to-automation, and it stays test-centric — you're an expert at automating testing.

SDET (Software Development Engineer in Test). The engineering-heavy branch: you're a developer who specialises in quality — building test tooling, frameworks, infrastructure, sometimes contributing to product code. More coding than automation QA, closer to a software-engineer skillset. The SDET interview loop reflects it: real data-structures and coding rounds. Good fit if you enjoy the coding as much as the testing.

QA Lead. The pivot from doing to enabling: setting strategy, processes, and standards; coordinating testing across a team; still hands-on but increasingly about how the whole team tests. Leadership through expertise and influence rather than headcount — the shift from SDET/senior to lead catches people off guard because the skills are new.

QA / Engineering Manager. People management: hiring, growth, performance, org-level quality strategy. The work becomes mostly about people and outcomes, not testing directly. A different job that grew from QA — rewarding if you like developing people, frustrating if you went into QA to test.

Choosing a direction

• Love investigation, domain depth, finding the non-obvious → deepen manual/exploratory (a real path, not a phase)
• Enjoy building reliable systems and frameworks, test-focused → automation QA
• Enjoy coding as much as testing, want an engineer's skillset → SDET
• Like strategy, standards, and coordinating quality across a team → QA Lead
• Energised by growing people and org outcomes over testing itself → Manager
• The paths reward different strengths — pick toward what you like doing day to day
• Lateral moves are normal; you can switch branches, and skills transfer

How to actually choose

Two honest principles. First, none of these is "up" from the others. A deep senior exploratory tester and an engineering manager are both successful QA careers — the manager isn't more advanced, just pointed at people instead of testing. The industry sometimes implies leadership/management is the only "promotion," which pushes great testers into roles that make them miserable. Don't take that bait.

Second, choose by what you want to spend your days doing, not by title or salary alone. If you love the hands-on hunt for bugs, a management role that removes you from it is a demotion in everything but pay. If you light up building frameworks, SDET or automation will feel like play. The map exists so you can match the direction to your grain — and because the branches share a foundation, you can change roads later and carry your skills with you. Pick deliberately; drifting lands you somewhere, just rarely somewhere that fits.