Tell me about a conflict you had to resolve among teams and one that you had with your manager.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This question tests whether you can navigate disagreement in two different power dynamics: peer-like cross-team conflict and upward conflict with your manager. Interviewers want to see whether you can separate positions from underlying constraints, stay constructive under tension, and reach outcomes that preserve trust rather than just "win." They are also checking whether the scale and complexity of your examples match your level.
Key Insights
- Conflict does not need to be dramatic or emotional. Strong answers often describe misaligned incentives, different risk tolerance, or competing priorities, then show how you surfaced and reconciled those differences.
- You should show your own contribution to the situation, even if it was small. Honest ownership signals maturity; stories where everyone else was unreasonable usually read as low self-awareness.
- Because the question asks for both team-to-team conflict and conflict with your manager, interviewers are looking for range. Show that you can handle disagreement without authority in one case and with a power imbalance in the other.
What interviewers probe atlevel
Top Priority
At junior level, you do not need to solve everything alone, but you should still show initiative instead of acting like conflict resolution belongs entirely to someone more senior.
Good examples
🟢I prepared a short comparison of the options and shared it with my lead and the partner engineer so we could have a more productive conversation instead of talking past each other.
🟢When I disagreed with my manager, I came back with a revised plan that addressed his main concern rather than just defending my original idea.
Bad examples
🔴I brought it to my lead right away because it was really their job to sort things out with the other team.
🔴My manager and I disagreed, so I just did what he asked and moved on.
Weak answers hand the problem off; strong answers show appropriate initiative, even if a lead or manager is involved.
Valuable
Example answers atlevel
Great answers
One cross-team conflict I dealt with was with a QA engineer from another team during a small feature launch. I thought we could test the happy path and ship, but she was worried because a similar change had caused regressions before. I set up a quick chat, asked which scenarios were making her nervous, and we agreed on two additional checks that were cheap to add but covered the risky cases. We shipped a day later than I originally hoped, but without issues, and after that I started involving QA earlier. A separate conflict with my manager was about how much refactoring to do before adding a new endpoint. I wanted to clean up a larger section first, but he was concerned about timeline risk, so I proposed doing the smallest cleanup needed now and creating a follow-up task for the rest. That let us deliver on time and still improve the code in a controlled way.
On a small mobile app project I worked on, the design team wanted an eye-catching animated onboarding flow but the Android developers were worried it would slow down older phones. I paired with a designer to build a very small prototype and ran a short experiment with a handful of users and device-performance checks; the result showed the full animation only hurt a small subset of low-end devices, so we agreed to ship a simplified animation for those devices and the full version elsewhere. Separately, I had a disagreement with my manager about how to spend my next sprint: he wanted me to focus entirely on triaging a pile of bugs, while I was excited to own a tiny usability improvement I thought would reduce support tickets. I explained that shipping the improvement would likely reduce future triage work and proposed splitting my time—one day a week for focused bug triage and the rest building and testing the UI change—then committed to extra bug-help if the triage backlog grew. That compromise let the team make progress on both fronts and taught me to use small experiments and clear trade-offs when mediating between teams and managers.
Poor answers
For cross-team conflict, I once worked with another engineer who kept asking for extra changes before approving our work. I had already built the feature, so I explained that my approach was simpler and eventually they signed off. With my manager, I wanted to do something a different way, but he preferred a more cautious approach. I pushed for my idea because it would have been faster, and after some discussion we used most of my plan.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early July, 2026
Late June, 2026
Late June, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.