"Tell me about a time you had to set or reset expectations with both your engineering team and cross-functional stakeholders — for example with Product, Design, or XFN partners working in Workplace, Facebook, or Instagram surfaces. What was the situation, how did you communicate trade-offs, and what happened in the end?"
This question tests whether you can create clarity when different groups want different things. For an Engineering Manager at Meta, setting expectations is not just about status updates; it is about aligning on scope, timelines, risks, ownership, and decision-making when there is ambiguity or pressure. Interviewers want to see whether you can be transparent without creating panic, push back when needed, and keep both your team and stakeholders committed to the same plan.
A strong answer uses one specific example with real stakes, such as a launch, dependency, replan, or missed milestone. The best responses show how you tailored communication to different audiences, used data or milestones to anchor expectations, and took ownership for the outcome — including what you learned and how you improved your approach afterward.
