2026 Meta AI-Native Coding Interview, Experienced SWE and MLE Onsite: 3 Experiences
- Company
- Meta
- Reports
- 3 interview reports
- Level
- Full-time
- Stages
- Onsite
Meta calls them "AI-native coding" rounds, and every onsite in this set had two of them. The two software engineers who described their tasks got hard algorithm problems to solve with an AI model, not features to build.
Coverage: Experienced full-time hires who were changing jobs: two software engineers (one at E6, one whose level wasn't given) and one machine learning engineer. All three describe the onsite, and the two software engineers also mention the phone screen. The interviews took place in July–September 2026 and October–December 2026, and the reports went up between September 15 and November 10, 2026. No locations were given.
Roles in this article
- Software engineer, 2 reports: Kitchen Orders, Maximize Unique Characters, friend recommendations and a 36-card game in the AI-native rounds, plus four system design questions.
- Machine learning engineer, 1 report: two AI coding questions named without detail, plus two ML system design rounds.
Software engineer: Meta AI-native coding onsite (2 reports)
What came up
Both software engineers had an ordinary coding phone screen and then two AI-native coding rounds at the onsite, with Claude and GPT models to choose from. Both accounts keep returning to one tension: getting the AI's code right before trying to make it fast.
| Topic | Reports | Most recent report |
|---|---|---|
| Two AI-native coding rounds at the onsite, Claude or GPT models | 2 of 2 | Nov 10, 2026 (interview Oct–Dec 2026) |
| Checking the AI's code for correctness before optimizing | 2 of 2 | Nov 10, 2026 (interview Oct–Dec 2026) |
| Classic system design in the other onsite rounds | 2 of 2 | Nov 10, 2026 (interview Oct–Dec 2026) |
| Coding phone screen with no AI | 2 of 2 | Nov 10, 2026 (interview Oct–Dec 2026) |
| Scheduling steps across workers to finish fastest | 1 of 2 | Nov 10, 2026 (interview Oct–Dec 2026) |
| Picking words with no shared characters | 1 of 2 | Nov 10, 2026 (interview Oct–Dec 2026) |
| Friend recommendations on a large graph | 1 of 2 | Sep 15, 2026 (interview Jul–Sep 2026) |
| Card-game search with a benchmark over many games | 1 of 2 | Sep 15, 2026 (interview Jul–Sep 2026) |
Each report can count toward several rows. Both reports also had a behavioral round, with no questions named.
Questions we found
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Kitchen Orders: assign each recipe step to one of three chefs so the whole order finishes as early as possible | 1 report | Oct–Dec 2026 (report date Nov 10, 2026) |
| Maximize Unique Characters: choose words that share no characters so they cover as much of an alphabet as possible | 1 report | Oct–Dec 2026 (report date Nov 10, 2026) |
| Mutual-Friend Recommendations: recommend friends from users and friend pairs, tested up to about 100k users | 1 report | Jul–Sep 2026 (report date Sep 15, 2026) |
| Partition a Card Deck into Fifteens: a 36-card game of picking three cards that sum to 15 | 1 report | Jul–Sep 2026 (report date Sep 15, 2026) |
System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Ads click aggregator (Design an Ad Event Measurement Platform) | 1 report | Oct–Dec 2026 (report date Nov 10, 2026) |
| News feed (Design a Following News Feed Service) | 1 report | Oct–Dec 2026 (report date Nov 10, 2026) |
| Game score leaderboard that shows the nearest scores after a game (Design a Social Game Score Leaderboard) | 1 report | Jul–Sep 2026 (report date Sep 15, 2026) |
| Ride sharing (Design Ride-Hailing Dispatch and Trip Lifecycle) | 1 report | Jul–Sep 2026 (report date Sep 15, 2026) |
The last two were Meta's "AI-enabled SWE system design" rounds.
2 detailed candidate timelines
01: E6 engineer, failed after missing a bug in the AI's code
Report date: Nov 10, 2026 · Interview period: Oct–Dec 2026 · Role: Software engineer, E6 · Experience: changing jobs, referred · Result: Rejected
Phone screen
- Traditional coding with no AI. The problems weren't named.
Onsite: AI coding round 1, Kitchen Orders
- A kitchen has to cook one order made of several dishes. Each dish follows a recipe, which is a fixed sequence of station steps.
- Every step goes to one of three chefs, and the goal is to finish the whole order as fast as possible.
- Sending each step to its fastest chef is only a start. The order in which the steps are scheduled matters too: in the round's three-dish example, a better order saved 30 seconds.
Onsite: AI coding round 2, Maximize Unique Characters
- The input is a list of words and an alphabet. The task is to pick a set of words that covers as many characters as possible, with one rule: no two picked words may share even one character.
- This round went wrong. The candidate didn't read the AI's code closely, missed a bug, and moved straight on to optimizing it. With about ten minutes left, the interviewer tested correctness and found the problem. The candidate fixed it at the last second, but still failed.
How the AI rounds worked
- Both Claude and GPT models were available.
- The candidate didn't have to write their own tests.
- The models felt like weaker versions of the public ones, and what they wrote wasn't always free of bugs.
- Before sending a prompt, the candidate had to explain the plan and get the interviewer's approval.
Onsite: system design and behavioral
- System design 1 was an ads click aggregator.
- System design 2 was a news feed.
- The behavioral round used the usual questions; none were named.
The candidate said every question in this loop had been reported by other candidates before.
02: Engineer who passed, with a detailed playbook for the AI rounds
Report date: Sep 15, 2026 · Interview period: Jul–Sep 2026 · Role: Software engineer, level not given · Experience: changing jobs, referred · Result: Passed
Phone screen
- Two LeetCode-style problems, one easy and one medium, with no AI.
Onsite format
- Two "AI-native coding" rounds, two "AI-enabled SWE system design" rounds and one behavioral round. Those were Meta's own names for the rounds, according to the candidate.
- The coding rounds were harder algorithm problems handed over as a whole folder of mostly written code. The candidate, working with the AI, filled in the core logic.
- Each round was a fresh CoderPad session of about 40 minutes. The candidate worked in Java with Maven.
- The code ran in a shared container with roughly 1.5 CPU cores and 2 GB of memory, so multithreading or several agents at once weren't an option. The tools were sometimes flaky: one could report a timeout even though the edit had gone through.
- The models offered were Claude 4.8 and GPT 5.5. GPT 5.6 was already out, but the interview only had 5.5, and the candidate guessed the interview models trail public releases by a month or two.
Onsite: AI coding round 1, friend recommendations
- Given users and pairs of friends, implement a friend-recommendation strategy: friends of friends, popular users, and similar signals. The closest practice version is Mutual-Friend Recommendations, which keeps the mutual-friend ranking core.
- There were three test suites. The third had about 100k users and 1.5 million friend pairs, so it worked as a stress test.
Onsite: AI coding round 2, the 36-card game
- A deck of 36 cards with values 1–9. A move picks three cards that sum to 15.
- Only about 16 cards sit on the table at a time, and three new ones are dealt after each pick. You win if all 36 cards get used, which means 12 groups.
- The candidate had to write new tests that benchmark the algorithm over a large number of games, more than 1,000.
- Their final result: a 99.97% win rate on the 10k-game case, in 40 seconds.
- Partition a Card Deck into Fifteens practices the core question of whether a fully visible deck can be split into fifteens. It doesn't simulate the 16-card table or the benchmark.
How the candidate ran the AI coding rounds
- They opened each session with a prompt that told the AI about the time limit and the environment, and re-entered it every round since each one started fresh.
- They had the AI read the code and the task first, then restate the goal and what counted as passing.
- Correctness came first, then speed. They aimed straight for the final optimized algorithm instead of writing a brute-force version first.
- They worked in chunks of 2–5 minutes covering plan, implement and test. Any AI reply that would take more than about three minutes of work had to be broken down first, with the expected gain, effort and risk stated before any optimization.
- They kept outputs short and skipped test runs that weren't needed, since every Java run meant a build. No background or long runs, always a timeout, single-threaded only.
- They re-read files after every edit, because of the flaky timeout reports.
- For speed work they used a small measurement harness with a fixed seed and sample sizes of 20, then 100, then the full set. No claim of a speedup without a before-and-after on the same sample, and a running changelog.
- They warned that newer models may start the big test suites on their own and burn time, or hang before any optimization happens.
Onsite: AI-enabled system design
- The AI here was just a chat window offered "to unblock yourself", and the candidate found it close to useless. Neither interviewer gave it a real use.
- Design 1 was a video game score leaderboard: players, games, friends and high scores, and after a game, show the scores closest to the player's. The candidate saw it as a range search over a large dataset.
- Design 2 was ride sharing.
Onsite: behavioral
- One round. No questions were named.
Machine learning engineer: Meta AI coding and ML design onsite (1 report)
What came up
The one MLE report lists two AI coding questions that the author called frequently reported, without describing either, and two ML system design rounds: weapon-sale detection and video copyright matching.
Questions we found
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Ordering system for a menu (named only) | 1 report | Jul–Sep 2026 (report date Nov 6, 2026) |
| "Unique string" problem (named only) | 1 report | Jul–Sep 2026 (report date Nov 6, 2026) |
ML System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Design Video Copyright Matching Against a Reference Library | 1 report | Jul–Sep 2026 (report date Nov 6, 2026) |
| Design Weapon-Sale Ad Detection and Review | 1 report | Reports: Jul–Sep 2026 (report date Nov 6, 2026); Additional FastPrep history: May 29, 2026; Apr 24, 2026 |
1 detailed candidate timeline
03: MLE onsite, waitlisted
Report date: Nov 6, 2026 · Interview period: Jul–Sep 2026 · Role: Machine learning engineer · Experience: changing jobs, came through a headhunter · Result: Waitlisted
Onsite: AI coding
- Two questions, both of which the author called frequently reported: an ordering system for a menu, and a "unique string" problem. Nothing else about them was shared.
- The names sound close to Kitchen Orders and Maximize Unique Characters in report 01, but this report gives too little to say they are the same tasks.
Onsite: ML system design 1, weapons detection
- The author called it a heavily repeated question and didn't remember anything unusual. Practice version: Design Weapon-Sale Ad Detection and Review.
- The interviewer was friendly the whole way, barely pushed back on the design, and now and then mixed in questions on ML basics.
Onsite: ML system design 2, copyright detection
- How do you check whether an uploaded video duplicates one in a copyright library? Practice version: Design Video Copyright Matching Against a Reference Library.
- The main focus was comparing videos of very different lengths. The author had no experience with this and improvised.
Patterns across the reports
These patterns come from the two software engineer reports (01 and 02). Report 03 is a different role, so it stays out of the comparison.
-
AI only at the onsite. Both had a phone screen of ordinary coding with no AI, then two AI-native coding rounds at the onsite next to two system design rounds and a behavioral round.
-
Tests were mostly provided, with an exception. Report 01 didn't have to write tests. In report 02, the friend-recommendation round came with three test suites, the last one a stress test, while the card-game round asked the candidate to write new benchmark tests over more than 1,000 games.
-
Correctness before speed. Report 01 lost a round by optimizing AI-written code that still had a bug the interviewer then found. Report 02 checked correctness first and only claimed speedups measured on a fixed sample.
-
The interviewer stays in the loop. In report 01, every prompt needed the interviewer's approval of the plan first. Report 02 described the interviewer watching the whole exchange with the AI, which made a wrong turn costly.
-
System design stayed classic. Neither report describes AI changing the design questions. In report 02, the AI on offer in those rounds was a chat window the candidate barely used.
Keep practicing
- Mutual-Friend Recommendations: the friend-recommendation core from report 02's first AI-native round.
- Partition a Card Deck into Fifteens: the sum-to-15 card question from report 02's second AI-native round.
- Meta system design from these reports: ad event measurement and following news feed (report 01), social game score leaderboard and ride-hailing dispatch (report 02), weapon-sale ad detection and video copyright matching (report 03).
- Meta project coding questions: Meta's codebase-style practice projects. Sign-in required.
- Meta system design questions: every Meta design question on FastPrep. Sign-in required.
- Meta interview guide: Meta's interview process and question list.
- Meta hiring insights: hiring data for Meta.
- Experience feed: more candidate reports from every company.
AI coding rounds at other companies
- Google: Google AI coding interview: an online assessment with HackerRank's built-in assistant, and a live round on a multi-file project where using AI was optional.
- Stripe: Stripe AI coding interview: experienced engineers kept getting the same transaction rule parser, built step by step with a built-in model.
- Stripe interns: Stripe intern AI coding round: ten intern accounts of the same AI-assisted round.
- Rippling: Rippling AI coding interview: HackerRank's built-in AI on Rippling's familiar problems, plus an HR codebase at the onsite.
- DoorDash: DoorDash AI coding interview: AI CodeCraft: build and run several small services live with your own AI tool.
- LinkedIn: LinkedIn AI coding interview: one long, multi-part task in an IDE whose agent edits files directly.
- Shopify: Shopify AI coding interview: pair programming with your own AI on Shopify's well-known question set.
- Datadog: Datadog AI coding interview: bring any AI tool and share your screen; the tasks are easy, and the follow-ups decide the round.
- Capital One: Capital One AI coding interview: new grad Power Day agentic round: fix a bug, then add a feature to a large full-stack app with Claude Code.
- Bloomberg: Bloomberg AI coding interview: intern rounds that start in a small file and move to a large codebase, debugging with AI help.
- xAI: xAI AI coding interview: new grad take-homes and onsites where you build with AI.
- Adobe: Adobe AI coding interview: AI showed up as one step in a director round and in a take-home; the rest stayed classic.
- Snowflake: Snowflake AI coding interview: design and build a rate limiter or a retrying task queue while the AI writes the code; one AI Engineer onsite was in person with your own laptop.
- Snap: Snap AI coding interview: a backend-only chat service from an empty Python project with Claude or Codex, or a feature in an existing codebase.
- Ramp: Ramp AI coding interview: build inside a repo Ramp provides; one repo logged every prompt for the interviewer to read.
- Anthropic: Anthropic AI coding interview: review four pull requests, then improve one with Claude Code.
- Apple: Apple AI coding interview: CoderPad with a sidebar agent, alongside Apple's other recent interviews.
More companies with AI rounds on FastPrep:
- Amazon: Amazon interview report: an AI-assisted debugging OA (1 experience).
- Atlassian: Atlassian interview report: project coding and AI tool use (11 experiences, two parts).
- Circle: Circle interview report: three AI rounds: building, debugging and PR review (1 experience).
- Volta: Volta interview report: a deliberately vague data task with a token budget (1 experience).
Across companies: 2026 AI Coding OAs at 15 Companies: 32 Reported Problems and 2025–2026 AI Coding Phone Screens and Onsites at 43 Companies: 76 Reported Problems.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.