Meta Business Analyst Interview Questions (2026)

1. 1Recruiter screen30 minEasy

   Process overview, level calibration, and prep guidance — Meta recruiters actively coach on round formats.

2. 2Technical screen45 minHard

   Two DSA problems in 45 minutes on a plain shared editor with no autocomplete or execution.

3. 3Coding round ('Ninja')45 minHard

   Two more problems at loop difficulty; clean near-compilable code and verbalized complexity analysis expected.

4. 4System design ('Pirate')45 minHard

   Design a Meta-scale product system (feed, Stories, chat) with emphasis on read-heavy fan-out, caching, and data modeling.

5. 5Behavioral ('Jedi')45 minMedium

   Deep past-experience discussion on conflict, growth, and impact aligned to Meta values; graded as a real signal round.

1. Q1

   Design an A/B test for a new Facebook Feed ranking or recommendation change. Define hypothesis, primary metric, guardrails, randomization unit, and launch decision rule

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Context: Meta wants to balance engagement, creator health, and advertiser value.

   How to answer: A strong answer will define a clear, testable hypothesis for the Feed change (e.g., 'New algorithm increases user engagement'). The primary metric should directly reflect this hypothesis, such as 'total time spent in Feed' or 'number of unique posts viewed.' Crucial guardrail metrics like 'negative reactions per post' or 'uninstalls' must be identified to prevent unintended harm. The randomization unit should be the 'user ID' to ensure consistent experience, and the launch decision rule should involve statistical significance on the primary metric while ensuring no significant negative movement on guardrails.

2. Q2

   For Instagram Reels, should randomization happen at user, session, device, advertiser, or country level? Explain the tradeoffs

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Consider cross-device behavior, interference, marketplace effects, and operational feasibility.

   How to answer: Randomization for Instagram Reels should primarily happen at the user level to ensure independent observations and avoid contamination. User-level randomization allows for consistent treatment exposure across sessions and devices for the same user, which is crucial for measuring user-centric metrics like engagement and retention accurately. Session-level or device-level randomization can lead to a single user experiencing both control and treatment, contaminating results. Advertiser or country-level randomization might be appropriate for specific experiments targeting those entities, but not for general product feature A/B tests on Reels.

3. Q3

   Choose primary and guardrail metrics for a WhatsApp Business experiment aimed at improving meaningful social interaction rate. What metrics would prevent a harmful launch?

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Include user experience, partner health, revenue, reliability, and long-term retention considerations.

   How to answer: A strong candidate would identify 'meaningful social interaction rate' as the primary metric, defining it concretely (e.g., messages exchanged in a 1:1 or group chat, excluding automated replies or short, transactional messages). For guardrail metrics, they would propose 'message send rate' (overall volume), 'user retention' (D1, D7, D28), and 'block/report rate'. These guardrails ensure the experiment doesn't inadvertently increase spam, reduce overall engagement, or lead to negative user experiences.

4. Q4

   During a Marketplace experiment, the treatment/control split is 52/48 instead of 50/50. How would you diagnose sample ratio mismatch?

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Assume assignment logs, exposure logs, and eligibility filters may disagree.

   How to answer: A strong candidate would first confirm the SRM by checking the actual user counts in treatment and control groups against the expected split, and then perform a chi-squared test for statistical significance. To diagnose, they would investigate the randomization logic for potential bugs, such as incorrect bucket assignment or user ID hashing issues. They would also check for instrumentation errors, like data logging discrepancies or delayed event processing, and examine user eligibility criteria or pre-experiment filters that might inadvertently bias one group.

5. Q5

   The Stories experiment is trending positive after two days. A PM wants to stop early and launch. How do you handle peeking and sequential testing?

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Discuss pre-specified stopping rules, alpha spending, business urgency, and risk.

   How to answer: Explain that peeking early invalidates statistical significance due to increased Type I error rates. Discuss the importance of pre-determining sample size and experiment duration based on MDE and power. Suggest methods to mitigate peeking issues, such as using sequential testing methods (e.g., Always Valid p-values, sequential probability ratio tests) or Bonferroni correction if multiple peeks are unavoidable. Emphasize communicating the risks to the PM and advocating for the original experiment plan.

6. Q6

   A new Ads Manager feature shows a large week-1 lift in meaningful social interaction rate, but the effect fades by week 4. What could explain this and how would you design the test duration?

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Discuss novelty, learning effects, seasonality, and durable impact.

   How to answer: The fading effect could be due to novelty effect, where users initially engage more with a new feature but revert to previous behaviors as the novelty wears off. It could also be attributed to selection bias if early adopters are more engaged, or a learning curve where users initially struggle but then adapt. To design the test duration, consider the typical user adoption cycle and the feature's expected long-term impact. A minimum of 4-6 weeks is often necessary to observe stabilization and account for weekly cycles, with longer durations for features with delayed impact or significant learning curves.

7. Q7

   In a marketplace-like Facebook Feed feature, treatment users may affect control users. How would network effects or interference bias the experiment?

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Examples include advertiser supply, content inventory, delivery capacity, or pricing pressure.

   How to answer: Network effects, or 'interference,' in a marketplace-like Facebook Feed bias A/B test results by violating the Stable Unit Treatment Value Assumption (SUTVA). Specifically, if treatment users' actions (e.g., posting more, commenting differently) are seen by control users, it can either dilute the treatment effect in the treatment group or induce a 'spillover' effect in the control group. This leads to an underestimation of positive treatment effects or an overestimation of negative ones, as the control group is no longer a true baseline. The observed difference between groups will be smaller than the true impact of the feature.

8. Q8

   meaningful social interaction rate is a low-frequency event for Instagram Reels. How would you set up an experiment with enough power without waiting too long?

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Discuss proxy metrics, variance reduction, larger samples, longer windows, and risk of metric gaming.

   How to answer: To address the low-frequency nature of meaningful social interactions (MSI) on Instagram Reels, I would first consider using a proxy metric that is highly correlated with MSI but occurs at a higher frequency, such as 'likes on Reels' or 'shares of Reels'. Alternatively, I would explore increasing the exposure of the experiment by running it on a larger user base or for a longer duration, if feasible within business constraints. Another approach is to use a more sensitive statistical test, like a non-parametric test, or to focus on a subset of users who are more likely to engage in MSI, such as power users or users who have previously engaged in MSI. Finally, I would ensure the experiment design minimizes variance by using a pre-post analysis or CUPED (Controlled-experiment Using Pre-Experiment Data).

9. Q9

   Design a geo or country-level experiment for WhatsApp Business. When is this better than user-level randomization, and what are the analytical downsides?

   MediumStatistics & Experimentation RoundA/B TestingMeta-specific

   Context: Use matched markets, pre-period balancing, spillover checks, and fewer experimental units.

   How to answer: A geo-level experiment for WhatsApp Business involves randomizing entire countries or regions to either a treatment or control group, rather than individual businesses or users. This approach is superior when there are strong network effects, spillover effects between users in the same geography, or when the feature inherently requires a country-wide rollout (e.g., regulatory changes, payment integrations). However, it significantly reduces statistical power due to fewer experimental units, making it harder to detect small effects and increasing the risk of imbalance across groups due to confounding variables. Analytical downsides include increased variance, longer experiment durations, and challenges in causal inference due to potential unobserved differences between geo units.

10. Q10

    The Marketplace experiment lifts meaningful social interaction rate overall, but only for new users and only in one country. How would you evaluate heterogeneous treatment effects?

    HardStatistics & Experimentation RoundA/B TestingMeta-specific

    Context: Balance pre-planned segments with exploratory slicing and multiple testing risk.

    How to answer: A strong candidate would first define heterogeneous treatment effects (HTE) and explain why subgroup analysis is critical here. They would then propose specific methodologies like interaction terms in regression models (e.g., OLS or logistic regression, depending on the outcome) to statistically test for HTE across user cohorts (new vs. existing) and geographies. The answer should also cover practical considerations such as pre-registration of hypotheses to avoid p-hacking, ensuring sufficient sample size within subgroups for statistical power, and potentially using causal forest or uplift modeling for more complex HTE discovery if initial hypotheses are insufficient.

11. Q11

    Treatment improves meaningful social interaction rate but worsens feed load time for Stories. Walk through a launch recommendation

    HardStatistics & Experimentation RoundA/B TestingMeta-specific

    Context: Make a decision under conflicting metrics and quantify tradeoffs for stakeholders.

    How to answer: A strong recommendation requires quantifying the trade-off between meaningful social interaction (MSI) and feed load time. This involves understanding the business value of MSI (e.g., retention, engagement) and the user tolerance/impact of increased load time (e.g., abandonment, frustration). The recommendation should propose further analysis, such as segmenting users to see if the impact varies, and potentially suggest an adaptive solution or a phased rollout with close monitoring. Ultimately, a decision matrix or weighted scoring model comparing the long-term strategic value of MSI against the short-term user experience degradation is needed, with a clear go/no-go or iterative improvement plan.

12. Q12

    How would you design ramp-up, holdback, and post-launch monitoring for a successful Ads Manager A/B test?

    HardStatistics & Experimentation RoundA/B TestingMeta-specific

    Context: Include ramp stages, persistent holdback, alert thresholds, rollback criteria, and owner accountability.

    How to answer: A strong answer outlines a phased ramp-up strategy, starting with a small percentage (e.g., 1-5%) of traffic, closely monitoring key health metrics and primary KPIs for anomalies before gradually increasing exposure. For holdback, the candidate should propose reserving a small, unexposed control group (e.g., 1-2%) for an extended period to detect long-term novelty effects or contamination. Post-launch monitoring involves continuous tracking of critical business and system health metrics, setting up automated alerts for significant deviations, and establishing a review cadence to ensure sustained performance and identify potential regressions or interactions with other features.

13. Q13

    Midway through the Facebook Feed test, tracking for WhatsApp Business changed. How would you decide whether the experiment results are still usable?

    HardStatistics & Experimentation RoundA/B TestingMeta-specific

    Context: Compare instrumentation versions, affected traffic share, raw logs, and sensitivity analyses.

    How to answer: A strong candidate would first identify the potential impact of the tracking change on the experiment's validity, specifically concerning metrics related to WhatsApp Business. They would then propose analyzing the timing of the change relative to the experiment's start and the observed data patterns before and after the change in both control and treatment groups. Key steps include checking for a sudden shift or discontinuity in WhatsApp Business metrics, assessing if the change affected both groups equally (indicating a systemic issue rather than an experiment effect), and determining if the primary metrics of the Facebook Feed test are directly dependent on WhatsApp Business tracking. Finally, they would recommend a decision based on the scope and symmetry of the impact: either continue with caution, adjust analysis, or invalidate and restart.

14. Q14

    Two overlapping experiments on Instagram Reels both affect ad CTR and revenue per user. How would you detect and manage interaction effects?

    HardStatistics & Experimentation RoundA/B TestingMeta-specific

    Context: Discuss experiment registry, factorial design, exclusion rules, and interaction terms.

    How to answer: A strong candidate would first emphasize the importance of pre-experiment design to minimize overlap, but acknowledge it's not always possible. They would then discuss detection methods like subgroup analysis (users in both experiments vs. only one), interaction terms in regression models, and comparing observed vs. expected combined effects. For management, they would propose strategies such as sequential rollout, re-randomization, or using a robust causal inference framework like CUPED or switchback experiments if applicable, ultimately prioritizing user experience and revenue.

15. Q15

    Meta's Facebook Feed revenue suddenly drops 10% week over week. Structure a business case to diagnose the issue and identify the most likely drivers

    MediumProduct Analytics & Business CaseBusiness CasesMeta-specific

    Context: Consider traffic, conversion, pricing, mix, supply/inventory, outages, marketing, and seasonality.

    How to answer: A strong business case would first define the problem (10% WoW revenue drop in Facebook Feed), quantify its impact, and establish a clear objective to diagnose and mitigate. The candidate should then structure their analysis by segmenting the revenue drop into key components like user count, engagement (time spent, impressions), ad load, and eCPM (bid price, CTR, conversion rate). Prioritization of potential drivers should follow, starting with recent changes (product launches, policy updates, major bugs) and external factors (competitor actions, seasonality, macroeconomic shifts). Finally, the candidate should propose specific data points and analyses needed for each prioritized driver, outlining a clear path to identify the root cause and potential solutions.

Practice these with instant AI feedback in a live mock interview → Start a Meta Business Analyst mock

Be fast and correct on coding; for design, drive the conversation; prepare impact-focused behavioral stories

Indicative Business Analyst pay in India: ~₹7–26 LPA (role-level range, not a Meta-specific figure).

Other roles at Meta

Business Analyst interviews at other companies