Google·Software Engineer·Onsite - Behavioral / Leadership·Intermediate

IntermediatePrefer not to say

Apr 2026

Summary

Behavioral round at Google for a software engineering role. Just one question but it had a lot of moving parts and I felt like I was rambling by the end.

Questions Asked (1)

Tell me about a time you genuinely listened to someone else (a teammate, customer, or stakeholder) and actually changed your approach based on what they said. Walk through the context, how you made sure you understood them, what you did differently, and what happened.

Conflict ResolutionStakeholder ManagementAdaptability & Ambiguity

Author's notes

I had a decent story ready about a disagreement with a PM over scoping, but I kept second-guessing whether it was specific enough.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a specific instance where you actively listened to a teammate, customer, or stakeholder and adjusted your technical approach as a result. Use the STAR method to structure your answer, emphasizing how you ensured understanding and the positive outcome of the change. Highlight your humility, adaptability, and focus on collaboration.

Pro tip: Show that you not only listened but also validated the other person's perspective by asking clarifying questions and summarizing their points. Then, explicitly connect how their input led to a better technical decision or outcome, demonstrating impact.

1. Set the Context

Briefly describe the project, your role, and the situation that required listening to someone else's perspective. Mention the stakeholder and why their input mattered.

2. Demonstrate Active Listening

Explain how you made sure you understood them: ask clarifying questions, paraphrase their points, and acknowledge their concerns. Show that you were open-minded.

3. Describe the Change

Detail what you did differently based on their feedback. Be specific about the technical or process change and why it was a shift from your original approach.

4. Highlight the Outcome

Share the results: improved performance, better team dynamics, customer satisfaction, etc. Quantify if possible and reflect on what you learned.

5. Reflect and Connect to Google

Summarize the lesson learned and how it aligns with Google's values, such as user focus, collaboration, or innovation. Show how this experience makes you a better engineer.

Key Points to Mention

Active listening techniques: asking open-ended questions, paraphrasing, and summarizing to confirm understanding.
Humility and openness to feedback, even when it challenges your initial technical approach.
Specific change made: e.g., altering architecture, adopting a new tool, or adjusting communication style.
Positive outcome: e.g., increased efficiency, resolved conflict, improved user experience, or met stakeholder needs.
Alignment with Google's culture: user focus, collaboration, and data-driven decision making.
Learning and growth: how this experience improved your ability to work with others and adapt in ambiguous situations.

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