Series
From your first automation role to QA lead — portfolios, interviews, and the transitions nobody warns you about. The career arc most QA engineers actually walk: from manual to automation, building a portfolio that doesn't look fake, surviving the take-home and the SDET loop, and the shift from SDET to lead.
// overview
This series follows the career arc most QA engineers actually walk, and the parts of it nobody warns you about. It's deliberately practical rather than motivational — what to learn, what to build, and what each stage really tests.
It runs from the first transition (manual to automation), through the job hunt (a portfolio that doesn't look fake, surviving the take-home and the SDET interview loop), to the one that catches people off guard: moving from SDET to lead, where you stop being measured on what you ship and start being measured on what your team ships.
Wherever you are on that path, the throughline is the same — the differentiator is judgement and communication, not the length of your tool list.
// reading order
Not yes or no — which coding and for what. Reading code and light scripting help every tester; automation is where the roles are. Coding extends testing, doesn't replace the judgement.
Six months from your first if-statement to your first paid automation contract — if you focus. Here's the path I'd take if I were starting today.
What separates a portfolio project that gets you an interview from one that screams tutorial-follower.
What take-home reviewers actually score, and how to spend your limited time on the parts that count.
The SDET interview loop is four rounds in a trench coat: live coding, system design, framework selection, behavioural. Each round tests something different. Here's what each one is actually looking for.
The transition from SDET to QA Lead is brutal in a way the title doesn't telegraph. You stop being measured on what you ship and start being measured on what your team ships.
Course
Practice Project