Autodesk Software Engineer interviews reported by candidates range from project and recruiter discussions to coding, design, and behavioral rounds, with technical emphasis varying substantially by team and stack.
$173K
Avg. Base Comp
$220K
Avg. Total Comp
3-7 rounds
Typical Rounds
4-10 weeks
Process Length
Autodesk Software Engineer interviews appear highly team-dependent, but candidate reports repeatedly place your own work at the center of the conversation. Be ready to explain what you personally built, why you made particular design choices, and how you handled tradeoffs. Candidates described project or resume discussions with recruiters, hiring managers, or engineers before and alongside technical evaluation.
Technical content varied rather than following one universal script. Reported exercises included finding the longest substring without repeating characters, implementing a linked list with an array, building an LRU cache, and refactoring existing code. Practical follow-ups covered data-structure selection, thread safety, modernizing code, benchmarking improvements, complexity, edge cases, and optimization. Some discussions also touched on Java, object-oriented programming, operating systems, networks, SQL, unit testing, and debugging.
Design evaluation likewise depended on the team. One candidate was asked to design a reusable logging system, while another encountered the LRU-cache implementation in a low-level design round. Practice clarifying requirements, choosing suitable data structures and interfaces, identifying failure cases, and explaining performance tradeoffs aloud.
Behavioral conversations may cover project ownership, teamwork, impact, career motivation, or familiarity with Autodesk products and their industries. Prepare a concise project walkthrough that distinguishes your contribution from the broader team’s work. Reported processes ranged from several structured stages to more than seven interviews, and some candidates experienced long gaps or waits of a month or more. Confirm the expected format and stack with the recruiter while continuing other applications until you receive a decision.
Synthesized from 39 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Autodesk process.
The LLD round was the point where the process really broke down for me. I first had a recruiter phone screen focused on the projects I had worked on and my general fit for the role. The hiring-manager conversation then went much deeper into my resume, especially what I had personally contributed, and again felt primarily like a role-skill-fit discussion.
The next round was an LLD interview with another principal engineer. I was asked to implement an LRU cache. I explained the approach and began coding, but the interviewer interrupted every few seconds and kept pushing me toward a different data structure even though I had started with the correct one. I was able to lay out the logic and structure, but I could not finish the code under that level of intervention. At the end, the interviewer only said that he thought he had asked a lot of questions.
I received a rejection email after that round, along with a feedback form, and I wrote about not being given room to perform in the LLD interview. Afterward, the recruiter contacted me again, saying there had been a debrief and they wanted to continue. The architecture round asked me to design a logging system that other systems could use. That round went well, but I received another rejection email a few days later. The communication and reversal after the initial rejection made the overall experience feel highly unprofessional.
Prep tip from this candidate
Be ready to explain and implement an LRU cache while defending your data-structure choices, and practice designing a reusable logging system for other systems.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Autodesk
Write a function to determine whether or not two rectangles overlap.
| Question | |
|---|---|
| Daily Retention Summary | |
| Nearest Common Ancestor | |
| Hurdles In Data Projects | |
| Real-Time Hashtag Partitioning | |
| Priority Queue Using Linked List | |
| Cross-Region Inventory Sync | |
| Spam Classifier | |
| Secure Messaging Platform | |
| Deciding Between Solutions | |
| Scalable Data Pipelines | |
| Client Solution Pushback | |
| ReLu vs Tanh | |
| Parking Application System Design | |
| Flight Modeling | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Minimum Change | |
| Random SQL Sample | |
| Raining in Seattle | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter or early interviewer conversations that explore background, project ownership, interest in software engineering, and fit. Prepare a concise project walkthrough that separates your contribution from the broader team’s work and explains key technical choices.
Technical evaluations may use live coding, an online assessment, or a practical task. Reported topics include easy-to-medium DSA, code refactoring, data structures, concurrency, language fundamentals, and code explanation. Narrate correctness, complexity, edge cases, and tradeoffs as you work.
Some candidates report architecture or low-level design discussions, such as an offline-first issue tracker, a logging system, or a changing rules-engine task. Typically, explain assumptions first, then organize the design around interfaces, data flow, reliability, and extensibility.
Candidates report manager and behavioral rounds that revisit prior work, teamwork, career goals, and sometimes Autodesk product familiarity. Be ready to connect your experience to the team’s domain without assuming that any one product or topic will be assessed.
