Skip to main content
Strategy & Process
DEFINITION

What is Acceptance Criteria?

Acceptance criteria are specific, testable conditions that a user story or feature must satisfy to be considered complete and accepted by the product owner. They are agreed before development starts, often written as Given-When-Then scenarios, and they become the basis for acceptance tests, so a story is done only when every criterion passes.

No account needed · Scored in under a minute against a senior rubric

IN DEPTH

What does Acceptance Criteria mean in practice?

Acceptance criteria define the boundaries of a user story. They answer "How will we know this is done?" with concrete, verifiable conditions. Good acceptance criteria are specific (not vague), measurable (pass/fail), achievable (within scope), relevant (tied to user value), and independent (testable in isolation).

The most popular format is Given-When-Then (from BDD): "Given a logged-in user with items in cart, When they click checkout with a valid credit card, Then the order is created and a confirmation email is sent within 5 minutes." This format makes criteria directly translatable into automated test scenarios.

QA engineers play a critical role in acceptance criteria by joining backlog refinement sessions to ask clarifying questions, identifying missing criteria (error states, edge cases, performance expectations), and ensuring criteria are testable. Vague criteria like "the page should load fast" become "the page should load within 2 seconds on a 3G connection." Well-written acceptance criteria reduce ambiguity, prevent scope creep, and give testers clear targets.

WHY IT MATTERS

Why do interviewers ask about Acceptance Criteria?

Interviewers ask about acceptance criteria to see whether you collaborate effectively with product and development. Writing good criteria is a skill that prevents bugs before code is written.

EXAMPLE

What does Acceptance Criteria look like in a real project?

A story reads: "As a user, I want to reset my password." The QA engineer adds acceptance criteria: the reset email must arrive within 60 seconds, the reset link must expire after 24 hours, using an expired link must show a clear error message, and the user must be logged out of all sessions after a password change.

TIP

How should you talk about Acceptance Criteria in an interview?

Show that you actively contribute to acceptance criteria during refinement, not just consume them during testing. Give an example of criteria you improved or added.

Related Resources

Dive deeper with these related interview prep pages.

FREE TOOLS  /  no signup

Free QA career tools, no account needed

Instant and private, everything runs in your browser. Try them before you sign up.

EXEC.NOW

Ready to Ace Your QA Interview?

Practice explaining acceptance criteria and other key concepts with our AI interviewer.

Join 500+ QA engineers already practicing with AssertHired.

Question 1 · Automation · Mid-levellive scoring

A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.

Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.

Rather skip ahead? Create a free account

FREE.TO.START  ·  7.DAY.TRIAL ON PAID PLANS
Written by , Senior QA Automation Engineer, 50+ QA candidate interviews conductedLast updated July 2026