Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Product engineeringProduct company

Autodesk

Makes design and engineering software such as AutoCAD, Revit, Fusion and Maya for architecture, manufacturing and media.

Not known5 stage process documentedFounded 1982
Headquarters

San Francisco, California, United States

Headcount

5,000 and up

5,000 or more people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply

No careers page on file yet. Try their LinkedIn or the job boards below.

Website

Ask for a referral to Autodesk

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

How they hire

The technical round breakdown comes from a single write-up that appears to describe a campus hire in India, so the loop for experienced engineers in other regions may differ. Autodesk’s own material focuses on behavioural interviewing.

  1. 1

    First technical round

    Unverified
    Technical interview

    Questions on resume projects, data structures and algorithms, SQL basics and object oriented concepts.

    DSASQLOOP
  2. 2

    DSA round

    Unverified
    Live coding

    Mid to hard problems on arrays, linked lists and graphs, plus scenario based questions.

    ArraysGraphsLinked lists
  3. 3

    Fundamentals and resume deep dive

    Unverified
    Technical interview

    SQL queries, databases, operating systems and networking alongside a deep dive into past work.

    DBMSOperating systemsNetworking
  4. 4

    Behavioural interviews and final panel

    Official
    Panel interview

    Interviewers ask for concrete work examples, and panelists share feedback after the final interviews.

    Behavioural
  5. 5

    HR round

    Unverified
    Final HR round

    Company knowledge, location preferences and why you want to join.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Your contribution versus the team’s

    Official

    Autodesk’s recruiter says candidates stall when they do not separate what the team did from what they personally did, their approach and their impact.

  • Company values and products

    Official

    Candidates are encouraged to know the values of courage, customer-centricity, collaboration and impact, and the product range across design, engineering and media.

  • Recent, relevant examples

    Official

    Review the job description and research the company and interviewers, then choose recent examples that match the role.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Course
Grokking Data Structures & Algorithms for Coding Interviews

A foundations course that builds eleven core data structures from the ground up (arrays, matrices, stacks, queues, linked lists, trees and BSTs, hash tables, hash sets, heaps, graphs and tries), then covers sorting, searching, greedy and divide and conquer. Every chapter has practice problems, flashcards and an assessment. It suits students and career switchers whose foundations came from tutorials and who find pattern courses move too fast.

  • Job search
  • DSA
  • CS fundamentals
Design Gurus · Interview Prep · 4 to 6 weeks · Beginner
SubscriptionDetails
Course
Grokking Algorithm Complexity and Big-O

A short text course on algorithm analysis: all five asymptotic notations, time and space complexity, best, worst and average cases, and three methods for recursive complexity including the master theorem. It suits students and self-taught developers who can write working code but freeze when an interviewer asks for the time and space complexity, or who want to understand why one solution is faster than another.

  • Job search
  • DSA
  • CS fundamentals
Design Gurus · Interview Prep · 1 week · Beginner
SubscriptionDetails
Course
Grokking Tech Salary Negotiations

A practical course on negotiating compensation in tech, from preparing and building a strategy to specific tactics, the full package beyond base salary, handling multiple offers and asking for a raise. It has tailored sections for fresh graduates and experienced engineers. It suits anyone with an offer coming, and anyone who has ever accepted the first number out of discomfort.

  • Career
  • Job search
Design Gurus · Career Growth · 1 week
SubscriptionDetails
Roadmap
Engineering Manager Interview Roadmap

A sequenced path of six text-based courses for the engineering manager interview loop, combining coding, system design, microservices patterns, people management scenarios and senior leadership questions. It suits engineers moving into management and managers changing companies, who need to prepare for both the technical and the leadership rounds without piecing a plan together themselves.

  • Career
  • Leadership
  • Job search
Design Gurus · Career Growth · 2 to 3 months · Advanced
SubscriptionDetails
Guide
GeeksforGeeks

A very large site of articles on data structures, algorithms and core CS subjects such as operating systems, DBMS, computer networks and OOP, usually with code in several languages, plus practice problems and paid courses. It is handy for revising a university topic or finding a worked example of a specific algorithm. Quality varies because much is community written, so cross-check anything surprising against a textbook or official documentation.

  • DSA
  • CS fundamentals
  • Databases
GeeksforGeeks · Other · Ongoing reference
Roadmap
Sefism CS Core Subjects Roadmap

An eight-stage roadmap through the core CS subjects: how a computer runs a program, OOP and design, operating systems, computer networks, database theory and internals, software engineering and theory, finished with a systems project such as a shell, an HTTP server or a tiny database. It suits CS students and self-taught developers filling the same gaps, and favours understanding shown in working code over memorised answers.

  • DSA
  • CS fundamentals
  • Databases
Sefism · Other · About 216 hours, 22 to 46 weeks · Beginner
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the Autodesk page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the Autodesk page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

For every project you mention, spell out what you did yourself as well as what the team achieved. Keep examples recent and tied to the job description.

Sources

Whole profile last checked 2026-09-22.

Interviewed at Autodesk? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to Autodesk

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the Autodesk page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.