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

Intermediate

Apr 2026

Summary

Behavioral round at Amazon for a software engineer role, basically one question that took up most of the time. The whole thing revolved around how you handle criticism, which sounds easy until you're actually sitting there trying to remember a specific enough story that doesn't make you look defensive.

Questions Asked (1)

Tell me about a time you received critical or negative feedback. Walk through the context, your initial reaction, what you did with it, and how it changed your work or relationships going forward.

Adaptability & AmbiguityConflict Resolution

Author's notes

I had a story ready but I fumbled the 'initial reaction' part.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a specific instance of critical feedback that led to genuine growth, and narrate it using the STAR method, emphasizing your initial emotional reaction, the concrete actions you took to improve, and the measurable impact on your work and relationships. Show self-awareness and a learning mindset, and connect the experience to Amazon's Leadership Principles like 'Learn and Be Curious' and 'Earn Trust'.

Pro tip: Be candid about your initial defensiveness or frustration—it makes you relatable—but pivot quickly to how you processed it and turned it into a strength. Avoid choosing feedback that reveals a core skill gap for the role; instead, pick something that shows you can grow from any critique.

1. Set the Context

Briefly describe the project, your role, and the source of the feedback (e.g., a peer, manager, or code review). Provide enough detail to make the situation clear but stay concise.

2. Share Your Initial Reaction

Honestly express your first emotional response—surprise, defensiveness, or disappointment—and how you managed it. This shows self-awareness and emotional intelligence.

3. Describe Your Actions

Explain the concrete steps you took to understand and act on the feedback: seeking clarification, reflecting, creating an improvement plan, and applying changes.

4. Highlight the Outcome

Quantify the results: improved code quality, faster delivery, better team collaboration, or stronger relationships. Use metrics if possible.

5. Reflect on Long-Term Change

Summarize how this experience changed your approach to work or relationships going forward, and tie it to a broader lesson or Amazon Leadership Principle.

Key Points to Mention

Specific, constructive feedback (e.g., on code quality, communication, or design approach) that you initially resisted but ultimately embraced.
Your initial emotional reaction and how you regulated it—showing vulnerability and growth.
The concrete actions you took: asking for examples, seeking mentorship, practicing new habits, or adjusting your workflow.
Measurable improvements in your work (e.g., reduced bug count, faster review times, higher customer satisfaction).
Positive impact on relationships: increased trust, better collaboration, or more open communication with the feedback giver.
A lasting change in your mindset or process, such as proactively seeking feedback or adopting a growth mindset.

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