Cross-team conflict is normal — designers, backend, and frontend optimize for different things. Handling it well is about shared goals, curiosity over defensiveness, and constructive resolution.

Principles

1. Assume good intent. The designer isn't being difficult; the backend engineer isn't being lazy. Everyone's solving for their constraints. Start from "we both want a good product."

2. Anchor on the shared goal. Re-frame from "my way vs your way" to "what's best for the user / the product / the timeline." Conflicts shrink when the goal is explicit and shared.

3. Separate positions from interests. The position ("the API must return it this way") hides an interest ("I need to not break other consumers"). Ask why — understanding the underlying need usually opens up options nobody saw.

4. Communicate early, with data and options. Don't sit on a disagreement until it's a crisis. Raise it with specifics: the cost, the constraint, 2–3 options with tradeoffs. "This design causes a layout shift on mobile — here are two alternatives that keep the intent" beats "this won't work."

5. Talk, don't thread. For real disagreements, a 5-minute call beats a 30-comment thread. Tone is lost in text and conflict escalates.

6. Find the tradeoff, or escalate cleanly. Often there's a middle path — a phased approach, a small design tweak, a temporary shim. If you genuinely can't align, escalate to a manager/lead together, with the options laid out — not as a complaint, as "we need a tiebreak."

7. Disagree and commit. Once a decision is made — even if it wasn't your preference — commit to it fully. Re-litigating erodes trust.

Concrete examples

• With a designer: "A design needed an interaction that would've been janky on low-end devices. Instead of just refusing, I built a quick prototype showing the jank, then proposed a variation that kept the visual intent. We landed on the variation."
• With backend: "We needed data shaped differently than the API provided. Rather than demand a change, I asked about their constraints, learned it'd break another consumer, and we agreed on a new versioned endpoint — and I shimmed it on the frontend meanwhile so I wasn't blocked."

What interviewers listen for

Maturity, empathy, low ego, that you resolve through communication rather than escalation-as-first-resort or silent resentment — and that you can commit to decisions that didn't go your way. A real example makes it credible.