OfferDrill.

Interview questions

The hard ones

How to talk about a conflict with a coworker without sounding like the problem.

You have a real story and you're worried it makes you look difficult. This page shows you how to tell it honestly, keep yourself out of the villain seat without shading the truth, and land it in about a minute.

Why they ask it

They're not looking for someone who's never had a conflict. Everyone who has worked with other humans has had one, and an interviewer who hears "I get along with everybody" hears either a person who avoids hard conversations or a person who isn't being straight with them.

What they actually want to know is narrow and practical: when something goes wrong between you and another person, what do you do first? Do you go to the person, or do you go around them? Do you escalate early, late, or never? Can you describe someone you disagreed with as a reasonable adult with their own reasons, or does everyone who crossed you turn into an idiot in the retelling?

That last one carries the most weight. The interviewer is picturing you describing this interview's team to your next interviewer. If you're generous about a coworker who genuinely made your job harder, they relax. If you're not, they notice — even when you're right about the facts.

What not to say

"I don't really have conflicts. I'm pretty easygoing."

It reads as dodging, and it costs you the whole question. You get no credit for being agreeable. You just look like you either can't recall a time you had to say a hard thing, or you won't say it. Pick a real example, even a small one.

A story where you were completely right and the other person was completely wrong.

Even if that's how it actually went, telling it that way sounds like a person who doesn't examine their own part in things. Keep your facts. Add the one true thing you'd do differently — starting sooner, asking instead of assuming, writing it down. A single honest concession makes the rest of your account more believable, not less.

Naming the person's flaws. "She was disorganized." "He was territorial."

Character words turn a work problem into a personal grudge, and the interviewer starts imagining you doing this about them. Describe behavior and impact instead: "The files were coming to me two days after the deadline, which pushed my review into the weekend." Same facts, no verdict.

Choosing a conflict about ethics, harassment, or somebody's boss being terrible.

You may have lived through something serious, and it may have been the defining conflict of that job. It's still the wrong pick for this question. A heavy story pulls the room somewhere it can't go in twelve minutes and leaves the interviewer holding something they can't evaluate. Save it. Pick a process disagreement instead.

Ending with "and then I went to my manager."

Going to a manager is fine. Going to a manager first is what they're listening for. If escalation was part of your story, say what you tried directly before that, and what you brought with you when you escalated.

How to build a strong answer

  1. Pick a boring conflict on purpose.
    The best example is a disagreement about how work gets done, not about who somebody is. Two people wanted different timelines. Handoffs kept arriving late. You disagreed about which approach to take and both of you had a real case. Low heat, clear stakes, resolved. If you're deciding between a dramatic story and a dull one, take the dull one. The dull one lets them hear your judgment instead of your feelings.
  2. Give the other person a reason in your first ten seconds.
    Before you describe what bothered you, say why they were doing it. "He was protecting his team's capacity." "She'd been burned by a rushed launch before." This one move does more than anything else on this page. It proves you can hold two viewpoints, and it stops the interviewer from bracing for a rant. It has to be true — if you never learned their reason, say that: "I assumed he was just being difficult. Turned out he had a constraint I didn't know about." That version works too.
  3. Say what you did, and make it a direct conversation.
    The strongest middle is short and concrete: you went to the person, in private, and you asked before you argued. Name the actual move. "I asked if we could get fifteen minutes." "I said what I was seeing on my end and asked what it looked like from his." If you did escalate, say what you'd already tried and what you brought — dates, a document, two options. Avoid the word "communication." Describe the conversation instead.
  4. End with the outcome and one line on what changed in you.
    Say how it landed, in one sentence, including if it landed imperfectly. "We split the difference." "He didn't agree, but we had a rule after that." Then one sentence about what you carry forward — usually "I raise it earlier now" or "I ask what's behind it before I decide what it means." Then stop. The whole thing runs sixty to ninety seconds. Silence after it is fine. Don't fill it by relitigating the story.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career. A peer in another function whose late handoffs were wrecking your schedule.

On [the project], I owned [the review step], and the materials were coming to me about two days past the agreed date, most weeks. That meant my part landed on weekends. I'd been absorbing it and getting quietly annoyed, which wasn't helping anybody. So I asked [him] for fifteen minutes and said what I was seeing — here are the dates, here's what it does to my end — and asked what the holdup looked like from where he sat. Turned out he was waiting on [an upstream approval] he didn't control, and nobody had ever told him my deadline was real. We moved his target date up by three days to build in slack, and I started flagging in our Monday check-in when something was at risk instead of waiting until it was late. It mostly held after that. What I'd do differently is say something in week two instead of week seven. I let it build up, and by the time I raised it I was more frustrated than the problem deserved.

You give his reason before your complaint. The conflict is about dates, not character. The fix is specific, and the thing you'd change is a real admission that still makes you look better, not worse. Use the shape, not the words — your dates and your details.

Early career. A disagreement with someone more senior, where you weren't in a position to insist.

During my internship at [company], I was [pulling the weekly numbers] and I noticed [the report was double-counting a category]. I flagged it to [the analyst who built it], and she told me it was intentional and to leave it. I thought she was wrong. But she'd been there four years and I'd been there six weeks, so I went back and actually checked — I pulled [the source data] and built out the comparison so I could show the specific rows rather than just say I thought it was off. Then I asked her to look at it with me. She looked for about a minute and said I was right, that the rule had changed the year before and nobody had updated the logic. She fixed it that afternoon. The thing I took from that is that being right isn't the same as being useful. The second conversation worked because I brought the rows. The first one was just my opinion against her experience.

Being new is the situation, not an excuse. You don't pretend to have authority you didn't have. The lesson is about evidence, which is the exact thing an interviewer wants to hear from someone junior.

Anyone. A conflict that didn't fully resolve — which is more common than the clean version.

[My counterpart] and I disagreed about [how much testing to do before release]. He wanted to ship and fix in the field; I wanted another cycle. Both of those are defensible — he was under real pressure from [the client], and I'd been the one taking the support calls after [the last rough launch], so we each had a different part of the cost in front of us. We talked it through twice and didn't land in the same place. So I wrote up what I thought the risk was, the two options, and what each one would cost, and we took it to [our manager] together. She went with his call. I supported it and ran [the rollback plan] so we'd be covered. It went out mostly fine — we had [a few issues] and caught them fast. I still think the extra cycle was the better call, but the part I got right was taking it up together instead of going around him. That's why we could work on the next thing without it being weird.

It's honest that you lost and still think you were right — which is fine to say, as long as you show you backed the decision anyway. "We took it up together" is a line that makes hiring managers sit up.

What comes next

Answer this one well and the interviewer usually goes here:

  • How is your relationship with that person now?
  • What would you have done if the conversation hadn't gone well?
  • When do you decide something needs to go to your manager instead of staying between the two of you?
  • Tell me about a time someone gave you difficult feedback. What did you do with it?
  • Has anyone ever told you that you were hard to work with?
  • What kind of person do you find hardest to work with?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You already have the story — the work now is just trimming it, handing the other person their reason, and stopping when you're done.