I had a decent story ready but I think I spent too long on the setup and not enough on how we actually resolved it.
Choose a real disagreement where both sides had valid technical or product arguments, and focus on the process you used to reach a decision rather than on winning the argument. Show that you listened, used data or prototypes to resolve ambiguity, and committed fully to the outcome even if it wasn't your preferred option.
Pro tip: At Google, interviewers care more about how you disagree than whether you were right—demonstrate 'disagree and commit' by clearly stating that you supported the final decision and helped execute it.
Describe the project, your role, and the teammate's role in 1-2 sentences so the interviewer understands the stakes and why the decision mattered.
Explain your teammate's technical or product argument and your own, showing that you understood their reasoning and the trade-offs involved.
Focus on the process: listening, asking questions, gathering data, prototyping, or bringing in a neutral third party to evaluate the options.
Explain what was decided, why, and how you supported the outcome—even if it wasn't your original preference—to show maturity and teamwork.
Highlight the impact on the product or team and what you learned about collaboration, decision-making, or technical trade-offs.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.