Automation Test Engineer → SDET
A realistic transition from Automation Test Engineer to SDET: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 38%. Difficulty: Medium.
Difficulty: Medium6 stepsDuration: 9 to 13 monthsOverlap: 38%
Transition from Automation Test Engineer to SDET.
Transferable skills
- Programming (Java/Python/Go)
- Test framework design
- Docker / Kubernetes
Skills to learn
- API & contract testing
- CI/CD engineering
- Service virtualisation
- Performance testing
- Observability for tests
Step-by-step learning plan
1. Build on your Automation Test Engineer experience
2–4 weeks
Leverage
- Programming (Java/Python/Go)
- Test framework design
- Docker / Kubernetes
Map transferable skills — Programming (Java/Python/Go), Test framework design, Docker / Kubernetes — against what a SDET needs.
2. Learn the core of the SDET role
6–10 weeks
Learn
- API & contract testing
- CI/CD engineering
- Service virtualisation
Technologies
GoPactJMeter
Cover the biggest gaps first: API & contract testing, CI/CD engineering, Service virtualisation.
3. Master advanced SDET skills
6–10 weeks
Learn
- Performance testing
- Observability for tests
Technologies
GatlingKubernetes
Handle the advanced topics: Performance testing, Observability for tests.
4. Get productive with the SDET toolchain
4–8 weeks
Technologies
GoPactJMeterGatlingKubernetes
Be hands-on with Go, Pact, JMeter and the rest of the target stack.
5. Practise SDET work in real conditions
4–8 weeks
Ship a portfolio project or take on SDET tasks at work.
6. Get certified and position yourself as a SDET
4–8 weeks
Technologies
ISTQB Advanced Test Automation EngineerAWS Developer AssociateCertified Software Development Engineer in Test
Update your CV and LinkedIn around SDET, then apply to target roles.