The data describes a split, not a standard
Reporting: CoderPad’s March 2026 State of Tech Hiring report draws on more than 650 developers, recruiters and hiring leaders worldwide. Among surveyed recruiters and hiring leaders asked whether AI is allowed in technical assessments, 34% said it is banned, 46% allow it broadly or with constraints, and 20% decide case by case. When AI is allowed, the most frequently named signals of skill were catching and fixing AI mistakes (66%) and explaining trade-offs and correctness (56%). Those are survey responses from a vendor’s sample, not an industry census or evidence that one policy produces better hires. S1
Analysis: The split is not a reason to hunt for one universal rule. It is a reason to stop making candidates guess which test they are taking. A clear AI policy is part of the assessment design: without it, an interviewer may grade tool compliance while believing they are grading engineering judgment.
Put the protocol in the invite
Reporting: In June 2025, Canva Engineering said it expected backend, machine-learning and frontend candidates to use AI tools in technical interviews. The company also described piloting AI-assisted coding in place of its computer-science-fundamentals screen for backend and frontend roles, and said candidates were told about the format in advance. This is a dated company example, not a new industry standard. S2
Analysis: Put the permitted tools, account setup, network access, data-sharing limits and any no-AI portion in the interview brief. State whether tool choice or usage is scored. Use a task that resembles the role rather than making setup friction the hidden test. If you deliberately prohibit AI, explain which capability that round isolates and avoid presenting it as a simulation of the team's usual workflow.
Score the engineering loop
A practical round can begin with a small, realistic bug fix or feature request. Ask the candidate to clarify requirements and outline an approach before opening an assistant. Then let them use the tools permitted by the brief. Ask them to inspect one generated change, run a focused test, name an edge case and explain a trade-off they would keep or reject.
Score observable evidence in separate categories: problem framing, correctness, testing, debugging, judgment about generated code, and explanation. Do not treat prompt length, model choice or a polished first answer as a proxy for skill. The candidate should be able to show what they verified and what remains uncertain.
This is a field guide, not a claim that one interview format predicts job performance better. Keep the exercise consistent across candidates, tell them how it will be evaluated, and have interviewers record concrete evidence for each score. The useful question is not whether AI appeared in the session; it is whether the candidate can own the resulting engineering decision.
Sources and editorial method
This AI-assisted report synthesizes the sources below. Automated source checking is not independent human verification; follow the original reporting for context and updates.
Common questions
Should coding interview candidates be allowed to use AI?
Allow it when the role uses AI, or explain what a no-AI round is meant to measure; publish the rule before the interview.
What should an AI-assisted coding interview measure?
Assess problem framing, code review, verification, debugging and trade-off explanations—not just whether generated code runs.


