How do you handle conflict at work in an interview answer

Describe the disagreement from both seats. Say what the other person wanted, what they thought you were doing wrong, and what you conceded. An answer where you were reasonable throughout and the other person came around reads as a story you have never examined, and the follow-up will find that in one question.

What is the best answer to how do you handle conflict

There is no template that beats specificity here. Pick a conflict you partly caused, name your contribution before you name theirs, and finish with the working agreement you both changed. Owning one concrete failure early buys more credibility than a flawless resolution narrative.

Should I pick a conflict that was resolved

Pick one that changed how the two of you worked, which is not the same as one that ended in agreement. Interviewers are fine with unresolved disagreements that produced a functioning process. What they distrust is a conflict that ended with the other person simply seeing your point.

Tell Me About a Conflict With a Coworker (Examples)

Why interviewers ask this

When an interviewer says tell me about a time you had a conflict with a coworker, they are not listening for the conflict. They are listening for whether the other person exists. Recruiters phrase the same test as how do you handle conflict. Same test, different words. Almost every answer arrives with one reasonable narrator and one obstacle who was late, or territorial, or bad at communicating. The narrator is invariably the one who called the meeting that fixed it, and the obstacle is invariably the one who came around. What the interviewer wants to know is whether you have ever seriously considered that the person across from you had a version of events in which you were the problem. Most people have not. That capacity is the whole difference between someone who resolves friction on a team and someone who quietly relocates it to the next team, and it is very hard to fake in the second question.

An answer that sounds fine

I was running a campaign launch that depended on assets from one of our designers, and he kept missing the handoff dates we had agreed. It started to put the launch at risk, so rather than let it fester I asked him for a coffee and we talked it through properly. It turned out he was getting pulled onto another project by a different stakeholder and had never flagged it. We set up a short weekly sync so we could both see what was landing when, and I made sure to give him more notice on upcoming requests. The launch went out four days late instead of three weeks. We worked really well together after that, and honestly the relationship ended up stronger than before.

Where it breaks

That is a competent story, told fluently, and it is missing exactly one thing. The designer never says anything. He is described entirely from the outside, by his behaviour and by his effect on the timeline. The one line of interior life he gets is that he was being pulled onto another project. Even that arrives as an excuse the narrator has generously accepted, rather than as a reason that moves some of the fault back across the table. Notice that the resolution is also unilateral: she asked for the coffee, she set up the sync, she gave more notice. In a story about two people, one of them has no agency and no complaint. Anyone answering an interview question about conflict this way has answered how do you handle conflict at work without meaning to, and the answer is by managing the other person rather than negotiating with them. The coffee, the sync, the extra notice, all of it is administration applied to a colleague who never got asked what he wanted.

The follow-up

What did the other person think you did wrong?

Honestly, that is a good question. I think he probably felt I went to my manager about the delays before I came to him directly, which, fair, I did do that. And he said something once about the brief changing twice after he had started, which I had sort of filed under normal campaign stuff. I had not really thought about it from his side until just now.

Everything useful in this conversation is in the last sentence, and it took a direct question to produce it. She had gone above him before speaking to him, and she had changed the brief mid-build. Both are ordinary working failures that a hiring manager would forgive instantly, and neither of them survived into the prepared version, which is the detail worth sitting with. The prepared version was not dishonest. It was assembled from one seat, and a story assembled from one seat tells an interviewer precisely how the next disagreement on their team will get narrated to whoever is in the room afterwards. That is the thing being bought or declined in this question.

An answer that holds up

A designer on my campaign launch missed three handoff dates and I escalated to my manager before I had spoken to him about it directly, which I would not do again. When we finally talked, two things came out. He had been pulled onto another project by a different stakeholder, and I had changed the creative brief twice after he had started building, so from where he sat I was the source of the churn and then I complained about the speed. We agreed he would flag competing requests the day they arrived and I would freeze the brief once build started. Launch went four days late rather than the three weeks it was heading for. The part I actually took from it is that I escalate too early, and I now go to the person first even when the deadline makes that feel expensive.

The interviewer asks what the designer thought she did wrong.

That I went to my manager before I went to him, and that I kept changing the brief after he had started. He was right about both. The first one is the one I had to work on, because escalating felt efficient to me and felt like being reported on to him.

Practice this question

Say your answer to this question out loud, then get asked what the other person thought you did wrong. Answer it now, free, no account.

Tell Me About a Conflict With a Coworker