Separate decision rights from the debate. Product owns what and why, engineering owns how and how long, and most disagreements are really about a shared unknown rather than about authority. Surface the assumptions, bring data or a cheap experiment, and argue in terms of user and business outcomes rather than technical preference. If it stays deadlocked, escalate together with an agreed written statement of the options.
Why interviewers ask this
Interviewers want to see that you can be a genuine partner rather than an order taker or a blocker. They listen for respect for product's mandate, willingness to translate engineering concerns into business arguments (risk, maintenance cost, delivery speed) rather than vetoes, and the maturity to escalate jointly instead of running to a sponsor behind the other person's back.
How to structure your answer
- Name who owns which decision before arguing.
- Translate engineering concerns into business consequences.
- Find the testable assumption at the heart of it.
- Escalate jointly if it stays deadlocked.
Example answer
First I check whether it is even my call, because product owns what we build and I own how and how long, and a lot of manufactured conflict comes from engineering leaders trying to make roadmap decisions by proxy. If my objection is really about cost or risk, I say it in their language. Not this design is wrong, but this approach means we cannot support the enterprise contract in the fourth quarter without another rebuild, and here is the six week difference. That is a business argument they can weigh, and half the time it changes their mind on its own. Usually we can find the real disagreement underneath, which is normally a different guess about the same unknown, and then the useful question is what is the cheapest way to find out. On the last one we built a stripped down version for two customers in a week rather than arguing for a month, and the data settled it in their favor, not mine. When we genuinely cannot agree we go to shared leadership together with one written statement of the options, because going around each other separately is how partnerships die.
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 the product manager consistently ignores technical risk?
- How do you handle it when leadership sides against you?
- How do you build trust with a brand new product partner?
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