This one is sneaky because the obvious instinct is to just tell a story where you heroically said no and everyone thanked you later.
Choose a specific situation where you had a legitimate concern, explain how you gathered data and evaluated the request objectively, then describe how you proposed an alternative and collaborated to reach a solution. Emphasize that you maintained respect, focused on shared goals, and preserved the relationship by being transparent and constructive.
Pro tip: Frame your pushback as a shared problem-solving exercise, not a confrontation—show that you're optimizing for the team's success, not just your own preferences. At Google, data-driven reasoning and user impact are highly valued, so quantify the trade-offs whenever possible.
Briefly describe the project, your role, and the unreasonable request (e.g., an impossible deadline, a feature with no clear value, or pressure to skip testing). Keep it concise and focus on the stakes.
Explain how you assessed the request: what data, user impact, technical constraints, or team capacity you considered. Show that your conclusion was based on evidence, not emotion.
Describe how you raised your concerns respectfully, using 'I' statements and focusing on shared goals. Highlight that you listened to the other perspective and sought to understand their priorities.
Detail the alternative solutions you suggested, such as a phased approach, a reduced scope, or a process compromise. Explain how you framed them as benefits to the project or team.
Share the outcome: how the decision was made, what was implemented, and how you preserved trust. Emphasize any follow-up or acknowledgment of the other person's perspective.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.