Interview scorecard template

Quality Assurance (QA) Engineer interview scorecard

Evaluate Quality Assurance (QA) Engineer candidates across 4 weighted areas: technical proficiency, systems and trade-offs, evidence and rigour, and collaboration and communication. Technical proficiency leads at 35%, so probe testing depth: automation frameworks they built, and whether they can read the code they are testing. Use the rubric to compare role-specific evidence consistently.

See AI scoring
software dataqaquality engineeringsoftware testingtest automation
TL;DR
For technical proficiency, look for evidence the candidate builds and maintains automation themselves, and reads the code well enough to test where the risk actually is. For systems and trade-offs, look for evidence the candidate allocates testing effort by risk, and can defend what they deliberately left untested. Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework

What to assess and how to score it

Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.

01
Evaluation factor

Technical proficiency

35% weight

Probe testing depth: automation frameworks they built, and whether they can read the code they are testing.

Evidence to listen for

  • Command of the languages, frameworks, and data tools the role actually uses
  • Understands correctness, performance, and failure modes, not just syntax
  • Has opinions on testing and can justify them
  • Reads and reasons about code they did not write

Five-point scoring guide

1
Poor

Cannot work independently; fundamentals are missing.

2
Needs Improvement

Weak fundamentals; output needs heavy review.

3
Satisfactory

Competent for the role; needs guidance on complex or unfamiliar work.

4
Very Good

Strong practitioner; handles hard problems with little guidance.

5
Excellent

Builds and maintains automation themselves, and reads the code well enough to test where the risk actually is.

02
Evaluation factor

Systems and trade-offs

25% weight

Test how they decide what to automate, what to test manually, and what is not worth testing at all.

Evidence to listen for

  • Reasons about scale, latency, cost, and failure before writing code
  • Names the trade-off they chose and what they gave up
  • Understands the data lifecycle end to end
  • Anticipates what breaks at ten times the volume

Five-point scoring guide

1
Poor

No thinking beyond the immediate task; no awareness of scale or failure.

2
Needs Improvement

Limited architectural awareness; struggles with design decisions.

3
Satisfactory

Works within an existing design; makes sound local decisions.

4
Very Good

Designs for scale and maintainability; articulates trade-offs clearly.

5
Excellent

Allocates testing effort by risk, and can defend what they deliberately left untested.

03
Evaluation factor

Evidence and rigour

25% weight

Check how they handle a flaky suite and whether they can describe a bug that escaped to production.

Evidence to listen for

  • Validates results rather than trusting output
  • Knows how their work is measured and what a bad result looks like
  • Can describe a time their own analysis or model was wrong and how they caught it
  • Careful about data quality, leakage, and silent failure

Five-point scoring guide

1
Poor

Ships unvalidated work; no notion of how correctness is checked.

2
Needs Improvement

Validates superficially; misses obvious quality or leakage issues.

3
Satisfactory

Reasonable checks in place; rigour drops under time pressure.

4
Very Good

Validates thoroughly; can name a real error they caught in their own work.

5
Excellent

Fixes flakiness at the cause rather than by retrying, and is candid about a bug that escaped and why.

04
Evaluation factor

Collaboration and communication

15% weight

Assess how they raise quality problems with developers under release pressure without becoming a blocker.

Evidence to listen for

  • Explains technical work to non-technical stakeholders
  • Gives and takes code or peer review constructively
  • Documents enough that the work survives their absence
  • Aligns with team process rather than working around it

Five-point scoring guide

1
Poor

Cannot work in a team; resistant to feedback.

2
Needs Improvement

Communication issues create rework; lone-wolf tendencies.

3
Satisfactory

Adequate team member; documentation and review participation are light.

4
Very Good

Communicates well; reliable reviewer and collaborator.

5
Excellent

Raises quality risks with evidence and calibrated urgency, so releases improve rather than stall.

Evidence-led prompts

Interview questions for a Quality Assurance (QA) Engineer

Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.

  1. 01

    How many years have you worked in software testing and QA, and what kind of products were you testing?

  2. 02

    What QA tools have you actually used yourself, and what did you use each one for?

  3. 03

    Which automated testing frameworks have you built or extended, and in what language?

  4. 04

    What continuous integration tools have you run tests in, and how were the suites triggered?

  5. 05

    Walk us through a test strategy you defined for a project: what you chose to automate, what you kept manual, and what you decided not to test.

See the complete Quality Assurance (QA) Engineer question set
Put this rubric to work

Score every candidate against the same standard

Add these weighted factors to Hirevire and let AI evaluate recorded answers against your rubric.

Explore AI Scorecards