Behavioral: how do you handle disagreements with PMs or designers
Frame it around shared goals (user value, business outcome) rather than 'engineering vs. design'. Understand their constraints first, bring data or a quick prototype, present trade-offs not vetoes, and be willing to disagree-and-commit. Show you respect that PMs own priorities and designers own UX — your job is to make the trade-offs visible.
Disagreements with PMs and designers are different from peer conflicts: you're working across functions, each with different priorities. The interviewer wants to see you collaborate, not gatekeep.
The core principle: shared goal, different lenses
A PM owns priorities and business outcomes. A designer owns user experience. You own feasibility, performance, and maintainability. A disagreement usually means these lenses are pointing at the same goal from different angles — your job is to make the trade-offs visible, not to "win".
How to handle it — the steps
- Understand their constraint first. Ask why before you push back. A designer's "we need this exact animation" might be protecting a brand standard; a PM's "ship Friday" might be tied to a marketing date.
- Translate the cost into their terms. Don't say "that's hard." Say "that animation re-renders the list on every frame — it'll jank on mid-range Android, which is 40% of our users." Now it's a UX problem the designer cares about.
- Bring options, not a veto. "We can do A (the full design, 2 extra days), B (90% of it, ships Friday), or C (ship Friday, polish next sprint)." Let them choose with full information.
- Prototype when words fail. A 30-minute spike showing the perf cost or a slightly different interaction often ends the debate instantly.
- Disagree and commit. If you're overruled on a reversible decision, commit fully. Save the hill-to-die-on for things that are genuinely risky (security, data loss, accessibility).
A short STAR example
A designer wanted a custom-built date picker for brand consistency. I was worried about accessibility and maintenance. Instead of refusing, I showed them the keyboard/screen-reader gaps in the mock, and proposed we restyle an accessible headless library to match the brand. They got the look, we got accessibility and less code to own. Shipped on time.
What interviewers listen for
- You respect their domain — you don't think you should decide priorities or UX.
- You lead with curiosity ("help me understand…") not resistance.
- You quantify the trade-off so it's a shared decision.
- You know when to commit and when to escalate.
Senior framing
The senior signal is that you see PMs and designers as partners with different accountabilities, not obstacles. You make the implicit trade-offs explicit and let the right owner decide — and you escalate only the rare things that are truly non-negotiable. Engineers who "block" design and PM come across as hard to work with; engineers who inform decisions come across as senior.
Follow-up questions
- •When would you escalate a disagreement with a PM instead of committing?
- •How do you push back on scope without sounding like you're just avoiding work?
- •A designer insists on a pattern you know hurts performance — walk me through it.
Common mistakes
- •Saying 'that's not possible' instead of presenting trade-offs.
- •Treating it as 'engineering vs. design' rather than a shared goal.
- •Never committing — relitigating every overruled decision.
- •Dying on every hill instead of saving capital for what matters.
Edge cases
- •Non-negotiables (security, data loss, accessibility, legal) — here you must escalate, not just commit.
- •Repeated disagreements with the same person may be a process problem (engineers not in design reviews early enough).
Real-world examples
- •Scope vs. deadline, custom design vs. accessible component library, 'pixel-perfect' vs. responsive realities.