Skip to content

Behavioural · Medium

Tell me about a time you disagreed with an engineering lead. How did you resolve it?

Short answer

Use a real example structured as situation, task, action and result. Show that you understood the engineer's reasoning, separated facts from opinions, brought in evidence or users, and reached a decision you both committed to. End with what you learnt. Avoid stories where you simply won the argument or where the conflict was trivial.

Detailed answer

Framework: STAR with reflection

  • Situation: brief context.
  • Task: what you were responsible for.
  • Action: what you did, in detail. This should be most of the answer.
  • Result: outcome, ideally with evidence.
  • Reflection: what you would do differently.

What interviewers listen for

  • You assume good intent and seek to understand.
  • You use data and user evidence rather than authority.
  • You can disagree and commit.
  • You protect the relationship.

Worked example (structure only)

  • Situation: you wanted to launch a feature to all users; the engineering lead wanted a gradual rollout because the change touched the checkout service.
  • Task: you owned the launch plan and a date agreed with marketing.
  • Action: you met the lead one-to-one to understand the specific risks. You learnt that a similar change had caused an outage the previous year. You proposed a compromise: a staged rollout over a few days with clear rollback criteria, and you renegotiated the marketing message to say "rolling out this week" rather than a single launch moment.
  • Result: the rollout surfaced a performance issue at a small percentage of traffic, which was fixed before full release.
  • Reflection: you now involve engineering in setting launch dates rather than presenting them.

Common pitfalls

  • Choosing a story where you were simply right.
  • Speaking negatively about the other person.
  • Saying "we" throughout so your own contribution is unclear.
  • No reflection or learning.