Autodesk Interview Experience (Senior Software Engineer) [Bengaluru] β€” Nov 2025

autodesk logo
autodesk
Senior Software EngineerBengaluru8 yearsOffer
December 2, 2025 β€’ 45 reads

Summary

I recently interviewed at Autodesk for a Senior Software Engineer position in Bengaluru. The three-week process included coding, system design, and behavioral rounds, culminating in an offer.

Full Experience

πŸ“ž Round 0 β€” Recruiter Screening

My journey started with a brief phone call with the recruiter. We discussed my salary expectations, the role's fit with my background, and some general background information. It was a smooth and straightforward conversation, after which I received an email to schedule my first technical round, which I set for a week later.

πŸ§‘β€πŸ’» Round 1 β€” Coding (CoderPad, 1 hour, 2 interviewers)

This round began with approximately 20 minutes of discussion about my current role, projects I've worked on, challenges I faced, and decisions I made. Following that, we moved on to two coding questions:

  • Question 1: A classic LeetCode medium-level stack problem. I solved this quite quickly, in about 10 minutes.
  • Question 2: I was asked to imagine a simple filesystem structure composed of 'boxes-within-boxes'. I implemented an iterative solution efficiently. The interviewer then prompted me to improve upon it and consider a recursive approach, but we ran out of time as they wanted to delve into more resume-project related questions.

The final 15 minutes were again dedicated to project discussions. A week later, after a follow-up, I heard back that I had cleared Round 1.

πŸ›οΈ Round 2 β€” System Design & Coding (60 mins, 3 interviewers)

This round had a well-structured flow:

  • Resume Q&A (10 mins): A few questions about my experience and the projects I had listed.
  • System Design Portion (30 mins): The discussion revolved around two main areas:
    1. How I would design and scale a hypothetical system.
    2. How I would build a specific system on AWS, detailing which AWS components I would use and my rationale.
  • Coding (CoderPad, 15 mins): We returned to coding with two questions, both building upon the filesystem problem from Round 1:
    • Question 1: A variation of the Round 1, Question 2, which could be solved iteratively.
    • Question 2: A slight extension of the previous question. These became quite straightforward once I applied my understanding of recursion and tree traversal. The interviewers were very helpful throughout this section.

I completed this round on a Friday, and the following Monday, I received an email inquiring about my availability for the Hiring Manager round.

πŸ‘₯ Round 3 β€” Behavioural + Hiring Manager (45 mins)

This was a very conversational round. We discussed various aspects:

  • Team culture and dynamics.
  • My approach to collaboration.
  • My decision-making style.
  • A few specific questions about my most recent projects.
  • How the team operates internally.

There were no tricky questions; the focus was purely on assessing cultural and team fit. I left with a really positive impression of the team. The very next day, the recruiter reached out to inform me that an offer would be extended.

Interview Questions (3)

Q1
Filesystem with Boxes-within-Boxes (Iterative & Recursive)
Data Structures & Algorithms

I was asked to imagine a simple filesystem structure where 'boxes' can contain other 'boxes'. I initially solved it quickly with an iterative solution. The interviewer then asked me to improve it and think recursively.

Q2
Filesystem Variation (Iterative)
Data Structures & Algorithms

This coding question was a variation of the filesystem problem previously encountered in Round 1, designed to be solvable iteratively.

Q3
Filesystem Extension (Recursion & Tree Traversal)
Data Structures & Algorithms

An extension of the previous filesystem problem was presented. This problem became straightforward once the concepts of recursion and tree traversal were applied.

Preparation Tips

🎯 Final Thoughts & Preparation Tips

Each round felt fair and engaging, and Autodesk’s interviewers were friendly, providing ample space for thought and discussion. For anyone preparing for similar interviews, I recommend the following:

  • Practice recursion, trees, and array manipulation extensively.
  • Brush up on REST API design principles.
  • Refresh your understanding of AWS building blocks and their applications.
  • Be ready to deeply explain the projects mentioned in your resume.

Good luck to everyone preparing! πŸš€

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!