Manual testing fundamentals are still valuable — but automation is now table stakes for SDET and senior QA roles. This roadmap gives manual testers a concrete plan: what to learn, in what order, with what projects, over roughly six months.
Phase 1 (Month 1): Pick a language
Choose Java or Python. Java dominates enterprise testing (TestNG, Selenium, REST Assured). Python dominates data and AI testing. Don't try to learn both — go deep on one.
Phase 2 (Months 2–3): Master one automation framework
- Web — Playwright (modern) or Selenium (broad). Pick Playwright if you're starting fresh.
- API — REST Assured (Java) or requests + pytest (Python).
- Unit — JUnit 5 (Java) or pytest (Python).
Phase 3 (Month 4): Build a portfolio
- Automate a real open-source app (e.g. RealWorldApp, TodoMVC variants).
- Build a small CI/CD pipeline (GitHub Actions) that runs your tests on every PR.
- Add API tests for a public API (GitHub, JSONPlaceholder).
- Write a 1-page README explaining the architecture.
Phase 4 (Month 5): Production-grade patterns
- Page Object Model + custom fixtures.
- Test data factories + environment isolation.
- Reporting (Allure, ReportPortal).
- Parallel execution + flaky test triage.
Phase 5 (Month 6): Specialise
- Performance testing (k6, JMeter).
- Visual regression (Playwright, Percy).
- Contract testing (Pact).
- Cloud device farms (BrowserStack).
Why this roadmap works
Manual testers already have a transferable skill set: test case design, defect reproduction, stakeholder communication, and risk analysis. The roadmap adds automation as a tool, not a replacement. The hardest part is not the technology — it is learning to think in terms of data, fixtures, and assertions instead of clicks and screenshots. Most manual testers cross that bridge in the first 4–6 weeks of writing Playwright or Selenium code.
- Transferable skills — test case design, exploratory testing, defect prioritisation, stakeholder communication.
- New skills — programming (loops, functions, error handling), automation frameworks (Playwright/Selenium/REST Assured), CI/CD, Git basics.
- Time investment — 6 months of focused practice (10+ hours/week) is realistic. Less than that and you ship a thin portfolio.
Project ideas that get you hired
Hiring managers in 2026 want a portfolio that demonstrates real judgment, not just a green CI badge. Build these projects and write one-page READMEs explaining the trade-offs you considered.
- E-commerce smoke suite — login, search, add to cart, checkout. Playwright + Page Object Model + GitHub Actions.
- API contract tests — Pact consumer-driven contract tests against a public API (GitHub, JSONPlaceholder).
- Performance baseline — k6 load test against your e-commerce smoke target; report p95 latency and throughput.
- Visual regression — Playwright + Percy/Chromatic against Storybook; cover 20 key components.
- Data factory — generate realistic test data with Factory Boy (Python) or Java Faker; document the design.
The interview loop and how to prepare
Most SDET interviews follow a five-stage format. Knowing the loop helps you prepare the right artefacts.
- Phone screen — basics: STLC, severity vs priority, one automation scenario. 30 minutes.
- Take-home — automate 5–10 test cases against a provided web app. 2–4 hours.
- Technical deep-dive — walk through your take-home; discuss trade-offs, page object model, waits, CI integration. 60 minutes.
- Live coding — write a Page Object, a fixture, or a custom command. 45 minutes.
- Behavioural — STAR-format answers about a bug you found, a process you improved, a conflict you navigated. 45 minutes.
Common mistakes manual testers make when transitioning
Awareness of the common traps saves you months of frustration. Watch out for these.
- Automating everything — some tests should stay manual (exploratory, visual judgment, ad-hoc). Aim for the test pyramid.
- Hardcoding waits — `time.sleep(3)` is the number-one cause of flaky tests. Use explicit waits or auto-waiting frameworks.
- Skipping CI — tests that run only on your laptop are not portfolio-worthy. Wire them into GitHub Actions from day one.
- Brittle selectors — XPath from DevTools breaks on the first CSS change. Use `data-testid`.
- No version control — your portfolio projects live on GitHub, not on your hard drive.
Resources — books, courses, communities
Beyond the projects above, these resources build the depth that separates a junior SDET from a mid-level one in 2026.
- Books — "The Selenium Guidebook" (Dave Haeffner), "Continuous Testing for DevOps Professionals" (Eran Kinsbruner), "Mastering Playwright" (use the official docs until a definitive book lands).
- Courses — Test Automation University (free, Applitools), Ministry of Testing courses, Udemy Playwright/Selenium courses.
- Communities — Ministry of Testing, Test Tribe, Selenium Slack, Playwright Discord, r/QualityAssurance.
- Certifications — ISTQB CTFL (foundational), ICAgile Test Automation (intermediate), tool-specific certs from Cypress and Playwright.
FAQ
- Do I need a CS degree? No. A portfolio of working automation + a clean GitHub profile + a tester's mindset gets interviews.
- Java or Python? Java dominates enterprise (Selenium/TestNG/REST Assured). Python dominates data and AI. Pick by target industry.
- Can I skip the CI step? You can, but you will lose interview points. CI is the difference between "I wrote tests" and "I shipped testing".
- What is the realistic timeline to a first SDET job? 6 months of focused practice plus 3–6 months of job search. Faster if you are transitioning internally at your current employer.
