How to Use AI in a Coding Interview (and Still Own It)

Some coding interviews now expect you to use AI. Others still ban it. The skill is the same in both cases: know the rule for your round, follow it, and when AI is allowed, use it in a way that shows your own judgment. This guide gives the rules we could source, then a routine for the rounds where AI is allowed. For the formats themselves, see our AI coding interview overview and what an AI coding round is.

One thing first. Using AI in a round where the company does not allow it is cheating. We do not help with that, and this guide is not about hiding AI use.

Practice the habits on AICodingRound. Work real tickets in multi-file apps with your own Claude or Codex as a coach, then get a report that includes how you used the AI. Start with Another company's invoice opens from a forwarded link (medium, about 30 min). The beta is free and places are limited: get a place.

First: is AI allowed in your round?

The rule is set per company, and often per round. Here is what we could confirm, opened on October 29, 2026.

Across the industry, the default is still no. In Karat's survey of 400 engineering leaders, "over half (62%) of organizations still prohibit AI use in technical interviews" (Karat, January 7, 2026). So unless your recruiter says AI is allowed in a specific round, assume it is not, and ask. A good question is: "Is any AI assistant allowed in this round, and if so, which one, and can it edit code?"

The three rules you will meet

• No AI. You write and reason alone. Documentation lookups may still be allowed; ask.
• Chat only. The AI explains and suggests, but you type or paste every change. Meta's round is reported to work this way.
• Full tools. You use your own editor and assistant, and the AI may write code. Canva's round and Shopify's reported pair programming round are in this group.

Prepare for the rule you will actually get. A routine built on an agent that edits files falls apart in a chat-only round.

Why hidden use is a bad bet

Beyond the rules, the tools record what you do. CodeSignal says hiring teams get "session replays" and "transcripts of all AI interactions" in its AI-assisted assessments (CodeSignal, May 28, 2025). CoderPad describes "keystroke playback" and an integrity toolkit with "Code similarity checks, IDE exit tracking, randomized questions, and AI-assisted webcam proctoring" (CoderPad).

In an AI-allowed round, your chat with the assistant can be part of the evidence. Write prompts you would be happy for the interviewer to read.

Before you prompt

Most of the value comes before the first question to the AI.

1. Read the task twice. Note the expected behavior, the inputs and anything the ticket says must not change.
2. Run what exists. Run the app or the tests once. Seeing the failure yourself gives you something concrete to ask about.
3. Form a guess. Write one sentence on where you think the problem is. It can be wrong. It gives the AI's answer something to be checked against.
4. Decide what to hand off. Good jobs for an assistant: explaining an unfamiliar module, listing callers of a function, drafting a test fixture, writing boilerplate. Keep the design decision and the final fix for yourself.

Asking well

Narrow questions get checkable answers.

• Weak: "Fix the bug."
• Better: "In the invoice routes, which code path handles a request for an invoice from another organization? Point me to the lines."
• Better: "List the edge cases for this rate limiter that the current tests do not cover."

Give context the AI cannot see: what you already ruled out, the constraint from the ticket, the shape of answer you want (a list, a line number, a yes or no with a reason).

Checking what it gives you

Treat every answer as a claim to check. Meta's round is reported to use the line "Explain the output. Test before using" (Hello Interview; reported).

• Check one claim per answer. Open the file it named. Search for the caller it described. Does the code say what the AI said?
• Run the tests after every change. A change that turns one test green and another red is not done.
• Read the diff, even in a chat-only round. Pasting a whole function can drop an edge case you already handled.
• Note what it got wrong. You will want this later.

Canva lists one of its questions as: "Can they identify and fix issues in AI-generated code?" (Canva Engineering)

Explaining code you did not type

Expect follow-up questions. GitLab says it expects that you "can explain your prompts and technical decisions, and do not present AI-produced content as your own," and asks you to disclose "which tools you leveraged" (GitLab). Canva says "we expect engineers to take full ownership of any code they produce."

So before you finish, be able to say for every line you kept: what it does, why it is in that place, and how you know it works. If you cannot, cut it or rewrite it.

Practice the routine on AICodingRound

For each session:

1. Pick a codebase you have never seen and a ticket that starts from a symptom.
2. Spend five minutes reading and running it with no AI.
3. Use the AI for explanation only. Log each question, what you checked, and whether it was right.
4. Make the fix yourself. Run the full test suite.
5. Explain your change out loud in two minutes, including one thing the AI got wrong or could have.

Five problems from our library that fit this routine:

• Another company's invoice opens from a forwarded link (medium, Python, about 30 min). A security bug where a confident wrong answer is easy.
• A downloaded invoice makes the spreadsheet show a security warning (medium, Python, about 40 min).
• Moved meetings leave ghost bookings (medium, Python, about 45 min). A bug report that spans several files.
• Test the API rate limiter's edges (medium, Python, about 10 min). Ask the AI for edge cases, then check each one.
• Review the AI's retry PR (medium, Python, about 10 min). Judge code an AI wrote.

AICodingRound is built around this routine. You bring your own Claude or Codex, and it runs as a coach: it reads code and explains, but it does not write the fix, which trains the asking and checking directly. For a no-AI round, leave it closed. When you submit, your work is checked automatically, and a short debrief asks you to explain your own change. The report shows a level per skill (Strong, Solid or Developing), including how you used the AI, so you can see whether your habits hold up.

One problem a day builds the habit. The beta is free and places are limited: get a place.

For more on what interviewers mean by AI skill, read our guide to the AI fluency interview.