Tell me about a conflict you had to resolve among teams and one that you had with your manager.
Asked at:
NVIDIA
Meta
Rubrik
Oracle
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.
“Tell me about a time you had to navigate a disagreement with another team, and another time you pushed back on your manager.”
“Can you share one example of resolving cross-team friction and one example of handling a disagreement with your boss?”
“Describe a situation where you and a partner team were misaligned. Then describe a separate situation where you and your manager saw things differently.”
“What is a meaningful conflict you've worked through with another team, and what is one you've worked through with your manager?”
“Have you ever had to settle a tough disagreement across teams? How about with your manager?”
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, interviewers mainly want to see that you did not treat disagreement as a battle of opinions and that you tried to understand why others were pushing back.
Good examples
🟢I realized the other team was worried about support load because they had been paged for similar issues before, so I asked what failure modes they were most concerned about before proposing changes.
🟢When my manager pushed back on my timeline, I asked what tradeoffs he was seeing that I was missing, and that surfaced a launch dependency I hadn't considered.
Bad examples
🔴The other team kept blocking us, so I just explained again that our approach was simpler and asked my lead to back me up.
🔴My manager wanted extra testing, but I already knew the change was safe, so I tried to convince him we were overthinking it.
Weak answers assume resistance is irrational; strong answers investigate what legitimate concern sits underneath the disagreement.
A good junior answer ends with a workable solution and a healthy relationship, not just with you being proven right.
Good examples
🟢We adjusted the implementation to include the safeguards the other team wanted, and after launch they were comfortable working with us on similar changes.
🟢My manager and I landed on a smaller first step, and once it worked we expanded it, which built trust for future design discussions.
Bad examples
🔴Eventually they accepted my suggestion, and we used my version.
🔴My manager agreed after I explained it again, so that worked out.
Weak answers define success as winning; strong answers define success as a solution others can genuinely support.
Valuable
Interviewers know upward conflict is harder, so they want to see respectful candor with your manager and professionalism with peers.
Good examples
🟢I brought my concern to my manager in a one-on-one so I could ask questions and understand his reasoning without putting either of us on the spot.
🟢With the other team, I tried to separate the technical disagreement from the person and kept the conversation focused on tradeoffs.
Bad examples
🔴I kept pushing my manager in the meeting because I wanted everyone to hear the better option.
🔴The other engineer was wrong, so I was pretty direct that their concerns did not make sense.
Weak answers ignore how context and audience affect disagreement; strong answers choose a respectful channel and tone.
Your story can be small, but it should still matter enough to show judgment and collaboration under real tension.
Good examples
🟢The disagreement affected how two small components would integrate and whether we could ship on time, which was meaningful for my role.
🟢My manager and I disagreed about how much validation to add before release, which mattered because it affected customer impact and my team's workload.
Bad examples
🔴The conflict was basically about whether to use tabs or spaces in a shared file, and I helped settle that with my manager.
🔴Another team wanted a different variable name, and we talked it through.
Weak answers pick conflicts too trivial to reveal much; strong answers pick situations with enough consequence to show real judgment.
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.
Late June, 2026
Rubrik
Manager
Mid February, 2026
Meta
Manager
Early January, 2026
NVIDIA
Senior
Hello Interview Premium
Your account is free and you can post anonymously if you choose.