How to Answer "Tell Me About a Difficult Colleague"

This question, and its variations about conflict and disagreement, is one of the most revealing in any interview. It is not really asking about the other person at all.

The interviewer wants to know how you behave when something goes wrong between you and someone you cannot simply avoid. That is a daily reality in any job, and your answer tells them what you will be like when it happens on their team.

The Trap

The obvious trap is criticising the colleague. Candidates walk into it because the question appears to invite it, and because a genuinely difficult person is easy to describe.

The moment you start listing someone else’s faults, the interviewer stops hearing a story about workplace resolution and starts hearing how you will talk about them in eighteen months. It is one of the fastest ways to lose an interview.

The second trap is the opposite: claiming you have never had a difficult relationship with anyone. Nobody believes it, and it reads as either evasion or a lack of self-awareness.

Choose the Example Carefully

The right example has four features.

It was a professional disagreement rather than a personal clash. Different priorities, different working styles, a dispute over an approach, or a handover that kept failing.

You had some agency in it. A story where a senior person behaved badly and you simply endured it does not show anything you did.

It was resolved, or at least improved. You do not need a heartwarming ending, but you need to have moved it somewhere.

It is old enough to be safe. Something from your current team last month is uncomfortable for everyone, and it makes the interviewer wonder whether the situation is really over.

Good territory includes a colleague who worked to a very different standard of detail, someone whose deadlines kept slipping into yours, a peer who resisted a change you were implementing, or a stakeholder who kept going around an agreed process.

Structure It

Use the same shape you would use for any behavioural question. Set the scene briefly, describe the specific problem in terms of impact rather than personality, explain what you did, and give the outcome.

The impact framing is the key move. Instead of describing someone as disorganised, describe that reports were arriving after the deadline and that this pushed your team’s work into evenings. The first is a judgement about a person. The second is a fact about work, and it lets you tell the whole story without ever criticising anyone.

If you have not used it before, our guide on the STAR method sets out the structure properly.

Spend the Most Time on What You Did

This is where the marks are, and where most answers are thinnest.

Strong actions to describe include going to the person directly and privately before escalating, asking questions to understand their pressures before assuming, proposing a specific change to how you worked together, agreeing something concrete, and following up to check it held.

Weak actions include going straight to a manager, sending a passive email chain, complaining to other colleagues, or waiting for it to resolve itself.

Interviewers particularly like hearing that you found out something you had not known. Discovering the other person was being pulled in a direction you could not see turns the story from a conflict into a piece of problem solving, and it demonstrates that you check your assumptions.

Show Some Self-Awareness

An answer where you were entirely right and handled it perfectly is less convincing than one where you acknowledge a small part you played.

Something as simple as recognising that you had assumed bad intent, or that you had let it run for too long before addressing it, adds enormous credibility. It signals that you can reflect, and that you are not going to be the person who is never wrong.

Keep it proportionate. One honest sentence, not a confession.

The Outcome Does Not Have to Be a Friendship

Not every difficult relationship becomes a warm one, and pretending otherwise sounds false.

A perfectly good outcome is that you found a workable arrangement, that the work stopped being affected, and that you continued to deal with each other professionally. That is what actually happens most of the time, and interviewers recognise it as real.

If the situation genuinely was not resolved, you can still use it, provided you can say what you learned and what you would do differently. That version needs to be told carefully, so only use it if you have a stronger reflection to offer than resolution.

Variations to Prepare For

The same preparation covers several questions: a time you disagreed with your manager, a time you had to work with someone you did not get on with, a time you had to give difficult feedback, and how you handle conflict in a team.

One well chosen story usually stretches across most of them with a change of emphasis. Prepare two so you are not repeating yourself if more than one comes up, which they often do. Our guide on competency-based interview questions covers how these clusters tend to be structured.

The One Line to Remember

Talk about the problem, not the person. Everything else in the answer follows from getting that right.