Working With a Difficult Teammate or Making a Difficult Decision
Company: Amazon
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Onsite
In a fully behavioral round built around the company's leadership principles, the interviewer asked for a past experience of either dealing with a difficult teammate or making a difficult decision. The report does not say which of the two was asked, so this practice version asks both.
Answer each Part with one real situation from your own experience, and expect the interviewer to probe the details of each story.
### Clarifying Questions
- Does a "difficult teammate" have to be on my own team, or does an engineer on a partner team, or a stakeholder, count?
- For the difficult decision, should it be a decision I made myself, or can it be one where I shaped someone else's call?
- Is a story from an internship or a school project acceptable if it is my strongest example?
### Part 1 — A difficult teammate
> Tell me about a time you had to deal with a difficult teammate. What made it difficult, what did you do, and how did it turn out?
```hint Describe behavior, not character
Pick a situation where the friction affected the work, and describe what the person did rather than what kind of person they were. The interviewer is listening for how fair you are.
```
```hint Show your own part
Include what you did to understand their side before acting, and anything you would change about your own behavior.
```
#### What This Part Should Cover
- A concrete conflict with a cost to the work, described through behavior rather than personality
- How the candidate sought the other person's perspective and addressed the issue directly
- The candidate's actions and the outcome for both the work and the working relationship
- Reflection, including the candidate's own share of the friction
### Part 2 — A difficult decision
> Tell me about a time you had to make a difficult decision. Why was it difficult, how did you decide, and what happened?
```hint Make the difficulty real
Choose a decision with a genuine trade-off, incomplete information or a cost to someone, not one where the right answer was obvious.
```
```hint Show the reasoning
Walk through the options you weighed, the data you had and lacked, and how you limited the damage if you turned out to be wrong.
```
#### What This Part Should Cover
- Why the decision was hard: competing goals, incomplete data, time pressure or a cost to someone
- The options considered, the criteria used, and how risk was limited
- Ownership of the decision and its consequences, including how disagreement was handled
- The outcome and what the candidate learned about making decisions
### What a Strong Answer Covers
- Two distinct, specific stories rather than one story stretched to fit both prompts
- The candidate's own actions, told with "I" rather than "we", with evidence behind each claim
- Measurable outcomes and an honest account of what did not go well
- Judgment about when to resolve things directly, when to escalate, and how to commit once a decision is made
- Concise delivery with enough real detail to hold up under follow-up probing
### Follow-up Questions
- If we asked that teammate about that period, what would they say about you?
- With the same information, would you make the same decision again? What would change your mind?
- When did you escalate, and why not earlier or later?
- How did you communicate the decision to the people who disagreed with it?
Overview: A behavioral interview question asking for a real experience of either working with a difficult teammate or making a difficult decision. It tests how a candidate handles conflict fairly, reasons through trade-offs under uncertainty, owns the outcome and reflects on what they would change.
Read the full Amazon Software Engineer interview experience this question came from