← Google Interview Insights

Google·Product Manager·Onsite - Behavioral / Leadership·Senior

Senior
May 2026

Summary

Google PM interview, got asked the classic engineering disagreement question. Not much else to report but it's the kind of question that sounds easy until you actually have to answer it live.

Questions Asked (1)

Q1

Tell me about a time you disagreed with an Engineering team member or team.

Conflict ResolutionCross-functional AlignmentStakeholder Management
Author's notes

I had a story ready but it came out way more passive than I intended.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a specific disagreement where you and an engineer had different perspectives on a product decision, and show how you resolved it through data, user empathy, and collaboration. Focus on the process of reaching alignment and the positive outcome, not on winning the argument. Emphasize that you value engineering input and that the best solution often emerges from healthy debate.

Pro tip: Show that you can disagree without being disagreeable—demonstrate that you actively sought to understand the engineer's technical constraints and that you were willing to change your mind if presented with compelling evidence. This signals maturity and earns trust with engineering teams.

1. Set the Context

Briefly describe the project, the team, and the specific decision where you and the engineer(s) disagreed. Make sure the situation is relevant to product management and cross-functional collaboration.

2. Explain Both Perspectives

Clearly articulate your viewpoint as the PM and the engineer's viewpoint, showing that you understood their concerns (e.g., technical debt, feasibility, scalability). Avoid making the engineer sound unreasonable.

3. Describe Your Approach to Resolution

Explain the steps you took to resolve the disagreement, such as gathering data, running a small experiment, consulting users, or facilitating a discussion. Highlight how you listened actively and sought common ground.

4. Share the Outcome

Describe the resolution and its impact. If you compromised or changed your mind, say so and explain what you learned. If you convinced the engineer, explain how you did it respectfully.

5. Reflect and Learn

Conclude with what you learned from the experience and how it improved your ability to work with engineering teams in the future. Show self-awareness and a growth mindset.

Key Points to Mention

  • Demonstrate empathy for the engineer's technical constraints and priorities.
  • Use data and user research to inform the decision, not just opinions.
  • Show that you actively listened and considered the engineer's perspective.
  • Highlight the importance of maintaining a positive working relationship.
  • Explain how you reached a mutually agreeable solution or compromise.
  • Reflect on how the experience strengthened your cross-functional collaboration skills.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.