Career Change  ·  QA/SDET → SDE

Will AI replace QA engineers?

SDETs already write real production-quality code — the move to general SDE is one of the more natural technical pivots, closing a specific set of gaps rather than starting over.

SDETs (software development engineers in test) build automated test frameworks and infrastructure, which is genuine software engineering. The transition to general SDE work is mostly about broadening beyond testing-specific code into full feature development.

What carries over, and what you'll need to build

Typical responsibility changes

You move from being responsible for catching bugs to being responsible for building the features in the first place. The accountability shifts from quality gatekeeping to direct ownership of what ships — a real change even though the coding skill itself transfers well.

A realistic transition roadmap

1. Contribute feature code, not just tests, on your current team. Volunteer for small feature tickets alongside your testing work — direct proof you can do the job, and often the fastest path to an internal transfer.
2. Build a portfolio project outside testing. A side project that's pure feature development (not test automation) demonstrates range beyond your current job title to external hiring managers.
3. Target companies or teams that value your testing background explicitly. Some engineering teams specifically want SDEs with strong testing instincts — lean into that as a differentiator rather than hiding your QA background.
4. Ask your manager directly about an internal SDE transfer. Many companies have an established SDET-to-SDE internal path precisely because the skill overlap is so direct.

Portfolio and project ideas

Ship a real feature, even a small one, end to end outside of your test-automation work — a side project or an internal tool — direct evidence you can build, not just verify.

Internal mobility strategy

This is one of the more established internal tech pivots — many companies have a formal or informal SDET-to-SDE track, since the underlying coding skill is already proven.

How AI is reshaping both sides of this move

For QA/SDETs, test-script generation automates while test strategy stays human — see the AI risk breakdown for QA automation engineers. For SDEs, boilerplate automates while architecture and debugging stay human — see the AI risk breakdown for software developers.

Will AI replace QA engineers?

Not the SDET kind — test-script generation automates fast, but the test-strategy judgment behind it doesn't. SDETs who already write real code for test frameworks are well-positioned to move into general software engineering, where that same verification instinct is increasingly valued.

How hard is it to move from QA/SDET to SDE?

Less hard than most people assume. SDETs already write real code and often just need broader feature-development exposure, not a fundamentally new skill set.

Will I take a pay cut moving from SDET to SDE?

Typically not. SDET and SDE roles are usually leveled comparably at most companies, since both require genuine software engineering skill.

Also worth reading: QA/SDET to Engineering Manager · SDE to Staff/Principal Engineer · all career change guides · how we score this →