10 QA engineer interview questions and how to answer them

A QA engineer interview almost always follows the same script. Here are ten of the most common questions and what the interviewer wants to hear.

Basics

• “What is the difference between smoke and regression testing?” Smoke checks the critical path: does the app work at all. Regression covers everything the change could have affected. Show that you know when to run each.
• “What are boundary values?” Give an example: an age field from 0 to 120. Check −1, 0, 1, 119, 120, 121.
• “What does a good bug report look like?” Steps, expected and actual results, environment, priority, attachments. Most of all, it must be reproducible.

APIs and tools

• “How do you test an API without a UI?” Postman: collections, variables, checks on status codes and schemas. Mention HTTP methods and response codes.
• “What do you look at in DevTools?” Network (statuses, timings, payload), Console (JS errors), Application (local storage).

Experience

• “Tell me about the hardest bug you found.” Use STAR: situation, task, action, result. Numbers make the answer stronger.
• “Why QA and not development?” Give an honest answer about your interest in root-cause analysis and product quality, not “I didn’t get into development.”

Practise your answers out loud, and the right wording will come on the day. The AI interview trainer will help you rehearse →

Try Realtime Interview Copilot: live subtitles and AI answers on any call. Download for Windows →