Meta Interview Experiences & Questions
89 real Meta interviews shared by candidates: every round, the questions they were asked, how they answered, and whether they got the offer. Latest: Aug 2026.
What to expect at Meta
Based on 89 real interviews
By role
The Meta interview process
Most common round types: Behavioral (35), Coding (33), System Design (19), Technical (15), Analytical (14), Product Design (12).
Real Meta interview questions
- Do you have experience with A/B testing?
- Implement an efficient sparse matrix times vector multiplication.
- Describe your current role, team, project work, tools, AI usage, preferred language, and coding versus leadership split.
- You're a product manager at Meta and you're tasked with making a tool to connect handymen with consumers. How would you design the product?
- How would you design a system like Google Street View?
- Given a library-style schema with books, users, and check-in/check-out data, write a query to find for each user the number of books they checked out and did not return before the due date, and return the username and…
- What would you do when there is a customer drop or a specific metric drop in the dashboard for an Instagram-like product?
- Walk me through your experience and what you delivered in your previous projects.
- Is this a valid palindrome?
- You're the product manager for notifications, basically the bell icon in Facebook. Why would Meta want to build this, how would you set goals, and how would you measure success?
- How would you handle an underperforming engineer?
- How do you measure the success of a payment product?
- Design a data model for an Uber ride app.
- Given a product problem, what metrics would you come up with, how would you measure them, and why do they matter here?
- How would you approach depth from a single image?
- Here is how you were evaluated in the first coding rounds and what to expect in the onsite.
- When you have a team you disagree with, how do you deal with conflict?
- It was a 30 minute call with 2 SQL questions and one product case study using the tables from the SQL
- Implement a k-nearest neighbor search.
- Can you walk me through your experience and the projects you've been working on?
- You're a product manager at Meta. You've been put in charge of a brand new product for volunteering. What would you do and why?
- Design TikTok's video recommendation system.
- Given users, books, and checkout data, find the number of users who checked out books in the geography category grouped by age.
- Based on your product sense answer, design a data model for that use case.
- Walk me through one of your most recent projects.
- Vertical level order traversal of a binary tree.
- Comments on group posts are decreasing day by day. What data will you pull to look at why it is happening?
- If you had a high performer on your team, how would you continue to motivate them?
- How do you measure the success of a marketplace?
- Given a stream of Uber ride requests, compute the number of ride requests in every 15-minute window.
- How do we determine if X is better than Y?
- Implement find your way through a maze
- What's the general idea for the third question?
- Tell me about a time you had conflict at work.
- Now move over to the Meta Llama board and prototype the solution you have in mind.
- Assume you are building an e-commerce site like Amazon. What security threats do you see, and how would you handle them?
- Find the number of people who checked out a book on the same day that another person returned that same book.
- Answer generic Python questions.
- Can you walk me through your previous experience, including projects you've worked on and what you studied?
- Solve this maze traversal problem and use the AI tools however you normally would.
Showing 40 of 356 questions. Open any experience for every question and how the candidate answered.
All 89 Meta interview experiences
“Overall, it followed Meta's typical PM loop and most questions came from the Meta question bank. What didn't go well is the time recruiter takes to schedule and team match time it takes.”
“The interview was a standard FAANG type of interview, where the recruiter screen talked about resume and behavioral questions, and the first coding round was a non-AI traditional leetcode question.”
“What caught me off guard was that one of the coding rounds was not generic LeetCode at all. It was AI coding, with things like sparse matrix times vector multiplication and k-nearest neighbor…”
“Very rigorous. Interviewers were in a rush. I believe it’s crucial to get a feel of what you should expect during the interview and what kinds of signals you need to give. So I strongly recommend…”
“Was hard, and the interviewer tried to get me focused, but I was just too excited. They asked me to build a renters product with them, and the product strategy question just didn't go well. I…”
“The process was pretty rigorous, mainly because the bar at E6 felt more about scope and judgement than just solving the questions. Recruiter was clear and helpful. The coding rounds went ok, but I…”
“traditional interviews for MLE. coding rounds are AI-enabled meaning you can use claude or codex to write the code.”
“The interview went smoothly overall. 1 round of phone screen followed by the full loop of 4 rounds packed in a day. 2 coding 1 behavior 1 system design.”
“The process was smooth, general interview skills, prepare well to discuss you solution before coding / jumping to the optimized solution”
“The process was more rigorous than anything I’d done at other big tech companies, but the recruiter was accurate and helpful about what to prepare, which I really appreciated. A few things did catch…”
“Casual and easy. Questions are standard and not difficult. there are many follow up questions though.”
“My interview process took a bit longer because a lot of sessions were rescheduled due to reorgs at Meta. Recruiter was helpful in providing guidance in between sessions”
“The questions were concentrated to product sense and analytical thinking, but there were a lot of follow-up questions for each case.”
“The questions weren't too difficult, and the interviewers were friendly enough.”
“Process was good and people were nice. I think it was rushed at times on back to back interview so better to break them.”
“Process was nice, hard questons, too many interjections by interviwers. But structured responses can sail you through”
“Meta is still leetcode heavy and medium to hard questions should be expected. Since it's leetcode style interview you can predict the out come and also prepare easily. What didn't go well - For the…”
“Not all interviewers may be able to adequately ask the right questions to go in depth, but they are absolutely looking for you to provide that depth by yourself. Your examples should not be surface…”
“The interview is definitely hard, but achievable with preparation because the timing is very less. In the screening, you get five Python and five SQL in one hour, and you need to pass at least three…”
“It was really fast, about 2 weeks total, I felt like I answered the qeustions perfectly but I didn't make it to the full loop round.”
“The interview began with a brief self-introduction, followed by two questions: Most challenging project. What do you want to work on at Meta? The discussion lasted exactly 15 minutes. The…”
“The overall process was rigorous and comprehensive, more challenging than many interviews I have done with other large technology companies. However, the recruiter’s guidance was accurate and…”
“The overall process was rigorous and comprehensive, more challenging than many interviews I have done with other large technology companies. However, the recruiter’s guidance was accurate and…”
“Technical screening wasn't that hard. Have to solve 3 SQL and 3 Python. You are fighting against the time.”
“More difficult than I had expected. The questions were new, and there was a lot more counter questioning than expected. Especially in the product design round.”
“Overall, the interview process was pretty straightforward and well organized. The interviewers were friendly and gave me a good opportunity to talk through my experience and approach to problems.…”
“Overall, I felt that the interview went well. I was able to clearly explain my experiences, discuss the projects I have worked on, and connect them to why I was interested in the position. I was…”
“The Overall Interview ProcessStep 1: Online Assessment (OA): A 60-90 minute screening on platforms like Codility or HackerRank, often featuring 2 LeetCode Medium coding questions and sometimes logic…”
“I basically felt like a guinea pig because Meta had just rolled out the AI PM round, and after I vibe coded a volunteering app in Llama the interviewer started grilling me on token usage, latency,…”
“The interview process consisted of several stages: an initial recruiter screening, an online assessment, technical/product interviews, and a final round of behavioral interviews. The recruiter…”
“The AI enabled round was actually pretty unique. I used bit mask first, then hit a collision because the input had letters and numbers, and the LLM started hallucinating new functions, so I had to…”
“There’s a new AI coding section I haven’t seen before. They still want to test my coding skill, so I first implement by myself, then use AI as a code reviewer for readability and missing test cases.”
“Meta interviews are extremely structured, with very little small talk. The questions can sound simple, but they’re actively looking for signals and they expect a detailed, end-to-end solution.”
“The process was more rigorous than most interviews I’ve done at other large tech companies. The recruiter was accurate and helpful about what to expect, which made it easier to prepare. The…”
“In the age of AI, I could feel the interviewer adding little follow-up questions just to make sure I actually understood the problem, because if you were using AI tools, there’d be a lag. Even…”
“I was really confident of getting an offer, but they told me I scored higher on the management side and failed coding and product design. What surprised me most was hearing the product design…”
“One of my interviewers felt a bit more like a rainy day. They had a specific framework or pathway in mind and wanted me to go down that path, even though that’s not where I wanted to go with my…”
“I had done really poorly on the easy coding question, but I still got through to the next round, which was really surprising. Then in behavioral, the interviewer said, "that does not sound like a…”
“I got feedback that I performed well on the coding interviews even when I did not feel like I performed up to a requisite level, so I think the bar has more flexibility than we may give ourselves…”
“The process started with a recruiter screening testing some behavioral questions and some technical questions she read from a question bank. Then, I did a coding interview online. Finally, a 4…”
“The process was standard, with a recruiter chat first, then scheduling round 1 with 2 PMs: 1 on product sense and the other on metrics. Product sense - the interviewer likes to know how you frame…”
“I was a little complacent because I’m already ex-Meta, and the surprising feedback was that my project retrospective was only leaning toward hire because I answered a constructive feedback question…”
“Fairly solid process. Recruiter was helpful with quick turnaround. Felt a little rushed during team match”
“The process was very straightforward. In both technical rounds, I was asked questions from the top 50 Meta tagged LC questions list. Behavioral was also very standard.”
“I basically treated this interview like a syllabus. I found the common Meta PM question bank online, practiced it in mocks, and most of the actual questions came straight from that same list.”
“I think I was one of the first people to take Meta’s AI round, and the models I had were really bad, like ChatGPT mini. I tried asking for test cases and it would just spit out something completely…”
“What stood out to me is that every loop round started with product sense, then I had to turn that answer into a data model, and from that they jumped straight into SQL and Python. One case was even…”
“Clear, some interviews are chiller than others. Just need to put in the work and you'll be okay. Should know all of the Meta products well enough to do an interview on them.”
“It was hard. Two medium leet code in 45 minutes and you're alright. System Design needs lots of practice and quick explanations.”
“Culturally, they struck me as much more direct about conflict than my current company. The vibe was state your view, defend it with data, then move on. They also wanted every answer tied back to the…”
“Overall pretty straightforward, their interviews are pretty standard and are not there to surprise you. Recruiter and interviewers were professional.”
“It was nothing different than the guide they give you. Just learn everything on there are it is a straight forward interview. It is a rolling hiring so you can schedule your interview a month out so…”
“The internal tooling and the data is incredible. When I was there last year, they had their own Meta AI wired into the most commonly used databases, so I could reference tables and column names and…”
“Overall the interview process went very smoothly. I was suprised at the time to get an AI related product sense question since the majority of the ones I had prepared were more standard (solution…”
“It was as expected since this was my second time interviewing with them. With practice, the loop is fairly reasonable. Did not pass the behavioral questions before.”
“The interview was highly rigorous but followed a format: four interviews and then five rounds of on-site. The preparation material provided by the recruiter did really help. It's always better to…”
“It was as expected. SQL: First define the metrics and then code them Product sense: How do you measure the success of a product/feature type questions with follow-ups Probability and statistics with…”
“It was a pretty standard interview. Didn’t have a single behavioral and everything was based on the technical, didn’t do perfectly, but still got the offer”
“Standardized”
“The process was fine and there was really little feedback during the interview so i couldnt tell how i did”
“One of the technical rounds was ridiculous, a LC hard (LC3548) ML Systems Design was pretty standard - design a recommender system Behavioral round fairly standard”
“The technical rounds were generally well structured and covered both coding and system design. I performed well in most of the technical discussions, but I found the system design round more…”
“- everyone was super nice - questions were like leet code but with a twist - time complexity always asked”
“The bar for leetcode was lower for PE rather SWE, but there was 2 rounds on SRE debugging and Linux debugging.”
“The process was rigorous. SQL speed and precision is the key. In depth product sense, modelling concepts are needed.”
“It went well it was clear on what to expect and the recruiters do prime you well from the start. They will let you know what to expect and prep required per stage. Usually there was enough time and…”
“The interview process was fast-paced and heavily practical. It consisted of an initial recruiter screening, a past project deep dive, a live technical case study focusing on customer scenarios, and…”
“The recruiter was very accurate on the whole process. The interviews are very structured. learn the frameworks for the questions and cases.”
“Not a hard process. Just communicate clearly. Must talked in a structured approach and take your time.”
“The process was very straightforward. The recruiters are very good. Most of the questions you can find online for coding and they are relatively easy. For the design round, if you practice the…”
“The process was overall good, recruiter provided lots of advice and pointers for what to study. The biggest challenege is the pressure and time crunch on making sure you can answer everything but…”
“Leetcode was doable based on the LC premium curated list, questions were similar. Culture round required thorough prep of examples for similar questions”
“The process was very nice, interviewed by people that would not be in my next team, but everybody was exceptionally nice. The questions in the ML system design round were not very deep and were more…”
“My interview process started with a CodeSignal GCF online assessment that had four sections with increasing difficulty. The earlier sections were more straightforward and focused on implementation…”
“Practice leetcode fundamentals (graph, tree), practice system design fundamentals, speaking/thinking out loud, being able to explain full flow of what happens from when user/request is received to…”
“It went pretty well. The interviewers were very nice, so it was easy to talk through my behavioral stories without putting on a super professional act. Coding challenges were mostly medium leetcode…”
“Initially considered for IC6 but performed poorly in the system design so got down-leveled to IC5. For IC6 consider how your system interacts with other systems.”
“The whole process was smooth for me, prepared well from meta tagged leetcode questions and for system design hello interview was more than enough”
“The overall interview process with Meta was structured and fairly fast-paced. The interviews focused on technical problem-solving, system design, and behavioral questions, with an emphasis on…”
“It mostly went well. I was thrown off by the fact that a lot of the focus in the system design rounds was on the product and UX side, only to discover it was product architecture later and that…”
“Coding focussed with focus on leetcode style problems. The design prompts are simple and abstract like design netflix or design instagram, etc. It is upto you to drive design discussion and this…”
“Everything was smooth. Interviewers were super friendly. They made me feel comfortable. I took my time to prepare which i highly recommend”
“The process was what was expected and they were quick in scheduling and re-scheduling as needed. All questions were ones I had seen before via LC tagged.”
“Similar to SWE Internship recruiting, just easier LC and addition of SQL questions. Actually had 3 rounds, not 2.”
“Technical questions move fast, dont trip on edge cases. 2 questions in 60 min slot, with multiple followups. Code quickly. With 10 min of intro and questions theres not much time.”
“It was an extremely smooth process, though team matching was rough. Questions didn't need to be 100% right interestingly, as one of the rounds I didn't finish.”
“Along the interview process, I think the recruiter reached out and she was very friendly. Things were smooth. I think I had multiple rounds and overall the interview process was great.”
“It was overall a smooth experience. Be prepared to wait for 2 weeks to schedule interviews due to lack of interviewers.”
“At Meta, a product growth analyst is not considered any less than a PM. About 40% of them convert into PMs in one or two years because you are expected to know how even a red button versus a blue…”
Frequently asked questions
How many rounds are in the Meta interview?
Candidates report a typical 3 rounds, usually including a recruiter screen, online assessment, phone screen, take-home assignment.
How hard is the Meta interview?
Candidates rate it 3.3/5 on average (medium), across 89 interviews.
How long does the Meta hiring process take?
About 4 weeks from first contact to decision, based on reported timelines.
What percentage of Meta candidates get an offer?
57% of candidates with a final result got an offer (39 of 69).
What does the Meta interview focus on?
The most common round types are Behavioral, Coding, System Design, Technical.