Katkat

Company

Meta interview questions

666 practice questions in the style of Meta's interviews, covering Coding & Algorithms, Analytics & Experimentation, Data Manipulation (SQL/Python), Software Engineering Fundamentals, Statistics & Math, Behavioral & Leadership, Machine Learning, ML System Design, Product Design & Strategy, Product / Decision Making, System Design.

Questions666

54 easy472 medium140 hard

Your progress0/666

Meta interview questions by the numbers

Last updated

Katkat has 666 Meta interview questions. The largest topics are Coding & Algorithms (32%), Analytics & Experimentation (17%) and Behavioral & Leadership (11%). By difficulty: 8% easy, 71% medium and 21% hard. The most common round is Onsite (54%). Frequent concepts include System Design, Causal Inference, Algorithms and Scalability.

Difficulty

  • Easy8% · 54
  • Medium71% · 472
  • Hard21% · 140

Interview rounds

  • Onsite54% · 358
  • Technical Screen40% · 268
  • Online Assessment3% · 23
  • HR Screen2% · 10
  • Other1% · 7

Roles

  • Software Engineer43% · 285
  • Data Scientist39% · 262
  • Machine Learning Engineer11% · 70
  • Data Engineer3% · 21
  • Product Manager2% · 13

Frequent concepts

  • System Design4% · 28
  • Causal Inference3% · 20
  • Algorithms3% · 19
  • Scalability3% · 19
  • Distributed Systems2% · 14
  • Metrics2% · 14

Showing 151–180 of 666 results

  • This problem tests your ability to manipulate complex pointer structures and maintain object identity across a deep copy operation in a non-linear linked list.

    MetaMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Define Product Metrics: Align Stakeholders, Measure Success, Improve Results states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaData ScientistBehavioral & LeadershipOnsite
  • Design a comprehensive measurement and experimentation framework for a new community feature, evaluating true incremental value while detecting cannibalization across existing surfaces and mitigating network spillover effects.

    MetaData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates the ability to define and compute shop-level visibility KPIs in SQL, testing skills in metric design (visibility_rate and impression_share), deduplication, session/window filtering, and data-quality concerns such as late-arriving events and bot filtering.

    MetaData ScientistData Manipulation (SQL/Python)Onsite
  • Define and validate product metrics evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaData EngineerAnalytics & ExperimentationOnsite
  • This question evaluates a data scientist's competency in metric framework design, distributional analysis of heavy-tailed user behavior, monitoring and anomaly detection, and experimental setup for measuring healthy engagement, including considerations like unit of analysis, treatment of heavy users, and anti-spam guardrails.

    MetaData ScientistAnalytics & ExperimentationOnsite
  • This problem evaluates your ability to translate product goals into actionable metrics and design a scalable, reliable data schema to support those metrics.

    MetaData EngineerSystem DesignTechnical Screen
  • This question evaluates a data scientist's communication and leadership competencies, including concise elevator pitching, product sense, end-to-end experimentation design and statistical rigor, causal reasoning, and the ability to quantify measurable business impact within a product context.

    MetaData ScientistBehavioral & LeadershipTechnical Screen
  • This set of behavioral prompts evaluates communication, teamwork, leadership, stakeholder explanation, conflict resolution, and self-reflection skills relevant to a software engineer role.

    MetaSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates leadership, program execution, stakeholder management, risk and tradeoff reasoning in machine learning engineering, along with expertise in data privacy, regulatory compliance, and operational data governance for user-data-driven systems.

    MetaMachine Learning EngineerBehavioral & LeadershipOnsite
  • The Meta Data Scientist onsite behavioral & leadership round: answer a set of STAR-format leadership prompts spanning cross-functional collaboration and conflict, giving/receiving feedback, disagree-and-commit, being wrong and course-correcting, overcoming obstacles and winning skeptics, driving breakthroughs, ambiguous work under time pressure, breaking-metric triage, learning from peers, diversity & inclusion, inclusive meetings, proactive alignment, and building long-term trust. Each answer must name stakeholders, state trade-offs, and quantify impact against a baseline.

    MetaData ScientistBehavioral & LeadershipOnsite
  • This question evaluates proficiency in online experimentation and sequential decision-making, covering Bayesian bandits (Thompson Sampling), safety guardrails for churn, delayed-conversion handling, traffic allocation and stopping/rollback policy design.

    MetaData ScientistMachine LearningOnsite
  • This problem tests your ability to derive the Ordinary Least Squares (OLS) closed-form solution for a simple linear regression model and analyze the underlying mathematical assumptions.

    MetaMachine Learning EngineerMachine LearningTechnical Screen
  • The question evaluates combinatorial reasoning, discrete mathematics, and constructive extremal analysis by asking for the maximum number of distinct frequency counts in an array and a matching construction.

    MetaSoftware EngineerStatistics & MathTechnical Screen
  • This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Describe Overcoming Ambiguity and Building Cross-Team Collaboration states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaData ScientistBehavioral & LeadershipOnsite
  • Meta Data Scientist onsite behavioral & leadership round, anchored on describing a challenging project end-to-end with follow-up prompts on stakeholder influence, collaborating across work styles, mentoring and onboarding teammates, managing cross-functional relationships under disagreement, learning quickly, and quantifying impact and trade-offs. Includes a STAR-based rubric of what interviewers look for at each prompt, common pitfalls, and senior/IC6 expectations.

    MetaData ScientistBehavioral & LeadershipOnsite
  • Prepare a credible story about using an AI-assisted tool in analysis. The exercise tests whether you can justify the tool, validate it independently, protect sensitive data, plan for failure, connect model quality to a product decision, and explain how you build AI fluency.

    MetaProduct AnalystBehavioral & LeadershipHR Screen
  • This question evaluates communication, self-awareness, motivation, and cultural-fit competencies within the Behavioral & Leadership domain for a Software Engineer role.

    MetaSoftware EngineerBehavioral & LeadershipHR Screen
  • This question evaluates conflict resolution, initiative, ownership, influence, and learning from failure within a Behavioral & Leadership context for a software engineer.

    MetaSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates conflict resolution, leadership, cross-team collaboration, stakeholder management, and senior-level ownership and communication competencies in the Behavioral & Leadership category within the software engineering domain.

    MetaSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Prepare engineering manager or senior engineer behavioral answers for conflict resolution, proud projects, self-reflection, and mentoring. Includes STAR structures, sample story patterns, and pitfalls.

    MetaSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates a software engineer's proficiency in cross-team collaboration, conflict and constraint management, ownership alignment, and reflective learning from project failure, emphasizing interpersonal, leadership, and accountability competencies.

    MetaSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates a candidate's ability to perform under intense time pressure and multitask, specifically assessing prioritization, trade-off communication, stakeholder management, stress resilience, and execution skills relevant to machine learning engineering within a Behavioral & Leadership context.

    MetaMachine Learning EngineerBehavioral & LeadershipOnsite
  • This question evaluates a candidate's ability to influence without formal authority, covering stakeholder management, cross-functional communication, conflict resolution, and technical trade-off quantification within a Behavioral & Leadership interview for a Data Scientist role.

    MetaData ScientistBehavioral & LeadershipOnsite
  • The question evaluates a Data Scientist's leadership, cross-functional collaboration, stakeholder communication, conflict resolution, onboarding, and impact-measurement competencies within a product analytics context.

    MetaData ScientistBehavioral & LeadershipOnsite
  • This question evaluates leadership, cross-team collaboration, ownership, and reflective learning by asking about a candidate's proudest project and a specific instance of working across teams, and it falls under the Behavioral & Leadership category within the software engineering domain.

    MetaSoftware EngineerBehavioral & LeadershipOnline Assessment
  • This question evaluates persuasion, conflict-resolution, communication, and stakeholder-management competencies and falls within the Behavioral & Leadership domain.

    MetaSoftware EngineerBehavioral & LeadershipOnsite
  • This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Describe something you did to be inclusive states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaData ScientistBehavioral & LeadershipOnsite
  • This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Describe teamwork and stress handling states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaSoftware EngineerBehavioral & LeadershipOnline Assessment
  • A system design question on ephemeral stories that followers can view for 24 hours before they disappear, covering media upload, the tray of accounts with unwatched stories, playback, and viewer tracking. It tests expiry semantics, fan-out for popular authors, watched-state storage, and media delivery.

    MetaSoftware EngineerSystem DesignOnsite

Meta interview experiences

All 83 →
  • Full Onsite Loop Plus My AI Coding Interview PlaybookMeta · Software Engineer · Onsite · Sep 2026

    Most of the questions were the classic, well-worn ones you'd already find on the forum. Phone Leetcode easy + mid Onsite 2 AI coding rounds + 2 AI system design rounds + 1 BQ AI coding 01: Friend system: Implement a friend recommendation algorithm Given data: a list of users, a list of friendships (user-user pairs) Design a strategy to recommend new friends to a user (e.g., search for friends of…

  • Leadership and Fullstack Phone Screen, Rejected Over 'Not Enough Impact'Meta · Data Engineer · Senior+ · Technical Screen · Sep 2026
    Rejected

    From the recruiter to the interviewers, the whole thing gave off an absurd vibe. I was applying for a senior position, and the job description didn't even list a level at the time. After I applied, the recruiter had me submit my availability directly — no call at all. Once it was scheduled, I was told it would be one Leadership round and one Fullstack round. I thought that was a little strange at…

  • Offer After 1.5 Years Out of Work and 600+ Hours of PrepMeta · Software Engineer · Onsite · Sep 2026
    Offer

    I had been out of work for a year and a half. Once I got properly serious about the search, I fired off about 100 applications and basically got silence. A few startups got in touch, but nothing picked up speed. Then someone referred me at Meta and a recruiter asked to set up a call. One choice early on, I believe, defined everything that followed. I turned the startup conversations down and comm…

  • Explaining an AI System and Solving a Maze with AIMeta · Software Engineer · Technical Screen · Aug 2026

    This will most likely become a rejection story. At the beginning, I was asked to introduce an AI system I had designed and explain the problem it solved. I stumbled through the explanation, and the interviewer did not seem very satisfied. I probably did not make the project sound impressive enough. Next came AI coding. This really felt like a company going all in on AI, because everything involve…

  • Phone Screen Plus a Four-Round Virtual OnsiteMeta · Software Engineer · Onsite · Aug 2026

    Meta phone screen + virtual onsite writeup, with the questions and my thought process included. Since I signed an NDA, I'm coding the problem names as homophones — sorry about that. Phone Screen 45 minutes, two questions. The first five minutes were self-intro, and pretty much the rest of the time was spent coding. Question 1, coded 1091: a 2D grid, get from the top-left corner to the bottom-righ…

More companies