Tell Me About a Time You Worked With a Difficult Coworker
What interviewers are really scoring, a 6-step framework built for conflict answers, and five complete sample answers you can adapt to your own experience.
Why Interviewers Ask This Question
Almost every job involves working with someone whose style, standards or priorities clash with yours. Interviewers know this, and they know that how a candidate handles that friction is a far better predictor of day-to-day performance than any claim about being a "great team player". That is why "tell me about a time you worked with a difficult coworker" appears in graduate schemes, retail and hospitality interviews, NHS values-based panels and senior management hiring alike.
The question is deliberately uncomfortable. It invites you to criticise someone, and a surprising number of candidates take that invitation — which is exactly the trap. Interviewers are not interested in whether your colleague was genuinely difficult. They are interested in what you did about it, and in what the story reveals about how you will behave when a future colleague frustrates you.
Behavioural questions like this are scored against a defined competency framework. In a structured competency-based interview, the interviewer has a scoring sheet with behavioural indicators and will tick positive and negative evidence as you speak. For this question, four things are being scored:
- Ownership. Did you take responsibility for improving the situation, or did you wait for someone else — a manager, HR, the colleague themselves — to fix it? Strong answers show the candidate acting first.
- Emotional control. Can you describe the person fairly, without contempt or sarcasm, months or years later? Interviewers read your tone as a live sample of your professionalism, not just a report on a past event.
- Communication. Did you have a direct, respectful conversation with the person, or did you talk about them to everyone except them? The direct conversation is the single most important behaviour in this answer.
- Outcome and learning. Did the working relationship actually improve, and did you change anything in how you work as a result? An answer with no outcome reads as an unresolved grudge.
Every hiring manager has had to manage a team member who created friction and then described themselves as the reasonable one. This question is partly a screen for that risk. A candidate who shows genuine empathy for the other person's position — workload, pressure, a different definition of "done" — is far more reassuring than one who presents themselves as the blameless victim of an impossible colleague.
Question Variants and What Each One Is Really Probing
This question is asked in several wordings, and the wording matters. Each variant emphasises a slightly different competency, so the same core story needs its emphasis shifted. Listen carefully to the exact phrasing before you launch into your prepared example.
| Variant wording | Underlying competency | What to emphasise | Trap to avoid |
|---|---|---|---|
| "Tell me about a time you worked with a difficult coworker." | Interpersonal resilience | Your initiative in addressing it and the restored working relationship | Spending half the answer proving the person was difficult |
| "Tell me about a conflict you had at work and how you resolved it." | Conflict resolution | The specific resolution steps and the agreement you reached | Describing a disagreement that was never actually resolved |
| "Describe someone you found hard to get along with." | Self-awareness | Your own contribution to the friction and what you adjusted | Character assassination; naming or mimicking the person |
| "Tell me about a time a team member wasn't pulling their weight." | Accountability and delivery | Protecting the deliverable while supporting the individual | Going straight to the manager without speaking to the colleague |
| "How do you handle working with people whose style differs from yours?" | Adaptability | How you flexed your own approach to make the partnership work | Answering in generalities with no concrete example |
| "Tell me about a time you disagreed with a colleague." | Influence and judgement | The evidence-based case you made and how you handled the decision | Treating a professional disagreement as a personality problem |
Note the difference between the last two rows and the rest. A disagreement about what to do is a professional difference of opinion and should be answered with evidence and influence — closer to the approach in our guide to disagreeing with your manager. A difficult working relationship is a behavioural problem and needs the empathy-and-direct-conversation treatment described below. Mixing the two up is one of the most common reasons answers miss the mark.
If the question arrives as a hypothetical — "what would you do if a colleague refused to cooperate?" — you are in situational interview question territory. The strongest approach is still to answer with a real example first, then generalise: "Here's what I did when that happened to me, and that's the approach I'd take here."
The 6-Step STAR+ Framework for Conflict Answers
Standard STAR structure — Situation, Task, Action, Result — works for most behavioural interview questions, but it under-serves conflict answers because it leaves the "Action" step as one undifferentiated block. Interpersonal answers are scored on the sequence of your actions: did you seek to understand before you confronted, and did you confront before you escalated? This six-step version makes that sequence explicit.
Frame the situation neutrally (15–20 seconds)
Set the context in two sentences: the project, your role, the colleague's role, and what was at stake. Describe the behaviour, not the personality.
- Say: "A colleague on the project was consistently missing our internal deadlines."
- Don't say: "She was lazy and impossible to work with."
- Never name the person or the employer in a way that identifies them
Show you sought to understand first
Explain what you did to find out why the behaviour was happening before you reacted to it. This is the step that separates mature answers from defensive ones.
- Checked whether they were overloaded or blocked by something upstream
- Considered whether your own expectations had been clearly communicated
- Looked for a pattern rather than reacting to a single incident
Have the direct conversation
The centrepiece of the answer. Describe approaching the person privately, framing the issue around shared goals and impact rather than blame, and asking an open question.
- Chose a private, low-stakes setting — a coffee, a one-to-one call
- Led with impact: "When the draft arrives on Friday, I can't get review comments back before the client meeting"
- Asked what would make it easier from their side, and listened to the answer
Agree a concrete change in how you worked together
Vague goodwill is not a result. Name the specific mechanism you both agreed: a new handover point, a shared tracker, a mid-week checkpoint, a different division of tasks.
- Make it mutual — something you changed too, not just a demand on them
- Keep it lightweight enough that it actually survived contact with a busy week
Escalate only if it genuinely didn't work — and say why
If you did involve a manager, make clear it came after the direct conversation, and that you escalated the delivery risk rather than complaining about the person.
- Frame it as flagging a risk to the work, with the steps you had already taken
- Escalation before a direct conversation is scored negatively almost everywhere
- Safeguarding, bullying, harassment or safety issues are the exception — those go up immediately, and saying so is a strength
Close with the result and what you changed permanently
Give a concrete outcome — the deadline met, the error rate down, the relationship workable — then one sentence on what you now do differently with every new colleague.
- Quantify where you honestly can: "we delivered two days early for the rest of the project"
- End forward-looking: "I now agree handover points at kick-off rather than assuming them"
Most candidates invert this and spend 60% of the time on the situation — effectively building a case against their old colleague. Time yourself: context in about 20 seconds, then move to what you did. A complete answer should run 90 seconds to two minutes. Practising this out loud is far more effective than re-reading your notes; see our mock interview practice guide for a structured way to rehearse.
Five Full Sample Answers
Each answer below is written as it would actually be spoken, at roughly the right length. Use them as structural models — borrow the sequence and the phrasing, but the specifics must be your own, because follow-up questions will quickly expose a borrowed story.
1. Graduate / first job: a colleague who dismissed your input
"In my first role as a marketing assistant, I shared a reporting team with a colleague who had been there eight years. Whenever I suggested a change to our weekly report, the answer was 'that's not how we do it', usually in front of the team, and I started avoiding raising anything at all.
I decided the problem was partly how I was raising things — I was proposing changes in a group meeting with no warning. So I asked if we could grab fifteen minutes, told her honestly that I valued how well she knew the data and that I wanted to understand the reasons behind the current format before suggesting anything else. She explained that two of the fields I wanted to cut were there because of a finance audit request. She also said the changes had felt like criticism of work she'd built.
We agreed I'd run ideas past her before meetings, and she agreed to tell me when something was a hard constraint rather than a preference. Two months later she backed my proposal to automate the report, which saved us around three hours a week, and she asked me to show the rest of the team how it worked."
Why this works: the candidate owns part of the problem, has the direct conversation, learns a concrete fact they didn't know, and ends with a measurable result plus the former adversary as an advocate.
2. A colleague who repeatedly missed deadlines on a shared project
"On a six-week client project I was responsible for the final report, and a colleague owned the data section that fed into it. His input was late three weeks running, which compressed my review time to a few hours each time and meant I was working late to cover it.
Before raising it, I checked our project tracker and saw he was simultaneously staffed on two other deliverables — so this looked like a capacity problem, not carelessness. I asked for a short call and led with the impact rather than the lateness: with the data arriving Friday afternoon, I couldn't quality-check it before the Monday client send. He said the real blocker was that he was waiting on a system export that only landed on Thursdays.
We moved his internal deadline to Tuesday for the previous week's export, which he could hit comfortably, and I restructured the report so the data section slotted in last. I also flagged the double-staffing to our project lead as a scheduling risk, with the fix we'd already agreed. We hit every remaining deadline, and the client's feedback specifically mentioned the quality of the data section."
Why this works: it diagnoses a structural cause instead of a character flaw, escalates the system issue rather than the person, and shows the candidate changing their own process too.
3. A senior stakeholder who blocked your work
"I was rolling out a new booking process across four branches, and one branch manager — considerably senior to me — simply didn't engage. He missed two briefing calls and told his team to keep using the old spreadsheet, which meant our central reporting didn't reconcile.
Rather than treating it as obstruction, I went to his branch for a morning and sat with two of his staff. The new process added a step at check-in that was fine in the larger branches but genuinely slowed his queue at peak times, and he'd had no route to say so because the pilot hadn't included him.
I asked for twenty minutes with him, acknowledged that the pilot had missed his branch's volumes, and asked what a workable version looked like. We agreed a batched check-in variant for peak hours, which I took back to the project sponsor with his queue data attached. It was approved, he rolled it out himself within a fortnight, and all four branches were reconciling by month end. The wider lesson I took was to include the most sceptical site in the pilot rather than the easiest one."
Why this works: it reframes resistance as unheard feedback, shows influence without authority, and demonstrates the candidate gathering evidence before escalating upward.
4. A personality clash: different working styles
"I was paired with a colleague on a tender submission and our styles were close to opposite. I plan in detail and work to interim milestones; she worked in intense bursts close to the deadline and found my check-ins intrusive. After a fortnight we were both frustrated — I thought nothing was happening, she thought she was being chased.
I suggested we spend half an hour agreeing how we'd work rather than arguing about it. It turned out she wasn't resisting the plan, she just didn't want to report progress daily on work she considered half-formed. So we split the submission into two clearly owned halves, set three shared milestones instead of daily updates, and agreed she'd tell me immediately if a milestone was at risk.
It worked. We submitted a day early, won the tender, and I stopped treating my own planning style as the default. On every project since, I've started by asking people how they prefer to be kept in the loop — it takes ten minutes and prevents exactly this kind of friction."
Why this works: it treats a style clash as a process problem with no villain, and the learning is transferable to any team the interviewer might put the candidate on.
5. A remote-team communication breakdown
"Working in a distributed team, I had a counterpart in another time zone whose messages read as blunt to the point of rudeness — one-line replies, no context, occasionally just 'no'. I'd started to dread the handover and was escalating small decisions to our manager to avoid dealing with him.
When I thought about it honestly, every interaction we'd had was asynchronous text. So I asked for a weekly fifteen-minute call in the small overlap between our days. On the first call he was friendly and detailed, and explained he wrote terse messages because he was answering on his phone at the end of a long shift — and that he'd assumed my longer messages meant he was being audited.
We kept the call, agreed that anything needing nuance waited for it, and I started flagging urgency explicitly so he knew what needed an immediate reply. Our handover errors dropped to almost none over the following quarter, and I now default to a short call with any new remote colleague before judging their tone in writing."
Why this works: the candidate names their own avoidance behaviour, identifies the channel rather than the person as the problem, and the fix is simple enough to be believable.
A well-chosen difficult-colleague story usually answers three or four questions in an interview: this one, plus conflict questions, teamwork questions and communication questions. Prepare two such stories rather than one, so you don't have to reuse the same example twice in the same interview — and keep a customer-facing version ready in case they ask about a difficult customer instead.
Choosing Your Example
The example you pick determines most of your score before you say a word about your actions. Run your candidate stories through this checklist.
A strong example meets all six tests
- Real friction, not trivial. It affected work that mattered — a deadline, a client, quality, a patient, a shift. "He played music too loudly" doesn't give you anywhere to go.
- You had agency. You were able to act. Stories where you could only wait for a manager to intervene leave nothing to score.
- You spoke to the person. If no direct conversation happened, pick a different story — this is the behaviour the question exists to test.
- It resolved, at least partially. Full resolution is ideal; a workable arrangement is fine. Unresolved stories need very careful framing (see the FAQ).
- You come out of it changed. There is something you now do differently, which is what makes the answer useful to the interviewer.
- It's safe to tell. No identifiable people, no confidential details, nothing that suggests you'd discuss a future employer's internal problems with strangers.
Examples that backfire
- Anything involving a protected characteristic or serious misconduct. Harassment, discrimination and bullying are not "difficult coworker" stories. If asked directly about such a situation, the only correct answer is that you reported it through the proper channel — not that you handled it informally yourself.
- The colleague you got dismissed. Even where justified, a story that ends in someone losing their job reads as high-risk unless the misconduct was unambiguous and you simply followed policy.
- A disagreement you won by going over someone's head. It demonstrates exactly the escalation-first instinct interviewers screen for.
- Your current manager, in an interview for an internal move. Word travels. Choose a peer, or an example from a previous employer.
- A clash that was entirely about you being right. If there is no point in the story where you concede anything, the interviewer hears a self-assessment, not a story.
Doing an impression of a former colleague's voice, calling them "toxic", or naming them and their employer are all fast routes to a negative score — and they are more common than you'd expect, because candidates relax once the story gets going. Interviewers are explicitly listening for how you talk about absent colleagues. Keep the description behavioural and the tone level, and remember that the same restraint is what makes a good answer to "how would your colleagues describe you?" credible.
The Seven Mistakes That Sink This Answer
1. Badmouthing
Contempt, sarcasm or labels like "nightmare" and "toxic". The interviewer hears how you'll one day describe their team. Describe behaviour and impact instead.
2. No resolution
The story stops at the frustration. Without a result and a changed working relationship, you've described a grievance rather than a competency.
3. A trivial example
Fridge thefts and loud phone calls signal either a very sheltered work history or poor judgement about what matters. Pick friction that threatened the work.
4. Pure blame
Zero acknowledgement of your own contribution. Even one line — "in hindsight I hadn't made the deadline explicit" — transforms how the answer lands.
5. Endless context
Ninety seconds of org chart before anything happens. Interviewers stop taking notes. Two sentences of setup, then act.
6. "I've never had one"
Read as either dishonesty or inexperience, and it costs you the chance to score. There is always a difference in standards or style worth describing.
7. Escalating first
Going straight to a manager or HR without speaking to the colleague is scored negatively almost everywhere, except for misconduct and safety issues.
A final, subtler mistake: answering in the abstract. "I always try to see things from the other person's perspective and keep communication open" is a philosophy, not an example, and competency interviewers cannot score it. If you notice yourself speaking in the present tense and the general "you", stop and restart with "There was a project last year where…". The same discipline applies across the most common interview questions.
Follow-Up Questions and How to Handle Them
Expect at least one probe. Structured interviewers use follow-ups to test whether the story is genuine and to fill gaps in their scoring sheet, so prepare these four in advance.
"What would you do differently?"
Never answer "nothing". Give one specific, modest improvement — usually acting sooner. "I let it run for three weeks before saying anything. Now I raise a pattern after the second occurrence, while it's still a small conversation." This is the probe candidates most often fumble, and a good answer materially lifts the score.
"How did they react?"
Be honest, including an initially defensive reaction. "She was quite defensive for the first few minutes — I think she expected a complaint. Once I'd explained I wanted to understand the constraints, the conversation changed." A frictionless reaction sounds invented; a recovered one sounds real and shows composure.
"Have you ever had to report a colleague?"
Answer the policy question, not the gossip question. Explain that you'd always try a direct conversation for performance or style issues, and that anything involving safety, misconduct, discrimination or harassment goes to a manager or the relevant policy route immediately. If you have reported something, describe the process you followed rather than the details of the incident.
"What if that happened here?"
Translate your framework into their context in three steps: understand the cause, have the direct conversation, agree a concrete working arrangement — and mention escalation only as a last resort with a stated trigger. If you know anything about how the team is structured, anchor your answer to it. This is also a natural moment to show the flexibility interviewers probe with adaptability questions.
Most candidates practise the main answer and are caught out by the follow-ups, which is where the honest detail lives. Record yourself answering the question, then immediately answer all four probes above without stopping. Two or three rounds of this is usually enough to make the whole sequence feel natural rather than scripted.
Frequently Asked Questions
Prepare for Every Stage, Not Just the Interview
Most employers screen with aptitude and situational judgement tests before you ever reach a behavioural interview. Practise both — free timed tests and worked answers.
Keep reading
- Article · Strategy & ScoringTell Me About a Time You Worked in a Team: Complete Graduate Interview Guide 2026
- Article · Strategy & ScoringTell Me About a Time You Solved a Difficult Problem: Complete Graduate Interview Guide 2026
- Article · Strategy & ScoringTell Me About a Time You Received Difficult Feedback: Complete Graduate Interview Guide 2026
- Article · Strategy & ScoringTell Me About a Time You Made a Difficult Decision: Answer Framework and Examples
- Guide · Strategy & ScoringSTAR Interview Technique: Complete Guide with Worked Examples
- Guide · Strategy & Scoring"Why Should We Hire You?" Best Answer Framework & 6 Worked Examples