[UAT/Delivery] A defect is raised in UAT, but engineering says it matches the documented requirement. How do you handle it?

Instruction: Answer this as a real UAT tension where the delivered build and the written requirement may both be internally consistent.

Context: Assesses whether the candidate can investigate the gap between documented scope and user expectation without defaulting to blame.

Official answer available

Preview the opening of the answer, then unlock the full walkthrough.

I would slow the conversation down and figure out what kind of gap we are actually dealing with. If engineering says the build matches the requirement, that may be true. But it does not automatically mean the user concern is invalid. The issue could be that the requirement was incomplete, too vague, approved without full understanding, or changed...

Related Questions