Make the disagreement explicit and time boxed. Get both positions written down with tradeoffs and the assumptions each one depends on, then identify which assumptions can be tested cheaply with a spike or a benchmark. Set a decision date. If evidence does not settle it, you decide, explain the reasoning openly, and keep the choice reversible where you can so being wrong stays cheap.
Why interviewers ask this
Interviewers want to see that you neither rubber stamp the loudest voice nor let debate run for weeks in the name of consensus. They look for structure (written tradeoffs, testable assumptions, a deadline), willingness to make the call yourself when needed, and attention to the relationship afterward. How you treat the engineer whose approach you did not pick tells them plenty about retention on your team.
How to structure your answer
- Time box the debate and say so out loud on day one.
- Force the tradeoffs into writing with explicit assumptions.
- Test the cheap assumptions with a spike rather than arguing.
- Decide if evidence does not, explain why, and protect both relationships.
Example answer
The first thing I do is put a date on it, because unbounded architecture debate is expensive and both of them know it. Then I ask each of them for a page: the approach, the tradeoffs, and crucially the assumptions it depends on. Nine times out of ten the disagreement is not about the design, it is about a hidden assumption on load, on team skills, or on where the product is going in a year. Last time this happened it came down to whether we would need multi region inside eighteen months, which is a product question, not an engineering one, so I pulled the product lead in and it resolved in twenty minutes. When it is genuinely technical I ask what the cheapest experiment is, and we spend two days on a benchmark instead of two weeks on opinions. If it is still tied at the deadline I decide, write down why, and say plainly that it was close and here is the trigger that would make us revisit. Then I make sure the person who lost the call owns something meaningful in the build.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What if one of them refuses to accept the decision?
- How do you avoid becoming the bottleneck for every technical decision?
- How do you tell a reversible decision from an expensive one?
Related engineering manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions