real interview stories, told over a cup of tea ♡
Meta Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
83 results
- 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 2026Rejected
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 2026Offer
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…
- Six Weeks of E5 Preparation and an Equity NegotiationMeta · Software Engineer · Senior+ · Onsite · Aug 2026Offer
Sharing my recent Meta E5 interview experience. Hope it helps people preparing. Background: Bay Area Backend / Distributed Systems About 7 years of experience Target level: E5 Senior Software Engineer Preparation time: About 6 weeks Overall impression: Meta E5 doesn't lean especially heavily on hard algorithms. It looks more at a senior engineer's overall ability: consistent coding, depth in syst…
- Four-Round Onsite, Rejected After Two AI Coding RoundsMeta · Machine Learning Engineer · Onsite · Jul 2026Rejected
I applied online to a search/ads/recommendation MLE role. The onsite was four rounds in total: behavioral, system design, and two rounds of AI coding. The behavioral round was just everyday questions, and the system design was a recommendation system. For coding, one question was a triple card game and the other was the maximum number of unique characters, both of them questions you can find onli…
- Meta Data Engineer interview with timed SQL, Python, modeling, and product scenariosMeta · Data Engineer · Technical Screen · Jul 2026
After recruiter outreach, I went through a structured set of rounds built around speed and clear problem solving. The recruiter call covered role fit and process details. Then came a technical screen with several SQL and Python tasks under tight time limits. I had to keep working until each task was fully resolved with the expected results, while the interviewers kept returning to my thought proc…
- Meta Data Scientist interview: timed SQL cases and A/B experiment designMeta · Data Scientist · Technical Screen · Jul 2026
After a recruiter and screening step, I faced a fast, high-pressure set of SQL and case tasks. The Python and SQL round covered SQL mechanics and quick reasoning, including common data structures, CASE statements, and window functions. The pace stood out because the window closed as soon as it was time for the case study, so accuracy and efficiency both mattered. The case work was more demanding…
- Meta Machine Learning Engineer interview with a conversational-assistant design and declined offerMeta · Machine Learning Engineer · Onsite · Jul 2026Offer
The process dragged on longer than I expected. It felt drawn out from the early weeks onward. I went through screenings on core ML knowledge, including attention and its variants, before later stages shifted into more high-pressure technical work. Onsite day was intense and tightly structured. In the system-design round, I had to build a conversational assistant and include safety measures. That…
- Meta Machine Learning Engineer interview: paperwork after technical roundsMeta · Machine Learning Engineer · Technical Screen · Jul 2026
The technical rounds were not the main issue for me. A friendly, detailed recruiter screen covered the role and its expectations, then I moved into familiar LeetCode-style coding interviews with screen sharing. The coding itself did not feel unfair. I handled the problems and kept the normal pace while explaining my approach. Even so, I did not get an offer, and the reason I heard was paperwork r…
- Meta Product Designer interview: peer rounds followed by a bench waitMeta · Product Designer · Technical Screen · Jul 2026
I went through three peer interview rounds with technical and behavioral parts. The format matched what I had seen for this type of role, and the technical questions lined up with the resources I had found beforehand. After those rounds, I expected a decision to move forward. Instead, I was told to wait while they decided which team or role might fit me. I understood it as something like being he…
- Meta Product Manager interviewMeta · Product Manager · Technical Screen · Jul 2026
After the recruiter stage, I had two timed, structured parts: product sense and product analytics. Product sense required a clear framework, while analytics tested how I interpreted and used data. The interviews resembled common mock formats, where I had to walk through an approach rather than have a free-form discussion. I used the framework I had prepared, but the analytics bar did not match wh…
- Meta Software Engineer Interview Experience: A fast coding loop with system design and values checksMeta · Software Engineer · Technical Screen · Jul 2026
The process began with a recruiter call, then continued through several rounds that mixed fast coding, system design, and behavioral checks. The coding loop was intense. I had two data-structure and algorithm problems in a tight window and had to keep moving even when the clock made every step feel consequential. I remember needing to solve problems quickly while also justifying my approach. Syst…
- Meta Software Engineer Interview Experience: Easy and medium LeetCode with time-space trade-offsMeta · Software Engineer · Online Assessment · Jul 2026Offer
After a recruiter reached out, I started with an online assessment. Then I moved into the technical loop. The first coding sequence had two LeetCode problems, one easy and one medium. I had to explain my approach thoroughly, including why I chose certain data structures and what the time and space trade-offs were. The next rounds continued in the same coding-focused style through virtual meetings…
- Meta UX/UI Designer interview: full loop canceled before scheduleMeta · UX/UI Designer · Other · Jul 2026
I began with a recruiter phone screen and then met the hiring manager. The hiring manager told me to prepare for the full loop, so I organized around completing the rest of the process. The full-loop interview was canceled one day before it was scheduled because the role no longer existed. I never reached the later rounds. Having completed the early steps and prepared for more, I felt disappointe…
- Meta UX/UI Designer interview: peer rounds followed by a bench waitMeta · UX/UI Designer · Technical Screen · Jul 2026
I went through three peer interview rounds with technical and behavioral parts. The format matched what I had seen for this type of role, and the technical questions lined up with the resources I had found beforehand. After those rounds, I expected a decision to move forward. Instead, I was told to wait while they decided which team or role might fit me. I understood it as something like being he…
- Meta Data Scientist interview: SQL, product sense, and the full loopMeta · Data Scientist · Technical Screen · Jun 2026Rejected
A recruiter contacted me first, and I then went through what felt like a standard path from screening to the loop. The initial technical screen covered SQL and product sense. The questions were very much about connecting data work to business decisions. A couple of weeks later, I moved into the full loop. That loop had four rounds: analytical execution, analytical reasoning, technical skills, and…
- Meta Software Engineer interview: 45-minute coding and leaderboard designMeta · Software Engineer · Technical Screen · Jun 2026
After I was scheduled, I had a coding round built around speed and follow-through. I worked through two LeetCode-style problems in 45 minutes and focused on optimization. At least one had a follow-up that required improving the solution instead of stopping once it worked. The onsite loop added coding, behavioral discussion, and system design. The design question involved a leaderboard-style compo…
- Bombed Coding, Strong Design Rounds, Follow-ups Before E6 Team MatchingMeta · Software Engineer · Senior+ · Onsite · Apr 2026In progress
Meta had been on my wishlist ever since it began hiring in Bangalore in February 2025. An old colleague, now an E7, gave me a referral, and through all of 2025 I applied to a wide spread of openings without once checking the level requirements. Job alerts were on, and any new posting got an application from me right away. At some point a recruiter hiring for an E6 role based in London reached out…
- E5 Full Loop with a Card-Deck AI Coding RoundMeta · Software Engineer · Senior+ · Onsite · Apr 2026
Recruiter reachout came in late February. After that, every step got scheduled about a month out — the whole process moved at a pretty relaxed pace. Phone Screen LC 65 (medium; also the second question from a 12/4 compiled coding list on the forum). VO (virtual onsite) Coding: LC 121; LC 199 AI coding: a card deck problem BQ: favorite project (scope/complexity) / conflict resolution / moving fast…
- Five Rounds Including AI Coding and a New Agentic System Design RoundMeta · Software Engineer · Onsite · Apr 2026Rejected
The full loop has a new format now — five rounds, and I got the rejection letter a week later. Round one, behavioral (BQ). Went pretty well — the usual how-do-you-resolve-conflict stuff, plus some talk about impactful projects, especially AI projects. Round two, AI coding: a card game — find three cards that sum to 15. Split into three steps: find the bug, implement the algorithm, optimize the al…
- Passed a Four-Round AI-Enabled Onsite, Team Match Still in LimboMeta · Software Engineer · Senior+ · Onsite · Apr 2026In progress
Position: Software Engineer, Product Result: Target E5 Pass The OA was pretty old at this point, but the questions are in the forum's question bank. The recruiter waived my phone screen and put me straight into the onsite. The onsite was 4 rounds total. AI-Enabled System Design Billed as "AI-Enabled," but the interviewer seemed to be doing this format for the first time — his question bank wasn't…
- Passed the Screen, Then the Full Loop Was CancelledMeta · Engineering Manager · Senior+ · Technical Screen · Apr 2026
This one began well. A recruiter contacted me first, and she was friendly, professional and really helpful. In this market it is hard to even get a recruiter to notice you, so that alone felt like a big deal. They were flexible about scheduling, and I booked my screening for the EM1 role about two weeks out. To get ready I used an online interview prep course. I worked through all of the top syst…
- Two Phone Screens and an Inexplicable RejectionMeta · Site Reliability Engineer · Senior+ · Technical Screen · Apr 2026Rejected
Two phone screens for Meta PE (the SRE-equivalent role there), 45 minutes each. Round 1, System (full-loop troubleshooting): same prompt as another thread posted on this forum, but the interviewer didn't seem to have a specific answer in mind. They asked a bunch of pretty open-ended things — how do you make sure everything keeps running smoothly during the days you're on call? If something breaks…
- Bombed Algorithmic Coding, Got a Retry and Reached Team MatchMeta · Software Engineer · Senior+ · Onsite · Mar 2026In progress
Background A recruiter cold-emailed me about an E5 position at Meta two years ago. I was already half-looking to leave my job, so I went for it. I made it to the last round, but the product architecture round and one of the coding rounds went badly for me. I'm back this time because layoffs look likely where I work now, and I wanted to prepare differently. My prep came down to three things: an on…
- Same Forum-Famous Questions, Completely Different NumbersMeta · Data Scientist · Onsite · Mar 2026In progress
SQL: Active Ads AR: Ads algorithm AE: Fake account Behavioral: Breakthrough project, disagreeing with someone, reporting to someone new to the team, how to make others feel welcome These are all old questions from the forum — really grateful to everyone who shared before me. Though it might be because they're old questions, the interviewer had changed them. The SQL one especially — same framework…
- Strong E6 Onsite, Rejected at Hiring CommitteeMeta · Software Engineer · Senior+ · Onsite · Mar 2026Rejected
A while back I interviewed for an E6 INFRA role at Meta. Every single interview felt positive, but I ultimately got cut at the hiring committee round, with no specific feedback. Pretty frustrated, but nothing to do except move on. Phone screens: I got "Er Liu" and "Odd Mutant" — aced both. Onsite coding: "Commander" and "Yao San San" — also aced both, and the follow-up edge cases the interviewer…
- the OA Was Basically the Same as a Study ArticleMeta · Software Engineer · Online Assessment · Mar 2026
The Meta RS OA wasn't too hard. I'd previously studied from an article that turned out to basically be the exact same questions. Q1: You need to find the index computed from rating divided by prices. If two entries tie, keep the one with the smaller index. When comparing, you don't need to compute the actual decimal — just cross-multiply to compare the two fractions directly. Q2: You need to comp…
- Two AI Coding Rounds, a LeetCode System Design, and an AI-Enabled Design Round With No AIMeta · Software Engineer · Onsite · Mar 2026In progress
Two AI coding rounds, one traditional system design, one AI-Enabled Design round. AI coding 1: Max Unique Character Subset — given a list of words, find a subset of words where no two words in the subset share any repeated letters, and the subset covers the largest possible total number of unique letters. AI coding 2: Kind of a mess. This round the interviewer opened by telling me he hadn't reali…
