Tell me about a time you disagreed with an engineer about a design decision

Behavioral CORE: Context, Obstacle, Resolution, Evaluation

What They’re Really Asking

Can you navigate cross-functional conflict while prioritizing user needs and business goals?

Framework: Use the CORE: Context, Obstacle, Resolution, Evaluation framework to structure your answer.

Strong Sample Answer

At Meta, I pushed back on an engineer who wanted to compress a newsfeed card to improve load time. Using Figma, I prototyped both versions and ran a 50-user A/B test on UserTesting. The compressed version increased load speed by 15% but reduced content comprehension by 22%, measured via recall quizzes. I presented data showing the full card led to 30% higher engagement and shared research on attention spans. We compromised: lazy-loaded images behind a skeleton screen, cutting load time by 10% while preserving comprehension. Engagement rose 18% with no drop in retention. That taught me to anchor disagreements on user data, not opinion.

Common Mistake to Avoid

Don’t do this: Framing the conflict as personal or ignoring the engineer's valid technical concerns.

Company-Specific Variants

Google Variant

At Google, pair your argument with launch metrics and a quantitative risk assessment of each option.

Apple Variant

At Apple, emphasize craft and visual polish, and validate with pixel-perfect prototypes in Origami.

Meta Variant

At Meta, reference data from internal A/B tests and tie the trade-off directly to growth or retention metrics.

📚 Recommended Resource

The 0-1 PM Interview Playbook (2026 Edition)

Product design thinking and UX interview frameworks used at Google, Apple, and Meta.

Get it on Amazon →