QA & Testing interviews. 8 titles, each with its own model.
Each page shows the competency model, the questions that test it, what changes with seniority, and where candidates lose the interview.
Last reviewed
Every QA & Testing title
8 titlesWhat the report looks like for QA & Testing
- The situation in one sentence: where, what was short, and by how much.
- The decision that was yours rather than the team’s, and what you chose not to do.
- One number or one consequence that shows it worked.
Every competency is scored out of five with a line you actually said as evidence, and the weakest answers are rewritten as structure and specifics, never a script.
What QA & Testing interviewers keep scoring
Test strategy & risk-based prioritisation
Decides what to test, how deeply and at which level based on risk, change impact and user value, rather than testing everything equally.
Test design & exploratory testing
Designs tests that find real defects using techniques like boundary analysis, state models and equivalence classes, and explores beyond the specification.
Test automation engineering
Builds automated tests that are reliable, maintainable and fast, at the right layer, and keeps flaky tests from eroding trust in the suite.
Defect investigation & reporting
Isolates defects to reproducible steps, gathers logs and evidence, assesses severity honestly and writes reports developers can act on immediately.
Quality advocacy & shift-left
Influences quality before code is written by reviewing requirements, pairing with developers and challenging release decisions with evidence.
Performance, security & compatibility testing
Tests beyond functionality: load and performance, basic security checks, accessibility and cross-browser or device compatibility, with meaningful targets.
Release judgement under deadline pressure
Gives honest, evidence-based go/no-go input when deadlines are tight, and negotiates scope or risk acceptance rather than quietly cutting testing.