Articles

Autodesk SWE Intern Interview 2027: Coding, Design, and Interview Timeline

Prepare for Autodesk SWE intern interviews in 2027 with the Oslo application deadline, coding and design exercises, candidate evidence, and timeline advice.

Autodesk SWE intern interview preparation for 2027 should cover coding fundamentals, a clear explanation of your projects, and design decisions at the scale of a small feature. A current Oslo internship provides a concrete application opportunity. Autodesk also publishes a student interview overview, but it does not establish one identical assessment for every team or country.

The useful distinction is between the job you are applying for and the interview format your recruiter confirms. This guide separates official information, older candidate reports, and original preparation exercises.

Evidence checked September 7, 2026. The specific 2027 opportunity below is in Oslo; historical interview accounts come from other locations.

The confirmed 2027 opportunity: Autodesk Oslo

Official role facts: Autodesk lists Software Engineering Intern Summer 2027, requisition 26WD100046, in Oslo. It is paid, full-time, and on-site. Applications receive rolling review and close at the end of September 2026. The posting does not specify an exact closing hour. Official internship listing.

The role contributes to Forma architecture and construction software, including web-based 3D tools and cloud systems. Relevant computing study is preferred, ideally in the penultimate year, while strong earlier students are welcome. Norway work eligibility is required. Applicants should supply a CV, cover letter, academic transcripts, and relevant diplomas or certificates; the listing requests PDF documents.

Official general eligibility: Autodesk's FAQ also specifies a minimum age of 18, active enrollment, and residence and university attendance in the internship country. If your circumstances sit between the general FAQ and a particular posting, clarify them with recruiting. Do not assume that work eligibility alone resolves every enrollment or location requirement. Autodesk careers FAQ.

Preparation advice: save the requisition, location, document requirements, and application confirmation together. Check that your portfolio opens without a login and that your transcript is readable. Apply with a coherent project story instead of delaying for another week of unrelated algorithm practice. A different Autodesk vacancy needs its own eligibility and deadline check.

What Autodesk says about coding and interviews

Official student guidance: Autodesk describes two to three virtual interviews with the hiring manager and team members. A technical assessment may involve a simple coding question or a 30–60-minute coding exercise. The page describes an outcome within two weeks after all interviews finish, with variation by role. Autodesk students page.

That leaves several practical details open: the platform, supported languages, assessment order, and whether coding happens live. There is no basis here for promising every 2027 applicant a HackerRank invitation or a separate system-design round.

Autodesk's broader FAQ describes recruiter and hiring-manager conversations, a possible functional assessment, and an interview team. That company-wide overview has different wording from the student page. Treat these as overlapping descriptions, not consecutive stages to add together.

Use the invitation to resolve the ambiguity:

What the invitation says	What to confirm	What to rehearse
Technical assessment	Live or asynchronous, language, duration, permitted tools	A complete solution with tests and complexity analysis
Hiring-manager or project interview	Which project to prepare and whether a demonstration helps	Your contribution, one tradeoff, and one result
Design discussion	Feature design, object modeling, or broader architecture	Requirements and state changes before infrastructure
Final interview	Remaining stages and expected feedback date	Specific questions about the team and intern project

The Oslo role mentions AI tooling in everyday engineering. Official interview guidance is separate: Autodesk restricts outside interview assistance, with exceptions for relevant assessment instructions or accommodations. Follow the invitation's rules; workplace AI use does not imply permission to use an assistant during an assessment.

What candidate reports establish

Candidate report, Birmingham: an account posted February 19, 2026 describes an interview in November 2025. The candidate reports an OA, a behavioral stage, and an in-person interview plus another technical assessment. They mention object-oriented concepts and a geometry question. This is an anonymous historical UK account, not evidence of the Oslo 2027 sequence. Glassdoor internship reports.

Candidate report, London: an account posted July 27, 2026 actually dates its interview to June 2024. It describes a project discussion, a string problem, and follow-ups about complexity and edge cases. The publication date does not make the interview current-cycle evidence.

The reviewed sources did not establish two independent reports from the same 2027 internship cohort. These accounts support practising code explanations and project discussions. They cannot establish an exact question list, difficulty distribution, cutoff, or offer probability.

Do not spend your remaining preparation time memorizing a reported geometry question. If your team works with graphical models, it is more useful to explain coordinate assumptions and boundary cases than to assume one old question will return.

Coding practice: a selection box for a design tool

Original practice exercise: this simplified 2D problem is inspired by design-tool work. It is not a reported Autodesk question or a description of Forma's implementation.

A drawing contains rectangular objects. Each rectangle has two opposite corners, which may arrive in either order. Given selected object IDs, return the smallest axis-aligned rectangle enclosing all selected objects. An empty selection returns None; an unknown ID is an error. Repeated IDs do not change the result.

First agree that coordinates are finite numbers in a common coordinate system. A zero-width rectangle is allowed. Rotation is outside this exercise. Those statements prevent you from solving a different problem from the one the interviewer intends.

For object A, the corners are (4, 3) and (1, 1). Normalization gives bounds (1, 1, 4, 3). Object B has bounds (3, 0, 6, 2). Selecting both must return (1, 0, 6, 3). Summing their areas would answer a different question; the enclosing box includes space between or around objects.

def selection_bounds(objects, selected_ids):
    bounds = None
    for object_id in selected_ids:
        x1, y1, x2, y2 = objects[object_id]
        left, right = min(x1, x2), max(x1, x2)
        bottom, top = min(y1, y2), max(y1, y2)
        if bounds is None:
            bounds = (left, bottom, right, top)
        else:
            l, b, r, t = bounds
            bounds = (min(l, left), min(b, bottom),
                      max(r, right), max(t, top))
    return bounds

With constant-time dictionary lookup, this takes O(k) time for k selection entries and O(1) auxiliary space. Duplicate IDs are harmless because repeating the same minimum or maximum changes nothing. The function assumes the agreed input contract; dictionary lookup raises KeyError for an unknown object.

Test the example, empty input, reversed corners, negative coordinates, duplicates, and a rectangle entirely inside another. Then ask how the function should behave if the user deletes an object while it remains selected. Rejecting stale input and silently dropping deleted IDs produce different user experiences. Choose deliberately instead of hiding the decision in exception handling.

For timed practice, explain the invariant after each iteration: the accumulated bounds enclose exactly the objects processed so far. Use that invariant to explain correctness and handle a follow-up change.

Design preparation: make edits and analysis agree

Preparation inference: the Oslo posting's product context makes small feature discussions useful rehearsal. It does not confirm a design interview. Extend the selection exercise only after you can implement and test its core behavior.

Suppose selecting objects triggers a background calculation. The user changes the model while the calculation runs. An older result finishes after the newer edit. Should it replace what the user currently sees?

One simple design gives every model revision a version ID and attaches that ID to each analysis request. Display a result only when its version matches the model being shown. Cancellation can reduce wasted work, but checking the version still protects the interface when a canceled job completes anyway.

Walk through a concrete race: request analysis for version 7, edit to version 8, then receive the version 7 result. Keep the version 8 view intact. If the interface intentionally offers historical results, label the older version explicitly rather than presenting it as current.

Next consider undo. For a small prototype, retaining immutable model snapshots can make undo behavior easy to reason about. The cost grows with model size and edit count. A command history can use less storage, but inverse operations become complicated when edits depend on each other. Start by stating your prototype's scale and choose an approach that fits it.

A useful follow-up is whether undo restores an old version ID or creates a new revision with equivalent geometry. Either choice needs a clear relationship between model identity and cached analysis. Explain what your design guarantees before proposing a cache.

This is enough scope for a productive rehearsal: selection state, model revisions, asynchronous results, and undo. Add collaboration, permissions, or multiple servers only when the interviewer introduces requirements that need them.

Explain a project as a product decision

Official hiring-manager advice: Autodesk's historical internship tips emphasize computer-science fundamentals, communication, and willingness to learn. The author also describes intern work reaching actual users. That supports preparing an understandable project discussion; it is not a published 2027 scoring rubric. Autodesk internship tips.

Official recruiter advice: another Autodesk article recommends distinguishing your personal contribution from the team's work. Its author discusses recruiting experience focused on UX roles, so use it as communication guidance rather than evidence about SWE interview stages. Autodesk recruiter interview tips.

For your own project, prepare a short explanation of the user problem, the part you owned, and one decision you changed after feedback. Then prepare a deeper answer about a bug or limitation. If you built a modeling tool, explain why a particular interaction needed immediate feedback and what you moved into background work.

Use evidence you actually have: a failing test you fixed, a review comment, a measured latency, or a user observation. When no measurement exists, say how you would evaluate the change next. Invented impact numbers weaken an otherwise credible student project.

Five practice questions with a specific purpose

The harder state-management questions are optional extensions; complete a smaller correct solution before exploring their full scope.

Practice question	Connection to this preparation
Remove and Compact a Parent-Index Forest	Reason about deletion and index changes in a hierarchy, relevant practice for a model's object tree.
Implement a Set with Readable Snapshots	Explain historical state without accidentally changing an earlier snapshot.
Minimize Delivery-Grid Inconvenience	Practise coordinate reasoning and explicitly defining a distance measure.
Implement a Reusable Locker Allocation System	Keep allocation and release operations consistent across a sequence of updates.
Evaluate an AI-Assisted Engineering Workflow	Explain how you checked AI-generated work, while separating project tooling from interview permissions.

Application and interview timeline: keep the clocks separate

Official calendar: Autodesk's FAQ identifies September–November and February–April as typical recruiting seasons. Those broad windows are not deadlines for individual jobs. The Oslo role's September 2026 closing guidance belongs specifically to that Summer 2027 requisition.

Planning advice: track three dates separately: application submission, any assessment deadline, and the final completed interview. The student page's two-week outcome guidance starts after all interviews, not after applying. It does not promise an interview invitation within two weeks of submission.

At the end of a conversation, confirm the next stage and expected response date. If that date passes, follow up with your requisition number and interview date. Continue other applications while waiting. Your most useful preparation record is the current invitation, the team's product context, and the questions you still need answered—not a timeline borrowed from another location.