I recently had the opportunity to interview with Autodesk for the Software Development Engineer 1 role. The entire interview process took about a month to complete and consisted of three rounds: two technical interviews and one with a hiring manager.

In Round 1, the discussion started with fundamental concepts of OOPS, SOLID principles, and some specific Java-related questions. I also talked about the projects I had worked on at my previous company. This round included two DSA problems. The first was a relatively easy, standard LeetCode problem where I had to break a given sentence into individual words, handling various edge cases. For instance, 'Tommy is good dog' should yield 'Tommy', 'is', 'good', 'dog'. I was asked to run my code locally against test cases provided by the interviewer. The second problem involved reading data from a CSV file and performing some analysis. I wasn't very familiar with CSV file reading in C++, but the interviewer was very supportive and allowed me to use Google for syntax.

Round 2 was quite interactive and covered a mix of topics. I faced several behavioral questions and also discussed theoretical questions related to JavaScript and React. We delved into my previous projects again. A specific technical task in this round was to flatten an array in JavaScript, with the constraint of using only a for loop. I had a good discussion with the interviewer throughout this round.

Finally, Round 3 was primarily a behavioral round where I had to explain some of my previous work in full technical detail. The interviewer also provided a comprehensive overview of the role itself and what working at Autodesk entails.

My interview experience for the Software Development Engineer 1 position at Autodesk involved a comprehensive technical discussion.

The conversation started with an in-depth dive into my resume and past technical experiences. I was asked about my migration experience, specifically the learnings and challenges I faced while moving code from Node.js to Spring Boot. Following this, the interviewer inquired about the deployment lifecycle, and I explained the CI/CD process I was familiar with from my time at Chubb.

We then moved on to core computer science concepts, where I had to explain different types of sorting algorithms and provide an implementation example, such as Bubble Sort.

Several system design and problem-solving scenarios were presented. One question involved a caching scenario: how to refresh or update the cache if the response contract changes but old values are still present. Another challenge was about efficiently searching through millions of records, where I discussed techniques like indexing, caching, and distributed search.

I also shared my knowledge on application optimization techniques, covering database queries, caching strategies, asynchronous processing, and scaling methods. The discussion touched upon handling sudden traffic spikes, where I talked about solutions like load balancing, autoscaling, and queues. Finally, I explained the CAP Theorem, detailing consistency, availability, and partition tolerance with examples.

The interview concluded with a deep dive into my previous projects, discussing the design choices I made, the challenges I encountered, and how I resolved them.

Despite a thorough technical discussion, I received a rejection. The reason provided was that another candidate had already completed the interview process earlier.