QA Automation Engineer → SDET

A realistic transition from QA Automation Engineer to SDET: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 51%. Difficulty: Easy.

Difficulty: Easy6 stepsDuration: 4 to 8 monthsOverlap: 51%

Transition from QA Automation Engineer to SDET.

Transferable skills

  • Programming (Java/Python/Go)
  • Test framework design
  • API & contract testing
  • Performance testing

Skills to learn

  • CI/CD engineering
  • Service virtualisation
  • Docker / Kubernetes
  • Observability for tests

Step-by-step learning plan

  1. 1. Build on your QA Automation Engineer experience

    2–4 weeks

    Leverage

    • Programming (Java/Python/Go)
    • Test framework design
    • API & contract testing
    • Performance testing

    Map transferable skills — Programming (Java/Python/Go), Test framework design, API & contract testing — against what a SDET needs.

  2. 2. Learn the core of the SDET role

    6–10 weeks

    Learn

    • CI/CD engineering
    • Service virtualisation

    Technologies

    GoPactJMeter

    Cover the biggest gaps first: CI/CD engineering, Service virtualisation.

  3. 3. Master advanced SDET skills

    6–10 weeks

    Learn

    • Docker / Kubernetes
    • Observability for tests

    Technologies

    GatlingPostman

    Handle the advanced topics: Docker / Kubernetes, Observability for tests.

  4. 4. Get productive with the SDET toolchain

    4–8 weeks

    Technologies

    GoPactJMeterGatlingPostman

    Be hands-on with Go, Pact, JMeter and the rest of the target stack.

  5. 5. Practise SDET work in real conditions

    4–8 weeks

    Ship a portfolio project or take on SDET tasks at work.

  6. 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.

Alternative routes