QA Engineer interview prep, what to expect

Build the proof yourself, because the interview will ask for it. Pick one stack (TypeScript + Playwright is the safest bet), automate 15–20 scenarios against a public demo app, put it on GitHub with a README explaining your locator strategy and how you handle waits and flakes. That repo becomes your answer to half the practical round. In parallel, drill LeetCode easys into mediums for 8–12 weeks, since automation-first teams filter at the coding screen before anyone looks at your test skills. Apply to titles that say SDET, QA Automation, or Test Engineer rather than plain QA Analyst; the loops match the prep described in this guide. An ISTQB certificate helps with consultancies and enterprise IT in Europe but carries little weight at product companies.

Same question pool, slightly more forgiveness. Google, Amazon, and Microsoft pull SDET coding questions from the SWE bank, mostly LeetCode easy-to-medium on arrays, strings, and hash maps, and grade on working code plus how you test it. Where a SWE candidate might need the optimal solution quickly, an SDET candidate usually passes with a clean correct solution plus strong test-case reasoning about their own code. The trap is assuming the bar is low: most rejected QA candidates fail here, not on test knowledge. Four weeks of daily drilling covers it; the guide's prep plan splits time half on coding, half on automation for exactly this reason.

Reviewers grade structure, not scenario count. Five well-organised tests beat twenty brittle ones. Use page objects or a similar separation so a UI change touches one file, prefer role- and text-based locators over CSS chains, rely on the framework's auto-waiting instead of sleeps, and make assertions specific enough to fail usefully. Then spend 30 minutes on the README: what you covered, what you deliberately skipped, how you'd scale it to CI, and how you'd handle flakes. That README is often the tiebreaker, because it shows the judgment the on-site would otherwise have to probe for. Submitting a day early with a smaller, cleaner suite is the right trade.

Answer with ownership, never with apology. The losing versions are "I'm working toward a developer role" (tells them you'll leave the function) and "I fell into it" (tells them nobody chose you). The winning version names what the role uniquely owns: you sit where the release decision gets made, you build the automation other engineers depend on, and you're the person who knows how the system actually fails. If you do want to move to SWE eventually, keep that out of this loop; interviewers hire for the role in front of them. A concrete story about a release call you made or a bug class you eliminated lands the point better than any framing sentence.

Yes, and the gap to close is specific: the coding screen and the practical automation round. The test-design and behavioural rounds will play to your strengths, since manual QA builds exactly the case-enumeration and bug-advocacy skills those rounds grade. Budget 8–12 weeks: one language (Python or TypeScript), LeetCode easys into mediums, and a small Playwright suite you built end to end. Automation-first teams filter at the coding screen, so that's where the prep time goes.

Loops run 3–5 weeks. Give yourself 6–8 weeks of prep, split roughly half on the coding screen and half on one automation project you can defend in detail. Practise test-case enumeration out loud; it's the round people wing and lose.

Underestimating the coding round. QA candidates prepare test theory, then get filtered by a LeetCode-medium, because at big tech the SDET coding bar sits just under SWE. Four weeks of drilling moves more than any amount of framework knowledge.

Most variation is at the edges. Major tech companies (FAANG, scale-ups, mid-size SaaS) follow processes within 1–2 rounds of what's described. Smaller startups often run fewer rounds (3–4) but the bar at each round is similar; less-tech-mature companies sometimes skip system design or behavioural rounds entirely. Read the JD and ask the recruiter at the screen, they'll tell you what's coming.

This guide covers the general bar at L4 / IC3. The free scan reads your specific job description and returns predicted questions for that exact role + company, a calibrated comp benchmark, and (with your CV) experience-gap analysis and an ATS resume check. PDF emailed.