Tell Me About a Time You Resolved a Conflict: Complete Graduate Interview Guide 2026
One of the most probing questions in any competency interview — and one most candidates answer badly. Learn the SCAR framework, what employers are really measuring, and five full example answers across different backgrounds.
Why Employers Ask This Question
The conflict resolution question appears in virtually every competency-based interview at major graduate employers — Goldman Sachs, Amazon, PwC, Deloitte, KPMG, McKinsey, and beyond. It shows up in slightly different forms: "Describe a time you disagreed with a colleague," "Tell me about a situation where you had to navigate a difficult interpersonal dynamic," or "Give me an example of a time you had to challenge someone else's view." The surface wording varies, but the underlying measurement is the same.
Interviewers use this question to assess a cluster of competencies that are genuinely difficult to test any other way:
- Interpersonal maturity: Can you disagree without damaging relationships? Can you separate the issue from the person?
- Communication under pressure: Do you retreat, escalate, or find a constructive path through?
- Self-awareness: Can you recognise your own contribution to tension, not just point at the other party?
- Professionalism: Do you keep working relationships intact even when things get uncomfortable?
- Outcome orientation: Do you care about resolving the problem, or just about being right?
Most candidates describe the conflict vividly but spend barely a sentence on their own actions. Interviewers are not interested in how bad the conflict was — they are interested in what you specifically did to resolve it. The ratio should be roughly 20% setting up the situation and 80% on your actions and the outcome.
The question is also a subtle test of character. Candidates who paint themselves as entirely blameless and the other party as clearly wrong rarely come across as self-aware or emotionally intelligent. The strongest answers acknowledge complexity — a situation where both parties had legitimate perspectives, and where the candidate's skill lay in finding the path through rather than simply being correct.
For roles at highly collaborative firms (consulting, Big Four, investment banking), the ability to manage conflict constructively is treated as foundational — not a nice-to-have. These environments are high-stakes, fast-moving, and inherently prone to disagreement about approach, priorities, and resources. Employers need to know before they hire you that you will handle those moments professionally.
The SCAR Framework
The standard STAR method (Situation, Task, Action, Result) works for most competency questions, but conflict questions benefit from a more specific adaptation. The SCAR framework — Situation, Conflict, Action, Resolution — is designed to keep your answer tightly structured around the dynamics that matter most for this particular question type.
After covering Resolution, a one-sentence reflection ("What I took from that experience was...") elevates a good answer to an outstanding one. It signals emotional intelligence and genuine self-awareness — two qualities that differentiate the strongest graduate candidates. Keep it concise: the reflection should be a sentence, not a paragraph.
Pacing Your Answer
A well-structured SCAR answer runs between 90 seconds and 2.5 minutes when delivered out loud. As a rough word-count guide:
| SCAR Component | Recommended Length | What to Cover |
|---|---|---|
| Situation | 10–15% of answer | Context, who was involved, stakes |
| Conflict | 15–20% of answer | Nature of disagreement, both perspectives |
| Action | 50–60% of answer | Your specific steps, conversation, approach |
| Resolution | 15–20% of answer | Outcome, relationship, lesson |
Most candidates get this backwards — they spend 60% of the answer describing the conflict and barely touch their own actions. If you find your answer running long, trim the Conflict section, not the Action section.
Choosing the Right Example
The quality of your example is the single biggest determinant of how well this answer lands. A technically polished answer built around a weak example will still disappoint an experienced interviewer. Here is how to select a strong one.
What Makes a Strong Conflict Example
- A genuine disagreement, not just a misunderstanding: "We miscommunicated about the deadline" is a misunderstanding. "We disagreed about which analytical approach to take and I had to make the case for mine" is a real conflict. Interviewers can tell the difference.
- Substantive stakes: The conflict should have mattered — to the project quality, to the team, to the outcome. Trivial disagreements signal that you have never been in a situation where it counted.
- A conflict you helped actively resolve: You should be the protagonist — the person who took action to bring things to a constructive conclusion. Examples where the conflict "just sort of resolved itself" or "someone else sorted it out" do not showcase your skills.
- A preserved or strengthened relationship: Ideally your example ends with the working relationship intact, or even stronger. This signals that you can handle conflict without leaving wreckage behind.
- Recency: Aim for an example from the last two to three years. Examples from school group projects are acceptable if you are a first-year student, but a work placement or internship example is far stronger for most graduate candidates.
Do not use: conflicts that escalated to HR or formal disciplinary processes; conflicts rooted in someone else's behaviour that was clearly unacceptable (bullying, discrimination); situations where you were clearly in the wrong and have not acknowledged it; or conflicts so trivial that they do not demonstrate any real interpersonal skill. These all raise more questions than they answer.
Where to Find Examples if You Are Struggling
If you feel you have never had a significant conflict, look more broadly. Conflict does not have to be a heated argument. It includes: a meaningful disagreement about project direction; a time you challenged a more senior person's decision; a situation where two team members had conflicting priorities and you helped navigate the tension; a client or customer who pushed back strongly on your recommendation; or a situation in sport, student societies, or volunteering where team members disagreed about the best course of action.
Company-Specific Expectations
Different employers weight the dimensions of this question differently, based on their culture and the specific competencies they are hiring for. Understanding those nuances allows you to tune your answer appropriately.
| Employer | Competency Being Assessed | What They Particularly Value |
|---|---|---|
| Goldman Sachs | Interpersonal Effectiveness | Demonstrating you can push back on senior colleagues with evidence and respect. They want intellectual confidence paired with professional tact. |
| Amazon | Have Backbone; Disagree and Commit | Amazon explicitly values respectful disagreement followed by full commitment once a decision is made. Mention that you voiced your position clearly, then supported the final decision fully. |
| PwC | Relationships / Collaboration | Emphasis on preserving the working relationship. PwC wants evidence that you resolved the conflict in a way that strengthened trust, not just achieved the task. |
| Deloitte | Inclusion & Collaboration | Deloitte's culture emphasises diverse perspectives. Highlight that you actively sought to understand the other party's point of view, not just advocate for your own. |
| McKinsey / BCG / Bain | Personal Impact | Consulting firms want to see that you used structured reasoning and data to resolve the conflict — not charm or authority. Frame your actions in terms of how you made the case analytically. |
| KPMG / EY | Teaming / Integrity | Focus on the process of resolution, not just the outcome. These firms value transparency and fairness in how conflicts are handled, not just speed of resolution. |
Amazon is explicit about expecting employees to voice strong disagreement and then — once a decision is made — commit to it fully without ongoing reservation. An ideal answer for Amazon includes a moment where you made your case clearly, the decision went against your recommendation, and you then threw your full effort behind the chosen direction. That arc is exactly what their Leadership Principles are testing for.
5 Full Example Answers
The following examples cover a range of backgrounds. Select the one closest to your own experience and adapt it — do not use any of these verbatim. The most compelling answers are always specific and personal, not generic.
Example 1: University Group Project (Undergraduate)
"During my second year, I was part of a four-person team completing a financial modelling assignment worth 40% of the module grade. Midway through, my teammate and I disagreed sharply about how to structure the DCF model — he wanted to use a simplified single-stage Gordon Growth Model for speed, while I believed a two-stage model was necessary given the company's high near-term growth trajectory. It was a substantive technical disagreement, and both of us had invested time building our respective approaches.
I asked if we could spend 30 minutes comparing both models side by side rather than arguing in the abstract. I built a quick sensitivity table showing how the two approaches diverged at different terminal growth rate assumptions. When we looked at the numbers together, it became clear that in the specific scenario we were analysing — a company with a four-year high-growth phase — the single-stage model undervalued it by roughly 18%. That was a meaningful difference for a finance assignment.
He agreed we should go with the two-stage approach. We split the modelling work to save time and finished the assignment ahead of schedule. We received a distinction, and the examiner's feedback specifically praised the rigour of the valuation methodology. More importantly, we went on to collaborate on two further projects that year — the disagreement actually built mutual respect, because we both knew we were each willing to argue on substance and back it up with evidence."
Example 2: Internship / Work Placement
"During my summer internship in the operations team, I was asked to produce a report comparing two vendor contracts. I identified what I believed was a significant discrepancy in the way costs were being categorised — a categorisation that, in my reading, was inflating the apparent cost of the preferred vendor. When I raised this with the analyst overseeing the project, she disagreed and told me the categorisation was standard practice and that the report should proceed as-is.
I did not want to simply defer, but I also did not want to create conflict that would undermine our working relationship. I asked if I could take an hour to document my concern with supporting references from the firm's own cost-accounting guidelines, and then bring it back to her to review together. She agreed. When I presented the comparison, she could see that the guidelines did support my categorisation approach, but she also explained context I had not had — a prior decision made by the finance director about how to handle these specific contract types. That context changed my view: the original categorisation was defensible after all, given that background.
We submitted the report with a footnote clarifying the categorisation methodology, which satisfied both of our concerns. I learned that raising a concern clearly and with evidence, while staying genuinely open to being wrong, is a much more effective approach than either deferring immediately or digging in. The analyst mentioned my approach favourably in my end-of-internship feedback."
Example 3: Student Society / Extracurricular Leadership
"As president of the university investment society, I faced a significant internal disagreement about the direction of our annual stock pitch competition. The events committee wanted to open it to all students across the university, arguing that broader participation would raise our profile. Our existing core members — about 30 dedicated members who had built the competition over three years — strongly preferred to keep it exclusive to finance students, worried that opening it up would dilute the technical quality of pitches and the prestige of winning.
Both groups had entirely legitimate points. I arranged a joint meeting rather than trying to decide unilaterally. I asked each side to present their case in ten minutes, then opened it to questions between the two groups. What emerged from the discussion was a middle path: we would create two competition tracks — an open track with a more accessible brief, and an advanced track with full DCF and valuation requirements. Both groups felt heard. The core members retained the prestige they valued, and the events committee achieved the broader engagement goal.
That year's competition had 115 entrants — a 40% increase — with no drop in the quality of the advanced track finalists. Two of the society's long-standing members told me afterwards that it was the best decision we had made in years. What I took from it was that most conflict between legitimate groups is actually a problem of framing — once you stop treating it as either/or and start looking for structural solutions, the energy changes."
Example 4: Part-Time Job (Customer or Colleague Conflict)
"While working part-time in a busy café during my degree, I had a recurring tension with a colleague about how we divided closing duties. She felt that I consistently left the harder cleaning tasks for her, and she raised it with me directly, which I actually respected — though my initial reaction was defensive because I thought I was contributing equally. I could tell she was frustrated, so I did not argue in the moment. I asked if we could talk through it properly at the end of the shift when things were quieter.
When we sat down, I listened to her specific examples rather than immediately defending myself. She was right that on two specific nights I had signed off the floor before the deep-clean was done, which left more for her. I had not realised she was absorbing that extra work — I had assumed the earlier tasks I completed balanced it out, but from her perspective they did not. I apologised genuinely and suggested we create a shared checklist so we could both see in real time what was complete and what was not. She agreed, and we proposed it to the manager, who implemented it for the whole team.
The tension disappeared within a week. We went on to work closely together for the rest of the year with no further issues. I learned that when someone raises a grievance directly, treating it as a genuine problem to solve together — rather than a personal attack — changes the entire dynamic of the conversation."
Example 5: Challenging a More Senior Person
"On a consulting internship, I was part of a team preparing a client presentation on operational efficiency. Three days before the presentation, a senior analyst decided to remove a slide I had built showing variance in process cycle times across the client's regional offices. His reasoning was that it was too granular and the client's leadership team would not engage with it at that level of detail.
I thought this was a mistake — the regional variance was actually the core insight that explained the performance gap the client had hired us to diagnose. Without it, the recommendation section lost its evidential foundation. I did not challenge him in the team meeting, but I asked afterwards if I could walk him through my reasoning one-to-one. I prepared a one-page summary showing how the regional data underpinned each of the three recommendations, and which recommendation would look unsupported if that slide was removed. I also acknowledged his concern about executive attention spans and proposed a condensed version of the slide — three key numbers rather than the full chart.
He reviewed it and agreed that the condensed version addressed both concerns. That version made it into the final deck. During the client presentation, the regional variance data was the slide that prompted the most discussion — the regional operations director had not seen the data presented that way before. I learned that challenging a senior decision is most effective when you come with a solution, not just a counterargument."
Interviewers frequently follow up with "Can you give me a different example?" or "Do you have an example from a different context?" Preparing two strong examples from different settings (academic and professional, or professional and extracurricular) ensures you are never caught without a second story.
Follow-Up Questions to Expect
Interviewers at major graduate employers — particularly in finance and consulting — rarely accept the first answer without probing. The conflict question almost always generates at least one follow-up. Here are the most common ones and how to handle them.
"What would you do differently if you faced the same situation again?"
This is a self-awareness probe. The interviewer is testing whether you have genuinely reflected on the experience or whether you are simply reciting a prepared story. A strong answer acknowledges a specific thing you would change — not the other party's behaviour, but your own approach. For example: "I would raise the concern earlier rather than letting tension build," or "I would seek to understand their perspective before presenting my own view." Saying "I would not do anything differently" signals low self-awareness and should be avoided.
This cliché appears in around half of all conflict answers and immediately signals a rehearsed, generic response. Every interviewer has heard it dozens of times. If the team relationship did improve, describe specifically why — what changed in how you communicated, or what mutual respect developed from the experience.
"Was there ever a conflict you were unable to resolve?"
This is a credibility check. Claiming that every conflict you have ever experienced was neatly resolved would be implausible. A strong answer acknowledges a situation where resolution was partial or where you had to agree to disagree — and focuses on how you managed the situation professionally despite an imperfect outcome. What matters is that you remained constructive, kept the working relationship functional, and did not let unresolved tension undermine the project or team.
"How did the other person respond to your approach?"
This question tests whether your conflict resolution was genuinely two-way or whether it was simply you imposing your view more diplomatically. The best answers show that the other party's response was positive — that they felt heard, not overruled. If they were initially resistant, describe what you did specifically to shift that. If the resolution was primarily one-directional (they changed their position, you did not), be prepared to explain why that was the right outcome rather than just the comfortable one for you.
"What did you learn about yourself from that experience?"
Frame your learning around a concrete behavioural insight, not a generic growth observation. "I learned that I have a tendency to go into problem-solving mode before fully listening" is specific and credible. "I learned the importance of communication" tells the interviewer nothing. The best answers connect the lesson directly to something that changed in how you subsequently approached similar situations.
6 Mistakes That Sink Most Candidates
These are the patterns interviewers at graduate employers see repeatedly. Each one signals a different underlying weakness — and all of them are avoidable with preparation.
| Mistake | What It Signals to the Interviewer | How to Avoid It |
|---|---|---|
| 1. Making yourself entirely blameless | Low self-awareness; unreliable narrator | Acknowledge at least one thing you could have done better or earlier |
| 2. Spending most of the answer describing the conflict, not your actions | Missing the point of the question entirely | Keep S + C under 30% of your answer; Action should dominate |
| 3. Choosing a trivial disagreement | You have never had to navigate genuine difficulty | Pick an example with real stakes — project quality, team performance, a significant decision |
| 4. Describing a conflict with no resolution | Poor conflict management skills | If using an unresolved conflict, explain exactly how you managed it professionally despite that |
| 5. Being vague about your actual actions | You did not really handle this; you are embellishing | Use precise verbs: "I asked," "I prepared," "I proposed," "I initiated a meeting" |
| 6. Portraying the other party negatively throughout | Low emotional intelligence; difficulty working with others | Acknowledge the legitimacy of their position at some point, even if your approach was ultimately the right one |
The most common cause of rambling, vague conflict answers is not lack of preparation — it is candidates who have thought through their answer but never actually spoken it aloud. Delivery in an interview is meaningfully different from planning in your head. Time yourself: 90 seconds to 2.5 minutes is the target. If you are consistently running over 3 minutes, your Conflict section is too long. If you are under 60 seconds, your Action section is too thin.
Frequently Asked Questions
Prepare for Every Stage of the Hiring Process
From SHL aptitude tests to competency interviews — our practice platform and knowledge library cover everything you need to progress at Goldman Sachs, PwC, Amazon, Deloitte, KPMG and beyond.