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 211–240 of 666 results

  • Meta machine learning system-design prompt on restaurant recommendations for food apps, covering retrieval and ranking models, features, cold start, implicit feedback, offline metrics, A/B testing, and marketplace guardrails.

    MetaData ScientistMachine LearningOnsite
  • This question tests your ability to design a multi-stage recommendation pipeline for a high-traffic short-video platform, focusing on candidate retrieval, ranking models, and system scalability.

    MetaMachine Learning EngineerML System DesignTechnical Screen
  • This problem tests the ability to implement a parser for basic mathematical expressions, specifically focusing on handling operator precedence and parentheses using a stack-based approach.

    MetaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question tests the ability to design a high-throughput, distributed system that maintains a real-time ranking of the most popular items across a massive global user base.

    MetaSoftware EngineerSystem DesignOnsite
  • This problem evaluates your ability to design a class interface that maintains an ordered collection of events and allows efficient retrieval based on time-based criteria.

    MetaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates a candidate's understanding of distributed systems architecture, media processing and delivery concepts including upload resiliency, transcoding into multiple bitrates, scalable storage and low-latency streaming.

    MetaSoftware EngineerSystem DesignOnsite
  • This question evaluates object-oriented design and stateful system skills, including time-ordered event processing, scheduling and cancellation semantics, balance accounting, and top-k aggregation using appropriate data structures.

    MetaSoftware EngineerCoding & AlgorithmsOnline Assessment
  • Design a bank system with scheduling and rankings 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 DesignTechnical Screen
  • This question evaluates system-design and transactional engineering skills for financial services, including API design, data modeling, correctness under holds and transfer expirations, idempotency, merge semantics, and complexity reasoning.

    MetaSoftware EngineerSystem DesignHR Screen
  • This question evaluates a candidate's ability to design and implement an in-memory banking API, focusing on data modeling, API semantics, invariants (such as monotonic timestamps and non-negative balances), idempotency, and basic concurrency control.

    MetaSoftware EngineerSystem DesignOnline Assessment
  • This question tests the ability to design a cluster-randomized experiment when interactions between users (network interference) violate the stable unit treatment value assumption (SUTVA).

    MetaData ScientistAnalytics & ExperimentationHR Screen
  • This question evaluates experimental-design and causal-inference competencies for cluster-randomized experiments, covering metric selection, power and design-effect calculations, intracluster correlation, spillover detection, sequential monitoring, guardrails, and operational rollout within the Analytics & Experimentation domain for a Data Scientist role. It is commonly asked to determine how applicants balance statistical rigor and real-world operational constraints—such as cluster choice, monitoring thresholds, and analysis strategy—testing both conceptual understanding and practical application in production experimentation.

    MetaData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates understanding of designing scalable, reliable content-processing systems that handle high-throughput ingestion, ML-based classification and rule evaluation, priority/backpressure mechanisms, storage and API design, experimentation hooks, and operational concerns like observability and cost.

    MetaSoftware EngineerSystem DesignOnsite
  • This question evaluates a data scientist's competency in experimental design, causal inference, statistical power analysis, and product-metric trade-offs within the Analytics & Experimentation domain, and is commonly asked to assess the ability to increase monetization while protecting user and creator experience.

    MetaData ScientistAnalytics & ExperimentationOnsite
  • This problem tests your ability to design a scalable backend for a fitness tracking application, focusing on high-frequency sensor data ingestion, geospatial route storage, and efficient retrieval of historical user activities.

    MetaSoftware EngineerSystem DesignOnline Assessment
  • This question tests the ability to design a high-scale search platform that aggregates volatile data from heterogeneous third-party providers while maintaining low latency and high availability.

    MetaSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a high-throughput, low-latency leaderboard system, focusing on data structures for ranking, storage trade-offs, and scalability under heavy write and read loads.

    MetaSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's ability to design scalable, fault-tolerant distributed systems for web-scale data acquisition, covering competencies such as crawler architecture, URL frontier management, deduplication, per-domain rate limiting and robots.

    MetaSoftware EngineerSystem DesignOnsite
  • This problem tests your ability to design a high-throughput, real-time messaging system capable of handling sudden spikes in concurrent viewers and maintaining low latency for chat delivery.

    MetaSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's ability to design scalable, reliable ingestion and processing pipelines, time-series price storage and querying, deduplication across users, and notification/alert mechanisms for a large-scale price-tracking service.

    MetaSoftware EngineerSystem DesignOnsite
  • This interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design a mini banking system states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    MetaSoftware EngineerSystem DesignTechnical Screen
  • This problem tests the ability to design an end-to-end ML system for predicting user dissatisfaction, focusing on label definition, feature engineering, and the integration of negative signals into a ranking pipeline.

    MetaMachine Learning EngineerML System DesignOnsite
  • This question evaluates a candidate's ability to design access control and visibility mechanisms for social posts, covering privacy models, efficient read-time enforcement, data modeling, caching strategies, and handling dynamic friendship and privacy updates.

    MetaSoftware EngineerSystem DesignOnsite
  • This question evaluates system-design competencies such as scalable architecture, data modeling for time-series price history, external data ingestion and integration, alerting and monitoring, and trade-off reasoning for large-scale services.

    MetaSoftware EngineerSystem DesignOnsite
  • This question evaluates system design competencies for building a large-scale notifications platform—covering architecture, APIs, data modeling, event pipelines, delivery semantics (retries, deduplication, idempotency), targeting/segmentation, localization, monitoring, and legal compliance such as GDPR/CCPA.

    MetaSoftware EngineerSystem DesignOnsite
  • This problem tests your ability to design a multi-stage recommendation pipeline that balances low-latency retrieval with high-precision ranking at scale.

    MetaSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's ability in scalable real-time system design, covering competencies such as stream processing, event aggregation, time-windowed metrics, handling late and out-of-order events, and designing for very high write throughput.

    MetaSoftware EngineerSystem DesignTechnical Screen
  • A Meta software-engineer system-design onsite question: design a real-time messenger supporting 1:1 and group chats at 100M MAU with p99 send-to-receive latency under 150 ms. It covers APIs, message ordering and idempotency, delivery semantics, multi-device sync, WebSocket fanout, storage/search, E2EE, abuse controls, retention/GDPR, multi-region failover, and observability.

    MetaSoftware EngineerSystem DesignOnsite
  • This question evaluates competence in designing large-scale recommendation systems and ML engineering skills such as candidate generation, feature store design (offline/online and point-in-time correctness), real-time signal ingestion, ranking and re-ranking, online exploration, cold-start strategies, feedback-bias mitigation, experimentation, and operational reliability. It is commonly asked to assess the ability to make architecture-level trade-offs for scalability, latency and throughput targets, multi-objective optimization, data governance and outage fallback behavior; it falls under the System Design and Machine Learning domain and requires practical, architecture-level application with conceptual trade-off reasoning rather than low-level implementation detail.

    MetaMachine Learning EngineerSystem DesignOnsite
  • This question evaluates expertise in large-scale ML system design and distributed training for Mixture-of-Experts (MoE) models, covering competencies in model architecture, parallelism and communication strategies, memory and optimizer sharding, data curation and tokenization, monitoring, checkpointing, and fault tolerance; it is categorized under ML System Design and targets practical application with systems-level architectural reasoning rather than purely theoretical concepts. It is commonly asked to evaluate the ability to balance throughput, stability, and cost when scaling pretraining to hundreds of GPUs, reason about routing and capacity trade-offs, and design production-grade pipelines that can extend to larger clusters.

    MetaMachine Learning EngineerML System 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