Start here. This is the direct spoken answer to practice first.
Why this question matters
Code review disagreement is common. Interviewers want to hear how the candidate protects quality while keeping trust with teammates.
Use this as an adaptable model, not a story to claim as your own. Replace the project, constraints, your actions, collaborators, outcome, evidence, and reflection with truthful details from your experience.
I disagreed with a change that added a convenient shortcut in the API but bypassed the normal authorization helper. I first asked about the intent instead of assuming it was careless. Then I explained the risk: the endpoint looked internal today, but the pattern could spread and weaken resource ownership checks. I suggested using the existing policy helper and adding a small test for the denied case.