Why Your Next Game Art Interview Should Ask About LODs

Imagine you're in a windowless conference room, facing a lead artist who's just asked, 'So, what's your process?' You've rehearsed your sculpting workflow, your texturing secrets, your favorite brushes in ZBrush. But the question that actually reveals whether you'll survive in production isn't about your art—it's about your LODs. Level of detail, the humble system that swaps a 15,000-triangle character for an 800-triangle version when the camera pulls back, is the boring, invisible backbone of every shipped game. And yet, in most game art interviews, nobody asks about it.

Why LODs Are the Question That Separates Hobbyists from Pros

When you're starting out, you obsess over the high-poly sculpt. You spend hours in ZBrush pushing DynaMesh around, adding every pore and wrinkle. Then you retopologize, bake, texture, and light. And then you drop it into the engine and it runs at 12 frames per second. That's the moment you learn what every technical artist already knows: game art is not about the hero asset. It's about the 800-triangle version that no one will ever look at closely. The fact base is blunt about this. Unity's own optimization guidance says to spend your polygon budget on silhouette and large forms, not small triangles, and to let textures and normal maps handle the fine detail (Unity mobile optimization guide). A lead who asks about LODs isn't testing your ability to sculpt a nose; they're testing whether you understand that your art exists to serve the frame rate.

The Boring Numbers That Win You the Job

So what does a real LOD chain look like? The fact base gives us a concrete spec: a technical artist might set an LOD0 character at roughly 15,000 triangles with 2048x2048 textures and 2-3 draw calls, scaling down through LOD3 at 800 triangles (Technical artist roles). That's the difference between a next-gen console and a mobile phone. And here's the kicker: Unity recommends reducing triangle counts by roughly 50% between successive LOD levels (Unity mobile optimization guide). So your LOD1 should be around 7,500 triangles, LOD2 around 3,750, and LOD3 at 800. If you can rattle off those numbers in an interview, you're not just an artist—you're a problem-solver. You're saying, 'I know that my job isn't to make the most beautiful mesh; it's to make the most beautiful mesh that still runs.'

Why the High-Poly Dream Is a Trap

I've seen portfolios full of gorgeous ZBrush sculpts, and I've seen those same artists struggle to make a simple prop that doesn't tank the draw call budget. The high-poly sculpt is the bait. The real work is in the low-poly game mesh and the LODs that follow. Consider Unreal Engine 5's Nanite: it can stream film-quality meshes with hundreds of millions of polygons in real time, and it removes the need to hand-author LODs or bake normal maps (Unreal Engine documentation). That sounds like a dream, but it's also a trap. If you rely on Nanite to do your LODs for you, you never learn how to think about polygon efficiency. And when you move to a project that doesn't use Nanite—like a mobile game or a Unity project—you're lost. The fact base shows that dynamic batching in Unity only works for small meshes of roughly 225-300 vertices, depending on the shader (Unity Manual: Draw call batching). That's a brutal constraint, and it's exactly why you need to know how to build LODs by hand.

The Interview Question That Flips the Script

So here's my advice: when you're in an interview and the lead asks if you have any questions, don't ask about the team culture or the coffee machine. Ask about their LOD pipeline. Ask, 'How do you handle LODs for your hero characters? Do you use automatic tools or hand-tuned chains?' That question does three things. First, it shows you understand production realities. Second, it gives you a chance to talk about your own experience, whether it's hand-tuning LODs in Unity or using ZBrush's ZRemesher for quick quad-based retopology (ZBrush official). Third, it opens a conversation about the engine they're using, which is where you can really shine. If they're on Unreal, you can talk about Nanite and its limitations. If they're on Unity, you can reference the 50% rule and the 225-300 vertex batching limit. You're not just answering questions anymore; you're having a peer-level discussion about craft.

What LODs Teach You About Art Direction

Here's the deeper point: LODs aren't just a technical necessity; they're an art direction tool. When you design a low-poly mesh, you're forced to decide what's essential. That 800-triangle version of a character has to read as the same character from across the street. That means you're making choices about silhouette, about color blocking, about what detail matters. This is the same discipline that makes stylized art age better than realism. The fact base notes that stylized games like The Legend of Zelda: The Wind Waker still hold up decades later, while realism-heavy games from the same era look dated (Creative Bloq). Why? Because a strong silhouette and a clear color palette are timeless, while a texture that tried to be photorealistic in 2003 just looks muddy now. LODs force you to find that essential shape, and that skill translates directly to better art direction.

How to Actually Prepare for the LOD Question

So, how do you prepare? Don't just read about LODs; build one. Take one of your existing characters, and create a proper LOD chain: LOD0 at 15,000 triangles, LOD1 at 7,500, LOD2 at 3,750, and LOD3 at 800. Use ZBrush's ZRemesher to generate a quad-dominant mesh, or hand-retopologize in Maya's Quad Draw for animation-friendly edge flow (Game art pipeline). Then bake your normal maps and test the results in Unity or Unreal. Look at the silhouette from a distance. Does it still read? If not, adjust the low-poly mesh, not the texture. That exercise will teach you more than a hundred tutorials on sculpting. And when you walk into that interview, you'll be able to say, 'Here's a character I made, and here's how it performs at 800 triangles.' That's the kind of specificity that gets you hired.

What I'd Actually Do

Here's my blunt recommendation: in your next interview, ask about LODs. Don't wait for them to bring it up. Make it your question. And if they don't have a good answer, that's a red flag—because it means their pipeline is reactive, not planned. You want to work at a studio that treats performance as part of art, not as an afterthought. And you want to show that you're the artist who thinks that way too. So go build that LOD chain, memorize the numbers, and walk in with a question that proves you're not just a sculptor—you're a game artist.

Sources

• Technical artist roles - https://www.gamesindustry.biz/technical-art-roles-what-they-are-and-how-to-get-one
• Unity mobile optimization guide - https://unity.com/how-to/mobile-game-optimization-tips-part-1
• Unity Manual: Draw call batching - https://docs.unity3d.com/6000.3/Documentation/Manual/optimizing-draw-calls.html
• Unreal Engine documentation - https://dev.epicgames.com/documentation/en-us/unreal-engine/nanite-virtualized-geometry-in-unreal-engine
• ZBrush official - https://www.maxon.net/en/zbrush-for-ipad-key-features
• Stylized art longevity - https://www.creativebloq.com/art/character-design/the-new-star-fox-shows-how-easy-it-is-to-overdesign-a-beloved-character