Conflict Interview Questions: How to Answer (With STAR Examples)

"Tell me about a time you disagreed with a colleague." "Describe a conflict at work and how you handled it." "Have you ever had to deal with a difficult customer?"

These questions come up in almost every competency-based interview in the UK, and the weakest possible answer is "I don't really have conflicts." Nobody believes it, and it suggests you either avoid problems or haven't noticed them.

The interviewer isn't looking for someone who has never disagreed with anyone. They want evidence that you can disagree well: calmly, professionally and in a way that leaves the work, and the relationship, in better shape.

---

What the interviewer is assessing

Conflict questions are a shortcut to several competencies at once. In two minutes, the panel learns how you behave under pressure.

• Do you stay calm and professional?
• Do you listen and try to understand the other side?
• Do you focus on the problem, not the person?
• Can you reach a resolution, or at least a workable compromise?
• Do you reflect and learn?

Look at the job advert and person specification before the interview. If they mention "stakeholder management", "influencing" or "customer service", pick a conflict story that shows exactly that. CVPilot's keyword extractor will pull those competencies out of an advert in seconds.

Key Takeaway: A conflict question is really a question about judgement, listening and influence. Choose a story that proves the competencies the role asks for.

---

The many versions of the question

Interviewers phrase conflict questions in different ways, but they are usually testing one of four scenarios. Have a story ready for each.

How it's asked	What they're really testing	Best type of story
"Tell me about a time you disagreed with a colleague"	Peer collaboration	A disagreement about approach, resolved with evidence
"Describe a time you challenged a decision"	Courage and respect for authority	Raising a risk with a manager, with a solution
"How have you handled a difficult customer?"	Composure and service	Calming an upset customer and fixing the cause
"Tell me about a time a teammate wasn't pulling their weight"	Directness and fairness	A private, supportive conversation that changed things

Key Takeaway: Prepare four short stories, one for each scenario, and you can answer almost any conflict question without improvising.

---

Use the STAR structure

1. Situation: brief context
2. Task: what was at stake or what you needed to achieve
3. Action: what you did (the longest part)
4. Result: the outcome, and what you learnt

Spend most of your time on the action. That's where the interviewer sees your behaviour. As a rough guide, keep situation and task to a couple of sentences each.

Use "I", not "we", when describing actions. The panel is scoring you, not your team, and they can't give you credit for something they can't attribute to you.

Key Takeaway: Pick a conflict about work, not personalities, and make sure you come out of it as the person who helped resolve it.

---

Example 1: Disagreeing with a colleague

Situation: In my last role, a colleague and I were jointly planning a customer email campaign. We disagreed on timing: he wanted to send it before a bank holiday, and I thought engagement would be low.

Task: We needed to agree a plan by the end of the week so the design team could start.

Action: Rather than debating it in the team chat, I suggested we sit down for 20 minutes. I asked him to talk me through his reasoning first, which was about getting ahead of a competitor promotion. I shared open-rate data from our previous bank holiday sends. We agreed to split the list and send half before and half after, so we could compare.

Result: The post-holiday send had a noticeably higher open rate, and we used that result to plan future campaigns. More importantly, we agreed to test disagreements like that with data in future, which made working together easier.

Why it works: the candidate listens first, moves the conversation off a public channel and turns a clash of opinions into a test. Nobody "wins", and the team learns something.

Key Takeaway: With a peer, show that you asked for their reasoning before arguing your own, and that you used evidence rather than persistence.

---

Example 2: Disagreeing with your manager

Situation: My manager asked me to cut the testing phase of a website update to meet a launch date.

Task: I was worried a checkout bug would reach customers, but it was his decision to make.

Action: I asked for ten minutes with him and explained the specific risk, with the list of untested payment scenarios. I suggested a compromise: launch on time, but test the checkout journey first and delay two lower-risk pages by a week.

Result: He agreed. Testing found a payment error that would have affected some customers, and it was fixed before launch. I learnt that it's much easier to disagree with someone senior when you bring a specific risk and a solution rather than just an objection.

Why it works: the candidate respects that the decision belongs to the manager, but makes it easy to say yes by offering a practical compromise.

Key Takeaway: When you challenge someone senior, bring a specific risk and a workable alternative. An objection on its own sounds like resistance.

---

Example 3: A difficult customer

Situation: While working at a hotel reception, a guest arrived to find their room booking had been lost and the hotel was full.

Task: They were angry and tired, and I needed to find a solution quickly.

Action: I apologised, listened without interrupting and kept my tone calm. I checked our booking system to understand what had happened, then called two nearby hotels and found a room. With my manager's approval, I arranged a taxi and offered a discount on a future stay.

Result: The guest thanked me and later left a review mentioning how the problem was handled. I also flagged the booking error so it could be investigated.

Why it works: it shows composure, ownership and the right level of authority. The last line matters most: fixing the cause, not just the complaint, is what separates a good answer from a great one.

Key Takeaway: For customer conflicts, show empathy first, then action, then a fix that stops it happening again.

---

Example 4: A teammate not pulling their weight

This one works well if you have little work experience, because it happens in every group project.

Situation: In my final year, I was one of four students on a group research project worth a third of the module. One member had missed two meetings and hadn't started his section.

Task: We had three weeks left, and I was coordinating the timeline.

Action: Instead of raising it in the group chat, I messaged him privately and asked if everything was okay. It turned out he was working extra shifts and felt too far behind to catch up. We agreed he would take a smaller, clearly defined section, and I moved our meetings to a time he could attend.

Result: He delivered his section on time, and we submitted a complete project. I learnt that what looks like laziness is often a problem you can't see, and asking privately gets you much further than calling someone out.

Key Takeaway: Group projects, societies, sports teams and part-time jobs all make valid conflict examples. The behaviour matters more than the setting.

---

Mistakes to avoid

Mistake	Why it hurts
"I don't really have conflicts"	Sounds evasive or inexperienced
Blaming the other person	Makes you sound difficult
A conflict you "won"	They want resolution, not victory
A very personal or heated story	Raises more questions than it answers
Escalating straight to HR or a manager	Suggests you can't handle things directly
No result or reflection	Misses the part that shows growth

Also be ready for follow-up questions such as "What would you do differently?" or "How is your relationship with that person now?" A calm, honest answer to either one strengthens the whole story.

Key Takeaway: Keep the other person's dignity intact in your story. If they come across badly, so do you.

---

Build a story bank, then apply

You don't need a new story for every interview. Four or five strong examples can be adapted to most competency questions. Our guide to building a career story bank shows how, and our UK competency interview questions guide covers the other common themes.

Of course, you need the interview first. Before you apply, check your CV against the advert with CVPilot's free ATS checker so it gets past the first screen.

Ready to optimise your CV? Try CVPilot free and see your ATS score in under 60 seconds.