0Describe a Time You Received Harsh Feedback and How You Responded - Google STAR Walkthrough
In this scenario, the candidate received tough feedback about latency spikes caused by their code outside their team’s ownership. They explicitly stated the scope boundary, took initiative to investigate and fix the issue, and quantified the impact as zero latency spikes and $8K weekly revenue recovered. The reflection identified organizational gaps in cross-team reliability SLOs. Key takeaways: clear ownership beyond assigned scope, measurable impact, and deep self-awareness with systemic insight.
Keep the situation concise and focused on the feedback and cross-team context. Avoid lengthy system architecture explanations that lose interviewer interest.
Spending 90 seconds on system architecture before reaching the problem - interviewer loses interest.
Explicitly state the scope boundary to prove ownership. This clarifies you acted beyond assigned responsibilities.
Jumping to investigation without stating scope boundary; ownership proof is absent.
Use 'I' for every sentence to clearly show your individual contribution. Avoid 'we' to prevent diluting ownership.
Using 'we' language such as 'we figured out the root cause together' makes individual contribution invisible.
Include metric delta, business impact, and second-order effect to demonstrate full impact.
Ending with 'things got better and team was happy' - no quantification or business translation.
Provide specific, story-related insights rather than generic statements about communication.
Saying 'I learned communication is important' - too generic and uninformative.
"I did escalate it - I sent them a Slack message and they handled it."
Sending Slack = routing responsibility, not ownership. Confirms candidate handed off the problem.
"I flagged the issue to their tech lead for visibility but brought a complete fix with tests and monitoring alerts. Escalating without a solution would have added weeks at their sprint velocity."
"My manager suggested I look into this since I had bandwidth."
Delegating initiative to manager removes candidate’s ownership and growth signal.
"I received tough feedback directly from the Platform team’s code reviewer about latency spikes caused by my code. I reflected deeply on the root cause and took initiative to fix it without waiting for assignment."
"The bug was fixed and the rate improved. Team was happy."
No metric delta or business translation; vague impact.
"I tracked latency spike rate dropping from 0.3% to zero, which translated to recovering $8K in weekly lost revenue. Additionally, the Platform team adopted my alerting pattern, improving long-term reliability."
"I learned communication is important."
Generic reflection that applies to any story; lacks specificity.
"In retrospect, I would propose shared webhook reliability SLOs earlier to improve cross-team visibility, addressing the organizational gap that caused delayed detection."
- I escalated it by sending a Slack message
- They handled the fix
- The latency improved and the team was happy
- No explicit scope boundary stated
- No quantified impact or personal ownership
Lead with how you received and processed tough feedback, emphasizing your learning and improvement.
Reflection on feedback, specific actions taken to improve, and measurable outcomes.
Technical details unrelated to personal growth or feedback.
Focus on taking initiative beyond your team boundaries and driving the fix end-to-end.
Explicit scope boundary, individual actions, and proactive solution delivery.
Team collaboration or vague 'we' statements.
Highlight quick identification, rapid investigation, and timely fix deployment despite no ticket or assignment.
Speed of response, minimal viable fix, and alerting to prevent recurrence.
Lengthy analysis or waiting for approvals.
Focus on technical learning from feedback, clear individual actions, and basic impact metrics.
Adds organizational thinking, trade-off articulation, and systemic insight beyond code.