--- title: "QA engineer interview questions and what to expect | Orbit" description: "What qa engineer interviews usually test, the usual stages, and 17 practice questions with what a good answer covers. Practise free in the warm-up." canonical: https://orbitanswer.com/roles/qa-engineer last_reviewed: 2026-10-18 --- [Companies](https://orbitanswer.com/companies) [Roles](https://orbitanswer.com/roles) [Free warm-up](https://orbitanswer.com/warmup) - [Home](https://orbitanswer.com/) - [Roles](https://orbitanswer.com/roles) - QA engineer Role interview guide # QA engineer interview questions and what to expect QA and test engineer interviews usually test how you think about what could go wrong: writing test cases for an everyday feature, reporting a bug clearly and deciding what to test first. Candidates commonly report questions on testing types and the bug life cycle, and for automation and SDET roles, coding in a language such as Java or Python plus tools like Selenium, Playwright or API testing frameworks. What candidates commonly report; it varies by employer, level and country. Last reviewed 18 October 2026. [Practise a qa engineer mock interview](https://orbitanswer.com/register) [Warm up free on these questions](https://orbitanswer.com/warmup?track=role%3Aqa-engineer) ## The usual stages - 1 Recruiter or HR screen - 2 Online test or written exercise: test cases for a feature, testing concepts, sometimes basic coding - 3 Technical round on testing types, test design and the bug life cycle - 4 Automation round for automation and SDET roles: write a test or discuss a framework - 5 Hiring manager or behavioural round ## What interviewers check - Thinking beyond the happy path: edge cases, errors and odd inputs - Clear bug reports a developer can act on straight away - Prioritising tests by risk when time is short - Automation that is reliable and maintainable, not just recorded - Checking APIs and data, not only the user interface - Working with developers as partners on quality ## Behavioral questions ### Tell me about the most important bug you've found. How did you find it? A good answer covers - What made you look there - How you reproduced it and narrowed down the conditions - Its impact, and what happened after you reported it ### Describe a time a developer said a bug you reported wasn't a bug. A good answer covers - The disagreement, and what the requirement actually said - How you showed the evidence calmly - How it was settled, and what you'd clarify earlier next time ### Tell me about a release where testing time was cut. What did you test, and what did you leave out? A good answer covers - How you ranked areas by risk and by how much they're used - What you told the team about what wasn't tested - What happened after the release ### Tell me about a bug that reached production despite your testing. What did you learn? A good answer covers - Why the tests missed it, honestly - How it was found and fixed - The change you made to your tests or process ## Questions about the job ### How would you test a login page? Talk me through the cases you'd cover. A good answer covers - Valid and invalid logins, empty fields, case sensitivity, very long inputs - Security: locking after repeated failures, a hidden password field, injection attempts - Usability, accessibility, and different browsers and devices ### Explain verification versus validation, and functional versus non-functional testing. A good answer covers - Verification: was it built right? Validation: was the right thing built? - Functional tests check what it does; non-functional tests check speed, security and usability - An example of each from a project ### What's the difference between severity and priority? Give an example where they differ. A good answer covers - Severity is the impact; priority is how soon it should be fixed - A high-severity, low-priority bug, and the reverse - Who usually decides each ### Walk me through the life of a bug, from when you find it to when it's closed. A good answer covers - A report with steps, expected and actual results, evidence and environment - Statuses such as new, assigned, fixed, retest, closed or reopened - Retesting the fix and running regression tests around it ### What's the difference between smoke, sanity and regression testing? A good answer covers - Smoke: is the build stable enough to test at all? - Sanity: a focused check after a small fix or change - Regression: making sure existing features still work, and why it suits automation ### How would you decide which tests to automate and which to keep manual? A good answer covers - Automating stable, repetitive, high-value checks such as regression - Keeping exploratory, one-off and fast-changing areas manual - Weighing the cost of maintaining a test against the time it saves ### Your automated UI tests pass sometimes and fail other times with no code change. What would you do? A good answer covers - Finding the pattern: timing, test data, test order, environment - Fixes: proper waits instead of fixed sleeps, independent test data, stable locators - Separating flaky tests so they don't hide genuine failures ### How would you structure a test automation framework so it stays easy to maintain? A good answer covers - Page objects or similar layers that keep locators in one place - Test data and configuration kept out of the test code - Running in CI with clear reports and screenshots on failure ### How would you test a REST API, for example one that creates an order? A good answer covers - Status codes, the response body, and the order saved correctly - Invalid input, missing fields, authentication and permissions - Tools such as Postman or code-based tests, and checking the database where needed ### Explain equivalence partitioning and boundary value analysis, using an age field that accepts 18 to 60. A good answer covers - Grouping inputs that should behave the same and testing one from each group - Testing just below, at and just above each boundary: 17, 18, 60 and 61 - Why this finds bugs with fewer test cases ### How would you approach performance testing for a ticket-booking site before a big sale? A good answer covers - Expected load, the shape of the peak, and the key user journeys - Load and stress tests with a tool such as JMeter or k6, watching response times and errors - Finding the bottleneck with developers and testing again after fixes ## Motivation and fit ### Why do you want a career in testing rather than development? A good answer covers - What you enjoy about finding problems and protecting users - An example that shows that mindset - Where you want to grow: automation, performance, security testing ### How do you keep learning new testing tools, and what are you learning right now? A good answer covers - A specific tool or skill you're learning, and why - How you practise it: a side project, a course, tasks at work - How it would help in this role ## Tips - When asked to test anything, first ask what it's for and who uses it, then list cases in groups: functional, edge, negative and non-functional. - Bring a sample bug report you've written (with nothing confidential in it) and be ready to explain why it's clear. - For automation roles, expect to write code live; practise basic programming in your test language, not only tool commands. - Be honest about which tools you've used and which you've only read about; follow-up questions find the difference quickly. - Mention API and database checks; testing only through the screen is a common gap. ## Practise it out loud A mock interview asks what qa engineer interviews usually test, follows up on your answers and gives you a report. The warm-up is free, needs no account and checks five of these questions as you answer. [Practise a qa engineer mock interview](https://orbitanswer.com/register) [Warm up free on these questions](https://orbitanswer.com/warmup?track=role%3Aqa-engineer) ## About this guide Written by Orbit from what candidates and interviewers commonly describe for this kind of job. The questions are Orbit's own practice questions, not questions taken from any employer's interviews. Processes change, so check the job post and what your recruiter tells you. ## Company guides to read with this one - [BrowserStack BrowserStack runs a cloud testing platform that lets teams test websites and apps on real browsers and devices, and it describes itself as remote-first. 14 practice questions](https://orbitanswer.com/companies/browserstack) - [Adobe Adobe's careers site describes a call with a Talent Partner, an interview with the hiring manager, then skills assessments and team interviews: coding… 14 practice questions](https://orbitanswer.com/companies/adobe) - [Accenture For freshers in India, candidates commonly report online cognitive, technical and coding assessments and a spoken-English communication test, followed by one… 14 practice questions](https://orbitanswer.com/companies/accenture) - [CRED Candidates commonly report that CRED's engineering interviews include problem-solving and machine coding or design rounds, followed by conversations about how… 13 practice questions](https://orbitanswer.com/companies/cred) ## More guides: software engineering - [Software engineer Software engineer interviews usually combine coding (solving a problem out loud, often in a shared editor), computer science fundamentals and a discussion of… 17 practice questions](https://orbitanswer.com/roles/software-engineer) - [Backend developer Backend developer interviews usually focus on APIs, databases and how a service behaves under load or failure, alongside coding in the role's main language… 17 practice questions](https://orbitanswer.com/roles/backend-developer) - [Cybersecurity analyst Cybersecurity analyst interviews usually test networking and operating-system basics, common attacks, and how you'd respond to an alert or incident. 17 practice questions](https://orbitanswer.com/roles/cybersecurity-analyst) - [DevOps engineer DevOps and site reliability interviews usually cover Linux, networking, CI/CD, containers and at least one cloud platform, and lean heavily on… 18 practice questions](https://orbitanswer.com/roles/devops-engineer) - [Embedded engineer Embedded engineer interviews usually go deep on C, microcontroller basics and how software meets hardware: interrupts, memory, timing and communication… 17 practice questions](https://orbitanswer.com/roles/embedded-engineer) - [Frontend developer Frontend developer interviews usually test JavaScript, HTML and CSS fundamentals, then a framework such as React, often through a live exercise building or… 17 practice questions](https://orbitanswer.com/roles/frontend-developer) [All 32 role guides](https://orbitanswer.com/roles) [Guides by company](https://orbitanswer.com/companies)