AI-Assisted Coding Interviews: How Allowed-AI Rounds Work and How International Candidates Should Prepare
Some interview loops now hand you an AI assistant and grade how you steer and check it, so here is how those rounds work and how to prepare while an OPT clock runs.

An AI-assisted coding interview is a live technical round in which the employer gives you an AI assistant, or lets you bring your own, and grades how well you break the problem down, direct the tool, check what it produces and explain your choices. It is not a test of typing an algorithm from memory. As of November 1, 2026, Canva has said publicly since June 2025 that it expects candidates to use AI in one engineering round, Meta has trialled an AI-enabled CoderPad round since late 2025 according to CoderPad and candidate reports, and many other employers still ban AI in live interviews. If you are on OPT, STEM OPT or H-1B, confirm your loop's rules with the recruiter in writing before you prepare.
Status line, as of 2026-11-01: these rounds are company hiring practices, not law, and they change without notice. We separate what a company published itself (Canva) from what candidates and prep sites report (Meta, Shopify).
What is an AI-assisted coding interview, in plain terms?
An AI-assisted coding interview, also called an AI-enabled coding round, is a timed live interview where an AI assistant is allowed or required. You still solve a realistic engineering problem in front of an interviewer, but the score rests on judgment: how you split the work, what you ask the tool for, how you verify the output and how clearly you explain each decision.
Three nearby formats get confused with it:
- A take-home with AI allowed is unsupervised and judged on what you submit and later defend; see our guide to AI tools on take-home assessments.
- An AI-run screen is one where software, not a person, asks or scores; see what to expect in an AI-run technical interview.
- A no-AI round stays a no-AI round even if another round in the loop allows AI. Using an assistant where it is banned is the risk covered in our guide to prohibited AI use in interviews.
People also search for a "vibe coding interview." That phrase names the behavior these rounds mark down: accepting whatever the model writes without reading it.
Which companies allow AI in coding interviews?
Only a handful say so publicly, and the evidence is uneven: Canva published its own policy, Meta's round is documented through a vendor post and candidate reports, and Shopify's through prep-site reporting alone. For everyone else, read the invite and ask if it is silent.
Allowed-AI coding rounds, as of 2026-11 (formats change; confirm with your recruiter)
| Company | What is known | Where it comes from |
|---|---|---|
| Canva | An "AI-Assisted Coding" competency replaced its Computer Science Fundamentals screening for backend and frontend engineering roles | Canva engineering blog, 2025-06-11 (the company's own statement) |
| Meta | An AI-enabled round on CoderPad, trialled since late 2025; reported to replace one of two onsite coding rounds for software engineering and engineering manager loops, run 60 minutes, and include a built-in AI chat with a model picker | CoderPad blog quoting Meta's recruiting team, 2025-10-30; format details from candidate reports compiled by Hello Interview (read 2026-11-01) |
| Shopify | Reported to let you use your own IDE and any AI tool over screen share, on one open-ended problem that grows with follow-up requirements | Hello Interview, from candidate reports (read 2026-11-01); we found no company page |
| Everyone else | Often live rounds without AI; some say so in the invite, many say nothing | Your interview invite and your recruiter |
Canva's post states the expectation plainly: candidates "are expected to use their preferred AI tools to solve realistic product challenges" (Canva Engineering, June 11, 2025). CoderPad, whose platform hosts Meta's round, quoted Meta's recruiting team in an October 30, 2025 post: "It's not 'cheating,' it's how the job is evolving."
How the Meta AI-assisted coding interview works (as reported)
We found no public Meta candidate guide for this round, so every detail below is reported, mainly from Hello Interview's compilation of candidate accounts (read 2026-11-01). Ask your recruiter which parts apply to your loop.
- Length and setting. About 60 minutes in a three-panel CoderPad layout: a file explorer, a code editor, and an AI chat panel that also holds the instructions. The assistant reportedly reads the project files but answers only in chat; it does not edit your files, so you move code across yourself.
- One problem in phases. A multi-file codebase you did not write, worked in stages: fix a bug, build the core feature, then optimize as larger test files expose slow code. Whether AI is allowed in the bug-fix phase reportedly varies by interviewer, and candidates report that not finishing every phase can still be acceptable.
- A model picker. Candidates describe a choice of models from several vendors; some found one large model too slow under interview conditions.
- A practice environment. Scheduled candidates reportedly get access to a practice problem in the same interface. If no link arrives, ask for it.
- A traditional round remains. The loop reportedly keeps a standard coding round with no AI.
How is the AI-enabled round graded?
Mostly on the same skills as a classic coding round, with the AI treated as a tool you are responsible for. According to the same candidate reports, Meta scores four areas: Problem Solving, Code Quality, Verification and Communication. Canva's June 2025 post says its interviewers ask, "Can they identify and fix issues in AI-generated code?"
Canva's October 20, 2025 guide, written by one of its interviewers, names three areas: engineering problem-solving, technical depth and ownership, and how effectively you collaborate with AI. "We're assessing your engineering capabilities enhanced by AI collaboration, not your AI skills in isolation," it says. Mapped onto Meta's four reported areas, strong and weak signals look like this:
| Area | Strong signal | Weak signal |
|---|---|---|
| Problem solving | You split the task and choose the approach before you prompt | You paste the whole problem into chat and wait |
| Code quality | You edit AI output to match the codebase's names, structure and error handling | AI style mixed into existing code, with unused helpers left behind |
| Verification | You run the tests, add an edge case yourself and check the complexity claim | "This should work" without running anything |
| Communication | You say what you asked for, why, and what you kept or threw away | Silence while the model generates |
Common misconception: "If AI is allowed, the round is easier, so I can prepare less."
Correction: the problem is reportedly larger than a classic single-function question, the code is someone else's, and the clock is still about an hour. The AI removes typing, not thinking, and Verification and Communication are where candidates who let the tool drive lose points.
The decompose, prompt, verify, narrate loop
Run the same four-move loop for every subtask, so you never improvise process under pressure:
- Decompose in the editor before you open the chat. Run the provided tests in CoderPad (or your own IDE, if the round allows it), read the files you will touch, and type a three-line plan as code comments. Say the plan aloud.
- Prompt the assistant for one bounded piece. Name the file, the function, the signature, the language version and anything that must not change, and ask for a one-line complexity estimate.
- Verify the output before you accept it. Read every line, run the test suite, add one edge case of your own, and check the AI's complexity claim against the loops you can actually see.
- Narrate the decision. Accept, edit or reject, with the reason in one sentence.
Repeat the loop for each subtask, then spend the last few minutes summarizing what works, what is untested and what you would do next.
A bounded prompt looks like this:
In Scheduler.java, write nextBatch(): return every task whose dependencies
are all complete. Keep the Task class unchanged. Java 17. Do not edit tests.
After the code, give the time complexity in one line.
Compare that with "solve this problem," which hands the model your problem-solving score.
A worked example: one 60-minute round, minute by minute
This scenario is hypothetical but built on the reported format. You are on post-completion OPT. A recruiter emails on Tuesday, 2026-11-03, to schedule a virtual onsite for Tuesday, 2026-11-17, including one AI-enabled round. You ask for the practice environment the same day and run it on 2026-11-10. If no employer is reported for you in SEVIS, each of those 14 days counts toward your 90 (our arithmetic). The real problem turns out to be a task scheduler spread across four files, with one failing test.
| Minutes | Phase | What you do | What you say |
|---|---|---|---|
| 0-6 | Orient | Run the tests, open the two files the failing test touches, pick the model you tried in practice | "I'll run the tests first so I know the baseline." |
| 6-15 | Fix the bug | Read the comparator yourself; if the interviewer allows AI here, ask it only to explain one unfamiliar method | "I think ties are broken by insertion order. I'll confirm with the test." |
| 15-40 | Build the core | Write the plan as comments; prompt for nextBatch() alone; read, run, add a test for a task with no dependencies | "It rescans the whole list every call. Fine for now, but I'll note it." |
| 40-55 | Optimize | The large test file times out; ask the AI for the complexity, check it against the nested loop, switch to a queue of ready tasks | "The AI says linear, but this inner loop makes it quadratic, so I'm changing the approach." |
| 55-60 | Close | Summarize what passes, what is untested, what you would refactor | "Phases one and two pass. Next I'd add cycle detection." |
The strongest moment in that hour is minute 45, when you catch the assistant's wrong complexity claim: one correction that shows Problem Solving, Verification and Communication at once.
Phrases for narrating AI use when English isn't your first language
Here is an advantage that is easy to miss: your prompt is written English the interviewer can read. Read it aloud as you type it, and one sentence does two jobs. Keep prompts short and imperative; precision matters far more than grammar.
| Moment | Phrase that works |
|---|---|
| Before you open the chat | "I'll plan this myself first, then ask the assistant for one function." |
| Sending a prompt | "I'm asking for only the parsing step, and I told it not to change the interface." |
| Reviewing output | "Before I accept this, I'll read it and run the tests." |
| Rejecting output | "This changes the method signature, so I'm not using it." |
| Editing output | "The logic is right, but I'll rename these to match the codebase." |
| Checking a claim | "It says O(n). Let me check: one loop, but this lookup is linear, so O(n squared)." |
| Waiting on the model | "While it generates, I'll write the edge-case test." |
These sit on top of the general technique in our guide to thinking out loud in a live coding interview when English isn't your first language, which covers restating the problem, trade-offs and recovering from a vocabulary gap. Rehearse both until the phrases come out without thinking.
Should you still practice LeetCode?
Yes, with a different balance. Meta's loop reportedly keeps a no-AI coding round, many employers still run only no-AI rounds, and the optimization phase above depends on you recognizing a quadratic loop the assistant misjudged. You cannot verify what you do not understand.
Our suggestion, not a published rule: keep your algorithm practice going, and add sessions on reading unfamiliar code, writing tests and working across files, which classic problem sets rarely train.
AI coding interview practice that matches the real round
- Practice on multi-file code. Take a small open-source project, break one test on purpose, then fix it and add a feature with an assistant under a 60-minute timer.
- Choose your model before the day. Try the options in the practice environment and settle on the most capable one that still answers quickly; a slow reply costs minutes you will feel in phase three.
- Record yourself. Play it back and count the silent stretches; each one is lost Communication credit.
- Rehearse with a human interviewer. A friend who interrupts and redirects you is closer to the real thing; the role-swap habits in our driver-navigator pair programming interview guide transfer directly.
How to ask your recruiter which AI tools are allowed
Ask once, in writing, as soon as the loop is scheduled. A short email works:
Thanks for scheduling my interviews. Could you confirm which rounds allow AI tools, which tools or models are available, whether I use your environment or my own IDE, and whether AI is allowed in every phase of that round? If there is a practice environment, I would appreciate the link.
Keep the reply, and raise sponsorship as its own question so neither answer gets lost.
Why the allowed-AI round matters more on OPT, STEM OPT or H-1B
The round has the same rules for everyone. Your margin for error is different.
- Your clock. Post-completion OPT allows 90 days of unemployment and STEM OPT 150 days in aggregate (in effect, unchanged as of 2026-11-01), counted from the actual OPT start date for each day without employer information, per SEVP's SEVIS Help Hub. A loop often runs for weeks, and some employers ask rejected candidates to wait months before reapplying, so one lost loop can use up days you may not have. Our guide to how STEM OPT unemployment days count walks through the math; your DSO confirms your own count.
- A thinner market. Indeed's overall Job Postings Index stood at 103.8 on 2026-10-16, with software development around 78 to 79, the lowest of the five sectors it charted (Indeed Hiring Lab, 2026-10-22). Fewer openings mean each onsite counts.
- The employer's cost. Sponsoring you adds filing and legal costs to a normal hire. The $100,000 H-1B payment under Proclamation 11069 is blocked as of 2026-11-01, though the proclamation itself stays on paper: USCIS says a court "vacated agency guidance implementing the $100,000 payment requirement" and that DHS still plans to collect it if that order is lifted (USCIS I-129 page). Even on paper, it does not apply when USCIS grants a change of status inside the US, the usual route from OPT; a denied change of status or a consular-notification petition would be covered (USCIS H-1B page, updated 2026-09-21).
- The level you land. Wage-weighted H-1B cap selection has been in effect since 2026-02-27 (a Level IV registration counts four times, a Level I once), per the weighted selection final rule. Our reading: a round that shows senior judgment can affect the level and pay you are offered, and the offered wage is what the selection weights. The employer's immigration attorney, not the recruiter, can tell you how your offer maps to a wage level.
Common mistakes
- Pasting the whole problem into the chat. You hand over the Problem Solving score in one move.
- Accepting code you have not read. Unread code that breaks a test costs more than code you typed slowly.
- Going quiet while the model generates. Use that time to write a test or explain your next step.
- Using AI in a phase where the interviewer said not to. Rules can differ by phase and by interviewer; ask at the start of the round.
- Bringing a tool that was not offered. A second-screen assistant in a round that provides its own tool counts as prohibited use, not AI-assisted coding, unless the recruiter confirmed in writing that it is allowed.
Frequently asked questions
What is an AI-assisted coding interview?
It is a live, timed coding round in which the employer allows or requires an AI assistant and grades how you direct it, verify its output and explain your choices. As of November 2026, Canva has said since June 2025 that it expects candidates to use AI in one engineering round, and Meta has trialled an AI-enabled CoderPad round since late 2025, according to CoderPad and candidate reports. Many other employers still ban AI in live rounds, so confirm the rules with your recruiter in writing.
Which companies allow AI in coding interviews?
Few say so publicly. Canva's engineering blog (June 11, 2025) says candidates are expected to use their preferred AI tools in its AI-Assisted Coding round, and CoderPad (October 30, 2025) quoted Meta's recruiting team on Meta's AI-enabled pilot. Prep sites also report allowed-AI rounds at Shopify. Formats change without notice, so treat any list, including this one, as a question to put to your recruiter.
How is the AI-enabled round graded?
According to candidate reports compiled by Hello Interview (read November 1, 2026), Meta grades the same four areas as its traditional rounds (Problem Solving, Code Quality, Verification and Communication), with AI treated as a tool. Canva says its interviewers check whether you can identify and fix issues in AI-generated code. Reading, testing and explaining the output earns more credit than how much code the AI writes.
Should I still practice LeetCode if AI is allowed?
Yes. Meta's loop reportedly keeps one traditional coding round without AI, many employers still run only no-AI live rounds, and you cannot verify or optimize AI code whose algorithm you do not recognize. Shift some practice toward multi-file problems, reading unfamiliar code and testing, but keep core data structures and complexity analysis sharp.
How do I narrate my use of AI if English isn't my first language?
Use short, fixed phrases and let your typed prompt do half the work by reading it aloud as you write it. Say what you are asking for, then whether you accept, edit or reject the answer and why, in one sentence each. Rehearse until the phrases are automatic, because these rounds weigh communication heavily and silence while the AI generates looks like lost control.
Sources
- Canva Engineering, Yes, You Can Use AI in Our Interviews. In fact, we insist (2025-06-11)
- Canva Engineering, AI Interview Success: An Interviewer's Inside Guide (2025-10-20)
- CoderPad, AI in the interview isn't cheating, it's the job. Just ask Meta. (2025-10-30)
- Hello Interview, Meta AI-enabled coding and Shopify AI-enabled coding (prep site, candidate reports; read 2026-11-01)
- SEVP, SEVIS Help Hub: unemployment counter
- USCIS, Form I-129 page (updated 2026-10-30) and H-1B specialty occupations page (updated 2026-09-21)
- Federal Register, Weighted selection process for cap-subject H-1B registrations
- Indeed Hiring Lab, US labor market snapshot, October 2026
How we checked this: we read Canva's two engineering posts, CoderPad's Meta post, Hello Interview's Meta and Shopify pages, the SEVIS Help Hub, the USCIS I-129 and H-1B pages, the Federal Register rule and Indeed's October snapshot on 2026-11-01.
This is general information, not legal or tax advice; your own I-20, EAD, I-94 and notices, and your DSO or immigration attorney, govern your situation.
If you are preparing for allowed-AI loops on OPT or STEM OPT and want help finding employers set up to sponsor, F1Jobs can talk it through with you.
Frequently asked questions
What is an AI-assisted coding interview?
It is a live, timed coding round in which the employer allows or requires an AI assistant and grades how you direct it, verify its output and explain your choices. As of November 2026, Canva has said since June 2025 that it expects candidates to use AI in one engineering round, and Meta has trialled an AI-enabled CoderPad round since late 2025, according to CoderPad and candidate reports. Many other employers still ban AI in live rounds, so confirm the rules with your recruiter in writing.
Which companies allow AI in coding interviews?
Few say so publicly. Canva's engineering blog (June 11, 2025) says candidates are expected to use their preferred AI tools in its AI-Assisted Coding round, and CoderPad (October 30, 2025) quoted Meta's recruiting team on Meta's AI-enabled pilot. Prep sites also report allowed-AI rounds at Shopify. Formats change without notice, so treat any list, including this one, as a question to put to your recruiter.
How is the AI-enabled round graded?
According to candidate reports compiled by Hello Interview (read November 1, 2026), Meta grades the same four areas as its traditional rounds (Problem Solving, Code Quality, Verification and Communication), with AI treated as a tool. Canva says its interviewers check whether you can identify and fix issues in AI-generated code. Reading, testing and explaining the output earns more credit than how much code the AI writes.
Should I still practice LeetCode if AI is allowed?
Yes. Meta's loop reportedly keeps one traditional coding round without AI, many employers still run only no-AI live rounds, and you cannot verify or optimize AI code whose algorithm you do not recognize. Shift some practice toward multi-file problems, reading unfamiliar code and testing, but keep core data structures and complexity analysis sharp.
How do I narrate my use of AI if English isn't my first language?
Use short, fixed phrases and let your typed prompt do half the work by reading it aloud as you write it. Say what you are asking for, then whether you accept, edit or reject the answer and why, in one sentence each. Rehearse until the phrases are automatic, because these rounds weigh communication heavily and silence while the AI generates looks like lost control.