The 5-stage software testing career path (1970)
This roadmap reflects hiring patterns observed on QA Jobs Radar across 4,000+ active QA and SDET requisitions in 1970. Timelines assume steady learning and one role change every 2–3 years.
1. Junior QA / Trainee Tester
- Manual testing
- SDLC / STLC
- Test cases in TestRail/JIRA
- Bug lifecycle
- Basic SQL
- Git basics
2. QA Engineer
- Selenium or Playwright
- One language (Java/Python/TS)
- Postman + API basics
- TestNG/JUnit/PyTest
- CI awareness (Jenkins/GH Actions)
- POM basics
3. Senior QA / SDET
- Framework design + POM
- REST Assured contract tests
- Docker + parallel execution
- CI/CD sharding
- SQL + performance basics
- Code review + mentoring
4. Lead SDET / QA Lead
- Multi-project framework strategy
- Cloud test infrastructure
- Performance (JMeter/k6)
- Test-data services
- Team leadership
- OKR / KPI ownership
5. Test Architect / Principal SDET
- Enterprise test strategy
- Cloud + Kubernetes test infra
- AI-eval + LLM testing
- System design
- Cross-org quality standards
- Vendor + tooling decisions
Specialization branches
Around stage 3 (Senior QA / SDET), you can branch into a specialization. All four pay 15–40% above the mainline SDET track by stage 4.
Performance Engineer
JMeter, k6, Gatling, distributed load, observability, SRE overlap.
Security / DAST Engineer
OWASP, Burp, ZAP, API security testing, CI-integrated scans.
AI / LLM QA
Prompt evals, guardrails, hallucination testing, red-team suites.
DevOps / SET
Pipeline ownership, IaC (Terraform), release engineering.
Learning plan for each stage
- Stage 1 → 2: Testing fundamentals + one language + Selenium/Playwright + Git. See basics Q&A.
- Stage 2 → 3: Framework design + REST Assured + CI/CD. Practice on SDET Q&A.
- Stage 3 → 4: Multi-project ownership + performance basics + mentoring. Rehearse with AI Mock Interview.
- Stage 4 → 5: System design + cloud infra + AI-eval. Ship 1 conference talk or OSS project.
Skills that matter more in 2026
- AI-assisted test authoring (Copilot, Cursor, custom LLM evals)
- API-first testing (Playwright APIRequestContext, REST Assured)
- Contract testing (Pact) between microservices
- Observability + tracing (OpenTelemetry) as part of test analysis
- Cloud test infrastructure (Docker, K8s, GitHub Actions matrices)