Tell me about a time you faced a conflict while working on a team. How did you handle it?

Illustrative answer

This is a fictional example. Replace it with an experience you can describe truthfully.

A designer and I disagreed about a bulk-edit feature. I proposed saving every change immediately to simplify implementation; the designer wanted a review step because a mistake could affect many records. Our discussion had become focused on defending our designs.

I asked to compare the failure cases together. I explained the implementation constraint and asked the designer to walk me through a user's correction task. We agreed that preventing an unintended bulk change was a requirement, while some visual refinements could wait.

I built a small prototype of a review screen with a clear change summary, and the designer tested the interaction with representative tasks. We took the results and effort estimate to the product owner, who approved a narrower first release that retained the review step.

We delivered that agreed scope. In the reviewed tasks, users could identify and correct a mistaken selection before saving. That was useful evidence about the design, not proof that users would never make errors. I learned to make the competing concerns testable early instead of treating a disagreement as a contest between disciplines.

Follow-up to practice

What would you have done if the evidence still supported different choices, or the decision was outside your authority?