The skills SDET and QA engineers use on the job, from testing fundamentals and test design through automation programming, UI and API testing, CI/CD, performance, quality strategy, and AI-assisted testing. Start at the top and work down, basics first. Free to read, no signup required.
How to use this: tap a step on the map to open its details, skill pills, and guidance in a side panel. Work down the spine in order; each stage assumes the ones above it. The early steps get you into QA; the programming and framework steps are what open up higher-skill SDET roles.
Build a real automation framework
Reading about testing doesn’t prove you can do it. A working automation project does. It’s also the most convincing thing you can show an interviewer: real tests, wired into CI, that you can walk through and defend.
A UI automation suite for a real (or open-source) web app using the Page Object Model.
An API test suite that validates status, schema, and error cases against a public API.
The two combined into one framework with shared fixtures, data-driven tests, and reporting.
Wire it into a CI pipeline so it runs on every push, and keep it flake-free.
Put it on GitHub with a README that explains your test strategy: what you chose to automate, at which level, and why. Interviewers will dig into that reasoning.
Frequently asked questions
They sit on a spectrum. A manual tester focuses on executing and exploring; a QA engineer owns test design and quality strategy; an SDET (Software Development Engineer in Test) adds building automation frameworks and tooling as a real developer. This roadmap covers the whole span so you can move up it, and the programming steps are what open the SDET end.
Not for entry-level manual QA, where strong test design and a sharp eye for defects can get you started. But to grow into automation and SDET roles, where the demand and pay are highest, you do need real programming ability. It’s the single most valuable investment for a QA career.
There’s no fixed number. Consistent practice matters most. You can reach entry-level manual QA relatively quickly with strong fundamentals; moving into solid automation and SDET work takes longer because you’re also becoming a programmer. Building a real automation project speeds it up.
They change the work rather than remove it. Automation replaces repetitive manual checking, which pushes QA toward test design, strategy, and building and maintaining automation, all higher-skill work. AI adds new systems that themselves need careful testing. Deciding what quality means and what to test stays a human judgement.
Learn the principles (stable locators, waits, the Page Object Model, structuring a framework) more than any single tool, because Selenium, Playwright, and Cypress share the same underlying ideas. Pick one popular tool, get good with it, and the concepts transfer to the others.
No. Testing fundamentals, test design, and a programming language are the core. Performance testing, security testing, and quality leadership you deepen as roles demand. Few people are equally strong across all of it.
Get a personalized plan for real interviews
This page covers what to learn. When you’re ready to get hired, Interview Ready turns it into a personalized 30-day plan built around your resume and a specific target role: real practice in the right order (automation, test design, behavioural), a guided Build-a-Project track alongside it, and progress tracking the whole way. Start free.
