Your question is Delivering a Timeline Slip. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Tell me about a time you had to deliver bad news to a stakeholder that a project would miss its timeline. What was the situation, how did you communicate it, and what did you do next?
At Meta, Business Analysts often work across Product, Engineering, Data Science, and Operations, where timelines can shift because of data quality issues, changing scope, privacy reviews, or upstream dependencies in tools like Meta's internal dashboards and reporting workflows. This question tests whether you surface risk early, communicate clearly under pressure, and take ownership of the recovery plan instead of just reporting a delay.
Interviewers are looking for judgment: how you balanced transparency with credibility, how you handled stakeholder reactions, and whether you influenced next steps without formal authority. They also want to see whether you could separate what was truly blocked from what could still ship.
A strong answer uses one specific example with real stakes, names when you realized the timeline was at risk, explains exactly how you delivered the message, and shows the concrete mitigation plan you drove afterward. The best responses are structured in STAR format, quantify the impact, and include what you learned about communicating bad news earlier or better.