AI Interview Index
Which companies let you use AI in their coding interviews, which ban it, and which built the interview around it. Anyone can edit; every change is public and revertible.
Companion to Coding Interviews Should Allow AI on Scaling Knowledge.
- No AI in interviewsBanned in the technical rounds.
- Has AI interviewsAllowed in at least one round.
- AI-native interviewsThe interview is built around it.
16 of 16
| Candidates work in a real codebase and ship a pull request. | San Francisco | ||
| No coding interview in the traditional sense. Paid contracting on real work, then a work trial, then an offer. | New York | ||
| No coding interview at all, in practice. | New York | ||
| Canva | AI tools are permitted in interviews. Candidates are expected to explain and defend what the tools produced. | Sydney | |
| AI use is expected rather than tolerated. | Sunnyvale | ||
| Self-serve CoderPad assessment as step one, roughly 1-1.5 hours, no AI allowed. | San Francisco | ||
| Two separate coding rounds on the same day: a 1h "Backend Build" in CoderPad with AI switched off, and a 1h "AI-Assisted Interview". | New York | ||
| No non-AI coding round in the loop. | San Francisco | ||
| One round where AI is allowed and a separate round where it is not, deliberately run as two different signals. | New York | ||
| AI use is prohibited by default in technical assessments, per their published careers policy. | Paris | ||
| One-hour LeetCode-style coding interview after the recruiter call. | Boston | ||
| LeetCode-style screen. No AI assistance. | New York | ||
| A 45-minute practical programming problem, explicitly not algorithmic, in any language. | New York | ||
| Full-stack coding screen plus questions on graph algorithms and HTTP fundamentals. No AI assistance. | New York | ||
| AI use is prohibited by default in technical assessments, per their published candidate policy. | San Francisco | ||
| Replaced coding and algorithm rounds with an AI-native onsite. | San Francisco |