The second part is where I think most people stumble and I almost did too.
Use the STAR method to describe a specific disagreement, focusing on how you raised it with data and respect, and then how you committed to the final decision. Emphasize Amazon's Leadership Principles like 'Have Backbone; Disagree and Commit' and 'Customer Obsession' by linking your reasoning to customer impact and team goals.
Pro tip: Show that you can disagree without being disagreeable: highlight that you listened to opposing views, sought to understand their perspective, and ultimately prioritized the team's success over being right.
Briefly describe the situation, your role, and the decision you disagreed with, making sure it's relevant to software engineering and Amazon's values.
Articulate why you disagreed, focusing on data, customer impact, or technical reasoning, and how you respectfully raised your concerns to your manager or team.
Explain how the decision was ultimately made, whether your input was incorporated or not, and how you accepted the outcome professionally.
Detail the actions you took to support the final decision, such as advocating for it, helping with implementation, and ensuring team alignment.
Summarize the results, what you learned, and how it strengthened your ability to balance conviction with adaptability.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.