AI in Job Interviews: What's Allowed, What Gets You Cut

Whether you can use AI in a job interview in 2026 depends on the specific round, not the company name on the offer letter. Some employers now hand you an AI assistant and score how well you drive it. Others call any AI use an unfair advantage and disqualify you on the spot. The safe move is the same in both worlds: confirm the policy in writing before the session, and never submit code you cannot walk through line by line. This guide covers who allows what, how interviewers catch hidden AI use, and the exact scripts and drills to stay on the right side of the line.

The landscape split down the middle

There is no single rule anymore, and the dividing line often runs through a single company's interview loop rather than between companies.

On the permissive side, a growing set of firms expect you to use AI and grade you on how you direct it. Meta introduced an AI-assisted coding round in late 2025 for mid-level (E4) and senior (E5) software engineers, replacing one traditional onsite coding round with a 60-minute problem in an editor that has an embedded AI assistant. Canva expects backend, frontend, and ML candidates to reach for Copilot, Cursor, and Claude. Shopify, Stripe, Vercel, and most early-stage YC startups are relaxed about AI in take-homes because they care about the result and your reasoning, not whether you typed every character.

On the restrictive side, the reasoning is consistent. Amazon told recruiters in internal guidance to disqualify candidates who use generative AI during interviews, describing it as an "unfair advantage" that blocks assessment of authentic skill. Goldman Sachs has asked applicants to stop using tools like ChatGPT because it wants to hear candidates in their own voice. Anthropic, whose entire product is an AI assistant, asks candidates to skip AI so it can assess personal interest and unassisted communication. Google still runs its standardized algorithmic loops with AI disabled while piloting a separate AI-assisted comprehension round for junior and mid-level roles on select US teams.

The pattern: the harder a company leans into AI as a product, the more it wants to watch you use AI well. The more it is testing raw problem decomposition under observation, the more likely AI is banned outright.

Confirm the policy before you touch anything

The single highest-value action is asking, in writing, before every loop. Policy now lives at the round level, so a recruiter who says "we allow AI" about the company may be wrong about your specific session. Get it in email so you have a record.

Here is a template you can send the day you schedule:

Subject: Quick question on AI tool policy for my [Role] loop

Hi [Recruiter],
Two quick things before the interview:
1) What is your policy on AI tools (Copilot, ChatGPT, Cursor) during
   the interview, and does it differ by round?
2) If a round permits AI, which specific tool or model should I use?
Thanks, [Name]

That second clause about differing by round is the important one. When they reply, keep the thread. If they answer verbally on a call, send a one-line confirmation back: "Confirming what we discussed: AI is not permitted in the live coding round, but is allowed for the take-home. Let me know if I have that wrong." Now you have documentation if anything is ever disputed.

How interviewers catch live AI use

Two things catch candidates: proctoring signals and one unscripted follow-up.

Proctoring has caught up. Pasted blocks of code, suspicious timing where a full solution appears after a long pause, and tab-switching are all flagged in modern platforms. Amazon's internal tips to recruiters reportedly include watching for unnatural pauses and eyes tracking a second screen. But the more reliable detector is not software. It is a single follow-up question about code you did not actually write.

Interviewers who suspect AI-generated answers reach for prompts that reward genuine understanding and expose memorized or pasted output. Two you should expect:

"Dry-run this on the input [3,1,4,1,5] and tell me the value of your accumulator after each iteration." A candidate who wrote the code answers immediately. A candidate reading pasted output stalls, because tracing state by hand is not something you can paste.
"Now the input arrives as a stream and you cannot see its length up front. What breaks, and what do you change?" This micro-constraint invalidates any solution that indexes to the end of an array. Someone who understands their own invariant adapts in a sentence. Someone who outsourced the thinking freezes.

A strong answer sounds like ownership. For the stream variant on a problem like Maximum Number of Consecutive Values You Can Make, you would say something like: "I relied on sorting the coins first, which needs the full array, so with a stream I would either buffer or switch to a running-reachable-total approach and reject the greedy sort. The invariant is that I can make every value up to reach, and I extend it whenever the next coin is at most reach + 1." That answer proves you hold the idea, not the output.

A mid-interview self-audit checklist

Whether or not AI is allowed, run this quick check before you say "I think this is done." It is the same signal interviewers grade, and it keeps you from over-relying on a tool you have to defend:

State one invariant of your solution in a single sentence.
Trace the code out loud on one small example, naming a variable's value at each step.
Give time and space complexity, then name the specific edge case that stresses it (empty input, all duplicates, single element).
Point to one line you are least sure about and say how you would test it.

If you cannot do all four, you do not understand the solution well enough to submit it, AI-assisted or not.

The take-home disclosure that protects you

For take-homes at AI-friendly companies, the winning move is transparency plus artifacts. Disclose what you used, then show your judgment. Drop a short note in the README:

## AI usage
I used Claude to scaffold the CSV parser and to draft the retry
wrapper. I wrote the concurrency logic and the data model by hand
because generated versions were subtly wrong on ordering.
Artifacts included:
- /docs/prompts.md  (the prompts I used, in order)
- git history       (separate commits for generated vs hand-written)
- /tests            (tests I wrote to catch two bugs in the draft)

This does two things. It answers the integrity question before anyone asks, and it demonstrates the exact skill AI-permitted rounds grade: can you judge code, not just produce it. Reviewers consistently reward candidates who can say what they did not trust the AI to do.

A two-week practice plan with real reps

You cannot rehearse AI fluency the night before. Here is a concrete plan you can run in two weeks. Treat the numbers as targets, not guarantees.

Focus	Weekly reps	How
Core patterns, no AI	12 to 15 problems	Solve on a plain editor, explain out loud, then check
Timed mock interviews	3 sessions, 45 to 60 min	Full format, talk through every decision
AI-assisted drills	4 sessions	Give the AI small, specific instructions, then review its output for planted bugs
Spaced repetition	daily, 20 min	Re-solve missed problems on a 1, 3, 7 day interval

For the no-AI reps, rotate difficulty so you are not only grinding easy problems. Mix a junior warm-up like Minimum Amount of Time to Fill Cups with a mid-senior graph or tree problem like Find Duplicate Subtrees, and one staff-level stretch such as Number of Ways to Stay in the Same Place After Some Steps. If dynamic programming is your weak spot, Domino and Tromino Tiling is a clean recurrence to drill until you can derive it cold. You can run timed sessions with AI feedback on DevInterview's practice tool and target specific loops on the company breakdown pages.

For the AI-assisted drills, practice the meta-skill: prompt the tool for a first draft, then read it as if a fast junior wrote it. Run it, write your own test, and narrate what you keep and what you throw out. That narration is exactly what an AI-assisted round scores.

Does hidden AI use follow you around

Getting caught in a no-AI round is treated as cheating and usually ends that loop immediately. Whether it follows you further is less certain. Some recruiters describe internal do-not-hire flags for candidates caught using covert tools, but these accounts are anecdotal rather than published policy, so treat the risk as real but unquantified. The most public cautionary tale is Interview Coder, an invisible overlay tool whose creator was suspended from Columbia University after using it against companies including Amazon. The lesson holds regardless of the flagging question: covert overlay tools optimize for producing an answer, which is the one thing that no longer earns points in either format.

FAQ

Can I use ChatGPT during a coding interview?

Only if the company explicitly permits it for that specific round, and you should confirm in writing first. Meta, Google (in a pilot), Canva, and Shopify allow or require an approved assistant in certain rounds. Amazon, Goldman Sachs, and Anthropic prohibit it, and using a hidden tool there is treated as cheating.

How do interviewers know if I used AI?

Modern platforms flag pasted code blocks, suspicious timing, and tab-switching. The more reliable check is one unscripted follow-up, like asking you to dry-run your code on a specific input or adapt it to a streaming constraint, which exposes anyone who cannot trace their own logic.

Is it cheating to use AI in a take-home?

Not at companies that allow it, which is most startups and several larger firms. The safe approach is to disclose what you used in the README, separate generated and hand-written code in your commits, and include the tests you wrote. Verify the specific company's policy before you submit.

What if the recruiter's answer about AI is vague?

Ask the round-level version of the question: "Does the policy differ between the take-home and the live round, and which tool should I use if it is allowed?" Then send a short email confirming their answer so you have a record. When in doubt, do not use AI in a live, observed round.