I went with a real example from a cross-functional project where design and engineering had completely different priorities.
Use the STAR method to describe a specific conflict, focusing on how you listened to understand the other person's perspective, separated the problem from the people, and drove toward a data-informed resolution. Emphasize the positive outcome and what you learned about collaboration, showing that you can disagree without being disagreeable.
Pro tip: Show that you proactively seek to understand the other person's underlying interests and constraints before advocating for your own solution—this demonstrates maturity and aligns with Google's collaborative culture.
Briefly describe the project, your role, and the nature of the conflict (e.g., technical disagreement, priority clash, or communication breakdown) without assigning blame.
Explain how you actively listened to the other party's perspective, asked clarifying questions, and identified shared goals or underlying interests.
Describe how you proposed a data-driven or objective approach to evaluate options, such as prototyping, user research, or consulting a neutral third party.
Explain the agreed-upon resolution, how you ensured alignment, and any steps taken to prevent similar conflicts in the future.
Share what you learned from the experience and how it improved your ability to handle future conflicts or cross-functional collaboration.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.