Where QA candidates lose points in interviews: data on the most common weaknesses
Across 533 scored mock interviews from 277 QA candidates, technical accuracy is almost never the weakest dimension. Candidates lose points on concrete examples and on depth: examples is the lowest-scoring dimension in 44 percent of reports, depth in 41 percent, technical accuracy in 3 percent. The pattern holds in every interview type with enough reports to say.
What do the four dimensions score, and which one is lowest?
Every full mock interview on AssertHired is scored on four dimensions from 0 to 100: technical accuracy, communication, concrete examples and depth. The overall score is the plain mean of the four. Across 533 reports the means are close together, but which dimension comes last in a given report is not evenly spread at all.
| Dimension | Mean score | Lowest in N reports | Share of reports |
|---|---|---|---|
| Technical accuracy | Mean score65.4 | Lowest in N reports14 | Share of reports3% |
| Communication | Mean score61.4 | Lowest in N reports101 | Share of reports19% |
| Concrete examples | Mean score57.7 | Lowest in N reports233 | Share of reports44% |
| Depth | Mean score56.9 | Lowest in N reports219 | Share of reports41% |
A report that ties on two dimensions counts under both, so the last column can sum past 100 percent.
Technical accuracy is the lowest dimension in 3 percent of reports. Concrete examples is the lowest in 44 percent and depth in 41 percent. Candidates mostly know the material. What they do not do is anchor an answer in something they actually did, or go past the first layer when the interviewer waits.
Does the pattern change by interview type?
It changes in which of the two non-technical dimensions comes last, not in the headline. Categories with at least 30 reports are shown individually; the rest are grouped, because a per-dimension claim on a dozen reports would be a guess with a table around it.
| Interview type | Reports | Candidates | Most often lowest | Lowest in |
|---|---|---|---|---|
| Behavioral QA | Reports317 | Candidates253 | Most often lowestDepth | Lowest in168 (53%) |
| Test Automation | Reports66 | Candidates45 | Most often lowestConcrete examples | Lowest in55 (83%) |
| Manual Testing | Reports44 | Candidates27 | Most often lowestConcrete examples | Lowest in32 (73%) |
| General QA Theory | Reports35 | Candidates14 | Most often lowestConcrete examples | Lowest in18 (51%) |
| Live Coding | Reports32 | Candidates15 | Most often lowestDepth | Lowest in18 (56%) |
| Other technical rounds (API Testing, CI/CD & DevOps) | Reports39 | Candidates23 | Most often lowestNot stated | Lowest inUnder 30 reports each |
The sharpest result is in Test Automation rounds (66 reports from 45 candidates): concrete examples is the lowest dimension in 55 of them, with a mean of 47.7 against 62.9 for technical accuracy. Candidates can explain what a locator or an auto-wait is; they struggle to describe a specific suite they built and a specific failure they fixed. In Behavioral QA rounds the weakest dimension is depth, lowest in 168 of 317 reports: the story is there, but the answer stops before the trade-off, the measurement or what changed afterwards.
What does the score distribution look like?
Scores are deliberately calibrated against a senior rubric, so a 57 is not a school grade. 227 of 533 reports (43 percent) score under 60 overall. Read the bands as where a candidate sits against an interviewer who expects senior answers, not as a pass mark.
| Overall score | Reports | Share |
|---|---|---|
| 0-9 | Reports9 | Share2% |
| 10-19 | Reports8 | Share2% |
| 20-29 | Reports17 | Share3% |
| 30-39 | Reports23 | Share4% |
| 40-49 | Reports61 | Share11% |
| 50-59 | Reports109 | Share20% |
| 60-69 | Reports143 | Share27% |
| 70-79 | Reports95 | Share18% |
| 80-89 | Reports51 | Share10% |
| 90-100 | Reports17 | Share3% |
What should a candidate do with this?
Prepare examples before you prepare facts. For each tool or practice on your CV, have one specific story ready: the system, what you built or found, one number, and what you would do differently. That single habit targets the dimension that comes last in 44 percent of reports.
Then practise going one layer deeper than the question asked. When an interviewer asks how you handled flaky tests, the first layer is the fix; the second is how you measured the flake rate before and after and what you changed in the pipeline. Depth is the lowest dimension in 41 percent of reports because most answers stop at the first layer.
The rubric itself is tested in public; see how the scoring is evaluated.
How was this measured?
Snapshot taken 2026-09-28 from the production database by a read-only script whose only output is the data file this page renders. Included: every feedback report with all four dimension scores and an overall score, which only exist for completed full interviews. The no-account two-question flow and the free onboarding answer are scored separately and are not in this set.
Excluded: 16 reports from the operator's own accounts, test aliases and reserved domains, using the same rule the analytics use; 0 reports could not be matched to an interview category. A candidate is a distinct account; 277 candidates produced 533 reports, so the sample is weighted towards people who practised more than once.
The scoring rubric was recalibrated on 2026-09-04. 45 of the 533 reports were graded under the current rubric; the rest predate it and score lower on average. The dimension ordering above is about which dimension comes last within a report, which the recalibration was not designed to change, but the absolute means will move as the post-change sample grows. Aggregate only: no per-person data is published, and no report text is quoted.
What does this research answer?
Where do QA candidates lose the most points in technical interviews?
On concrete examples and depth, not technical accuracy. In 533 scored QA mock interviews, examples is the lowest-scoring dimension in 44 percent of reports and depth in 41 percent, against 3 percent for technical accuracy. Candidates usually know the material; they do not anchor answers in work they did, or go past the first layer.
What are the most common weaknesses in Playwright interview answers?
In 66 scored Playwright test automation mock interviews from 45 candidates, concrete examples was the lowest-scoring dimension in 55 of them (83 percent), with a mean of 47.7 against 62.9 for technical accuracy. Candidates can explain locators and auto-waiting; they struggle to describe a specific suite they built and a specific failure they fixed.
How do I stop losing points on examples and depth in a QA interview?
Prepare one specific story for each tool or practice on your CV: the system, what you built or found, one number, and what you would do differently. Then practise going one layer past the question: after the fix, say how you measured the problem before and after and what changed in the pipeline. Those two habits target the dimensions that come last most often.
Where does this data come from?
See where you would lose points
One question, scored on the same four dimensions this page reports.
Join 600+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
This single answer is scored on four dimensions: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account