I had a decent example from a project where me and another dev had completely different ideas about how to structure the data layer.
Choose a disagreement that was substantive but not personal, and focus on how you separated the problem from the person. Show that you listened to understand, used data or user impact to evaluate options, and either reached a better solution together or committed to the decision after escalation. Emphasize the outcome and what you learned about collaboration.
Pro tip: Google values 'disagree and commit' — show that you can advocate strongly for your position but also fully support the final decision once it's made. Avoid framing the teammate as wrong; instead, highlight how you sought to understand their perspective and found a path forward.
Briefly describe the project, your role, and the teammate's role so the interviewer understands the stakes and the relationship.
State the specific technical or design decision you disagreed on, and summarize both your position and your teammate's position fairly.
Explain how you sought to understand their reasoning, shared your own, and used data, user impact, or prototyping to evaluate options.
Describe how you reached a decision—whether through compromise, escalation, or experimentation—and how you committed to it regardless of the outcome.
Share the result, what you learned about collaboration or technical judgment, and how you've applied that lesson since.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.
Picked an internship story about shipping a feature that ended up getting adopted by more teams than originally planned.
Use the STAR method to describe a project where you exceeded expectations, focusing on the specific actions you took beyond your assigned tasks and the measurable impact on stakeholders and product metrics. Emphasize how your initiative aligned with team or company goals and the recognition you received.
Pro tip: Quantify the impact of your extra effort using metrics that matter to Google, such as user engagement, latency improvements, or cost savings, and highlight how you influenced cross-functional stakeholders without formal authority.
Briefly describe the project, your role, and what was initially expected of you, ensuring the scope is clear and relevant to the role.
Explain the additional opportunity or problem you noticed that was beyond your assigned responsibilities, and why you decided to act on it.
Detail the specific steps you took to deliver beyond expectations, including any collaboration, innovation, or extra effort involved.
Explain how you communicated with stakeholders, gained buy-in, and managed expectations throughout the process.
Present the measurable results of your extra work, using product analytics or metrics to show the value delivered to users and the business.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.
This is the one I'd prep hardest for next time.
Choose a real, non-trivial technical mistake where you had clear ownership, then structure your answer to show self-awareness, accountability, and a concrete change in how you work. Keep the focus on the learning and the improved outcome, not on blaming others or the process.
Pro tip: Pick a mistake that is meaningful but not disqualifying, and explicitly name the systemic fix you made so it can't happen again—Google values engineers who turn failures into durable improvements.
Describe the project, your role, and the goal in 1–2 sentences so the interviewer understands the stakes without unnecessary detail.
State exactly what you did wrong and your responsibility, avoiding passive language or blaming teammates, timelines, or tools.
Summarize the consequences and how you detected, communicated, and helped fix the issue, showing calm problem-solving under pressure.
Articulate the specific insight you gained about your technical judgment, process, or communication.
Describe the concrete action you took afterward—such as a new testing practice, design review, or checklist—and how it improved later work.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.
Talked about a project where the requirements kept shifting and nobody really owned the spec.
Use the STAR method to describe a specific project where requirements were unclear or conflicting. Focus on the concrete actions you took to break down the ambiguity, such as asking clarifying questions, prototyping, or defining assumptions. Highlight how you communicated with stakeholders to align on a path forward and the measurable outcome.
Pro tip: Emphasize that you proactively documented assumptions and shared them with stakeholders to get early feedback, rather than waiting for perfect information. This shows initiative and reduces risk in ambiguous situations.
Briefly describe the project and why it was ambiguous (e.g., unclear requirements, shifting priorities, or missing information).
Explain the specific uncertainties you faced and how they impacted your work or the team's progress.
Detail the steps you took to bring clarity, such as researching, consulting experts, creating prototypes, or facilitating discussions.
Describe how you communicated your findings and assumptions to stakeholders to ensure everyone was on the same page.
Share the outcome: how your actions resolved the ambiguity, delivered value, and what you learned for future situations.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.