1. Give an example of a time when you and a colleague had a difference of opinion about a project you worked on together.
The full question
Give an example of a time when you and a colleague had a difference of opinion about a project you worked on together. How did you reach a conclusion?
Model answer
- Situation — A colleague and I were working on a safer release process for services supporting the delivery journey. We agreed that releases needed better protection, but disagreed about the control: my colleague wanted every deployment blocked by a single, strict platform-wide health gate; I thought that would create false alarms for services with different traffic patterns and failure modes.
- Task — I needed to reach a decision that protected customers and on-call engineers without turning the shared deployment platform into a bottleneck. I also wanted to keep the discussion focused on evidence rather than personal preference.
- Action
- I first asked my colleague to explain the incidents behind their proposal. Their concern was valid: a release could look successful while a key customer-facing operation was failing, and teams did not always notice quickly.
- I explained my concern with a universal threshold: a low-volume service could fail a traffic-based check simply because it had too little data, while a broad aggregate could hide a problem in one important endpoint.
- We wrote down the outcomes we both wanted—detect harmful releases quickly, roll back reliably, and avoid blocking healthy releases—and reviewed recent incidents against those criteria.
- I proposed a compromise: require a small set of platform-level checks for every service, such as deployment health and basic availability, while allowing teams to add service-specific indicators and thresholds. We would also start with conservative rollout stages and make the decision and rollback reason visible to the on-call engineer.
- To test it, we piloted the approach with two services that had different traffic profiles. We deliberately exercised a failing check in staging, then reviewed false positives and the operator experience together.
- The results led us to refine the defaults and document when a service should define a custom check. I made sure my colleague was credited for surfacing the need for a stronger release gate and invited them to present the pilot findings with me.
- Result — We adopted the shared baseline plus service-specific checks, rather than either original proposal unchanged. That gave teams consistent protection while avoiding a one-size-fits-all threshold, and the pilot provided a repeatable way to validate future changes. I learned that a disagreement is often useful when both people make the risks explicit; a small, measurable experiment can turn it into a better design and preserve the working relationship.