Interview scorecard templates

QA Engineer interview scorecard template

Good QA engineers find the problems that matter before customers do. Use this scorecard to assess test planning, bug reporting, attention to detail, product understanding and risk assessment the same way across your panel.

Customize this scorecard

Free to use. Nothing you type on the scorecard is saved.

Interview scorecard

QA Engineer

Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.

Test planning

Turns a feature into a clear, prioritized set of tests that covers what matters within the time available.

Score for Test planning

Questions

  • Tell me about a time you planned testing for a new feature. Where did you start?
  • How did you decide what to test first when time was short?
  • Tell me about a test plan that missed something. What did you change afterward?

1: Below the bar

Describes testing as clicking through the feature. Has no written plan, no order of priority, and no sense of what is left out.

3: Meets the bar

Lists test cases from the requirements and puts the main ones first. Adjusts the plan when time shrinks, but with some prompting.

5: Above the bar

Starts from requirements and users, ranks tests by impact, says what is skipped and why, and updates the plan after misses.

Bug reporting

Writes clear, reproducible bug reports that help developers understand, find and fix problems quickly.

Score for Bug reporting

Questions

  • Tell me about a bug report you wrote that a developer fixed quickly. What did it include?
  • Tell me about a time a developer couldn't reproduce your bug. What did you do?
  • How do you decide how urgent a bug is and what to say about it?

1: Below the bar

Describes reports as short notes like "login broken." Leaves out steps, expected result or environment, and blames developers when they can't reproduce.

3: Meets the bar

Lists clear steps, expected and actual results, and the environment. Follows up when asked for more, and gives a reasonable urgency.

5: Above the bar

Gives minimal steps, evidence like logs or screenshots, and user impact. Narrows the cause and checks for duplicates before sending.

Attention to detail

Spots small inconsistencies in software and checks their own work before calling it done.

Score for Attention to detail

Questions

  • Tell me about a small defect you caught that others had missed.
  • Describe a time you found a mistake in your own testing. How?
  • How do you check a feature's behavior matches what was agreed?

1: Below the bar

Describes only obvious defects. Rarely rechecks own work and can't say how a missed issue got through.

3: Meets the bar

Gives a real example of a subtle defect found. Rechecks work with a simple routine, like a checklist or repeat run.

5: Above the bar

Describes catching subtle issues through a deliberate method, checks own work unprompted, and names what they now do to avoid the same miss.

Product understanding

Explains who uses the product, what they need, and how that shapes what gets tested.

Score for Product understanding

Questions

  • Tell me about a product you tested. Who used it and what did they need?
  • Tell me about a time knowing the users changed what you tested.
  • Pick a product you use daily. Which feature matters most to its users, and why?

1: Below the bar

Describes features only as a list of screens. Can't say who uses the product or why it matters.

3: Meets the bar

Names the main users and their goals. Links some testing choices to how people use the product.

5: Above the bar

Explains user goals and business purpose clearly, and gives examples where that knowledge changed what they tested or flagged.

Risk assessment

Identifies what could go wrong in a release and decides where testing effort matters most.

Score for Risk assessment

Questions

  • Tell me about a time you had too little time to test everything. What did you cut?
  • Describe a release where you judged a change was risky. How did you spot it?
  • Tell me about a bug that reached users. What risk did you miss?

1: Below the bar

Tries to test everything equally or guesses. Can't explain why some areas deserved more attention than others.

3: Meets the bar

Ranks areas by likely impact and failure, and focuses testing there. Explains the choice but rarely checks it afterward.

5: Above the bar

Weighs impact and likelihood with evidence, tells the team what was left untested, and uses past misses to adjust.

Overall recommendation

Decide on your own, before you compare notes with the rest of the panel.

Overall recommendation

Use this scorecard in PontaHR

With PontaHR, your team fills out scorecards on the candidate's profile. Compare ratings and feedback side by side when it's time to decide.

See how scorecards work in PontaHR, then try it with a guided free trial.

More interview scorecard templates

Hiring for a different role? Make your own scorecard