QA portfolio projects that don't look fake
What separates a portfolio project that gets you an interview from one that screams tutorial-follower.
Blog
Transitions, interviews, levelling up. From manual to automation, from automation to SDET, from SDET to QA lead.
What separates a portfolio project that gets you an interview from one that screams tutorial-follower.
Tool-list-as-skills, duties not achievements, no quantified impact, generic and untailored — and the reframe that fixes them: prove you're good at testing, don't describe the job.
Senior interviews assess judgement, prioritisation, and influence — not deeper tool trivia. Prep risk-based reasoning, trade-off thinking, and stories of influencing decisions.
Use STAR to keep a bug story focused on your judgement: brief Situation and Task, an Action with reasoning, and a Result with impact — and pick a bug that shows thinking, not luck.
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.
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.