Navigate Stakeholder Conflict During a Compressed Delivery Timeline
Company: Meta
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: hard
Interview Round: Onsite
## Interview Prompt
Describe a project whose deadline moved earlier after work had started and where
stakeholders disagreed about what should ship. Explain how you surfaced the
conflict, evaluated a solution that was not working, persuaded a manager or
partner to change course, and incorporated constructive feedback from a senior
engineer.
### Constraints & Assumptions
- Use one specific project with a clear original plan and revised deadline.
- Distinguish facts, stakeholder preferences, and your own recommendation.
- Include the delivered outcome and a concrete signal that showed whether the trade-off worked.
### Clarifying Questions to Ask
- Which constraint changed: scope, staffing, quality bar, or launch date?
- Who had decision authority, and who bore the risk of a reduced scope?
- What feedback materially changed your approach?
### What a Strong Answer Covers
- Early, direct communication of risk instead of silently attempting the impossible plan.
- A decision framework that compares scope cuts, sequencing, staffing, and operational risk.
- Respectful handling of competing opinions with evidence and an explicit decision owner.
- A measurable result, candid shortcomings, and a lesson applied afterward.
### Follow-up Questions
- What would you have done if the manager rejected your proposed scope cut?
- Which quality safeguard was non-negotiable despite the deadline?
- How did you repair trust with a teammate who preferred the original plan?
Overview: Describe a project where a deadline moved earlier and stakeholders disagreed about what should ship. Explain how you exposed the conflict, tested a failing approach, incorporated senior feedback, changed course, and used a concrete result to assess the compromise.
Read the full Meta Software Engineer interview experience this question came from