Describe a time you received critical, tough, or unexpected feedback. How did you process and apply it?

In Simple Words: Demonstrate growth mindset: avoid defensiveness, listen deeply, ask clarifying questions, and show concrete behavior modification.

The STAR Response:

• Situation: During a mid-year performance review, my engineering manager shared that while my technical output was outstanding, my code review feedback was coming across as overly blunt and discouraging to newer team members.
• Task: Shift my communication style to become an empowering, constructive technical mentor without compromising our high code quality standards.
• Action:
  1. Thanked my manager for the honest feedback and asked for specific PR examples to analyze my tone objectively.
  2. Realized I was writing curt comments like "This is inefficient, rewrite using a Map" without explaining the context or offering positive reinforcement.
  3. Adopted Google's Conventional Comments standard: prefixing comments with clear intent labels (praise:, suggestion:, question:, nit:) and explaining the 'Why' behind performance considerations.
  4. Started scheduling 15-minute pairing sessions to walk through complex architectural feedback face-to-face.
• Result: In my next review, peer feedback scores for collaboration jumped from 3.2 to 4.9/5.0, and two junior engineers explicitly cited my PR reviews as the most helpful learning experience on the team.

Practical Script & Summary Template

### Conventional Comments Transformation:
- **Before**: "This will cause an N+1 query. Fix it."
- **After**: "suggestion: Because this loop calls fetchUser() inside each iteration, it issues N individual network queries. Could we pre-fetch all users with a single WHERE id IN (...) query? Here is a quick example of how that looks in our repo..."