QA Engineer interview questions and sample answers

A qa engineer interview usually mixes two kinds of question: ones that test whether you know the job, and behavioral ones that ask for proof from your past. Below are 10 of the first with a short model answer, and 5 of the second with what the interviewer is really checking. Rewrite every answer in your own words and with your own numbers.

Job-specific questions

1. How do you decide what to automate versus test manually?

I automate repetitive regression tests and high-risk paths that run frequently, and keep exploratory or UI-heavy edge cases manual since automation maintenance cost isn't worth it for low-frequency scenarios.

2. How do you write a test plan for a new feature?

I break it into functional, edge case, and negative test scenarios based on the requirements doc, map each to acceptance criteria, and flag ambiguous requirements back to the PM before testing starts.

3. What's your approach to a bug report a developer says they can't reproduce?

I include exact steps, environment details, logs, and a screen recording if possible, and I try to reproduce it myself in a clean environment before escalating to rule out local setup issues.

4. How do you prioritize which bugs get fixed before a release?

I rate severity and frequency together, blocking release for crashes or data loss bugs, but letting low-severity cosmetic issues get triaged into the backlog if the release date is fixed.

5. How do you test an API without a UI?

I use Postman or a similar tool to hit endpoints directly, checking status codes, response schemas, and edge cases like malformed input or missing auth tokens, and I automate these in a CI pipeline.

6. What's your process for regression testing after a bug fix?

I retest the specific fix, then run the surrounding test suite for that module since fixes often introduce side effects, and I check the automated regression suite passes before signing off.

7. How do you handle flaky automated tests?

I investigate the root cause rather than just adding retries, often finding it's a timing or wait condition issue, and I fix the underlying test rather than disabling it and losing coverage.

8. How do you approach performance testing for a new release?

I use a tool like JMeter to simulate expected load, compare response times against baseline metrics, and flag any degradation over an agreed threshold, like a 20 percent increase in response time.

9. How do you work with developers when you find a critical bug close to release?

I report it immediately with clear reproduction steps and severity, and I push for a go/no-go conversation with the team rather than letting it slide through under deadline pressure.

10. How do you ensure test coverage on a project with limited time?

I focus on risk-based testing, prioritizing the most-used features and highest business impact paths first, and I'm upfront with the team about what didn't get tested if time runs out.

Behavioral questions

Answer these with STAR: the Situation in one sentence, the Task, the Action you took (most of the answer), the Result with a number.

11. Tell me about a result you are proud of.

What they are checking: A specific outcome with a number, and what you personally did to get it.

A result to build the answer around: Built an automation suite of 1,800 tests running on every pull request.

12. Describe a time you improved how something was done.

What they are checking: That you notice waste and fix it without being told, then measure the difference.

A result to build the answer around: Cut production bugs by 60% in a year.

13. Tell me about a time you had to deliver under pressure.

What they are checking: How you prioritise, communicate early and still finish to standard.

A result to build the answer around: Reduced regression testing from 3 days to 40 minutes.

14. Give an example of working with a difficult colleague or customer.

What they are checking: Calm, the other person's view stated fairly, and a result that helped both sides.

A result to build the answer around: Wrote API tests covering 250 endpoints.

15. What is something you learned from a mistake?

What they are checking: Ownership without excuses, and the habit you changed so it did not happen again.

A result to build the answer around: Introduced a bug triage process that halved time-to-fix for critical issues.

Before the interview

Interviewers read your resume just before they walk in, and most questions come from it. Every bullet on it should be one you can expand into a two-minute STAR story. Check that it matches the posting with the free ATS Match Score, and look at the qa engineer resume keywords the ad is likely to use.

Turn your notes into a qa engineer resume, free

No signup, no card. See the full qa engineer resume example and the cover letter example.

Interview questions for related jobs

All interview question lists · CV Forge — free resume generator