To answer “tell me about a time you dealt with a difficult coworker,” describe one real colleague by what they did, not by what kind of person they were, say how it affected the work, and spend most of the answer on what you did about it: usually a calm one-to-one conversation and a practical change in how you worked together. Finish with the result for the work and where the relationship stands now. About 90 seconds is enough.
The quiet test in this question is fairness: if the coworker heard your answer, they should recognize themselves in it. Below are the types of difficult coworker that make good stories, a structure with timings, five sample answers and the likely follow-ups.
What the interviewer is checking
Nobody gets to choose all of their coworkers. The question asks whether you can keep the work moving when someone is hard to work with, and it is scored on four things:
- Directness. Did you talk to the person before going to a supervisor?
- Fairness. Do you describe behavior and its effect, or do you label someone lazy or toxic?
- Focus on the work. Did the customer, patient or project come out all right?
- Self-awareness. Did you consider your own part, or what the other person was dealing with?
It sits close to several questions the site already covers. A disagreement over a decision is the conflict with a coworker question; a hypothetical about rudeness is covered in how do you deal with a rude coworker; and stepping in between two other people is resolving a conflict between coworkers. This question is about a pattern of behavior from one colleague that made your own work harder.
| Where it's asked | Why it matters there |
|---|---|
| Retail, grocery and food service | Shifts are assigned, so you work with whoever is on the rota |
| Call and contact centres | Team targets are shared, and one person's attitude spreads across the floor |
| Hospitals and care homes | Handoffs between colleagues are a patient-safety issue |
| Offices and corporate roles | Work depends on people in other teams you can't choose |
| Trades, plants and warehouses | Crews who don't communicate make mistakes and get hurt |
Five kinds of difficult coworker, and what each story can show
| Type | What it looks like | What your story should show |
|---|---|---|
| The territorial veteran | Redoes your work, says “that's not how we do it” without explaining | You learned their standard and earned their trust |
| The negative one | Constant complaining that drags down the team | You turned the complaint into something fixable |
| The unreliable one | Late handoffs, missing pieces, gaps you have to cover | You addressed the effect on the work (see a coworker not pulling their weight) |
| The one who goes around you | Takes your questions to your manager instead of you | You found the reason and removed it |
| The silent one | Won't explain, won't share knowledge | You changed your own approach first |
Stories to avoid: harassment, discrimination or anything that became a formal investigation (those belong in formal channels, not interview stories); a coworker you still clearly resent; and a story where your only fix was avoiding them.
A four-part structure: behavior, impact, action, outcome
| Part | What to say | Time when spoken |
|---|---|---|
| 1. Behavior | Their role (not their name) and what they did, in neutral words | About 15 seconds |
| 2. Impact | What it did to customers, patients, quality or your workload | About 10 seconds |
| 3. Action | The conversation you started, roughly what you said, and what you changed | About 45 seconds |
| 4. Outcome | The result for the work and a concrete sign of the relationship now | About 20 seconds |
It is the STAR method with the situation split into behavior and impact, which keeps you from spending a minute describing how annoying someone was. Before you rehearse, run the recognition test: would this coworker read your first sentence and say “fair enough”?
Five sample answers to “tell me about a time you dealt with a difficult coworker”
These are example answers we wrote to show the structure in different jobs; they are not real candidates' stories. Use your own experience and only numbers you can stand behind.
Entry-level (grocery deli clerk): a veteran who kept redoing my work
“When I started at a grocery deli, a coworker who'd been there nine years would rewrap or redo platters I'd made, sometimes in front of customers, and twice told me I was doing it wrong without saying what. It slowed the counter down and I was second-guessing everything. On a quiet afternoon I asked if she'd show me how she wanted the platters done, since she clearly knew the standards better than I did. It turned out there were labeling and portion rules nobody had covered in my training. She walked me through them for twenty minutes, and I wrote them on a card by the scale. She stopped redoing my work, and a few months later she asked me to train the next new hire on platters. What I learned: sometimes a difficult coworker is guarding a standard, and asking them to teach it changes everything.”
Customer-facing (contact centre agent): negativity spreading on the floor
“On my contact centre team, one agent spent the gaps between calls complaining loudly about customers and our new targets, and two newer agents started picking up the same attitude. Their quality scores were slipping on empathy. I didn't want to lecture a peer, so I asked him for a coffee, said the targets seemed to be really getting to him, and asked what bothered him most. Mostly it was that after-call time had been cut and he felt rushed on complicated billing calls. I suggested we take that one point to our team leader together, with a week of our own after-call times as evidence, instead of venting on the floor. The team leader adjusted the target for billing calls. He still grumbled sometimes, but at something fixable, and the newer agents' scores recovered within a month. I learned to treat constant complaining as information and give it somewhere useful to go.”
Healthcare (registered nurse): rushed handoffs
“As a day-shift nurse on a medical-surgical unit, I took handoff from a night nurse whose reports were very fast and incomplete, and who got defensive when I asked questions. I'd find out about pending labs or a family concern hours later, which is a patient-safety problem, not a personality clash. I asked to talk at the end of a shift, away from the desk, and said I knew she was exhausted by seven in the morning and my questions weren't criticism; I just needed a few specific items for each patient. I suggested we both use the unit's handoff template at the bedside, and I used it for my reports to her too. She agreed, and our handoffs got shorter and more complete. When it slipped once on a heavy night, I raised it with her directly rather than the charge nurse. The lesson: name the shared goal, the patient, and make the fix something you both do.”
Office (operations analyst): a colleague who went over my head
“In my second year as an operations analyst, a colleague in finance would email my manager, often copying her director, whenever he had a question about my reports, instead of asking me. Routine questions looked like escalations, and I was answering them secondhand. I asked him for fifteen minutes and said I wanted him to get answers quickly, and coming to me first would be faster for both of us. He told me a report of mine had once had an error that embarrassed him in a meeting, so he'd stopped trusting the numbers. That was fair. I offered to send him the reconciliation behind each monthly report a day before it went out so he could check it himself. The escalations stopped within two months, and he started inviting me to his budget reviews. I learned that when someone goes around you, there's usually a reason worth asking about.”
Trades (electrical apprentice): a journeyman who wouldn't explain anything
“As a first-year electrical apprentice, I was paired with a journeyman who barely talked, answered questions with 'just watch,' and got short with me when I was slow bringing materials. I needed to learn, and I worried my hours were being wasted. Instead of complaining to the foreman, I changed what I did: I read the plans the night before, staged materials for the next day's work and saved my questions for lunch, one or two at a time. After about two weeks he started explaining things without being asked, and later told me he'd had three apprentices in a row who stood around on their phones. By the end of the job he asked the foreman to keep me on his crew. I took two lessons from it: show you're serious before asking someone to invest in you, and try changing your own approach before escalating.”
Follow-up questions to expect
- “What would you have done if talking to them didn't work?” Give the next step: a second conversation with specific examples, then your supervisor, framed around the effect on the work rather than the person.
- “Did you involve your manager?” If you did, say why it had to go there. If you didn't, say why it didn't need to.
- “How is your relationship with them now?” Offer one concrete sign, such as being asked to train someone or being invited to a meeting.
- “What was your part in it?” Have an honest answer ready: you waited too long, or you assumed bad intent before asking.
- “What kind of people do you find hard to work with?” Name a behavior, not a type of person, and how you handle it.
Mistakes to avoid, and how to practise
- Labels instead of behavior. “Lazy,” “toxic” and “crazy” make the interviewer wonder how you'd describe them.
- No conversation. A story where you quietly put up with it, or quietly avoided them, shows neither directness nor teamwork.
- Escalating first. Going straight to a manager over a minor pattern suggests you can't handle normal friction.
- Winning. Ending with the coworker being written up or leaving is not the result interviewers want.
- Pick two coworker stories, one main and one backup, and write the behavior in one neutral sentence for each.
- Draft the four parts with the free STAR story builder, keeping the action longest.
- Say it out loud and time it. If the behavior and impact take more than 25 seconds, cut.
- Answer it in a free AI mock interview, which asks behavioral questions out loud and scores your spoken answer, then answer the follow-ups above.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant with a free practice side that suits this question well: the AI mock interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10, so you can hear whether your coworker story sounds fair or sounds like a complaint. The free practice demo has 145 questions in 10 tracks; type an answer and get a score out of 10 with strengths, areas to improve and a follow-up question, no signup needed.
The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month. It runs as a desktop app for Windows 10 and 11 and macOS 12 or later, a free iPhone and iPad companion on the App Store (iOS 16 or later) and an Android companion in beta. If you use live help in a real interview, follow your employer's rules; either way, the story has to be your own.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What if I've never had a difficult coworker?
Use a milder case: a teammate with a very different working style, a classmate in a group project or a volunteer who kept missing commitments. “I get along with everyone” sounds evasive, and the interviewer will usually ask again.
Should I name the coworker in my answer?
No. Use their role, such as “a senior technician” or “a colleague in finance.” Names add nothing and can sound like gossip.
Can I talk about a difficult manager instead?
Only if the question allows it. A clash with your boss is a different question; see <a href="/blog/disagreed-with-manager-interview-answer">tell me about a time you disagreed with your manager</a>.
How long should my answer be?
About 60 to 90 seconds. Keep the description of the coworker under 25 seconds and spend most of the time on what you did.
Is it OK if the coworker never really changed?
Yes, if you show what you controlled: the conversation you had, how you protected the work and how you kept it professional.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview