Offermic

Tell me about a time you had to work with a difficult coworker

Behavioral (Answer structure: STAR)

Updated

Written by

The short answer

Describe the behavior, not the person, then show what you did to make the working relationship function: a direct conversation, a clearer process or agreed expectations. Use STAR, keep your tone neutral and generous, and end with a result that shows the work got done and the relationship improved, even if you never became friends.

Hear the question

Read aloud with the voice from the app's practice mode.

Transcript: Tell me about a time you had to work with a difficult coworker

Key takeaways

  • Describe specific behaviors, such as missed handoffs, not labels like 'lazy' or 'toxic'.
  • Show that you tried to understand what was driving the behavior.
  • Focus on actions you controlled: a conversation, a process, clearer agreements.
  • A good ending is a functioning working relationship, not a friendship.
  • Only mention escalating to a manager after you tried to fix it directly.

To answer “Tell me about a time you had to work with a difficult coworker,” describe the difficult behavior factually, show the specific steps you took to understand it and work around it, and end with the work getting done and the relationship improving. Your tone about the other person is part of the answer.

Why do interviewers ask about difficult coworkers?

They are testing maturity. Everyone meets people who are hard to work with, so the interviewer wants to know how you respond when it happens to you:

  • Do you stay calm and professional?
  • Do you try to understand why the person behaves that way?
  • Do you take practical steps, or complain and wait?

A good answer also reassures them that you will not bring drama to their team.

How should you structure your answer?

Tell it as a STAR story. University career guides, including Iowa’s Tippie College of Business, recommend using “I” for the action section so your contribution is clear, and giving the story a clear beginning, middle and end.

  • Situation. The coworker’s behavior in one or two neutral sentences.
  • Task. What you needed from the working relationship.
  • Action. Usually a direct conversation plus a practical change in how you worked.
  • Result. What improved, for the work and between the two of you.

Weak vs strong answers

Weak answer

“There was this guy on my team who was just impossible. Everyone hated working with him. I kept my head down and eventually he left the company.”

Why it falls flat: Name-calling, no action and a result that came from luck, not effort.

Strong answer

“A teammate kept missing our shared deadlines and didn't answer messages. I asked to grab coffee and found out he was covering two roles after a colleague left. We agreed on a short Monday check-in to flag conflicts early, and I took over one recurring report he was struggling with. Our deadlines were back on track within a month, and I learned to ask about workload before assuming someone doesn't care.”

Why it works: Factual description, a curious conversation, a concrete fix and an honest lesson.

What does each AI interviewer probe?

Offermic’s AI interviewers are simulated personas, not real people. Expect them to test your fairness.

Sarah, HR SpecialistAI interviewer

Sarah may follow up with: “If that coworker were in this room, how would they describe working with you?”

Emily, Senior RecruiterAI interviewer

Emily may follow up with: “At what point would you have involved your manager, and why didn't you do it sooner?”

Raj, Senior DeveloperAI interviewer

Raj may follow up with: “What did you change in your own way of working because of that experience?”

How does the answer change by industry?

Industry Typical friction Strong resolution
Retail Uneven task splitting on shifts A clear checklist or area split
Finance Late inputs at month-end Shared tracker, early reminders
Engineering Harsh design reviews One-on-one pre-reviews, written feedback
Hospitality Front-of-house vs kitchen tension A shared pre-shift briefing

Example answers by experience level

Examples written for this page, not real candidates.

Entry level: Example answer — retail sales associate (retail)
  1. Situation

    A coworker on my closing shift often left before finishing her half of the recovery work, so I was staying late to refold her sections.

  2. Task

    I wanted closing to be fair without making it a fight.

  3. Action

    I asked her if something was going on. She explained that she took the last bus home and missed it if we ran late. I suggested we split tasks by area at the start of the shift and that she take the areas near the door, which were faster to finish.

  4. Result

    We both finished on time most nights, and our manager adopted the split-by-area checklist for all closing shifts.

Illustrative example written for this page, not a real candidate.

Mid-level: Example answer — accountant (finance)
  1. Situation

    A senior colleague in accounts payable consistently sent month-end accruals late and pushed back when I followed up.

  2. Task

    I needed her numbers by day three to close on time.

  3. Action

    I asked for 15 minutes to understand her process. She was waiting on approvals from three department heads who were slow. We set up an automatic reminder to those approvers on day one and a shared tracker so she could see which items were blocking me.

  4. Result

    Her accruals started arriving on day two or three. We closed on time for the rest of the year, and she started sending me heads-up messages when something was going to slip.

Illustrative example written for this page, not a real candidate.

Senior: Example answer — engineering lead (engineering)
  1. Situation

    A peer lead on another team was known for rejecting design proposals in public review meetings with sharp comments, and my engineers had started avoiding him.

  2. Task

    Our teams shared a platform, so we needed his input without the friction.

  3. Action

    I started sending him designs a few days before review and asking for his concerns one-on-one. His objections were usually valid reliability points. I also asked him directly if he would give written feedback instead of debating live, and he agreed.

  4. Result

    Review meetings got shorter, my engineers started seeking his input early, and two of his suggestions prevented outages. We worked well together from then on.

Illustrative example written for this page, not a real candidate.

Do this

  • Pick a story where your action clearly changed the situation.
  • Name what you learned about the other person's constraints or pressures.
  • Use a concrete mechanism: a check-in, a shared tracker, a written agreement.
  • Keep the description of the coworker to one or two factual sentences.

Avoid this

  • Venting or using emotional language about the coworker.
  • Stories where you did nothing and waited for them to leave.
  • Implying you find many people difficult.
  • Choosing an example involving harassment or misconduct, which calls for a different kind of answer.

Other ways it gets asked

  • “Describe a challenging relationship with a colleague.”
  • “Tell me about someone you found hard to work with.”
  • “How do you deal with coworkers who don't do their share?”

Questions people also ask

How is this different from a conflict question?

A conflict question is usually about one disagreement. A difficult-coworker question is about an ongoing working relationship, so interviewers want to hear how you adapted over weeks or months.

What if the coworker really was the problem?

They may have been, but the interviewer only hears your side. Describe what they did factually and spend the time on what you did. Fair-minded candidates are more believable.

Is it OK if the relationship never fully improved?

Yes, if the work still got done and you can explain what you learned. Be honest about the outcome.

Sources

  1. STAR Method – Career Guide, University of Iowa Tippie College of Business
  2. Using the STAR method for your next behavioral interview, MIT Career Advising & Professional Development

Written by, Founder

Can Garip is the founder and developer of this app. He builds the AI mock interview product and writes its interview preparation guides.

Drafted with AI assistance, then edited and fact-checked by the author.

How we write