Blog10 min readApplr Team
Meta AI-Enabled Coding Interview (2026): What Actually Changed
Meta's AI round: 60 minutes, a multi-file CoderPad, a menu of models. Meta's own prep guide still bans ChatGPT. What's graded, who gets it, a 4-week plan.
Meta now hands some onsite candidates an AI assistant for one coding round, while the interview guide Meta gives candidates still lists "AI tools, like ChatGPT" as banned outside help. Both are true, and the gap between them is where people get confused. The AI-enabled round is not a prompting contest. It is a 60-minute test of reading someone else's code, checking what a model hands you, and explaining every line, and the candidates who struggle are mostly the ones who pasted code they could not defend.
Below: what changed and when, how the round runs phase by phase, what Meta says it grades, the ways candidates fail, whether a new grad will see it, and a four-week plan.
What changed, and when
The plan surfaced in July 2025. Business Insider, following a 404 Media report, described an internal Meta post about a coding interview "in which candidates have access to an AI assistant", pitched as closer to how Meta engineers actually work and as a way to make "LLM-based cheating less effective". Meta confirmed it was testing the idea and said humans would stay in the hiring loop (Business Insider, Jul 29, 2025).
Real loops followed within weeks. A Blind poster interviewing for an E4 infrastructure role wrote on October 4, 2025 that their onsite had become a 45-minute coding round, a one-hour AI-enabled round, a 45-minute design round and a 45-minute behavioral, and that the recruiter could not explain the new format. They later reported clearing it and moving to team matching. Hello Interview dates the rollout to October 2025 and says it covers software engineer and engineering manager loops up to E7 and M2.
What has not changed is Meta's public paperwork. The Software Engineer Full Loop Interview Guide that metacareers.com links from its onsite prep page (file labelled IC4-6, v1, retrieved October 27, 2026) still describes four to six 45-minute interviews, about two problems in roughly 40 minutes per coding round, code the interviewer "will not compile", and no dynamic programming questions. It never mentions an AI round.
| Classic coding round | AI-enabled round | |
|---|---|---|
| Length | 45 min (Meta guide) | 60 min (Hello Interview; Blind, Oct 2025) |
| Task | About two separate problems in ~40 min (Meta guide) | One multi-file project in three phases (Hello Interview) |
| Running code | Interviewer does not compile it (Meta guide) | Test runner inside CoderPad (Hello Interview; DG Learning, Apr 2026) |
| AI | Outside AI tools banned (Meta guide) | Built-in chat, switchable models, cannot edit your files (Hello Interview) |
| Graded on | Communication, problem solving, coding, verification (Meta guide) | Problem solving, code quality, verification, communication (Hello Interview) |
The practical reading: the ban covers tools you bring. In the AI-enabled round the tool is supplied inside the interview pad, and Hello Interview says your recruiter tells you in advance which of your two coding rounds it is. Running your own assistant during the classic round is still cheating.
How the round runs, phase by phase
The accounts describe the same arc. Hello Interview's breakdown, which matches PracHub's June 2026 write-up:
| Phase | What happens | AI allowed? | What it shows the interviewer |
|---|---|---|---|
| Orientation | Read the file tree, tests and instructions (about 5-6 min) | Yes, but the reading is on you | Whether you understand code before touching it |
| 1. Bug fix | A failing test; find and fix the cause | Varies by interviewer; Hello Interview suggests going without | Debugging without a crutch |
| 2. Core feature | Implement the main logic (Hello Interview estimates 120+ lines) | Yes | Planning, splitting work, checking output |
| 3. Optimization | Larger tiered inputs that a naive solution times out on | Yes | Complexity reasoning; not finishing is acceptable |
The problems are algorithm puzzles wearing a codebase. Reported examples include a maze solver with path printing, maximising unique characters from a word list, a card game where you pick three cards summing to 15, and a friend-recommendation system (Hello Interview). A Google-tagged Blind poster who sat the card-game version in November 2025 said the round opened with a failing test caused by the validation of invalid moves, then asked for a strategy that keeps playing until no valid move remains.
The pool is small. Hello Interview cites an internal source putting it at roughly nine problems; a Meta-tagged Blind commenter said in November 2025 that only four had been vetted.
The model menu reported by candidates has included GPT-4o mini, GPT-5, Claude Haiku 3.5 and 4.5, Claude Sonnet 4 and 4.5, Claude Opus 4, Gemini 2.5 Pro and Llama 4 Maverick, switchable mid-session (Hello Interview). Do not assume any of them will help. The November Blind poster called their assistant a small model that was "not too reliable"; Hello Interview reports that GPT-5 was sometimes too slow and that some candidates found the AI less useful than in practice; PracHub collected E7 reports of Claude Sonnet producing wrong logic and of a candidate losing the round to a hallucinated maze solution.
What Meta grades
Meta's line, as quoted by interviewing.io from its prep materials, is that using the AI is optional and has no bearing on the outcome. The interviewing.io author, an engineer who has worked at Meta, thinks that is not entirely true in practice, because good AI use buys time. Hello Interview's internal source put it more bluntly: use AI, but show you understand the code, and "don't prompt your way out of it". Candidates who leaned heavily on the model got negative feedback.
Meta's treatment of its own engineers points the same way, and that changed recently. In November 2025 Business Insider reported that "AI-driven impact" would become a core expectation in 2026 reviews. Then a September 2026 memo from executives Maher Saba and Santosh Janardhan said Meta "will not use AI adoption dashboards or token counts to evaluate impact", and told managers to judge output quality, velocity, problem complexity and scope instead (InfoWorld, Sep 4, 2026). The trigger was "tokenmaxxing": engineers burning tokens to climb internal leaderboards (The Decoder, Sep 8, 2026).
My read, not Meta's statement: an interviewer working inside that culture is not counting your prompts. They are watching whether the code that ends up in the file is correct, whether you caught what the model got wrong, and whether you can say why.
What gets people rejected
- Pasting what you cannot explain. DG Learning (April 2026) calls big unreviewed pastes a red flag and notes that interviewers watch every AI interaction. Paste in small pieces and say what each one does.
- Skipping the read. Hello Interview reports candidates who regretted jumping at the bug before reading the code. Spend the orientation minutes on the tests; they define what "done" means.
- Trusting a weak model. See the reports above. Have a plan for finishing phase 2 if the assistant gives you nothing useful.
- Not recognising the algorithm. Hello Interview says candidates who knew the algorithm up front finished faster, and PracHub has one who completed all three phases in 40 minutes. Graph search, backtracking, tries and greedy keep coming up.
- Going silent while the model works. Blind users describe "pipelining": send a prompt, talk through the next step while it generates, then review the output. Silence wastes the communication score.
- Prepping for the wrong round. Recruiters gave inconsistent answers in late 2025 (Blind). Ask which of your two coding rounds is AI-enabled, and ask for the practice environment; Hello Interview says recruiters share one with a sample problem candidates call "the puzzle", which most found harder than the real thing.
Will a new grad get this round?
Maybe. Most reports come from E4 to E7 loops. Hello Interview's E3 guide says there is "a real chance" of seeing it as an E3 in 2026 but warns against assuming it, and describes the E3 onsite as two 45-minute coding rounds plus a 45-minute behavioral. DG Learning (April 2026) says E6 and below get one classic and one AI round, while E7 and above get only the AI round. The technical phone screen is still classic: 45 minutes, usually two medium problems, no AI (Hello Interview E3 guide).
So the classic round still decides more new-grad outcomes than the AI one, and seats are scarce. Meta said in April 2026 that it would cut about 10% of staff, roughly 8,000 people, and close 6,000 open roles (WBUR, citing a memo first published by Bloomberg).
The skill transfers beyond Meta. Google is piloting its own version: from the second half of 2026, junior and mid-level candidates on select US teams get a "code comprehension" round with Gemini, graded on "AI fluency, including prompt engineering, output validation and debugging skills" (Business Insider via Moneywise, May 14, 2026).
A 4-week plan
- Week 1, the classic round. Meta-tagged mediums in a plain editor, no running code, two problems per 40 minutes, out loud. Skip dynamic programming; Meta's guide says it does not ask it.
- Week 2, the AI round's algorithms. Grid search with constraints, backtracking with pruning, tries. Re-solve each reported problem type without any AI.
- Week 3, reading code. Take a small multi-file open-source project, break one of its tests, and give yourself 15 minutes to find the bug unaided. Then add a feature using a chat-only assistant that cannot touch your editor, pasting every line by hand.
- Week 4, full rehearsals. Two or three 60-minute runs with a deliberately weak model, narrating throughout. Get the practice puzzle from your recruiter and do it against the clock.
Practice
- Meta E3 software engineer mock interview for the classic new-grad loop
- Meta E4 software engineer mock interview: Applr's E4 mock includes a simulated AI-enabled round
- Polish your resume for Meta before the recruiter screen
- FAANG interview comparison 2026 if Meta is one of several loops
- New Grad 2027 tracker for which applications are open
Sources
- Meta Careers, "Preparing for Your Full Loop Interview at Meta" and the linked Software Engineer Full Loop Interview Guide (IC4-6, v1), retrieved Oct 27, 2026
- Business Insider (via AOL), "Meta will let some job candidates use AI in their coding interviews", Jul 29, 2025
- Hello Interview, "Meta's AI-Enabled Coding Interview: How to Prepare", Evan King, retrieved Oct 2026
- Hello Interview, "Meta E3 Interview Guide (2026)", retrieved Oct 2026
- interviewing.io, "How to use AI in Meta's AI-assisted coding interview", Githire B. Wahome, 2026
- DG Learning, "Inside Meta's New AI-Enabled Coding Round: What Changed and How to Prep", Apr 17, 2026
- PracHub, "Meta's AI-Enabled Coding Interview: What to Expect in 2026", Jun 28, 2026
- Blind, "Meta AI enabled coding round", Oct 4, 2025
- Blind, "First reviews of Meta AI-assisted code interviews are in", Oct 11, 2025
- Blind, "Meta AI enabled coding experience", Nov 25, 2025
- Business Insider (via Yahoo Finance), "Meta is about to start grading workers on their AI skills", Nov 14, 2025
- InfoWorld, "Meta minimizes role of token maxing in employee evaluations", Sep 4, 2026
- The Decoder, "Meta drops AI usage from engineer performance reviews after tokenmaxxing backfires", Sep 8, 2026
- WBUR Here & Now (via WFAE), "Meta announces it's laying off 10% of its workforce", Apr 24, 2026
- Moneywise (via Yahoo Finance), reporting Business Insider on Google's AI-assisted interview pilot, May 14, 2026
Frequently asked questions
- Can you use AI in a Meta coding interview?
- Only in the AI-enabled round, and only the assistant built into the CoderPad environment. Meta's Software Engineer Full Loop Interview Guide (retrieved October 2026) still lists AI tools like ChatGPT as unauthorized outside assistance, and Hello Interview reports that the other onsite coding round stays AI-free. Your recruiter tells you in advance which round is which.
- How long is Meta's AI-enabled coding interview?
- 60 minutes, against 45 for a classic round. Hello Interview and candidate reports on Blind (October and November 2025) describe one multi-file project in three phases: fix a failing test, implement the core feature, then optimize for larger inputs. Not finishing the last phase is reported as acceptable.
- Which AI models can you use in Meta's AI-enabled round?
- Candidates report a switchable menu that has included GPT-4o mini, GPT-5, several Claude Haiku, Sonnet and Opus versions, Gemini 2.5 Pro and Llama 4 Maverick (Hello Interview). The assistant answers in a chat panel and cannot edit your files. Lists vary by report, and several candidates found the models unreliable on the day.
- Does Meta grade how well you prompt the AI?
- Not directly. interviewing.io reports that Meta's prep materials call AI use optional with no bearing on the outcome, and Hello Interview lists the graded areas as problem solving, code quality, verification and communication. An internal source quoted by Hello Interview said candidates should use AI but show they understand the code, and heavy reliance drew negative feedback.
- Do Meta E3 new grads get the AI-enabled round?
- Not reliably. Most reports come from E4 to E7 loops. Hello Interview's E3 guide says there is a real chance of seeing it as an E3 in 2026 but not to assume it, and the technical phone screen is still a classic two-problem round without AI. Ask your recruiter which format your onsite uses.
- Is the AI-enabled round easier than a LeetCode round?
- Candidates do not describe it that way. Reported problems are graph search, backtracking and trie puzzles inside a codebase, and PracHub (June 2026) collected E7 accounts of Claude Sonnet giving wrong logic and of a hallucinated maze solution costing a candidate the round. Knowing the algorithm before you prompt is what made people fast.