The average employee spends 2.1 hours every week dealing with workplace conflict in some form — being pulled into disagreements, mediating between coworkers, or managing their own friction with someone else. That’s from the CPP Global Human Capital Report, which surveyed thousands of employees across multiple countries. Interviewers know this number implicitly, even if they can’t cite it. They ask about difficult people not because they want to hear drama, but because they need evidence that you can operate effectively inside that 2.1-hour reality without derailing yourself or the team around you.
This question is behavioral — meaning it requires a specific past story, not a philosophical answer about how you “prefer to communicate openly.” Generic responses will end your candidacy faster than an honest admission that a working relationship was genuinely hard.
Why Interviewers Ask This Question
Hiring managers ask this to assess several things at once, and it helps to know exactly what they’re scoring.
Emotional regulation. Can you describe a tense interpersonal situation without still sounding angry about it? Bitterness, blame-shifting, and score-settling are red flags that travel with a candidate from job to job.
Self-awareness. Do you have any insight into your own role in the conflict — or at least into how your working style might differ from someone else’s? People who explain every difficult relationship as 100% the other person’s fault consistently struggle in teams.
Conflict resolution skills. Did you take some concrete action, or did you just tolerate the situation until one of you left? Interviewers want to see that you have an actual approach — not just patience.
Professionalism under pressure. Did you keep the work product intact while the interpersonal tension was happening? That’s the real deliverable.
Fit for their specific environment. A startup with five people and no HR department needs someone who can resolve friction directly. A regulated enterprise needs someone who knows when to escalate. The story you choose signals your instincts about how organizations work.
Applying the STAR Framework to This Question
STAR — Situation, Task, Action, Result — is the standard structure for behavioral answers. For the “difficult person” question, each component has specific requirements.
Situation
Set the scene briefly. Name the role and relationship of the difficult person without making the intro a therapy session. Interviewers don’t need the full backstory — they need enough context to understand why the friction mattered. Two to three sentences is right.
What to include: what the project or goal was, who the other person was relative to you (peer, manager, report, vendor, client), and what made them “difficult” in concrete behavioral terms — not personality adjectives. “She dismissed my proposals in team meetings without explanation” is a situation. “She was passive-aggressive” is a diagnosis.
Task
Clarify what you were responsible for achieving — and why this relationship stood in the way of that. This is often the shortest part of the answer, but it anchors why the conflict mattered professionally. “I needed her buy-in to move the project forward” gives the interviewer a clear stakes statement.
Action
This is where most candidates lose the question. They either stay too vague (“I tried to communicate better”) or over-detail the conflict itself instead of their response to it.
Strong actions are specific, first-person, and proactive:
- You requested a one-on-one conversation.
- You asked a clarifying question to understand their perspective.
- You adjusted how you framed your requests to reduce friction.
- You looped in a third party (manager, skip-level, HR) when the situation warranted it.
- You created a shared document or process to reduce ambiguity between you.
Use “I” statements, not “we” statements, in this section. The interviewer is evaluating your judgment, not the team’s.
Result
Quantify if you can, but at minimum show two things: the professional outcome (project shipped, relationship stabilized, both parties moved to different teams amicably) and what you learned. A brief “what I took away” line is not weakness — it signals maturity and makes the story feel complete rather than triumphant.
12 Sample Answers Across Roles and Levels
1. Entry-Level — Difficult Peer in a Group Project (Academic/Internship)
“During my summer internship at a logistics company, I was paired with another intern on a client report due at the end of the program. My partner consistently missed our check-in deadlines and submitted sections that didn’t match the agreed format. I asked for a short sync where I laid out the deliverables and deadlines in a shared doc so we both had visibility. I also asked directly whether the timeline was realistic for him given his other projects. Turns out he’d been pulled into additional work he hadn’t mentioned. We renegotiated the split, and I took on a larger share of the formatting work. We delivered the report on time and the client manager gave it a positive review. I learned to build a shared reference early so expectations are explicit, not assumed.”
2. Customer Service Rep — Difficult Coworker Who Skipped Protocols
“At my call-center job, I worked alongside a senior rep who regularly bypassed our escalation protocol and gave customers unauthorized refunds to close tickets fast. It affected my queue because customers would call back expecting the same treatment from me. Instead of complaining to our manager first, I had a direct conversation with him and asked if he’d walk me through his reasoning — I wanted to understand, not confront. He explained that he felt the standard escalation path took too long. I took that feedback to our team lead and suggested a streamlined escalation path for a specific refund tier. The lead implemented a pilot. The senior rep’s workaround behavior dropped significantly, and average handle time for that category fell by about 15 percent over the next month.”
3. Software Engineer — Peer Who Blocked Code Reviews
“On my first engineering team, one senior developer had a habit of leaving pull request reviews open for four or five business days, which bottlenecked the entire sprint. I didn’t want to escalate immediately — I didn’t know if there was context I was missing. So I sent him a Slack message asking if there was a better way to flag PRs that were blocking other work. He mentioned he was overwhelmed with architectural decisions and wasn’t triaging code review as a priority. I suggested adding a ‘needs-review-today’ label that the team could use when a PR was on the critical path. He agreed, and our tech lead adopted it as a team norm. My average wait time for reviews on critical features dropped from four days to same-day.”
4. Marketing Coordinator — Difficult Manager Who Changed Direction Constantly
“My manager at my previous agency had a pattern of approving campaign concepts and then requesting major revisions after we’d already started production, which caused us to miss client deadlines twice in one quarter. Rather than just absorbing the rework, I proposed a two-stage sign-off process: a low-fidelity concept approval before production began and a final approval gate with a 48-hour turnaround commitment. I framed it as protection for both of us — it would create a paper trail that the client had approved the direction. My manager agreed to try it on the next campaign. We had zero mid-production pivots that quarter, and client satisfaction scores for that account went up. It also gave me a clearer document trail to reference when scope creep came up in billing conversations.”
5. Project Manager — Difficult Stakeholder Who Kept Expanding Scope
“I was managing a product integration project for a financial services client whose internal stakeholder kept adding requirements after the statement of work was signed. Each addition threatened our go-live date. I scheduled a scope review meeting, came with the original SOW and a log of every change request and its estimated impact on timeline and cost. I wasn’t adversarial — I framed it as ‘here’s where we are and here are the options.’ We agreed to a formal change-order process for anything beyond the original scope. The project launched three weeks late due to changes already in the pipeline, but no new scope was added after that meeting, and the client renewed for a second phase.”
6. Sales Representative — Competitive Peer Who Poached Leads
“At a previous sales job, a colleague and I were both working mid-market accounts in adjacent territories and he twice reached out to prospects I had already contacted, which created confusion and almost cost us one deal. I approached him directly — acknowledged that our territory line was ambiguous and suggested we create a simple shared spreadsheet to track active prospects so we’d both have visibility. He was actually relieved to have a system because he’d worried I was doing the same thing to him. We took the sheet to our sales manager, who formalized it as a territory overlap process for the entire team. Neither of us lost another deal to internal confusion that year.”
7. Operations Analyst — Difficult Cross-Functional Partner
“I needed data from a business intelligence team to complete a monthly ops report, and the analyst assigned to my requests consistently deprioritized them in favor of what he called ‘higher-visibility projects.’ I was missing my reporting deadline three months in a row. I set up a short meeting to understand what his workload looked like and what would make my requests easier to action. He showed me that my requests arrived with inconsistent formats, which added time for him. I standardized the request template and started sending it at the beginning of the month rather than mid-month. With those changes, he agreed to a 48-hour turnaround SLA. I haven’t missed a reporting deadline since, and we’ve built a working relationship where I’m now on his short list for ad-hoc data pulls.”
8. Team Lead — Direct Report Who Resisted Feedback
“One of my direct reports was technically strong but reacted defensively to any feedback — she’d dismiss concerns or go quiet for days after a code review. This was creating tension with the rest of the team. I changed my approach in our 1:1s: instead of leading with what needed to change, I started by asking her to self-assess the work first. That shift gave her ownership of the critique and made her less reactive. I also gave feedback closer to the event and in private rather than in group reviews. Over about six weeks, her openness to feedback shifted noticeably. She’s since become one of the people other junior engineers ask for code review because she models the same approach — specific, private, forward-looking.”
9. Product Manager — Difficult Engineer Who Pushed Back on Every Feature
“I had a senior engineer on my squad who challenged every feature we put in the sprint — sometimes productively, sometimes in a way that slowed the team down. Instead of treating him as an obstacle, I started involving him in the requirements process before tickets were written. He had strong opinions about implementation complexity, and it turned out many of them were valid. By moving him upstream, his concerns surfaced before we’d already committed to a design, which saved us rework. He also felt more invested in what we shipped. Our sprint completion rate improved because we weren’t renegotiating ticket scope mid-sprint anymore. Other PMs on the team asked me how I’d gotten him to stop blocking standups.”
10. Senior Manager — Peer Director Who Undermined Decisions in Meetings
“A peer director had a habit of publicly questioning decisions we had already aligned on in leadership team meetings — which confused our direct reports and created ambiguity about direction. I asked for a standing 30-minute sync before leadership meetings to align on any major topics we both touched. I framed it as efficiency, not confrontation: ‘I want to make sure we’re presenting a coherent picture to the team.’ In that private channel, he was actually willing to raise concerns and work through them. He stopped contradicting settled decisions in public because he now had a venue to raise objections earlier. The leadership team noticed that our two functions were more coordinated, and our VP mentioned it in a quarterly review.”
11. HR Business Partner — Difficult Hiring Manager Who Bypassed Process
“A business unit manager I supported was consistently extending verbal offers to candidates before compensation had been reviewed, which created compliance risk and twice led to offers we couldn’t honor at the number he’d quoted. I set up a 20-minute meeting to walk through why the pre-approval step existed — specifically the legal and equity risk — rather than just citing policy. I also offered to turn the compensation review into a same-day process for most roles so he wouldn’t feel it was slowing him down. We built a simple Slack-based approval flow that took under two hours for standard roles. He stopped jumping ahead, and we had zero compensation-related offer retractions in the following 12 months.”
12. Individual Contributor — Remote Teammate in a Different Time Zone Who Was Unresponsive
“I was collaborating with a contractor based in Eastern Europe whose working hours overlapped with mine for only about two hours a day. He rarely responded to async questions within the workday, which caused delays when I needed his input to unblock my work. I asked him directly in a video call what his preferred way to receive and respond to questions was. He mentioned he processed Slack reactively and lost track of threads. We agreed to move all blocking questions to a shared Notion doc with clear ‘needed by’ timestamps so he could batch his responses at the start of his day, which landed in my mid-afternoon. Within a week, I was getting responses consistently before I needed them. The project timelines returned to normal and we developed a collaboration rhythm that the rest of the team eventually adopted for other cross-timezone pairs.”
What NOT to Say
Even a good story can collapse if you step into one of these traps.
Don’t trash the person. Adjectives like “toxic,” “incompetent,” “narcissistic,” or “lazy” are off-limits. They signal that you’re still emotional about it and that you may be an unreliable narrator. Behavioral descriptions are your only tool: what they did, not what they were.
Don’t make yourself blameless. Interviewers are skeptical of stories where the candidate had zero part in the friction. Even a small acknowledgment — “I probably could have raised this sooner” or “I realized I’d been assuming they understood the timeline” — demonstrates self-awareness. Pure victimhood stories fail the credibility test.
Don’t pick a conflict with a protected characteristic. Avoid stories that center on someone’s personality being connected to their age, gender, race, or any other protected identity. Even if the observation is accurate, it raises concerns about your judgment in regulated workplaces.
Don’t say you’ve never worked with a difficult person. Every interviewer who has ever had a job knows this is false, and it signals either poor memory or avoidance. If you’re asked a follow-up and you claim the question doesn’t apply to you, you’ve ended the conversation.
Don’t pick your current manager (if you’re still employed). The interviewer may contact them as a reference. Describing your current boss as the difficult person is high risk even if it’s entirely true.
Don’t pick a story that’s still unresolved. The resolution is what demonstrates competence. An ongoing feud with no outcome is not a behavioral answer — it’s a complaint.
Don’t conflate “different working style” with “difficult.” Not everyone who is harder to work with than you’d like is genuinely difficult. Using a story about someone who just had different preferences — morning meetings vs. afternoon, detailed reports vs. bullet points — as your answer undersells the question. Pick something with real friction and real stakes.
Choosing the Right Story
If you have multiple options, apply this filter:
- Was there a concrete professional outcome at stake — a deadline, a deliverable, a decision — not just an interpersonal preference?
- Did you take a specific action beyond “I tried to be patient”?
- Can you describe the other person’s behavior without using adjectives that sound like a psychiatric evaluation?
- Does the story end with a result you can point to, even if the relationship itself never became warm?
If you can check all four boxes, you have a usable story. Practice it out loud twice before the interview. The goal is to tell it in under two minutes without reading from a script — fluency signals that you’ve genuinely processed the experience, not just prepared a corporate-friendly version of it.
The best answers to this question accomplish something most candidates don’t expect: they make the interviewer think “I would want this person on my team when things get hard,” rather than “this person gets along with everyone.” The first reaction is worth more.