How Meta interviews
Start with the reported process for your role, then use our practice rounds to rehearse the skills it tests. Follow your recruiter’s instructions for your team and location.
- Software Engineer
- Mid-level (E4) · 5 practice rounds · 3 h 45 min of practice
- Software Engineer, New Grad
- Entry-level (E3) · 3 practice rounds · 2 h 10 min of practice
- Product Manager
- Mid-level (L4/L5) · 5 practice rounds · 3 h 45 min of practice
- Product Designer
- Senior (L5) · 5 practice rounds · 3 h 45 min of practice
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.
Our 5 practice rounds
Technical coding screen
Deliver two clear solutions within the technical window while making the reasoning and correctness visible.
Practice focus: First algorithmic problem with explanation and verification. Second independent problem with explanation and verification.
Illustrative practice follow-ups: “Can you reduce auxiliary space?” “Which edge case would break the first draft?”
Practice this roundAlgorithmic coding
Maintain correctness and explanation quality while switching between two problem models.
Practice focus: First array, string or interval exercise. Second tree, graph or heap exercise.
Illustrative practice follow-ups: “How does the solution change if ordering is required?” “Can the same representation support an extra operation?”
Practice this roundCodebase 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.
Practice focus: One existing codebase extended through successive requirements.
Illustrative practice follow-ups: “Which existing behavior could this fix break?” “How would a new operation reuse the current state?”
Practice this roundSystem or product design
Build a coherent end-to-end service and defend the decisions that shape product behavior at scale.
Practice focus: A user-facing service with concrete APIs and a scaling follow-up.
Illustrative practice follow-ups: “What changes when one entity becomes extremely hot?” “How do clients recover from a lost or duplicated update?”
Practice this roundBehavioral: growth and impact
Demonstrate that you can deliver through ambiguity and collaboration, and change your behavior after feedback.
Practice focus: Resolving a substantive disagreement. Feedback that changed your work. A project with measurable personal impact.
Illustrative practice follow-ups: “What changed because of the feedback?” “Which outcome would have been different without your action?”
Practice this roundMeta Software Engineer interview questions
- Find a contiguous subarray satisfying a sum condition using prefix sums and a map. Candidate report
- Implement next() for an iterator merging multiple sorted arrays. Candidate report
- Extend a cloud store through storage operations, users and role-based access rules. Candidate report
- Read an existing algorithmic codebase, fix defects and implement missing functions through successive parts. Candidate report
- Describe conflict, feedback, ambiguity and delivered impact, then answer detailed personal-contribution follow-ups. Candidate report
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
- A US E4 candidate completed a traditional coding round and a separate AI-assisted codebase repair and extension round. Candidate report
- The E4 codebase round had four progressive parts, with the candidate fixing or implementing functions in existing code. 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 Software Engineer, New Grad interview
Meta's new-grad loop is two coding interviews and one behavioral interview. Coding rounds use LeetCode-style data-structure and algorithm problems, often two in 45 minutes, with follow-ups on complexity and edge cases. The behavioral interview covers project impact, conflict and what you learned.
Our 3 practice rounds
Coding Interview One
Tests algorithm selection, correct implementation, complexity awareness, and edge-case handling in a short coding session.
Practice focus: Standard array, string, tree, or graph problem. Pattern-recognition problem with a complexity follow-up. Two-part data-structure problem with edge cases.
Illustrative practice follow-ups: “How would your approach change if the input no longer fit in memory?” “Can you trace the code with an empty input and a duplicate value?”
Practice this roundCoding Interview Two
Tests decomposition, optimization, follow-up handling, and preservation of correctness under time pressure.
Practice focus: Multi-part tree, graph, array, or string problem. Optimization after an initial workable approach. Constraint or representation follow-up.
Illustrative practice follow-ups: “Which part becomes the bottleneck as the input grows?” “Can you revise the code for that constraint and trace the change?”
Practice this roundBehavioral Interview
Tests ownership, measurable project impact, collaboration during disagreement, and learning from challenges or feedback.
Practice focus: Project impact and technical challenge. Disagreement with a teammate or lead. Critical feedback or unfamiliar work.
Illustrative practice follow-ups: “What did you personally decide when the team disagreed?” “What would you change now, and why?”
Practice this roundMeta Software Engineer, New Grad interview questions
- Solve graph, array, and tree problems in a LeetCode-style format. Candidate report
- Describe your most impactful project and its challenges. Candidate report
- Describe a conflict and how you convinced another person, or accepted their view. Candidate report
- Describe a personal weakness or work outside your comfort zone. Candidate report
- Describe how you resolved a conflict. Candidate report
- Find the longest substring without repeated characters, then handle Unicode and variable-width characters. Independent guide
What candidates and sources report
- Recent exact-level candidate reports describe a final loop with two technical or coding interviews and one behavioral interview. Candidate report
- Recent exact-level candidates report LeetCode-style coding questions for Meta new-grad interviews. Candidate report
- Exact-level reports describe coding difficulty from basic or medium to medium-hard or hard. Candidate report
- Exact-level behavioral reports include project impact, project challenges, conflict resolution, accepting another view, weaknesses, and work outside a comfort zone. Candidate report
- Candidate reports show interviewer attention to time complexity, edge cases, code redundancy, solution explanation, and optimization during coding. Candidate report
How to prepare
- Prepare project stories: Prepare stories on impact, conflict, feedback, and unfamiliar work. State your action, result, and lesson.
Mistakes to avoid
- Do not code before confirming the input model and required output.
- Do not accept a brute-force approach without stating its complexity and limits.
- Do not hide uncertainty about complexity or skip a requested optimization.
- Do not let a follow-up erase correctness and explanation on the first approach.
- Do not describe team success without separating your own actions.
Questions to ask your interviewers
- Are current E3 University Grad interviews still two coding rounds and one behavioral round?
- Does this E3 loop include a technical screen, online assessment, or design discussion?
- What language, editor, execution policy, and coding-round duration should I use?
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.
Our 5 practice 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.
Practice focus: Choose and design a product for a specific social or community need.
Illustrative practice follow-ups: “Who is the first user you would serve, and why?” “How would you tell whether the proposed solution helped them?”
Practice this roundAnalytical thinking screen
Turn an ambiguous product objective or metric change into a decision, a diagnostic plan and a defensible action with guardrails.
Practice focus: Define success and diagnose a product metric change.
Illustrative practice follow-ups: “Which events and users does this metric count?” “What would you check before deciding the change is a product problem?”
Practice this roundProduct sense full loop
Practice choosing between competing user needs and defending the product opportunity you would pursue.
Practice focus: Prioritize a product opportunity under competing user needs.
Illustrative practice follow-ups: “You can fund only one of these user needs. Which do you choose?” “Your preferred solution improves growth but harms trust. What changes?”
Practice this roundAnalytical thinking full loop
Practice making a launch decision from an experiment, including cohort differences and explicit stopping thresholds.
Practice focus: Resolve an experiment trade-off with explicit action thresholds.
Illustrative practice follow-ups: “The aggregate metric improves while a valuable cohort declines. Would you launch?” “What result would make you stop the experiment?”
Practice this roundLeadership and drive
Show how you lead work through ambiguity and disagreement using specific examples of personal decisions, consequences and changed behavior.
Practice focus: Ownership, disagreement, feedback and concrete professional learning.
Illustrative practice follow-ups: “What did you personally say or change?” “What would the other person say you missed?”
Practice this roundMeta Product Manager interview questions
- Define goals and metrics for a product, or investigate a decline in registrations. Candidate report
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 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. The research uses a recent L4/L5 guide corroborated by an older candidate account; some pipelines add an early critique. In-room portfolio practice rehearses your narrative, while critique cases provide a self-contained product description.
Our 5 practice rounds
Initial portfolio review
Present your own work as a decision narrative that makes personal ownership, craft choices, evidence and learning easy to examine.
Practice focus: Past-work presentation: decisions, craft, partnership and measured impact.
Illustrative practice follow-ups: “Which part of this project did you own?” “Which craft decision made the greatest difference to the experience?”
Practice this roundPanel portfolio review
Revisit the portfolio skills from the initial review, this time rehearsing challenges to your evidence and rejected alternatives.
Practice focus: Past-work presentation: decisions, craft, partnership and measured impact.
Illustrative practice follow-ups: “How do you know the result came from your change?” “What was reasonable about the alternative your partner preferred?”
Practice this roundApp critique
Critique an existing product through one user task, explaining its interaction choices and where the experience breaks down.
Practice focus: Critique a familiar product through a specific task and its interaction decisions.
Illustrative practice follow-ups: “Where does this task become difficult for a screen-reader user?” “If you could change one interaction, which would you choose?”
Practice this roundDesign problem solving
Design a focused experience, state your assumptions, and revise the proposal when a new constraint appears.
Practice focus: Design a focused experience and refine it under a new constraint.
Illustrative practice follow-ups: “What assumption would you test before building this?” “The team can change only one step this release. How do you revise the design?”
Practice this roundCollaboration and growth
Show how you lead work through ambiguity and disagreement using specific examples of personal decisions, consequences and changed behavior.
Practice focus: Ownership, disagreement, feedback and concrete professional learning.
Illustrative practice follow-ups: “What did you personally say or change?” “What would the other person say you missed?”
Practice this roundMeta Product Designer interview questions
- Present two design case studies and defend important decisions. Independent guide
- Critique a familiar application through its user experience and interaction choices. Independent guide
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
- 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
Latest catalogue research: . Practice exercises and follow-ups 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 SWE New Grad Interview Experience - Menlo Park, California — Candidate report
- Meta Software Engineer New Grad Interview Experience - Menlo Park, California — Candidate report
- Interview Experience - 115 - Meta | Software Development Engineer | New Grad — Candidate report
- Meta Intevriew experience - Interview Experience - FrontendLead Discuss — Candidate report
- How high is the interview bar for E3 new grad at Meta? — Candidate report
- Meta-authored Product Manager interview guide, public mirror — Article
- Candidate preparing for Meta PM screening — Candidate report
- 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.