When you ask a director how disputes between two teams get settled, what should the answer contain?
answer
- Ask for a case, not a policy
- Who ends the argument here
- Listen for what the losing team dropped
- Warmth without a mechanism favours the loudest
- Dependencies decide how often this bites
basics
~20 sA usable answer names a decision owner or forum, gives a recent real dispute, states what was decided and says what the losing team dropped. Warmth without a mechanism means contested work goes to whoever pushes hardest.
solid answer
~50 sAsk it concretely — how a disagreement between two teams over the same work got settled recently, not how conflict is handled in general. What you want back has four parts: who or what decides, a specific recent case, the decision itself, and the cost the team that lost absorbed. Any of those missing is informative. `We're all adults, people work it out` sounds healthy and often means there is no owner, so contested priorities land with whoever escalates loudest or has the longer tenure. That matters more than usual for a backend team whose service is a dependency for three other teams, because you inherit every one of those arguments. Also listen for how the leader talks about the team that lost: whether their dropped work was tracked and rescheduled, or simply stopped being mentioned.
go deeper
Know that the useful version of this question asks for a specific recent example rather than a general policy. Have the sentence ready and let the leader talk without filling the pause.
Be able to name the parts of a complete answer — an owner, a case, a decision, and what the losing team dropped — and to notice out loud which part was missing.
Show that you can read an evasive or warm answer for what it implies about how contested work is really allocated, and connect it to the dependencies the team you would join carries.
Own the call about whether you can operate inside the arbitration mechanism you heard described, and be able to say what you would try to change about it in your first year if you joined.
## Why this is the highest-yield question in the skip-level round Cross-team arbitration is one of the few things a director can answer from direct experience, because they are often the person doing the arbitrating. It is also the mechanism you will spend real time inside if you join a backend team that other teams depend on. Most day-to-day pain in that position is not technical; it is three teams wanting incompatible things from the same service in the same quarter. ## Ask for a case, not a policy `How do you handle conflict between teams?` invites a values answer, and every organization's values answer is the same. Ask instead for the last time two teams wanted incompatible things from the same team, and what happened. A case has details that a policy does not: who convened, how long it took, what the decision was, and who absorbed the cost. ## The four parts of a usable answer **A decision owner or forum.** Someone or something ends the argument — a named review, a planning meeting where commitments are set, a leader who takes the call. The name matters less than its existence and the fact that the leader reaches for it immediately. **A real recent case.** Specificity is the tell. A leader who is describing a real mechanism reaches straight for an example; one who is describing an aspiration talks in general terms and then changes the subject. **The decision.** Someone got the work and someone did not. If the answer is that both teams were accommodated every time, either the example was not a real conflict or the resolution was to overload somebody, which you would then like to know about. **What the losing side dropped.** This is the part candidates forget to listen for and the part that carries the most information. A healthy answer tracks the dropped work: it goes back on a list, it gets rescheduled, its owner is told. An unhealthy one lets it evaporate, which over a few cycles is how a team ends up with a backlog of half-built commitments nobody will admit were dropped. ## Reading the answers you will actually get *`We're all adults and people work it out.`* Warm, and often true at small scale, but with no owner the outcome correlates with force of personality and tenure. Probe once: ask what happens when the adults do not agree. *`Escalation basically never happens here.`* Either the teams genuinely do not contend for the same resources — possible, and worth confirming by asking who else depends on this team — or escalation is culturally discouraged, which does not remove conflict, it drives it under the surface into slow work and quiet non-delivery. *`That would come to me.`* Honest and usually fine. Follow up on the input: what the leader wants to see before deciding. If the answer is a written case with the tradeoff spelled out, you have learned how to be effective there, which is worth the whole round. *A crisp case with a named forum and a tracked drop.* The best answer available, and it also tells you what your influence work would look like in the job. ## Feeding it back into the org chart Add the dependency arrows to the sketch you are keeping. If the team you would join sits under one bet but three other teams pull work from it, your real job is partly negotiation, and the quality of the arbitration mechanism determines whether that negotiation is survivable. A team with clear arbitration and a modest headcount range is often a better place to do good work than a team with a bigger plan and no way to end an argument. ## Two mistakes to avoid while asking Do not frame it as `is there a lot of conflict here` — that invites a denial and teaches you nothing. And do not read a weak answer as a verdict on the leader personally. You are testing a system, not the individual; a good leader can inherit a group where arbitration is still forming, and their honesty about that is itself a positive signal. What you want to leave with is a clear picture of how contested work gets decided, so you can judge whether you would be able to operate in it.
- How would you follow up if the director says such disputes simply do not arise?Test the premise rather than the claim: ask which other teams depend on this team's service and what happens when two of them want work in the same cycle. If several do and conflict is still described as absent, ask how those requests get sequenced. Either a mechanism surfaces or you have learned that it does not exist.
- Why does it matter what happened to the work the losing team gave up?It separates a decision from an evasion. Tracked and rescheduled work means someone owns the cost of the tradeoff; work that quietly disappears means commitments are being made that nobody reconciles. Over a few cycles the second pattern produces a backlog of half-finished promises that lands on whoever joins next.
- Does a leader saying disputes come to them personally count as a good answer?Usually yes, provided they can say what they want to see before deciding. A leader who asks for a written tradeoff is describing a repeatable path you can use. One who decides case by case on instinct is still a mechanism, but a slower and less predictable one, and worth noting on your sketch.
saying these in an interview costs you the question
- Asking whether there is much conflict, which only invites a denial
- Accepting a values answer instead of asking for a recent case
- Missing that no answer names who ends the argument
- Never asking what the team that lost had to drop
- Judging the leader personally instead of the mechanism they describe