Tell me about a time you handled conflict between engineering and business stakeholders

Problem Statement Description

Product context: Adobe is a creative, document, and marketing software company; its products include Creative Cloud, Photoshop, Illustrator, Acrobat, Adobe Express, Firefly, and Experience Cloud.

Adobe product teams often operate at the intersection of creative workflow depth, enterprise trust, AI-enabled capabilities, and business growth goals. In this behavioral question, you are being asked to describe a real situation where engineering and business stakeholders were in conflict, and you played a meaningful role in moving the team toward a decision or outcome.

Frame your example in a product environment relevant to Adobe’s work, such as Acrobat workflows for creative professionals, collaboration between document and media teams, enterprise customer requirements, AI feature delivery, monetization pressure, or quality and trust concerns. The conflict should be substantive: for example, a disagreement over scope, technical feasibility, launch timing, customer commitments, data/privacy risk, performance trade-offs, or revenue impact.

Your response should show how you understood both sides, clarified the real decision at stake, created alignment without simply escalating or compromising prematurely, and helped the team make progress. The strongest examples will demonstrate ownership, judgment under ambiguity, stakeholder empathy, and measurable product or team impact.

The experience should consider:

- The specific product, customer, and business context behind the conflict.

- Who the engineering and business stakeholders were, and what each side cared about.

- Your role, authority level, and how directly you influenced the outcome.

- How you separated facts, assumptions, risks, and emotions in the disagreement.

- The trade-offs involved, such as speed versus quality, revenue versus trust, or scope versus feasibility.

- How you communicated, facilitated decision-making, and maintained working relationships.

- The outcome for users, the business, the technical system, and the team.

- What you learned and how it changed your approach to future cross-functional conflicts.

The goal is to evaluate whether you can lead through difficult product tensions in a complex organization like Adobe, where high-quality execution, customer trust, creative workflows, and commercial priorities must be balanced thoughtfully.