Meta logo

Meta Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 10,018 interview experiences · FREE TO READ

2.5 Rounds average
37.3 Day average
Average Typical difficulty
56.3% Positive experience

Which role are you interviewing for?

30 roles · 10,018 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Meta.

Showing 4 of 10,018
Meta logo
Meta

Machine Learning Engineer

Engineering · nearly a year ago

Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Coding Technical System Design Behavioral

I applied online and got a recruiter call after about two weeks to chat about my background and if I'd be a good fit. Then I had a technical phone interview where I had to code some problems, like LeetCode medium-hard level, focusing on arrays and graphs. After that, I did a virtual onsite interview that had 4 parts: two coding rounds, one ML system design round where they asked about recommendation or ranking systems, and one behavioral round. The interviewers were really professional and let me ask questions at the end. They told me the results about a week after the onsite.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Meta logo
Meta

Technical Program Manager

Engineering · Boston, MA · nearly a year ago

Mid Difficult Positive experience No offer 5 rounds
Interview process
Onsite Onsite Onsite Onsite Onsite
Interview formats
Technical System Design Behavioral Other

The interview process consisted of 5 interviews: 1) Hiring Manager with some system design questions 2) Program Sense: Assessing the ability to manage complex projects from end-to-end, including early-stage roadmap creation, problem definitions, scope and requirements gathering, project planning, problem-solving, and risk mitigation. 3) Results Agility: Evaluating the results in new or unstructured situations. Responding to tough challenges. 4) TPM System Design: Evaluating understanding of the product by clearly identifying requirements and use cases (Product Sense) and going into the technical details (e.g. design, scaling, product enhancement, e2e system design, tradeoffs/benefits, solutions on how to scale, define MVP). 5) Product Sense: Evaluating the understanding of basic KPIs and metrics, and what it takes to launch a product; define business/performance related metrics.

Confirmed questions1 question
  • Design a recommendation engine for a multimodal content platform.
Meta logo
Meta

Software Engineer

Engineering · Australia · nearly a year ago

Mid Average Negative experience No offer 1 round
Interview process
Onsite Offer
Interview formats
Technical Coding

I recently interviewed for a Software Engineer role. The technical interviewers were professional, but the recruiting process was one of the most inefficient and deceptive experiences I’ve had in the industry. 1. Misleading and "Ghost-Rejection" Emailing Style: Two days after the full loop interview, the recruiter sent an email titled "Thank You for Your Time Today!" packed with overly enthusiastic language ("huge thank you," "enthusiasm," "here for you every step of the way"). For any experienced candidate, this reads like a "soft" rejection template, yet it was used just to tell me to wait for their result. It came across as a deliberate attempt to manipulate the candidate’s expectations instead of giving a clear, professional status update. 2. Pointless Sync Call for a 30-Second Rejection: Even though they had the result ready by Friday, the recruiter insisted on setting up a formal "sync call" for the following Tuesday morning. I had to rearrange my own work schedule and reserve a private room at my current office, only for the recruiter to spend 30 seconds reading a generic rejection script. When I shared feedback that this could—and should—have been handled over email to respect everyone’s time, the recruiter doubled down, saying they wanted to "show gratitude." There is no gratitude in wasting a candidate’s productive working hours for an update that fits into two sentences. 3. The Outcome: After all this "high-touch" (really: high-friction) communication, it ended in a standard 12-month cool-off period. Advice to Management Efficiency is a core value at Meta, but it is clearly missing in the recruiting department. Stop forcing "sync calls" for rejections. It is not "personal"; it is disruptive. If you have a decision on Friday, send the email on Friday. Respect candidates’ working hours and their professional time.

Confirmed questions1 question
  • Typical leetcode-style coding question, with AI tools allowed in one of the interviews.
Meta logo
Meta

Data Engineer

Engineering · Kirkland, WA · nearly a year ago

Mid Difficult Neutral experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Coding

Initial Screening 3 SQL 3 Python SQL: Star schema, sales transaction fact, book author etc dims * Identify authors who have published at least 5 books * Calculate the percentage of total sales completed on the same day the customer registered * Find customers who purchased 3 or more books on both the first and last day of sales, excluding those with only one transaction * Find the IDs of the top 5 customers, ordered by average payment per book made by the people they invited * Find the total number of authors registered with the bookstore. What percentage of them have a website URL that contains ".com", and what percentage never made a sale? * What was the total value of sales and the number of unique paying customers, grouped and sorted in descending order by payment type? * Having a transaction table find the sum of total orders and the count of unique customers Python: * Calculate the average book price from a list of prices * The bookstore gathered a list of customer comments from each shop location and wants to find the most common comment across all locations (ignoring duplicates from the same location). If multiple comments appear the same number of times, return any one of them. * Search an element in an unsorted list * Given a list of workshops, return the largest number of classes that were hosted in total across any consecutive years that had at least one workshop each.

Confirmed questions1 question
  • They asked SQL and Python questions.

Meta Interview Questions

Quoted word for word from Meta interview reports.

“Given an integer array nums and an integer k, find the length of the longest contiguous subarray whose elements sum up exactly to k. If there is no such subarray, return 0.”

Read reports →

“Given an array of strings, implement a function that returns all the strings that are anagrams.”

Read reports →

“Implement a function that returns a list of words that don’t have a matching (case-sensitive) counterpart between two strings, for example: (“Facebook is an awesome place”, “Facebook Is an AWESOME place”) → [“is”, “Is”, “awesome”, “AWESOME”].”

Read reports →

“What is the difference between HTTPS and HTTP? Why is it more secure?”

Read reports →

“write functions to allocate and free memory given an array of "available memory" and a list of alloc and free commands to execute”

Read report →

“Explain what happens behind the scenes when you type a URL into your browser?”

Read report →

“Can you measure a 1 GHz square wave with a 1 GHz oscilloscope/probe? What waveform would you see on the scope with that configuration and why, and what is a good general rule of thumb for signal integrity when measuring signals with an oscilloscope?”

Read report →

“How do you store the left and right channel audio data of a stereo audio signal.”

Read report →

“What is the big o of the algorithm and how could you make it better”

Read report →

Formats, difficulty and experience

Across all 10,018 Meta interview reports.

Interview formats

Technical 27.8%
Behavioral 27.8%
Coding 19.4%
Other 12.1%
System Design 5.1%

Interview difficulty

Easy 11.2%
Average 54.7%
Difficult 34.1%

Candidate experience

Neutral 26.1%
Positive 56.3%
Negative 17.6%

Reports by job function

Engineering 5,479
Analytics 903
Operations 673
Product 589
Research 502
Design 486