Autodesk Software Engineer candidates report team-dependent loops that commonly combine screening, coding or practical implementation, system design, and behavioral discussion of projects and collaboration.
$153K
Avg. Base Comp
$190K
Avg. Total Comp
3-6 rounds
Typical Rounds
4-6 weeks
Process Length
Autodesk Software Engineer interviews reported here are broad rather than uniform: candidates describe recruiter or hiring-manager conversations, coding assessments or live exercises, technical design discussions, and behavioral follow-ups. Prepare to explain your implementation choices as clearly as you solve the problem. One recent four-round account included a recruiter screen, technical screen, coding round, and panel; its coding prompt asked for the first duplicate in an array, while the panel explored rate limiting, scaling, and failure handling.
Other candidates encountered timed DSA screens, practical React work, and code or system-design conversations. Reported technical prompts include matrix, graph, array, and stack problems, along with broader design discussions. That variation makes it sensible to practice both concise coding communication and a structured approach to requirements, scale, failure modes, and tradeoffs—without assuming any one prompt will recur.
Project depth also appears repeatedly. Candidates report resume walkthroughs, discussions of past design decisions, and questions about C++/OOP, Java, React, or the stack relevant to their background. Prepare a few specific project stories: what you owned, why you chose an approach, how you handled constraints, and what you would change. Behavioral conversations have included collaboration, disagreement, conflict, stakeholder situations, and leadership. Evidence on a single standard loop is limited, so treat the sequence as team-dependent.
Synthesized from 19 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.
I've just finished my 2round of the interview. nothing special it was talk with hiring person about my work experience visa availability, and some of my projects and thought regarding ai use and how i use them. Nothing was surprising as it was based off from the job description. I was confident answering all of them except for the salary part, since i had no idea what to expect when they asked me that.
Questions asked: Second technical interview focused on data structures and problem solving.
Solved two LeetCode-style coding questions with medium difficulty. One question involved binary trees, where I had to traverse the tree and explain the time and space complexity of my solution. The other question involved implementing a queue-based algorithm and discussing edge cases. The interviewer asked me to explain my thought process before writing code and suggested possible optimizations after I finished. There were follow-up questions about complexity analysis, handling corner cases, and alternative approaches. Most of the interview was collaborative, with the interviewer asking clarifying questions while I coded.
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 | |
| 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 | |
| Rolling Bank Transactions | |
| String Shift | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening conversation with recruiting or a hiring manager about background, interest, role fit, and past work. Some reports begin with an assessment or pre-recorded screen instead, so the exact entry point may vary by team.
Candidates report timed DSA questions, a first-duplicate-in-an-array prompt, matrix and k-sum problems, and practical tasks such as calling an API and rendering it in React. Expect to explain a clean approach and respond to follow-up questions.
Reported discussions include rate limiting with scaling and failure handling, file storage at high request volume, REST and cloud concepts, databases, security, and language-specific fundamentals. The focus may be a design walkthrough, project decisions, or system tradeoffs rather than one fixed design prompt.
Candidates report panel, manager, or culture-focused conversations that mix technical discussion with behavioral questions. Be ready to describe project ownership and how you handle disagreement, conflict, stakeholder challenges, or collaboration.
