Interview guide
QA Tester Interview Questions & Answers Guide (2026)
A hiring-manager’s interview kit for qa testers — with specific “what to look for” notes on every answer, red flags to watch, and a practical test.
Key facts
- Role
- QA Tester
- Technical questions
- 14
- Behavioral
- 7
- Role-fit
- 5
- Red flags
- 8
- Practical test
- Included
How to use this guide
Pick 4-6 technical questions across difficulties, 2-3 behavioral, and 1-2 role-fit for a 45-minute interview. For senior roles, weight harder technical and role-fit higher. Always close with the practical test so you are hiring on evidence, not impressions. The “what to look for” notes are a scoring rubric: strong answers touch most points, weak answers miss them or replace them with platitudes.
Technical questions — Easy
1. Explain the difference between severity and priority. Give me an example of high severity / low priority and the reverse.
EasyWhat to look for: Severity = impact on system, priority = urgency to fix. Example: cosmetic typo on checkout page = low severity, high priority (brand/revenue-facing). Crash on a deprecated admin page used once a year = high severity, low priority.
2. Describe the automation pyramid and where most teams get it wrong.
EasyWhat to look for: Many unit → fewer integration/API → few E2E. Common mistake: ice cream cone (heavy E2E, little unit). Discusses why: E2E is slow, flaky, expensive to maintain. Good testers push tests down the pyramid.
3. A developer closes a bug as "cannot reproduce". What is your response?
EasyWhat to look for: Not confrontational. Provides better repro (video, exact build/env, network trace, user account), asks for pair session, checks if flaky/race condition, reopens with new data. Does not argue in comments.
Technical questions — Medium
1. Walk me through how you would design a regression suite for a SaaS app with 40 engineers shipping daily. What goes in it, what stays out?
MediumWhat to look for: Risk-based: critical user journeys (signup, checkout, core product workflow), not exhaustive coverage. Automation pyramid: heavy API tests, thin E2E. Discusses runtime budget, CI gating strategy, what to leave for exploratory.
2. Write (verbally or on paper) a Playwright test for a login flow including a failed attempt then a successful one. What selectors do you use and why?
MediumWhat to look for: data-testid or role-based locators (getByRole, getByLabel), NOT CSS class selectors. Explicit expectations with web-first assertions. Network mocking or seeded user. Proper test isolation (fresh context).
3. How do you test an API that returns 200 OK but with malformed JSON in the body? What layers of testing catch that?
MediumWhat to look for: Schema validation (JSON Schema, Zod, Joi) in API contract tests, not just status code. Postman tests with pm.response.to.have.jsonBody, or code-based contract tests. Should mention consumer-driven contracts (Pact) for microservices.
4. You are testing a checkout flow that integrates with Stripe. How do you test it without hitting real Stripe on every CI run?
MediumWhat to look for: Stripe test mode + test cards for staging/integration, Stripe CLI for webhook simulation, mock Stripe in unit/component tests, contract tests against Stripe mock server. Mentions idempotency key handling.
5. Walk me through an exploratory testing session charter you would run on a new feature.
MediumWhat to look for: Session-based test management: charter (mission + timebox 60-90min), notes on observations, questions, bugs, coverage. Mentions heuristics like SFDPOT (Structure, Function, Data, Platform, Operations, Time) or FEW HICCUPPS.
6. Your e-commerce app needs to be tested across Chrome, Safari, Firefox, Edge, iOS Safari, and Android Chrome. How do you scope the matrix without burning weeks?
MediumWhat to look for: Risk-based matrix: latest 2 versions of each, real-user analytics to prioritize, automated cross-browser on critical paths via BrowserStack/Sauce, manual smoke on lower-traffic browsers, documented scope. Not testing IE11 unless data justifies.
7. What is visual regression testing, when is it worth it, and what breaks it?
MediumWhat to look for: Screenshot diffing (Percy, Chromatic, Playwright snapshots). Worth it on design-system-heavy UIs and pre-launch pages. Breakers: dynamic content (dates, avatars), animation timing, font rendering across OS, anti-aliasing. Needs ignore regions or deterministic stubs.
Technical questions — Hard
1. You have a Playwright test that passes locally but fails 30% of the time on CI. Walk me through debugging.
HardWhat to look for: Trace viewer, video/screenshot on failure, identify race conditions, check for hard-coded waits vs auto-waiting locators, network mocking or seeded test data, CI resource contention, parallelization issues. Specific Playwright APIs (expect.toHaveText with timeout, test.describe.configure).
2. How do you do an accessibility audit on a new feature? Walk me through the actual steps.
HardWhat to look for: axe DevTools automated scan (catches ~30% of issues), keyboard-only walkthrough (Tab, Shift+Tab, Enter, Escape, arrow keys), screen reader pass (VoiceOver/NVDA), color contrast check, focus order, ARIA usage review. Knows WCAG 2.1 AA criteria (1.4.3, 2.1.1, 2.4.3, 4.1.2).
3. How do you load test a signup endpoint that is about to go on a Product Hunt launch?
HardWhat to look for: k6 or JMeter scenario modeling expected concurrency, ramp-up, think time. Measure P95/P99 latency, error rate, DB/CPU saturation. Test against staging with production-like data. Mentions warm-up, cache effects, and autoscaling behavior.
4. Describe a production bug that escaped your QA process. Why did it escape, and what did you change?
HardWhat to look for: Real story with ownership. Root cause of the escape (untested combination, missing env parity, timing), concrete process change (added test, added alert, tightened review). Avoids blaming devs or "we were rushed".
Behavioral questions
1. Tell me about a release you signed off on that shipped a bug to production. How did you handle it?
What to look for: Ownership, no deflection, walked through postmortem outcome, concrete improvement to test plan or process after.
2. Describe a time engineering pushed back on a bug you filed. How did you resolve it?
What to look for: Brought better data (video, logs, user impact), found shared understanding, escalated through the right channel if needed, not stubborn for ego.
3. How do you handle being the last line before production when product is pressuring a release?
What to look for: Clear risk communication in writing, offers trade-offs (ship with known issue X documented, ship without feature Y), does not cave on P0 blockers, does not become a martyr either.
4. Walk me through how you onboard yourself to a new product you have never used.
What to look for: Uses it as a customer first, reads PRDs and existing test plans, traces a user flow end to end, asks dumb questions early, draws a feature map.
5. Tell me about a time you found a bug no one else caught — what was your approach?
What to look for: Exploratory mindset, heuristics used (edge cases, unusual data, concurrent actions, unusual device), curiosity, not just running scripts.
6. How do you stay current on testing tooling and techniques?
What to look for: Concrete: follows specific people/blogs (Michael Bolton, James Bach, Angie Jones), reads Playwright/Cypress release notes, experiments on side projects. Not vague "I read stuff".
7. Describe a time you pushed for more automation and met resistance. How did you make the case?
What to look for: Used data (escape rate, regression hours, release frequency), proposed pilot, measured ROI after. Not ideological.
Role-fit questions
1. How do you split your time between manual, exploratory, and automation work on a mid-stage product?
What to look for: Honest and stage-aware answer. Often 50/30/20 or similar. Explains why that split fits product maturity. Not dogmatic "100% automation".
2. We use Playwright, TestRail, and Linear. Which have you used, and how would you ramp on the ones you have not?
What to look for: Honest gap assessment with a concrete ramp plan (docs, shadow a senior, ship small test first). Fakery is a red flag.
3. Our engineers merge to main 30+ times a day. What does that mean for your test strategy?
What to look for: CI-gated tests, fast feedback (under 15min), feature flags, trunk-based discipline, monitoring-in-production as a testing layer, canary releases.
4. How do you feel about working without a dedicated dev-QA handoff (no waterfall phases)?
What to look for: Embraces shift-left: PRD review early, pairs with devs during implementation, continuous testing rather than end-of-sprint crunch.
5. What does your first 30 days look like here?
What to look for: Product walkthrough, test plan audit, first clean bug by end of week 1, first Playwright test by week 2, regression suite audit by week 4. Not weeks of passive ramp.
Red flags
Any one of these alone is usually reason to pass, especially combined with weak answers elsewhere.
- • Confuses severity and priority or uses them interchangeably.
- • Automates everything by default without risk-based reasoning.
- • Writes Playwright/Cypress tests with CSS class selectors or page.waitForTimeout everywhere.
- • Cannot name a single WCAG 2.1 AA success criterion.
- • Files bugs without repro steps, video, or environment info.
- • Measures test value by line coverage percentage or raw test count.
- • Describes QA as "finding bugs" rather than "reducing risk".
- • Has never integrated tests into a CI pipeline.
Practical test
4-hour take-home split in two parts. Part 1: given a short PRD for a signup + email verification flow, write a structured test plan with test cases, risk assessment, and a documented device/browser matrix. Part 2: write a Playwright test suite (5-8 tests) covering the happy path, form validation, and one negative scenario, plus a Postman collection for the 3 underlying API endpoints with schema validation. Graded on: test plan rigor (30%), automation code quality and selector strategy (30%), coverage of edge cases (20%), and the written trade-offs README (20%).
Scoring rubric
Score each answer 1-4: (1) Misses most of the rubric or gives platitudes; (2) Hits some points but cannot go deep when pressed; (3) Covers the rubric and can defend the answer under follow-ups; (4) Adds unprompted nuance, trade-offs, or real examples beyond the rubric. Hire at an average of 3.0+ across technical, behavioral, and role-fit, with zero red flags, and a pass on the practical test.
Related
Written by Syed Ali
Founder, Remoteria
Syed Ali founded Remoteria after a decade building distributed teams across 4 continents. He has helped 500+ companies source, vet, onboard, and scale pre-vetted offshore talent in engineering, design, marketing, and operations.
- • 10+ years building distributed remote teams
- • 500+ successful offshore placements across US, UK, EU, and APAC
- • Specialist in offshore vetting and cross-timezone team integration
Last updated: April 12, 2026