"Tell me about a time you had to explain a sudden drop in an important metric to a non-technical stakeholder — for example, a PM or business lead for Facebook Feed, Instagram Reels, or Ads Manager. How did you investigate what happened, communicate the uncertainty, and align people on next steps?"
This question tests whether you can translate analytics into clear business language under pressure. At Meta, Business Analysts are often the bridge between data systems and decision-makers, so interviewers want to see ownership, structured thinking, and the ability to communicate confidently even when the root cause is not yet fully known.
It also probes how you handle ambiguity: whether you jump to conclusions, hide caveats, or instead separate facts from hypotheses and drive action. Strong candidates show they can calm stakeholders, preserve trust, and influence decisions without overstating certainty.
A strong answer uses a specific example with real stakes, explains how you validated whether the drop was real versus a logging or definition issue, and shows how you tailored the message for a non-technical audience. The best responses include quantified impact, a clear recommendation, and what you learned about communicating under uncertainty.