The question that decides it is what you chose not to automate. Expect to defend a test strategy on cost rather than coverage, and to explain how you dealt with a suite so flaky the team stopped trusting it.
Also advertised as QA Engineer, SDET, Test Automation Engineer — the loop is the same, and so is the practice below.
Engineering loops are the most structured of any discipline, and the most predictable. Expect a recruiter screen, one or two technical rounds, a system design conversation at mid-level and above, and a behavioral round that is usually underestimated.
The technical rounds are rarely won on the answer. They are won on narration — whether the interviewer can follow your reasoning while you work, and whether you say the trade-off out loud instead of silently picking one.
Each round is run by the interviewer built for it, with its own scoring axes — not one generic interviewer asked to change subject.
System design, trade-offs, and war stories from production.
Scored on Technical communication · Engineering depth · Ownership & collaboration
System design, trade-offs, and war stories from production.
Scored on Technical communication · Engineering depth · Ownership & collaboration
Hands-on problem solving, code quality, debugging, and engineering judgment.
Scored on Problem-solving communication · Engineering correctness · Adaptability & craft
System design, trade-offs, and war stories from production.
Scored on Technical communication · Engineering depth · Ownership & collaboration
Hands-on problem solving, code quality, debugging, and engineering judgment.
Scored on Problem-solving communication · Engineering correctness · Adaptability & craft
Six you can expect, in the register interviewers actually use. Answer them out loud before you read the next section — reading a question and answering one are different skills, and only the second is marked.
The gap between these two is most of your score, and it is easier to see than to be told.
“What did you choose not to automate, and why?”
"We automated everything we could." It signals no cost model, and a suite built that way is the one the team eventually ignores.
A named area you left manual — rarely-changed, expensive to stub, low blast radius — with the maintenance cost you were avoiding and the risk you accepted instead. Test strategy is an economic argument, and this loop is testing whether you know that.
The post-mortem nobody sends you. These are specific to this loop rather than general interview advice.
For QA Engineer / SDET, a general round runs with Kai — system design, trade-offs, and war stories from production. It is the fastest way to find out which round you actually need to work on. The first session is free.
Practise a QA Engineer / SDET interview →Before you practise, it is worth reading how the common rounds are marked: tell me about yourself, behavioral questions and STAR, and system design.