HeroApply
Auto Apply to hundreds of jobs in a few hours
English (US)EspañolItalianoPortuguêsFrançaisDeutsch日本語한국어
Sign up

3D Artist interview questions and how to answer them

A 3D artist interview is mostly a conversation about your portfolio, with a lead poking at the parts you didn't show. Expect to explain how you built a piece, why you made the calls you did, and how you'd handle a note you disagree with. The questions below are the ones that come up, with what the interviewer is really listening for.

11 questions7 minute read

Part 1

1.Walk me through one piece in your portfolio from reference to final render.

Why they ask

This tells them more than any other question. They want to see whether you plan before you model and whether you actually made every part of it yourself.

How to answer

  • Pick the piece closest to the work this studio does, not your favourite
  • Start with the reference board and what you were trying to match
  • Name each stage and tool: blockout in Blender, sculpt in ZBrush, retopo, UVs, bake, Substance Painter, present in Marmoset Toolbag
  • Point to one problem you hit and how you solved it
  • Say what you'd change if you rebuilt it now

2.How do you decide where to spend polygons on a game asset?

Why they ask

Game studios need artists who build to a budget without being told every time. This checks whether you understand silhouette and camera distance.

How to answer

  • Spend geometry on the silhouette and anything the camera sees up close
  • Let the normal map carry surface detail like bolts, seams and panel lines
  • Ask how close the player gets and how many copies will be on screen
  • Mention LODs and how you'd reduce the mesh for distance

3.Tell me about your UV and texel density process.

Why they ask

Bad UVs make textures blurry or inconsistent next to other assets. Leads want to know you'll match the rest of the scene without being chased.

How to answer

  • Set texel density to the project's target before you unwrap
  • Hide seams where the camera won't catch them
  • Straighten shells on hard-surface pieces so texture detail lines up
  • Pack tightly and explain when you'd use overlapping or mirrored UVs to save space
4.What goes wrong when you bake normal maps, and how do you fix it?

Why they ask

Every artist hits baking errors. This separates people who've shipped assets from people who've only rendered sculpts.

How to answer

  • Name real artifacts: skewed details, waviness, seams showing, rays missing the high poly
  • Talk about using a cage and adjusting it rather than just raising the distance
  • Mention matching smoothing groups or hard edges to UV splits
  • Say you check the bake in the target engine, not only in the baker
5.How do you set up PBR materials so they read correctly under different lighting?

Why they ask

An asset that looks great in your render and wrong in their engine costs the team time. They're checking that your materials are physically sensible.

How to answer

  • Keep albedo values in a believable range, no baked lighting in the color map
  • Explain how metalness and roughness do the work of making a surface read as a material
  • Test the asset under neutral lighting and in the actual scene
  • Mention using a calibrated reference or the project's material library

Part 2

6.An art director tells you your asset doesn't fit the style. What do you do?

Why they ask

Revisions are the job. They want to hear that you'll ask questions and adjust, not defend your first attempt.

How to answer

  • Ask for the specific references or existing assets it should match
  • Break the note into shape, material and color so you know what to change
  • Do a quick pass and check back before you spend a full day on it
  • Give one real example where you did this
7.How do you work with concept art that doesn't show the back or the sides?

Why they ask

Concepts are rarely complete. This checks whether you can fill gaps in a way that fits the design, and whether you know when to ask.

How to answer

  • Pull extra reference from the concept artist's other pieces and the style guide
  • Block out the missing views and send a quick screenshot for approval
  • Keep design language consistent: shape rhythm, trim, wear
  • Flag anything that doesn't make functional sense, like a hinge that can't open
8.What does your file look like when you hand it off?

Why they ask

Messy files break pipelines. Leads want to know the next person can open your work and use it without a call.

How to answer

  • Follow the project's naming convention for meshes, materials and textures
  • Freeze transforms, set the pivot where the animator or level designer needs it
  • Delete history and hidden junk geometry
  • Check it into Perforce or the studio's version control with a clear note
9.Tell me about a deadline you nearly missed.

Why they ask

Milestones slip and scope changes late. They want to see how you plan, when you raise a flag, and whether you cut the right corners.

How to answer

  • Set up the situation quickly and say what was at stake
  • Explain when you realised you were behind and who you told
  • Say what you cut or simplified and why that was the right call
  • End with what you now do differently at the start of a task
10.What part of the pipeline are you weakest in right now?

Why they ask

Every artist has gaps. This checks self-awareness and if you're working on it or hiding it.

How to answer

  • Name a real gap, like rigging-friendly topology or procedural texturing in Substance Designer
  • Say how it's affected your work
  • Describe what you're doing about it with a specific piece or course
  • Keep it short and move on

Part 3

11.How do you keep up with new tools and techniques?

Why they ask

Tools change often in this field. Leads want someone who picks things up on their own time without derailing the project.

How to answer

  • Name specific sources: artist breakdowns on ArtStation, tool documentation, studio talks
  • Give one thing you learned lately and actually used on a piece
  • Mention that you test new tools on personal work before bringing them to a production file

Questions to ask them

Ask at least two. It shows you're picking them too.

  • What does a typical asset brief look like here, and who signs off on it?
  • Which engine and DCC tools does the team use, and is there a tech artist who owns the pipeline?
  • How are art test results reviewed, and will I get feedback on mine either way?
  • What does the lead-up to a milestone usually look like for the art team?
  • How do artists here grow into senior or lead roles, and what did the last person who moved up do differently?

Related interview guides

Art Director