How Autodesk Interviews in 2026: Process, Sample Questions & What They Score

Reports describe a CodeSignal or Scaler test, usually with four problems (one older campus report had three), ranging from easy to hard (arrays, strings, sliding window, prefix/suffix, matrix, trees, DP). One Chennai report mentions a test scored out of 600. One October 2026 intern report mentions a HireVue interview invitation after the CodeSignal test, and one Q3 2026 Interview Query report mentions an 'AI interview round' without detail. Whether a test is used varies by region, level and team: the London and Toronto reports do not mention one, while a 2019 San Francisco report began with an online test.

The official first step. Reports describe a conversation about background, interest in Autodesk and logistics. One Interview Query report describes a thirty-minute recruiter screening. Order can vary; one candidate met the hiring manager without a recruiter call first.

The official second step. Reports say it covers a resume and project walkthrough plus behavioral questions (conflict, why someone might not want to work with you, and recently how you use AI tools). Length and placement vary by team; in some loops the manager round comes last (a LeetCode SDE1 report lists two technical rounds then a hiring manager round, and a Glassdoor report ends with an HR and managerial round).

Autodesk says candidates may be asked to take a functional assessment but does not define it, so reading it as the technical screen for software roles is an inference. Formats reported: a live DSA problem with complexity follow-ups, coding a banking system (OOP design), completing functions over screen share, a React app that calls an API (Toronto), and a 45-minute CoderPad session mixing frontend and backend. The format varies by team, so ask the recruiter.

Officially an interview team of typically 3-4 people; the FAQ does not say whether this is one panel session or several back-to-back interviews. Reports include an onsite with three technical rounds and one non-technical round (San Francisco, 2019). Others describe an hour-long experience deep dive with a senior engineer and coding with a principal engineer (London), a roughly 3-hour session split between technical and behavioral, and a roughly 2-hour full stack design exercise (both India). Content spans DSA, system design, C++/OOP fundamentals and team fit. Length varies by level and team, and some candidates had extra rounds added.

Autodesk says it does not typically provide specific interview feedback but updates candidates on their status as soon as possible after the last interview. Interview Query reports a 30-day process length. One SDE1 candidate on LeetCode said the process took almost a month. Individual reports range widely: campus processes reported as short as 1 day, a 2019 San Francisco process took 3 weeks, and Glassdoor's averages by job title run from 1 day to 330 days. Several reports mention generic rejection emails or slow scheduling.

Total rounds: the official outline lists the stages but gives no total. Reports range from 3 rounds (LeetCode, Glassdoor) to 4-6 (Interview Query) and more for some onsite loops, depending on team, level and region.