Top 6 Acceptance criteria Interview Questions
Browse 6 real-world technical and behavioral interview questions about Acceptance criteria. Review scenarios, edge cases, and architectural best practices.
What does a business analyst do on an agile team, and how does requirements work survive without a signed-off specification?
The analysis does not shrink, it changes container: elicitation, rule-finding and precision now land in refined backlog items and acceptance criteria at the point of build. What a specification gave you free — traceability, cross-cutting requirements, a scope baseline — you rebuild on purpose.
Everybody signed off the requirement and two of them still mean different things by it. How do you catch that before the build?
Agreement on wording is not agreement on meaning, so stop re-reading the text and test it with concrete examples that force a different answer from each reading. Attack the words that hide ambiguity, use real data rather than hypotheticals, and record the resolution as examples instead of a rewritten sentence.
The business insists on a requirement that nobody can test — "the system must be intuitive". What do you write instead?
Convert the adjective into an observable: who is doing what task, under which conditions, and what result counts as a pass. Where no honest measure exists, record it as a design constraint with a named reviewer rather than leaving an unverifiable sentence in a document somebody signs.
How do you plan and run UAT, and what happens if the business signs off something that does not meet the original need?
Plan UAT backwards from the business outcome rather than forwards from the specification, and have real users run real work on realistic data. If sign-off lands on the wrong thing, measure the gap against the original objective and raise it as a change with its own business case.
A stakeholder says the new request is not a change, it is just a clarification. How do you handle that?
Stop arguing about the label and test the request against the accepted criteria: if the behaviour or the effort changes, it is a change whatever it is called. Hand the product owner a delta and options rather than a refusal, and keep a log so a fortnight of small clarifications stays visible.
What is the Definition of Done, who owns it, and what do you do with an item that misses it at the end of a Sprint?
The Definition of Done is one shared quality standard every increment must meet, owned by the Scrum Team unless the organisation mandates a stricter minimum. An item that misses it is not partially done: it returns to the Product Backlog rather than being released or presented as complete.