Real, anonymous reports from people who interviewed for Software Engineer at Autodesk, newest first and distilled into what to expect across the loop.
After a recruiter call, I moved into a fairly structured sequence. I started with a short introduction where we talked through my university or personal project. Then I had a technical screen where I solved a single medium-level DSA problem: finding the longest substring without repeating characters. That was followed by follow-ups on complexity, edge cases, and what optimizations I would consider.
My hardest round was the kind that made everything feel tightly timed and multi-layered. I had a long interview where I was asked to design a full stack web application using React and Node.js, including writing both frontend and backend code and covering API design. The whole thing ran for about two hours, and the pressure wasn’t just writing code—it was coordinating pieces of an architecture end to end.
The interview process typically begins with a recruiter call, followed by a series of technical rounds that may include coding, system design, and behavioral interviews, often spanning several weeks. Candidates should expect a mix of technical and managerial discussions, with the structure generally feeling organized but sometimes slow-paced.
Candidates will face multiple technical interviews focusing on coding challenges, often using LeetCode-style problems, C++, Java, or data structures. The difficulty can vary, but many candidates noted a focus on fundamentals and practical application rather than purely theoretical questions.
Expect to engage in system design discussions that require you to articulate architectural choices and design trade-offs, often under pressure. This round is seen as one of the most challenging aspects of the interview process, requiring clear communication and critical thinking.
Behavioral interviews focus on team fit and past experiences, often using situational questions to gauge how candidates approach challenges and communicate. These rounds can vary in tone, with some being more conversational while others may feel more evaluative.
A significant emphasis is placed on C++ and its core concepts, including OOP principles, multithreading, and STL. Candidates should be prepared to discuss language-specific details and demonstrate their understanding of how these concepts apply in real scenarios.
Candidates reported mixed experiences regarding feedback and communication throughout the process, with some feeling left in the dark after interviews. Clear communication from interviewers can vary, impacting overall candidate experience and expectations.