How Meta interviews Business Analysts

Meta does not publish a Business Analyst specific process. The only published loop is for software engineers, so it appears here with that label, as a guide to Meta's interview style rather than to a business analyst's rounds.

• Technical screen (software engineers). A 45-minute conversation with a Meta engineer, mostly coding: 5 minutes of introductions, 35 minutes of coding, 5 minutes for questions, in a collaborative editing tool when remote.
• The full loop (software engineers). A coding interview, a design interview, and a behavioral interview covering previous work experience and motivations, with the design and behavioral interviews each 45 minutes.

What a business analyst can take from that is the style: time-boxed single-topic interviews and a separate behavioral conversation about past work and motivation. Meta does not publish the number of rounds for analysts, whether there is a case exercise, or who interviews. Screen, case, behavioral and onsite are preparation categories on this page, not Meta's round names.

The published loop separates execution, design and previous work. A business analyst should prepare for the same separation with analyst content, while treating that as inference from the engineering loop rather than a published format.

Business Analyst interviews in general assess:

• Requirements and stakeholder analysis. Turning a vague request into testable requirements and knowing whose sign-off each needs.
• Process mapping. Describing how work flows, where it breaks and what a change costs.
• Data-backed recommendations. Choosing a measure, reading it honestly and recommending one option with its risks; at a company that publishes a coding-heavy loop for engineers, expect the data part of this to be taken seriously.
• Communication. Explaining the same finding to an engineer and to a director without changing its meaning, which is what a behavioral interview about previous work will probe.

Meta publishes no role-specific formats beyond software engineering, so the differences below are general practice.

• Compared with Data Analyst interviews, expect less live SQL and more on requirements, process and the organizational side of change: who owns the problem, who approves the fix, what breaks downstream.
• Compared with Product Manager interviews, expect less on product vision and roadmap prioritization and more on analyzing an existing process or system and building the case for improving it.
• Compared with the published engineering loop, the design conversation, if there is one, would be about a process or a decision rather than a system, and the coding block would be replaced by a case or an analysis exercise.

The published durations are per interview: 45 minutes, with 35 minutes of coding in the coding interviews for software engineers. Meta does not publish a timeline for any role.

If analyst interviews follow the same time-boxing, the difficulty is compression: a case has to be structured, analyzed and concluded inside one block, and a past project has to be described precisely in a separate conversation. Practice structuring an ambiguous problem in the first few minutes and reaching a recommendation before time runs out.

Mirror the published separation of execution, design and behavioral, filled with analyst material.

• Timed cases. Practice taking a vague business problem to a structured recommendation in a fixed block, aloud.
• Requirements stories. Two or three cases where a vague ask became testable requirements, including the stakeholder you had to persuade.
• A process map from memory. The before, the bottleneck, the change and the measured result.
• Previous work and motivations. The published behavioral interview covers both; prepare specific incidents and an honest reason for wanting this role.
• Rehearse the format. A mock interview with SubcueAI lets you practice a single time-boxed case followed by questions.