How to pass a coding interview when AI assistants are everywhere (2026)

Two kinds of coding rounds in 2026

In 2026 you can walk into two coding rounds at two companies in the same week and get opposite rules. At Meta, one of the coding interviews now comes with GPT, Claude, Gemini and Llama built into CoderPad, and you are expected to use them. At Amazon, the written guidance says not to use generative AI tools unless explicitly permitted, and the stated consequence is disqualification.

So the first skill is boring: find out which round you are in. The second is to prepare for both, because they reward different habits. This article covers who allows what, how the AI-enabled round is actually scored, and a drill you can do this week for each format.

Who allows AI, who bans it

Policies change every quarter, so treat this as the state in autumn 2026 from public employer statements and candidate reports. Before any loop, ask the recruiter directly: "Is AI assistance allowed in any of the rounds, and in which?" They answer this question routinely now.

How the AI-enabled round is scored

The surprise for most candidates: it is harder, not easier. Instead of two short algorithm problems you get one small codebase with several files, maybe an API endpoint, a shell script and a Dockerfile. You have to add or fix something in an hour. The assistant can write code fast. It cannot tell you whether the code fits this repository.

Interviewers score five things, and none of them is typing speed:

1. What you hand to the assistant. Boilerplate, a test scaffold, a regex: yes. The core logic before you understand the codebase: a red flag.
2. Whether you read what it returns. Catching a wrong answer from the model and fixing it is the single clearest positive signal reported from these rounds.
3. How well you understand the existing code. Spend the first eight to ten minutes reading. Say what you found.
4. Narration. Silent prompting looks the same as cheating on a video call. Say what you are asking and why.
5. Ownership. At the end, can you explain every line that ships, including the ones you did not type?

My take: candidates who grind LeetCode only struggle here, and not because of the AI. They have never opened an unfamiliar repository under time pressure.

When AI is banned: what still works

The classic round has not gone anywhere. It is still 45 minutes, one or two problems, a shared editor and a human watching how you think. What changed is that interviewers are now suspicious of perfect silence followed by perfect code. That shifts the balance toward talking.

• Say the brute force and its complexity before writing anything. It shows you can reason without help.
• Write small, run often, and narrate each test case.
• Keep pattern practice, but at a lower volume than in 2023. Twenty well-understood problems across the main patterns beat two hundred memorised ones.

The algorithms and data structures question list on this blog covers the patterns that still come up. Close specific holes on deep quizzes rather than doing random problems.

After the code works: the last ten minutes

Both formats end the same way. The code runs, and the interviewer has ten minutes left. This is where a lot of offers are lost, because candidates relax and stop thinking out loud. Expect three kinds of follow-up.

"What would break first?"

Name one input that makes the solution slow or wrong: an empty list, a million duplicates, a string with Unicode. Then say how you would test for it. One concrete case beats a vague "edge cases".

"How would you change it if…"

The requirement shifts: the data no longer fits in memory, two users edit at once, the list arrives as a stream. You do not need to rewrite the code. Sketch the change in two or three sentences and say what it costs.

"What did the assistant get wrong?"

In AI-enabled rounds this question comes up almost by design. If you caught a mistake, describe it: what the model produced, how you noticed, what you changed. If you did not catch anything, say what you checked and why you trusted the result. "It looked fine" is the weakest answer you can give.

A small habit helps here. Keep a three-line note during the session: one risk, one thing you would test next, one thing you changed from the model's output. When the follow-ups start, read from it. Interviewers rarely mind; it looks like the way engineers actually work.

A one-week drill for both formats

Friday is the day that matters. A partner who interrupts with "why did you accept that line?" is the closest you get to the real round without a recruiter on the call.

The short version

Ask which rounds allow AI. In the banned ones, talk more than you used to. In the allowed ones, read the codebase first, delegate small pieces, check everything the model returns, and narrate. Both formats punish the same thing: code you cannot explain.

Related: AI in interviews from the employer's side, the last week before an interview, how a pair mock works.