The short answer
Pick a real, work-related disagreement that ended well, and tell it with STAR. Keep the situation brief and neutral, spend most of your answer on what you did to understand the other person and find a solution, and close with the outcome and what changed in how you work together. Never make your teammate the villain.
Hear the question
Read aloud with the voice from the app's practice mode.
Transcript: Describe a time when you had a conflict with a team member. How did you resolve it?
Key takeaways
- Choose a genuine disagreement about work, not a personality clash.
- Describe the other person fairly; interviewers judge you by how you talk about them.
- Put most of the answer into your actions: listening, clarifying, proposing a way forward.
- End with a business result and a better working relationship.
- Avoid stories where a manager had to step in and settle it for you.
To answer “Describe a conflict with a team member,” tell a short STAR story about a real work disagreement: set up the situation neutrally, show what you did to understand the other person and find a solution, and end with a good result for the work and the relationship. The way you describe your teammate matters as much as the resolution.
Why do interviewers ask about conflict?
This is a classic behavioral question. The U.S. Office of Personnel Management describes structured interviews as asking candidates systematically about their behavior in past experiences. Your conflict story is the interviewer’s evidence of how you will handle the next one.
For conflict specifically, the interviewer is looking for:
- Directness. Do you raise problems early, or let them fester?
- Empathy. Can you state the other side’s view fairly?
- Judgment. Do you focus on the work outcome rather than on winning?
How should you structure your answer?
Use the STAR method: Situation, Task, Action, Result. MIT’s career office suggests a rough split of about 20% situation, 10% task, 60% action and 10% result. For conflict questions that 60% is essential, because the action is where you show how you handle people.
- Situation. Who, what project, and what you disagreed about. Two sentences.
- Task. What was at stake and what you needed to achieve.
- Action. The conversation you started, the questions you asked, the compromise or evidence you brought.
- Result. The outcome for the work and for the relationship.
Weak vs strong answers
“I had a coworker who never pulled his weight. I tried to ignore it, but eventually I told our manager, and she moved him to another project. After that things were much better.”
Why it falls flat: Blames the coworker, avoids the conflict and hands resolution to the manager.
“A teammate and I disagreed about whether to launch a report with partial data. I thought we should wait; he thought the sales team needed something now. I asked what sales would actually use it for, and it turned out they only needed two of the eight metrics. We shipped those two with a clear 'partial data' note and the full report a week later. Sales got what they needed on time, and he and I started checking requirements together at kickoff.”
Why it works: A real disagreement, a curious question that uncovered the actual need, a practical compromise and a lasting change.
What does each AI interviewer probe?
Offermic’s AI interviewers are simulated personas, not real people. Conflict answers tend to draw these follow-ups:
Sarah may follow up with: “How did you feel during that conversation, and how did you keep it from getting personal?”
Emily may follow up with: “What would your teammate say about how you handled it?”
Michael may follow up with: “Looking back, is there anything you would do earlier to prevent that conflict from happening at all?”
How does the answer change by industry?
| Industry | Common conflict to use | What to emphasize |
|---|---|---|
| Healthcare | Handoffs, workload, care decisions | Patient safety as the shared goal |
| Tech | Technical approach, scope vs quality | Data and trade-offs, not opinions |
| Sales | Territory or account ownership | Customer outcome and fairness |
| Retail | Shift coverage, task division | Fairness and the customer experience |
Related questions
- Tell me about a time you worked with a difficult coworker is a longer-term version of this story.
- Describe a time you disagreed with your boss raises the stakes.
- Describe a time you persuaded someone uses similar skills.
Example answers by experience level
Examples written for this page, not real candidates.
Situation
During my internship, another intern and I were co-writing a product launch email. She wanted a long, detailed version; I thought it should be short with one call to action.
Task
We had two days to hand our manager one draft, and we were going in circles.
Action
I asked her to walk me through why she wanted the detail. It turned out customers had complained that past emails left out pricing. I suggested we keep it short but add a clear pricing line and link to a full FAQ, and that we A/B test the subject line to settle the rest with data.
Result
Our manager approved the combined draft the same day. It had one of the higher click rates of the quarter, and we kept testing together for the rest of the internship.
Illustrative example written for this page, not a real candidate.
Situation
A colleague on nights and I disagreed about handoff. I found her reports rushed; she felt I asked for too much detail at 7 a.m. after a 12-hour shift.
Task
Handoffs were getting tense, and I worried something important would get missed.
Action
I asked to talk before a shift instead of at handoff. I admitted my questions came late and piled up, and she admitted she skipped items when tired. We agreed to use our unit's written handoff tool for every patient, and I would hold questions until the end.
Result
Handoffs got shorter and more complete. Our manager later asked us to demo the approach at a staff meeting.
Illustrative example written for this page, not a real candidate.
Situation
Our engineering lead wanted to pause features for a quarter to pay down technical debt. I had committed a feature to a large customer for that same quarter.
Task
We needed one plan that leadership could approve, without either of us overruling the other.
Action
I asked him to list the debt items by the incidents they had caused. We found that two of them were slowing down the exact feature I had promised. We proposed doing those two first, then the feature, and pushing the rest of the debt work into the following quarter, and presented it together.
Result
Leadership approved the joint plan. The feature shipped three weeks later than planned but with fewer bugs, and we kept planning the roadmap together after that.
Illustrative example written for this page, not a real candidate.
Do this
- Pick a conflict about something that mattered to the work, like priorities, quality or deadlines.
- Say what the other person wanted and why, in terms they would agree with.
- Show a specific conversation or step, not just 'we talked it out'.
- Finish with the outcome and how the relationship went afterward.
Avoid this
- Blaming or mocking the teammate.
- Choosing a trivial clash that shows nothing, such as office temperature.
- Saying you avoided the conflict and it went away.
- Escalating to the manager as your first move.
Other ways it gets asked
- “Tell me about a disagreement with a coworker.”
- “Give an example of a time you disagreed with a colleague's approach.”
- “How do you handle conflict on a team?”
Questions people also ask
What if I have never had a conflict at work?
Almost everyone has had a disagreement over priorities, approach or deadlines. It does not need to be dramatic. A difference of opinion about how to run a project counts.
Can I use a conflict from school or volunteering?
Yes, especially early in your career. Group projects and volunteer teams produce real conflicts. Just make it clear what role you played.
Should the conflict be resolved in my favor?
Not necessarily. A story where you changed your mind after hearing the other side can be stronger, because it shows you listen.
Sources
- Using the STAR method for your next behavioral interview, MIT Career Advising & Professional Development
- Structured Interviews, U.S. Office of Personnel Management
Written byCan Garip, Founder
Can Garip is the founder and developer of this app. He builds the AI mock interview product and writes its interview preparation guides.
Drafted with AI assistance, then edited and fact-checked by the author.