A good criterion is testable, specific, and free of implementation detail. Someone should read it and say pass or fail without interpreting anything. Cover the negative paths as deliberately as the happy one: invalid input, missing permission, timeout, empty result. If you cannot describe how you would test it, it is not a criterion yet, it is a hope.
Why interviewers ask this
Acceptance criteria are the analyst deliverable that developers and testers actually use, so this is a direct craft check. Interviewers want testability named as the defining property, coverage of negative paths, and a clean separation of requirement from solution. They also like hearing that criteria are reviewed with a developer and a tester before work starts, because that is where ambiguity gets caught cheaply.
How to structure your answer
- State the test: could someone mark it pass or fail unaided.
- Ban vague words like appropriate, quickly, user friendly.
- Cover negative and exception paths explicitly.
- Review the criteria with a developer and a tester before the build.
Example answer
My test is whether someone could read it and mark it pass or fail without asking me a question. If any interpretation is left, it is not finished. So I avoid words like appropriate, user friendly, and quickly, and replace them with something you could actually check. The other half of the job is the negative paths, which is where most defects come from. What happens with invalid input, what a user without permission sees, what happens when the downstream service times out, what an empty result looks like. Those are decisions somebody has to make, and if I do not make them with the business, a developer will make them at speed on a Thursday afternoon. I also walk the criteria through with a developer and a tester before the work is picked up. It takes twenty minutes and it always finds two or three things I had left ambiguous.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- Do you use given when then, and does the format actually help?
- How detailed should criteria be for a spike or a research task?
- Who owns the criteria when there is a product owner on the team?
Related business analyst questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions