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 181–210 of 666 results

  • This question evaluates a data scientist's competency in experimental design, metric selection and guardrails, power and sample-size calculations, logging and attribution specifications, and revenue impact estimation for a new feature on a social media platform.

    MetaData ScientistAnalytics & ExperimentationOnsite
  • This question evaluates a data scientist's ability to design product success metrics and a rigorous experiment plan, covering KPI formulation, guardrail metrics and thresholds, randomization and experiment design, logging instrumentation, and quasi-experimental causal inference.

    MetaData ScientistAnalytics & ExperimentationOnsite
  • This problem tests the ability to design an inverted index system that supports complex logical queries, high-concurrency updates, and consistent pagination over a distributed dataset.

    MetaSoftware EngineerSystem DesignOnsite
  • This problem tests the design of a scalable inverted index system capable of handling boolean queries (AND/OR/NOT) over a high-throughput stream of user status updates.

    MetaSoftware EngineerSystem DesignOnsite
  • Meta data scientist experimentation prompt on measuring Instagram Shopping impact with A/B tests, geo or cluster holdouts, engagement and revenue metrics, guardrails, selection bias, network effects, and rollout decisions.

    MetaData ScientistAnalytics & ExperimentationOnsite
  • This question evaluates understanding of tree algorithms (LCA using parent pointers) and selection algorithms (sorting, max-heap, quickselect), emphasizing data structures, algorithmic correctness, and time/space complexity within the Coding & Algorithms domain.

    MetaSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This interview question evaluates core ML concepts, assumptions, math intuition, training/evaluation trade-offs, and practical failure modes in a realistic interview setting. A strong answer for Design Machine Learning Model for Facebook Groups Post Ranking states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaData ScientistMachine LearningOnsite
  • This question evaluates a data scientist's skills in experimental design, causal inference, clustering and interference analysis, metric specification, and power/sample-size calculation within the Analytics & Experimentation domain for Data Scientist roles.

    MetaData ScientistAnalytics & ExperimentationTechnical Screen
  • This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Design Metrics to Track and Analyze Spam Impact states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates competency in designing large-scale machine learning systems for real-time recommendations and notification ranking, covering candidate generation, ranking, feature engineering, online serving, latency management, and multi-objective trade-offs; it is commonly asked to assess the ability to translate product objectives into system architecture and measurable evaluation metrics while addressing freshness, cold-start, moving users, and notification fatigue. The domain is ML system design—recommender systems, ranking, and online serving—and the level spans both high-level conceptual architecture and practical application concerns such as serving latency, data freshness, training labels, and evaluation.

    MetaMachine Learning EngineerML System DesignOnsite
  • This question evaluates machine learning system design skills specific to recommender systems, including competencies in feature engineering, candidate generation and ranking, data engineering, online serving, latency and real-time context handling, evaluation metrics, and fairness/bias mitigation.

    MetaMachine Learning EngineerML System DesignOnsite
  • This question evaluates skills in designing scalable, low-latency real-time systems, including distributed architecture, concurrency control and ordering, data modeling, API design, and fault-tolerance for high-contention auction workloads.

    MetaSoftware EngineerSystem DesignOnsite
  • Design a high-scale real-time ride-hailing dispatch and trip lifecycle backend. The problem tests geospatial indexing, high-throughput location ingestion, concurrent driver assignment without double-booking, and idempotent distributed state management.

    MetaSoftware EngineerSystem DesignOnsite
  • This question evaluates proficiency in SQL-based data manipulation—aggregation, JOINs, CASE expressions, window functions, ranking, and metric design for user tenure segmentation and temporal activity comparisons.

    MetaData ScientistData Manipulation (SQL/Python)Technical Screen
  • Design Sampling Strategy to Estimate Fake News Proportion evaluates statistical assumptions, formulas, estimation strategy, uncertainty, edge cases, and interpretation 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 ScientistStatistics & MathOnsite
  • This question tests the ability to design a scalable web crawler capable of handling billions of pages while maintaining freshness and avoiding redundant work.

    MetaSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's ability to design ML-powered developer tooling, covering competencies in LLM orchestration, deterministic tool integration, repository context management, code-analysis heuristics, safety and validation strategies, and inference cost estimation.

    MetaSoftware EngineerML System DesignOnsite
  • This problem tests the ability to design a high-throughput, memory-efficient data structure for time-series counting that balances concurrency, accuracy, and storage constraints.

    MetaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design a Dropbox-like file storage and sync service evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaSoftware EngineerSystem DesignOnsite
  • A system design interview question asking you to build a GPS fitness-tracking app in the style of Strava, where athletes record runs and rides, save routes and follow friends' activity feeds. It tests offline-tolerant recording, duplicate-free uploads, storage for large GPS tracks, feed fan-out and privacy controls.

    MetaSoftware EngineerSystem DesignOther
  • An ML system design question asking you to design a large-scale personalized recommendation system end to end, from candidate retrieval and multi-stage ranking to training data, evaluation, serving and monitoring. It tests problem framing, latency budgeting, cold start, feedback loops and online experimentation.

    MetaMachine Learning EngineerML System DesignOnsite
  • Design a Messenger-style chat backend for one-to-one conversations without WebSockets or other persistent connections, using only request/response web APIs. Tests message ordering, idempotent sends, cursor-based sync, cheap polling, push wake-ups, multi-device delivery and failure handling at very large scale.

    MetaSoftware EngineerSystem DesignOnsite
  • A system design question on a notification platform that takes events from many product services and delivers them to users through push and in-app channels. It tests ingestion contracts, preference checks, grouping and rate limiting, priority isolation, third-party push delivery, and deduplication under retries.

    MetaSoftware EngineerSystem DesignOnsite
  • A system design question on recommending people a user may know on a large social network, from candidate generation through ranking and serving. It tests graph-based candidate sourcing, batch versus real-time freshness, ranking signals and labels, filtering, privacy, cold start, and evaluation.

    MetaSoftware EngineerSystem DesignOnsite
  • A system design question on building the home news feed of a large social network: publishing posts and serving each user a ranked, paginated feed of posts from the accounts they follow. It tests fan-out strategy, accounts with huge follower counts, ranking under a latency budget, and correctness for deletes and privacy.

    MetaSoftware EngineerSystem DesignOnsite
  • A system design question on a real-time chat service with one-to-one and group conversations, instant delivery to online users, offline catch-up, and history across devices. It tests connection routing, per-conversation ordering, idempotent sends, message storage, group fan-out, and read receipts.

    MetaSoftware EngineerSystem DesignOnsite
  • A two-phase security engineering design prompt from Meta: design a browser-based collaborative coding pad with real-time co-editing, code execution and session playback, then threat-model your own architecture. It tests concurrent editing, sandboxing untrusted code, access control, tenant isolation and risk prioritization.

    MetaSecurity EngineerSystem DesignOnsite
  • An AI design question about a chatbot that answers user questions in real time. It tests the low-latency serving and retrieval path, training data collection for fine-tuning and preference learning, reinforcement-learning task and reward design, and the ability to name reward weaknesses and mitigate them.

    MetaMachine Learning EngineerML System DesignTechnical Screen
  • This question evaluates a candidate's ability to design a large-scale, real-time data processing system that continuously scores and ranks trending content under strict freshness constraints. It tests system design skills including stream processing, time-decayed scoring, and handling high write throughput at scale. This type of question is commonly used to assess architectural thinking for systems balancing timeliness, popularity, and novelty signals.

    MetaSoftware EngineerSystem DesignOnsite
  • Design an enterprise-scale notification platform supporting multi-channel delivery, recipient fanout, preference filtering, and resilient at-least-once delivery guarantees.

    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