← Back to Directory

Meta interview notes, page 71 of 238

FAANG / Big Tech

Most of these Meta write-ups come from Software Engineers (1,194), then Data Scientists (489) and Product Managers (453). The most reported rounds are the technical phone screen (1,190), the product sense round (466), the system design round (255) and the behavioral / leadership round (205).

2377 interview notes · updated Jul 2026

Meta·Software Engineer·Onsite - System Design / Architecture

May 2026
Meta system design round, one big question that took the whole session. The problem was meaty enough that I kept second-guessing my own design halfway through explaining it.
  • Design and implement a thread-safe job scheduler where jobs have expiry timestamps. The system needs to handle concurrent job submissions from multiple producer threads, a background cleanup thread that removes expired jobs, and worker threads that pull valid jobs in order. Walk through your data structure choices, locking strategy, and how you prevent races between the cleanup thread and the workers.

“I jumped straight to a priority queue and then realized mid-sentence I hadn't thought about what happens when the reaper pulls an expired job at the same moment a worker is trying to dequeue it.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

May 2026
Meta system design round for a software engineering role. The question was a full-blown online auction system, which sounds fun until you realize how many moving parts they actually want you to cover in under an hour.
  • Design an online auction system that handles listing creation, real-time bidding, bid increments, reserve prices, buy-it-now, anti-sniping, and auction closeout. Cover APIs, data model, consistency for winning bids, real-time updates, concurrency control, fraud detection, payments and settlement, scalability, fault tolerance, and monitoring.

“This is basically a distributed systems gauntlet dressed up as a product question.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE coding round with two problems back to back. The first was a classic array problem and the second was a tree traversal that required returning the actual path, not just the length, which tripped me up a bit.
  • Given a binary array of 0s and 1s, find the maximum length of a contiguous subarray with an equal number of 0s and 1s.
  • Given a binary tree, find the longest strictly increasing downward path (parent to child) and return the actual node values along that path, not just the length.

“Prefix sum with a hash map is the clean solution here.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta PM interview, product design question about building a travel product from scratch. Pretty open-ended, which sounds fun until you're actually in it.
  • You're a PM for Facebook Travel. What would you build?

“Blanked for a second because the question is so wide open.”

View Post

Meta·Data Scientist·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Meta for a Data Science role. One question, but it had a lot of moving parts and I left feeling like I probably undersold the validation piece.
  • Tell me about a time you had to learn a new analytical framework quickly, under a week, to deliver something high-stakes. Walk through your day-by-day plan, what you actually produced, how you checked your work under time pressure, what corners you cut, and what signals told you it worked or didn't. Also: what changes if the deadline moves up by 48 hours?

“This one is sneakier than it looks.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

May 2026
Meta SWE design round, focused entirely on an in-memory file system with per-user quotas. The problem kept growing with each new operation they asked me to add, which was a bit exhausting but also kind of interesting once I got into it.
  • Design an in-memory file system where each file has a name, size, and owner. Implement add_user, add_file_by, and add_file operations with per-user capacity enforcement.
  • Add a copy_file operation that duplicates a file under a new name, preserving the original owner and size, and fails if the owner's quota would be exceeded.
  • Implement get_n_largest, which filters files by a name prefix and suffix, then returns the top N by size descending (ties broken by name ascending), formatted as 'name(size)'.
  • Implement update_capacity, which changes a user's storage cap and, if their current usage exceeds the new cap, deletes their largest files until usage fits within the new limit.
  • Add compress_file and decompress_file operations. Compressing halves the file size and renames it with a fixed suffix. Decompressing reverses this, doubling the size and restoring the original name, but fails if the owner would exceed capacity.

“The base setup felt straightforward, a couple of hashmaps and some bookkeeping.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta production engineer interview with a coding-style question around text processing and frequency counting. Nothing too flashy but the follow-up discussion on memory constraints is where things got real.
  • Given a path to a text file (or a word stream), return the top N most frequent words in descending order of frequency, with ties broken alphabetically.

“Started with a Counter and full sort which works fine for small inputs, but they pushed back pretty fast asking what happens when the file is 50GB.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

May 2026
Meta SWE coding round with two array problems back to back. Nothing too wild but the second one definitely took more time to think through than I expected.
  • Given an integer array, return a new array where each element is the product of all other elements in the original array. No division allowed, and it must run in O(n) time.
  • Given a 2D binary matrix representing Conway's Game of Life, compute the next generation state of the board based on the standard neighbor survival and birth rules.

“The no-division constraint is the whole point of the problem.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Brutal causal inference question for a Meta DS role. The whole thing was basically one giant case study on whether web revenue growth was real or just eating into other channels, and they wanted a full analysis plan top to bottom.
  • You notice that web-sourced revenue is higher in 2026 compared to 2025. Design a full causal analysis to determine whether this growth is genuinely incremental or whether it's mostly cannibalization from other acquisition channels like API and mobile. Cover your identification strategy, model specification, key metrics, power analysis, robustness checks, and decision thresholds.

“This was a lot.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

May 2026
Meta ML engineer screen, one coding problem, felt straightforward on the surface but the expected solution was binary search and I definitely went the slow route first.
  • Given a sorted array of integers, return the maximum of the count of positive numbers and the count of negative numbers. Zero counts as neither.

“My first instinct was just to iterate through the whole thing and tally up.”

View Post