How Meta interviews
These are the Meta loops we have researched. Each one lists the rounds, what they test, the follow-up questions to expect, and how to prepare, with the sources we used.
- Software Engineer
- Mid-level (E4) · 5 rounds · 3 h 45 min
- Product Manager
- Mid-level (L4/L5) · 5 rounds · 3 h 45 min
- Content Designer (UX Writing)
- Mid-level / Senior · 3 rounds · 2 h
- Product Designer
- Senior (L5) · 5 rounds · 3 h 45 min
What Meta says about its interviews
Meta design leadership emphasizes craft, prototyping and learning from different perspectives. What fuels the future of creativity — Brett Westervelt
Meta Software Engineer interview
Meta E4 preparation combines fast algorithmic coding, a codebase extension and debugging round, system or product design, and behavioral evidence. Prepare two clear solutions within a traditional coding interview, then practice reading unfamiliar code and validating incremental changes. The design bar is a coherent end-to-end service with concrete trade-offs. Behavioral answers must show conflict resolution, growth, ownership, and measurable impact.
The 5 rounds
Technical coding screen
Deliver two clear solutions within the technical window while making the reasoning and correctness visible.
Expect: First algorithmic problem with explanation and verification. Second independent problem with explanation and verification.
Follow-ups: “Can you reduce auxiliary space?” “Which edge case would break the first draft?”
Algorithmic coding
Maintain correctness and explanation quality while switching between two problem models.
Expect: First array, string or interval exercise. Second tree, graph or heap exercise.
Follow-ups: “How does the solution change if ordering is required?” “Can the same representation support an extra operation?”
Codebase coding and debugging
Practice the code-reading and verification skills used in the AI-enabled format: understand existing behavior, change it deliberately and check the result.
Expect: One existing codebase extended through successive requirements.
Follow-ups: “Which existing behavior could this fix break?” “How would a new operation reuse the current state?”
System or product design
Build a coherent end-to-end service and defend the decisions that shape product behavior at scale.
Expect: A user-facing service with concrete APIs and a scaling follow-up.
Follow-ups: “What changes when one entity becomes extremely hot?” “How do clients recover from a lost or duplicated update?”
Behavioral: growth and impact
Demonstrate that you can deliver through ambiguity and collaboration, and change your behavior after feedback.
Expect: Resolving a substantive disagreement. Feedback that changed your work. A project with measurable personal impact.
Follow-ups: “What changed because of the feedback?” “Which outcome would have been different without your action?”
What candidates and sources report
- The Meta-authored full-loop guide describes coding, design and behavioral conversations lasting about 45 minutes. Article
- Traditional coding preparation targets about two problems in 40 minutes of technical work. Article
- The guide evaluates communication, problem solving, coding and verification as distinct signals. Article
- The guide directs candidates to prioritize common data structures and breadth rather than dynamic programming. Article
- A US E4 candidate completed a traditional coding round and a separate AI-assisted codebase repair and extension round. Candidate report
How to prepare
- Establish two-problem pace: Do two unseen problems in 45 minutes, including explanation and traces. Track time lost to modeling versus implementation.
- Broaden algorithm coverage: Rotate arrays, intervals, trees, graphs and heaps. Give the invariant and complexity before reviewing an editorial.
- Repair unfamiliar code: Take a small existing module, explain its state, then implement two changes with manual regression checks. Verify every suggested edit.
- Complete a design before scaling: Draw a working request path in the first half of a design mock; spend the remainder on one bottleneck and one failure.
- Prepare the behavioral evidence: Create six stories for conflict, feedback, ambiguity and results. Rehearse follow-ups until personal actions and impact remain precise.
Mistakes to avoid
- Do not sacrifice the second task to polish the first.
- Do not assume execution or AI is available.
- Do not rely on familiarity with a problem title.
- Do not treat any class of bug as automatically acceptable.
- Do not replace the whole module before understanding it.
Questions to ask your interviewers
- Is this role’s design emphasis product architecture or infrastructure?
- What does independent E4 ownership look like on this team?
- Which engineering change recently had the largest measurable user impact?
Meta Product Manager interview
Meta PM interviews test Product Sense, Analytical Thinking, and Leadership & Drive. Prepare two 45-minute screens, followed by another product-sense and analytical conversation plus a leadership interview. Build focused product arguments, make metrics decision-ready, and answer behavioral follow-ups with personal evidence. Team, level and recruiter instructions determine the final schedule.
The 5 rounds
Product sense screen
Demonstrate product judgment by choosing a valuable user problem and a focused solution, then defending its success measures and trade-offs.
Expect: Choose and design a product for a specific social or community need.
Follow-ups: “A new constraint cuts your proposed scope in half.” “A growth improvement creates a trust or quality regression.”
Analytical thinking screen
Turn an ambiguous product objective or metric change into a decision, a diagnostic plan and a defensible action with guardrails.
Expect: Define success and diagnose a product metric change.
Follow-ups: “The aggregate metric improves while a valuable cohort declines.” “Your data source changed during the measurement window.”
Product sense full loop
Demonstrate product judgment by choosing a valuable user problem and a focused solution, then defending its success measures and trade-offs.
Expect: Prioritize a product opportunity under competing user needs.
Follow-ups: “A new constraint cuts your proposed scope in half.” “A growth improvement creates a trust or quality regression.”
Analytical thinking full loop
Turn an ambiguous product objective or metric change into a decision, a diagnostic plan and a defensible action with guardrails.
Expect: Resolve an experiment trade-off with explicit action thresholds.
Follow-ups: “The aggregate metric improves while a valuable cohort declines.” “Your data source changed during the measurement window.”
Leadership and drive
Show how you lead work through ambiguity and disagreement using specific examples of personal decisions, consequences and changed behavior.
Expect: Ownership, disagreement, feedback and concrete professional learning.
Follow-ups: “What did you personally say or change?” “What would the other person say you missed?”
What candidates and sources report
- The Meta-authored PM guide describes Product Sense and Analytical Thinking as the initial interview categories. Article
- The full-loop guide covers Product Sense, Analytical Thinking and Leadership & Drive. Article
- The guide describes each interview as approximately 45 minutes. Article
- Product Sense assessment includes user understanding, problem selection, creative choices and product judgment. Article
- Analytical Thinking assessment connects product goals, metrics and trade-offs to decisions. Article
How to prepare
- Frame product opportunities: Practice selecting one audience and unmet need, then compare two plausible solutions before committing.
- Make metrics operational: Define events, denominators and guardrails; rehearse a diagnostic tree before prescribing a fix.
- Defend a product bet: Return to a product case and revise its scope under a constraint without abandoning the user problem.
- Resolve experiment trade-offs: Practice a ship, stop or learn-more decision with explicit uncertainty and affected cohorts.
- Prepare leadership evidence: Select distinct examples of ownership, disagreement, failure and coaching; reconstruct personal actions.
Mistakes to avoid
- Do not turn segmentation into an exhaustive list.
- Do not pitch features before deciding which problem deserves attention.
- Do not name many metrics without choosing a primary outcome.
- Do not assume a simultaneous change caused the observed movement.
- Do not cast a teammate as the obstacle without their perspective.
Questions to ask your interviewers
- What product decisions would this PM own in the first six months?
- How does the team balance growth with product quality and trust?
- Which partner relationships most often shape the roadmap?
Meta Content Designer (UX Writing) interview
Prepare to explain past work, write a clear product flow and defend decisions with cross-functional partners. Official Meta content-design accounts emphasize language, structure, accessibility and experimentation; candidate reports support portfolio and writing assessment. Current public evidence does not establish a universal loop. The three 40-minute rounds here are compact practice adaptations, including a live writing exercise in place of any recruiter-specified advance assignment.
The 3 rounds
Past-work review
Present your own work as a decision narrative that makes personal ownership, craft choices, evidence and learning easy to examine.
Expect: Past-work presentation: decisions, craft, partnership and measured impact.
Follow-ups: “The reviewer challenges whether the result came from your change.” “A partner preferred the alternative you rejected.”
UX writing exercise
Demonstrate content design in a concrete product flow, connecting accurate language, information hierarchy and inclusive decisions to a user outcome.
Expect: Write and revise a short product flow with clear decisions and recovery states.
Follow-ups: “The proposed phrase is difficult to localize.” “A policy change requires a more explicit choice.”
Cross-functional partnership
Show how you lead work through ambiguity and disagreement using specific examples of personal decisions, consequences and changed behavior.
Expect: Ownership, disagreement, feedback and concrete professional learning.
Follow-ups: “What did you personally say or change?” “What would the other person say you missed?”
What candidates and sources report
- Meta’s content-design account describes language, voice, tone, structure and timing as part of product design. Meta
- The official account connects content decisions to accessibility and a broad global audience. Meta
- A candidate who completed a Meta content-design process describes a past-work interview and storytelling about decisions and results. Candidate report
- Historical Meta candidate reports include a UX writing test and questions about work and stakeholders. Candidate report
- Public evidence reviewed does not establish the current order, timing or take-home versus live format of a complete Meta content-design loop. Candidate report
How to prepare
- Reconstruct past work: Prepare two examples connecting user and business context to a decisive content change and its outcome.
- Write a complete flow: Draft titles, body text, actions and recovery states; explain terminology and consequences without filler.
- Defend content decisions: Use concrete disagreement and feedback examples to show how evidence moved a cross-functional decision.
Mistakes to avoid
- Do not give a feature tour without a problem and outcome.
- Do not claim a team result without explaining your contribution.
- Do not hide a consequence behind cheerful tone.
- Do not use testing language without a task or decision to evaluate.
- Do not cast a teammate as the obstacle without their perspective.
Questions to ask your interviewers
- How early do content designers join problem framing?
- How does the team evaluate content beyond conversion metrics?
- Which localization and accessibility partners shape the work?
Meta Product Designer interview
Prepare a portfolio screen, panel portfolio review, app critique, design problem-solving exercise, and behavioral conversation. Meta design preparation rewards visible craft decisions, clear problem framing and constructive collaboration. In-room portfolio practice rehearses your narrative, while critique cases provide a self-contained product description.
The 5 rounds
Initial portfolio review
Present your own work as a decision narrative that makes personal ownership, craft choices, evidence and learning easy to examine.
Expect: Past-work presentation: decisions, craft, partnership and measured impact.
Follow-ups: “The reviewer challenges whether the result came from your change.” “A partner preferred the alternative you rejected.”
Panel portfolio review
Present your own work as a decision narrative that makes personal ownership, craft choices, evidence and learning easy to examine.
Expect: Past-work presentation: decisions, craft, partnership and measured impact.
Follow-ups: “The reviewer challenges whether the result came from your change.” “A partner preferred the alternative you rejected.”
App critique
Frame and refine a product experience with explicit interaction decisions, inclusive states and a focused way to validate the next iteration.
Expect: Critique a familiar product through a specific task and its interaction decisions.
Follow-ups: “A keyboard-only or screen-reader user cannot complete the task.” “The team can change only one step this release.”
Design problem solving
Frame and refine a product experience with explicit interaction decisions, inclusive states and a focused way to validate the next iteration.
Expect: Design a focused experience and refine it under a new constraint.
Follow-ups: “A keyboard-only or screen-reader user cannot complete the task.” “The team can change only one step this release.”
Collaboration and growth
Show how you lead work through ambiguity and disagreement using specific examples of personal decisions, consequences and changed behavior.
Expect: Ownership, disagreement, feedback and concrete professional learning.
Follow-ups: “What did you personally say or change?” “What would the other person say you missed?”
What candidates and sources report
- A recent Meta Product Designer guide describes portfolio screening followed by panel portfolio, app critique, whiteboard and behavioral assessment. Independent guide
- The guide covers L4 and L5, with 45-minute assessments and two portfolio projects. Independent guide
- A candidate’s 2022 experience corroborates two portfolio presentations, app critique, whiteboard and a hiring-manager conversation. Candidate report
- Meta design leadership emphasizes craft, prototyping and learning from different perspectives. Meta
- App critique examines interaction choices and product reasoning rather than asking the candidate to redesign everything. Independent guide
How to prepare
- Build two decision narratives: Choose complementary projects and rehearse the problem, pivotal decisions, evidence and your specific contribution.
- Defend portfolio depth: Prepare alternatives, constraints and attribution limits so a panel can probe beneath the polished outcome.
- Practice a task-based critique: Walk one user task, identify what works and prioritize a friction with an evidence-based improvement.
- Design through a constraint: Sketch a main path and recovery state, then refine the same design for accessibility or a narrower scope.
- Reconstruct collaboration: Prepare specific disagreement, ownership and feedback examples with what changed afterward.
Mistakes to avoid
- Do not give a feature tour without a problem and outcome.
- Do not claim a team result without explaining your contribution.
- Do not confuse a list of usability rules with a critique.
- Do not redesign the entire product before finding its main friction.
- Do not cast a teammate as the obstacle without their perspective.
Questions to ask your interviewers
- Where does this role need to raise the team’s craft bar?
- How are product designers involved in choosing problems before execution?
- How does the team validate new interactions with diverse users?
Sources
Research reviewed . Practice exercises are our own; they are not confidential interview questions.
- Meta-authored Software Engineer Full Loop Guide, public mirror — Article
- Meta E4 full-loop pass: coding, AI coding, design and behavioral — Candidate report
- Meta SE2 technical screen and assessment experience — Candidate report
- Meta SWE invitation with traditional and AI coding — Candidate report
- Meta-authored Product Manager interview guide, public mirror — Article
- Candidate preparing for Meta PM screening — Candidate report
- Get to know Susie: Content Design at Meta — Meta
- Storytelling in Meta’s past-work interview — Candidate report
- UX Writer / Content Designer interview reports — Candidate report
- Nailing the UX content strategy interview — Article
- Meta Product Designer interview guide — Independent guide
- Answering your design questions — Meta interview experience — Candidate report
- What fuels the future of creativity — Brett Westervelt — Meta
Independent preparation using Meta as a practice target. Not affiliated with, endorsed by, or sponsored by Meta.