Interview questions
QA Tester interview questions, from 74 real job postings
What employers ask QA Tester candidates about, based on the skills their open postings list. Each question says what a strong answer shows.
- Open postings
- 74
- Top skill
- Quality Assurance
- Fully remote
- 4%
- Posted pay
- –
74 list skills
in 100% of postings
of open postings
Not enough posted pay
What employers ask for
Share of 74 open QA Tester postings that list each skill.
- 100%
- 4%
- 3%
- 1%
- 1%
- 1%
- 1%
- 1%
- 1%
- 1%
Technical questions
Three questions for each of the 6 skills QA Tester postings ask for most.
Quality Assurance
In 100% of postings- 1
What is the difference between testing a product against specifications versus testing for unexpected failure modes?
What a strong answer shows: Explains that specification testing verifies design requirements are met, while exploratory testing looks for edge cases and failure modes not originally expected; describes both are needed for confident product quality.
- 2
You find a defect late in production—walk me through how you would assess its severity and decide whether to halt production or allow shipment.
What a strong answer shows: Describes documenting the defect in detail, checking against specifications and customer requirements, assessing safety implications, consulting with engineering or management, and creating a record of the decision.
- 3
Tell me about a quality issue you discovered, investigated, or helped prevent—what was the problem and what did you do?
What a strong answer shows: Describes a specific defect or failure mode found, what investigation or analysis they performed, what root cause was identified, and what action was taken (rework, process change, supplier communication).
Android
In 4% of postings- 4
Explain the Android activity lifecycle and why understanding it matters for saving user data.
What a strong answer shows: Lists key states (onCreate, onStart, onResume, onPause, onStop, onDestroy), explains onPause/onStop are where you save data because the app can be killed after, notes onResume is where you reload.
- 5
You're building an app that plays music and needs to keep playing even when the user switches to another app. What component would you use and why?
What a strong answer shows: Describes using a Service (not Activity), mentions foreground service needs notification on Android 8+, notes using MediaPlayer or modern APIs, explains the difference between Service types.
- 6
Tell me about a time you fixed a crash or unexpected behavior on Android that didn't happen on other devices.
What a strong answer shows: Describes a real issue tied to Android version, permission model, or device variation, names the specific Android version or device it affected, explains the workaround or fix they implemented.
Jira
In 3% of postings- 7
Walk me through how you'd structure a Jira project for a team of six people shipping a product every two weeks.
What a strong answer shows: Describes creating a board (Kanban or Scrum), setting up custom fields for priority and story points, organizing epics and stories, configuring workflows for their process, and setting up automation to reduce manual work.
- 8
Your team complains that Jira has become a burden—they're spending too much time updating tickets instead than shipping. What specifically would you audit and change?
What a strong answer shows: Describes examining whether there are too many fields, over-complicated workflows, unnecessary custom statuses, or lack of automation. Names a concrete simplification (like removing fields, automating status updates, or cutting ceremonies).
- 9
Tell me about a time you used Jira reporting or dashboards to surface a real problem or improvement opportunity for your team.
What a strong answer shows: Describes a specific metric they looked at (like burndown, cycle time, or unfinished work), what problem it revealed, and what the team changed based on that visibility.
Agile
In 1% of postings- 10
What problem is Agile trying to solve compared to Waterfall, and what does it assume about how software gets built?
What a strong answer shows: Explains that Waterfall assumes requirements are known upfront, while Agile assumes they'll change and evolves through iteration and feedback. Describes working software delivered frequently and responding to change.
- 11
You're on a team mid-sprint when a critical production bug appears. What do you do, and how does it affect the sprint?
What a strong answer shows: Describes breaking context to fix the bug, documenting why work in progress stopped, deciding whether to adjust sprint scope or burn down, and communicating status to stakeholders.
- 12
Tell me about an Agile team you've worked on. How often did you actually deliver working software, and what was the team's biggest struggle with the framework?
What a strong answer shows: Names the sprint length and delivery cadence, gives a concrete example of feedback that changed the product direction, and describes a real friction point (like unclear stories, scope creep, or ceremonies feeling like waste).
CSS
In 1% of postings- 13
Explain the CSS cascade and specificity. When would you use !important and why should you generally avoid it?
What a strong answer shows: Defines cascade as later rules override earlier ones, explains specificity scoring (inline > IDs > classes > elements), notes !important breaks the cascade and makes debugging harder.
- 14
You're building a layout that needs to work on phones, tablets, and desktops. Walk me through how you'd approach this with CSS.
What a strong answer shows: Mentions mobile-first approach, describes using media queries with breakpoints, explains using flexible units (em, rem) over pixels, discusses testing at actual sizes not just resizing.
- 15
Tell me about a time you solved a layout problem in CSS that turned out to have a simple solution.
What a strong answer shows: Describes the problem in detail (centering, spacing, overflow), explains what they tried first, names the CSS property that actually fixed it and why it worked.
Contract Management
In 1% of postings- 16
Walk me through the key terms and obligations you review when evaluating a new vendor or service contract.
What a strong answer shows: Covers scope of work, payment terms, liability limits, termination rights, confidentiality, and performance standards; explains why each protects the organization.
- 17
You notice a contract with a key vendor is about to expire—walk me through how you'd handle renewal negotiations and what changes you'd push for.
What a strong answer shows: Describes reviewing the existing contract to identify issues, preparing talking points for improvement, researching market rates, and negotiating terms before renewal deadline.
- 18
Tell me about a time you caught an issue in a contract before it was signed or resolved a dispute with a counterparty over contract terms.
What a strong answer shows: Describes a specific problematic clause or misunderstanding they caught, the risk it posed, and how they resolved it.
Behavioral questions
Have one real story ready for each.
- 19
Tell me about a critical bug you found—what was it and how did you discover it?
What a strong answer shows: Describes the bug clearly (what happens, when it happens, impact), how their testing uncovered it (which test case, scenario, or exploratory session), and severity. Shows they know what matters most to catch.
- 20
Describe a time you had to test a feature under time pressure—how did you decide what to test?
What a strong answer shows: Recounts the constraints (deadline), how they broke down the feature into risk areas, which scenarios they prioritized, and what they explicitly decided not to test. Shows pragmatic prioritization.
- 21
Give an example of a time you found a bug that the developer said was 'impossible'—how did you investigate and convince them?
What a strong answer shows: Describes the unexpected behavior, how they reproduced it reliably, the conditions or edge case that triggered it, and evidence they gathered to show the developer. Shows persistence and clear communication.
- 22
Tell me about a testing process or automation you built to catch more bugs or save time—what problem did it solve?
What a strong answer shows: Describes the manual or unreliable process they replaced, the testing tool or framework they built, and concrete impact (bugs caught earlier, time saved, coverage improved). Shows they think beyond ad-hoc testing.
- 23
Describe a situation where you had to report a bug diplomatically—the developer was defensive or dismissed it—how did you handle it?
What a strong answer shows: Recounts the bug, why the developer resisted, how they documented and re-explained it, and what happened (whether they accepted it or not). Shows they can communicate clearly without inflaming egos.
Questions to ask them
Use the data. Interviewers remember candidates who ask specific questions.
Timeline. QA Tester postings stay open a median 8 days (15 closed in the last 180 days). Ask when they plan to decide and how many rounds are left.
The role. Ask whether this is a new role or a backfill, and what happened to the last person in it. Check the company's hiring score on HirQ first.
- 1
How do you measure success for someone in this role during their first year?
What the answer tells you: Their answer reveals whether the company has clear expectations or vague goals, and what they actually care about you delivering.
- 2
Can you walk me through what a typical week looks like for someone in this position?
What the answer tells you: You'll learn whether the role matches the job description and whether the daily work aligns with what you want to do.
- 3
Why is this role open right now—did someone leave, or is this a new position?
What the answer tells you: If it's a backfill, you understand the workload; if new, you learn whether the company is growing or shifting priorities.
- 4
What's the team structure, and who would I be working with most closely?
What the answer tells you: You get a sense of your peer group, reporting lines, and whether you'll be isolated or have colleagues to learn from.
- 5
What's your timeline for making a decision, and what does the rest of the process look like?
What the answer tells you: You know when you'll hear back and what to prepare for, so you can plan next steps and avoid uncertainty.
- 6
What does onboarding look like here—do people have a ramp period or are they expected to contribute immediately?
What the answer tells you: Their answer shows whether the company invests in new hires or throws them in; this affects how quickly you can actually be effective.
- 7
What are the biggest challenges this team is facing right now?
What the answer tells you: You hear what problems are real versus what they said in the job posting, and whether you're equipped to help solve them.
- 8
How has this role evolved since it was first created, or how do you expect it to change in the next year or two?
What the answer tells you: You understand whether the job is stable, growing, or shifting—and whether your skills will stay relevant here.
- 9
What does a typical career path look like for someone doing well in this role?
What the answer tells you: You learn whether there's room to advance within the team or if you'd need to move around to grow.
- 10
What made you decide to work here, and what keeps you here?
What the answer tells you: Their honesty about why they stay tells you whether this is a place people actually want to be or just tolerate.
Practice for a specific job
Practice for a specific job
Uses 1 AI runPaste a HirQ job link or the job description. We write 8 likely questions with talking points from your resume (your profile resume if you leave it blank).
Skills come from the text of open postings on HirQ, matched against a fixed list of 230 skills. Questions were written once per skill and category with AI and checked against that list; they are not from any one employer.
Get new QA Tester jobs by email
Free alerts, daily or weekly. We only send jobs that are still open.
Questions people ask
What skills do QA Tester interviews focus on?
Based on 74 open QA Tester postings that list skills, employers most often ask for Quality Assurance (100%), Android (4%), Jira (3%), Agile (1%), CSS (1%). Expect technical questions on the first two or three.
How should I answer behavioral questions for a QA Tester role?
Use one real story per question: the situation, what you did yourself, and the result. Keep each under two minutes and be ready for a follow-up on what you would do differently.
How long does hiring for a QA Tester take?
QA Tester postings that closed in the last 180 days stayed open a median of 8 days (15 postings). Ask about the timeline at the end of your first interview.