Skip to content
RED SAGSkills
mediumQA Engineer interview question

A developer says your bug is "working as designed", but you think users will be confused. What do you do?

What the interviewer wants to hear

  • Stay calm and focus on user impact, not blame
  • Check the requirement or design for what is expected
  • Bring evidence such as user scenarios or data
  • Involve the product owner to decide
  • Accept and document the final decision

Model answer

I first check whether the developer is right about the spec. If the requirement really describes this behaviour, then the issue is not a code bug but a possible design or requirement problem. I explain my concern in terms of user impact, for example "users who enter a promo code after selecting COD lose the discount without any message, which may cause complaints". I bring evidence: steps, a screen recording, and if possible support tickets or analytics showing similar confusion. Then I involve the product owner, because deciding expected behaviour is their call, not mine or the developer's. If they agree, the ticket becomes an improvement story. If they decide to keep it, I accept that, close the bug with the decision noted, and maybe suggest a small help text. The goal is a good product and a good working relationship, not winning an argument.

Can you answer it under time pressure?

Take a timed medium round and get scored on every answer.

Start mock interview

More medium QA Engineer questions