UK Career Change · 2026
QA Engineer to Software Engineer
Difficulty
Moderate
Typical timeline
6-15 months
From → To
Tech → Tech
QA engineer to software engineer is one of the easier internal-tech transitions. QA engineers already understand the codebase, the deployment pipeline, and the engineering culture — they just need to shift from finding bugs to writing features. The transition typically happens internally first; external transitions take slightly longer because external hiring panels still differentiate QA from software engineering.
Salary impact
Slight uplift initially (+5-10%); reaches +20-30% within 18-24 months
Why this transition works
- ✓QA engineers already write code (test automation, frameworks, CI integration)
- ✓Deep understanding of codebase architecture from testing across the system
- ✓Awareness of common bug patterns translates directly to defensive coding skill
- ✓Internal transitions at the same company are common and have high success
The hard parts (don't skip these)
- !External hiring panels sometimes differentiate QA experience from 'real' engineering
- !Test automation work doesn't always count as production engineering on external CVs
- !Pace and ownership shift — QA reactive to feature releases; engineering proactive in feature design
- !Some QA-trained engineers struggle with feature creativity vs bug-finding mindset
Step-by-step plan
- 1
Internal transition first
Talk to your engineering manager about taking on feature development work. Most QA engineers can transition internally within 6-9 months by doing increasingly substantive engineering work. Internal success rate is high.
- 2
Build feature shipping evidence
Even within a QA role, contribute to feature development — fix bugs end-to-end, build small features, contribute to libraries. Each shipped feature is portfolio for the engineering transition.
- 3
Pick a stack and deepen
QA roles often span multiple stacks. For the engineering transition, deepen one — usually the language you already test most. Build personal projects in that stack.
- 4
Frame QA experience as engineering credibility on CV
"Built test framework for [system] with 1,200+ test cases" reads as engineering work. "Designed and implemented CI pipeline integration" reads as DevOps/engineering work. Don't hide QA; translate it.
- 5
External transitions: target stack-similar companies
If internal transition isn't possible, target companies on the same stack as your QA work. Junior or mid-level engineer roles at companies that hire from non-traditional backgrounds.
CV adaptations for this transition
- →Lead with feature work shipped, even if alongside QA responsibilities
- →Surface test automation as engineering work, not just testing
- →Highlight CI/CD and infrastructure work
- →Drop generic QA framing in favour of engineering vocabulary
Red flags that derail this transition
- ✗Pure QA CV without feature shipping evidence
- ✗Aiming for senior engineer roles directly without internal transition first
- ✗Hiding QA background — comes across as defensive in interview
- ✗Multi-stack scattergun without commitment to one