The QA Career Path in 2026: From Manual Tester to SDET (and Whether You Should Climb)

A professional ascending an office staircase, illustrating the QA career path from manual tester to SDET
In this post
  1. TL;DR
  2. The QA career path, rung by rung
  3. Whether you should climb at all
  4. A practical move for each starting point
  5. What to do Monday morning

The standard advice to any tester who asks about growth is three words: "become an SDET." It is not wrong, but it is lazy. It skips the actual rungs, ignores the branches, and quietly assumes the top of one specific ladder is what everyone should want. A real QA career path in 2026 has more than one direction, and the highest-paying move is not always the most technical one.

This is the map nobody draws for you: the levels, what genuinely changes between them, and an honest answer to whether you should climb at all.

TL;DR

  • The classic ladder runs manual tester to automation engineer to SDET, but two other directions, QA lead and domain/quality specialist, pay just as well and suit different people.
  • Each rung is a shift in what you own, not just what you can build. Execution to design to systems to strategy.
  • SDET is a software-engineering job with a testing focus. If you do not enjoy writing and maintaining code, it is the wrong summit, and that is fine.
  • The most future-proof move at any level is to deepen judgment and domain knowledge, the things AI and outsourcing cannot easily copy.

The QA career path, rung by rung

Forget titles for a second, because companies use them inconsistently. Think in terms of what you own.

Manual / functional tester β€” you own execution and observation

You run tests, explore the product, find bugs, and report them clearly. The undervalued skill here is not "clicking through the app." It is noticing what does not feel right and chasing it. This is where exploratory instinct is built, and it is the foundation every higher rung quietly relies on.

The trap at this level in 2026: staying purely in scripted execution. That is the slice being automated. The escape is to start documenting why you test what you test, which is the first move toward owning decisions instead of steps.

Automation engineer β€” you own repeatable checks

Here you turn manual checks into automated ones and keep them running. You learn a framework, write tests, fight flakiness, and read CI output. This is the rung most "move up" advice points at, and it is real, but it is also where a lot of testers discover whether they actually enjoy writing code or merely tolerate it.

Worth saying plainly: automation is a tool, not a personality. Being good at it means knowing what to automate (the stable, high-value, frequently-run checks) and what to leave to a human (the exploratory, the one-off, the judgment calls).

SDET β€” you own test systems and dev-adjacent quality

A Software Development Engineer in Test is, functionally, a developer who specializes in quality. You build test frameworks and tooling, write code that other testers and developers use, integrate testing into pipelines, and often contribute to the product code itself. The pay is good because the skill set overlaps heavily with software engineering.

This is the top of the technical ladder, and the honest gate is this: an SDET role is a coding job. If reading and fixing tests drains you rather than satisfies you, this summit will make you miserable even at a higher salary. There is no shame in deciding the technical ladder is not yours.

The branches most advice ignores

  • QA Lead / Test Manager. You own quality strategy and people: test plans across a team, release decisions, mentoring, stakeholder communication. This rung rewards judgment and communication over coding, and it pays well precisely because few strong testers develop those muscles.
  • Domain / Quality specialist. You go deep instead of broad: become the person who understands testing in healthcare claims, payments, or safety-critical systems better than anyone. In regulated industries this is one of the most durable, best-paid, hardest-to-outsource positions in the whole field.

Whether you should climb at all

Here is the contrarian part. "Up" is not the only good answer.

A senior manual tester with deep domain knowledge in a regulated industry can out-earn and out-last a generic mid-level SDET, because their judgment is scarce and their context is expensive to replace. Climbing toward SDET makes sense if you genuinely like building things in code. If you do not, the better path is to get deeper, not more technical: become irreplaceable through domain mastery, risk judgment, and the ability to lead quality decisions.

The mistake is treating the technical ladder as the only scoreboard. The market in 2026 pays for scarcity, and judgment plus domain depth is at least as scarce as automation skill, often more so.

A practical move for each starting point

  • If you are a manual tester: spend 30 days learning to read one language your team uses, and start writing one-page risk plans for features you test. You are buying optionality toward both the automation branch and the lead branch.
  • If you are an automation engineer: decide deliberately whether you are heading toward SDET (lean further into code and systems) or toward lead (lean into strategy, mentoring, and cross-team test design). Drifting is the slow path.
  • If you already write a lot of test code: pick whether your edge is depth in a domain or breadth in tooling, and stop spreading yourself across both.

What to do Monday morning

Write down, in one sentence, what you actually enjoy: solving problems in code, or making judgment calls about risk and quality. Your honest answer points you at the right branch of the QA career path, and saves you from climbing a ladder leaning against the wrong wall.

Whatever direction you pick, the durable core is the same: judgment, domain knowledge, and the ability to direct automation rather than fear it.

Building the technical baseline for any of these branches? A recognized foundation helps. Nopmark's ISTQB Foundation Level (CTFL) certification training covers the testing fundamentals every rung relies on, and for the AI-oversight skills the higher rungs increasingly need, the ISTQB Testing with Generative AI (CT-GenAI) course goes deep. Both are live virtual and recorded for replay.

Keep reading