QA Engineer Interview Questions: What to Ask at Each Stage

Last updated: August 19, 2026

The questions most teams ask in QA interviews are the wrong questions. Asking a candidate to define equivalence partitioning does not tell you whether they can apply it to your specific feature specification. Similarly, asking whether they have “experience with Cypress” does not tell you whether they can write a page object model or handle asynchronous test failures. This guide replaces generic interview lists with actual questions, the reasoning behind each, and what a strong answer looks like versus a weak one.

All 15+ questions below are organized by interview round so you can run a structured process that generates comparable signal across candidates. As a result, you avoid burning your engineering team’s calendar on weak candidates who should have been filtered in Round 1.

Interview Structure Overview

A well-structured QA interview process for nearshore candidates has four rounds, each with a specific gate. The total time investment for your team on a strong candidate is approximately 2.5 hours across all rounds. By contrast, the total time on a candidate who fails Round 1 is approximately 15 minutes of review time.

When working with a nearshore staffing agency like Kore BPO, candidates have already passed an internal technical and English screen before you see their profile. In that case, you can often compress Round 1 and Round 2 into a single 60-minute session, reducing time-to-offer by one calendar week. This compression alone can make a meaningful difference in whether you land the best candidates before a competitor does.

Round 1: English and Async Written Screen

Send this exercise by email or via a shared document. Ask the candidate to complete it without assistance and return it within 24 hours. Specifically, you are looking for clear written English, logical structure, and the ability to communicate a technical observation to a non-technical stakeholder.

Round 2: Test Design Methodology

This round is a live call. You are assessing whether the candidate can think through test coverage problems in real time, not whether they have memorized testing terminology. For this reason, present real scenarios rather than academic questions.

Round 3: Automation Technical Screen

Run this round on a shared screen with a live coding environment. For Cypress, use the Cypress online playground or a shared CodeSandbox. For Playwright, use a shared VS Code Live Share session. You are not evaluating whether the candidate memorizes syntax. Instead, you are evaluating whether they can write working test logic, structure tests correctly, and debug when something does not work.

describe('Login flow', () => {
  it('redirects to dashboard on valid login', () => {
    cy.visit('/login');
    cy.get('[data-testid="username"]').type('testuser@example.com');
    cy.get('[data-testid="password"]').type('ValidPass123!');
    cy.get('[data-testid="login-btn"]').click();
    cy.url().should('include', '/dashboard');
    cy.get('[data-testid="welcome-message"]').should('be.visible');
  });
});

Round 4: Team Fit Call

This round includes the engineering lead or the person who will work most closely with the QA engineer. You are not re-testing technical skills. Rather, you are assessing communication style, workflow assumptions, and red flags that technical screens do not surface.

Questions to Skip

These questions are commonly used in QA interviews and generate consistently low-signal responses. Removing them from your process reduces interview length without reducing decision quality.

Skip: “Tell me about yourself.” You already have the resume and cover letter. Use interview time instead for questions that reveal information you could not get from those materials.

Skip: “What is your greatest weakness?” This produces rehearsed answers that no candidate has ever answered honestly in an interview. Replace it with a scenario question about a specific time a bug shipped to production and what the candidate did as a result.

Skip: “Where do you see yourself in five years?” This is not relevant to whether a QA engineer can write a Cypress test and participate in your sprint effectively.

Skip: “Why do you want to work for us?” For nearshore roles where the agency handles sourcing, candidates often have limited prior exposure to your company. Asking this question penalizes candidates for lack of marketing research and, conversely, rewards candidates who are simply better at performing enthusiasm.

Skip: “What is a test plan?” Definitional questions filter for vocabulary, not skill. Replace with: “Give me an example of a test plan you wrote recently. What did you include and why?”

Scoring and Decision Framework

A simple scorecard prevents the bias that occurs when interviewers compare narrative impressions across candidates rather than structured scores. Use a four-dimension scorecard:

• Test design depth (1 to 5): Does the candidate apply equivalence partitioning, boundary value analysis, and exploratory testing correctly to real scenarios, not just in definitions?
• Automation skill (1 to 5): Can the candidate write working, maintainable test code in your framework without significant scaffolding? Do they use proper locators, avoid fixed waits, and structure tests correctly?
• English communication (1 to 5): Are bug reports, emails, and live speech clear enough for a US developer or PM to act on without clarification?
• Sprint integration readiness (1 to 5): Does the candidate’s description of their workflow match how your team operates? Do they take initiative on ambiguous scenarios, or do they wait for explicit direction?

Score each dimension independently. The minimum bar for an offer is no dimension below 3 and an aggregate score of 14 or above. A candidate with a 5 in automation and a 2 in English is not ready for a live-collaboration nearshore role regardless of technical skill. Similarly, a candidate with a 4 in English and a 2 in automation is not ready for an automation-focused role regardless of communication skill.

Frequently Asked Questions

Disclosure: Kore BPO is a nearshore and offshore staffing agency. This article reflects our direct experience placing QA engineers from Costa Rica with US engineering teams.