Stop Asking About Tools: The Interview Question That Filters Real Game Artists

You think the best way to hire a game artist is to look at their ArtStation and ask if they know ZBrush. That's wrong. A gorgeous portfolio tells you they can sculpt, but it doesn't tell you if they can ship a game. The real test is whether they understand that art is a pipeline, not a painting. The question that separates the pros from the pretenders isn't about brushes or render settings. It's about LODs. If you're not asking about level of detail in every interview, you're hiring portfolios, not problem-solvers.

The Misconception: Art Is About the Final Image

Most people outside the industry—and plenty inside it—believe game art is judged by the final screenshot. They scroll through a portfolio, see a stunning character, and think, "That's the artist we need." But that image is the result of a long chain of decisions, most of which happen before you ever see a pretty render. The game art pipeline follows a sequence: concept art, 3D modeling (blocking, sculpting, high/low-poly), retopology and UV mapping, baking and texturing, rigging and animation, then engine integration and QA (Game art pipeline, Wikipedia). Every one of those steps is a chance to screw up the whole asset. An artist who can sculpt a beautiful high-poly character but can't retopologize it into a low-poly mesh that animates cleanly is not a game artist—they're a digital sculptor. The game industry pays for shipped content, not for screenshots.

Why LODs Are the Ultimate Filter

Here's my blunt take: if you only ask one technical question in an interview, make it about LODs. Level of detail is the practice of swapping a mesh for a simpler version as it gets farther from the camera. It's not glamorous, but it's the backbone of performance. Unity's guidance is to reduce triangle counts by roughly 50% between successive LOD levels (Unity mobile optimization guide). That's a concrete, testable rule. Ask a candidate: "You have a character that's 15,000 triangles at LOD0. What do you do at LOD1, LOD2, LOD3?" A strong answer will mention that LOD1 might be around 7,500 triangles, LOD2 around 3,750, and LOD3 maybe down to 800. They'll talk about where to spend the polygon budget—on the silhouette and large forms rather than small triangles—and they'll mention using normal maps to fake the detail they're removing (Unity mobile optimization guide). A weak answer will be "I don't really do LODs, the engine handles it." That's a red flag. Even if you use Unreal Engine 5's Nanite, which can import film-quality meshes with hundreds of millions of polygons and automatically streams and scales them in real time, removing the need to hand-author LODs (Unreal Engine documentation, Epic Games), the artist still needs to understand the concept. Nanite doesn't exist in every engine, and even in Unreal, you'll still have to set up LODs for skeletal meshes or things that need custom optimization.

But LODs are just one part of the bigger picture: performance budgets. Technical artists set asset budget spec sheets, like 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, gamesindustry.biz). When you ask a candidate about LODs, you're really asking if they think in systems. Do they know that a game can't have a million polygons per character because the engine has to draw dozens of characters at once? Do they understand draw calls and why batching matters? Unity optimizes draw calls with static batching, dynamic batching, GPU instancing, and the SRP Batcher, but dynamic batching only works for small meshes of roughly 225-300 vertices (Unity Manual: Draw call batching). If an artist has no idea what a draw call is, they're going to make beautiful assets that tank the frame rate. That's not art; that's a problem.

The Counter-Argument: "But What About Style?"

You might be thinking, "Hold on, we've published articles about why stylized art beats photorealism, and you're telling me to grill candidates about LODs? Isn't that missing the point?" Fair enough. Style matters. Stylized art direction tends to age better than chasing photorealism—cel-shaded games like The Legend of Zelda: The Wind Waker still hold up decades later, while realism-heavy games from the same era look dated (Stylized art longevity, Creative Bloq). I'm not saying you should hire a realist who can't do stylized. I'm saying that style is a choice, but LODs are a constraint. A great art director can set a style, but a great game artist can execute that style within the technical limits of the platform. The two aren't mutually exclusive. In fact, the best stylized artists are often the ones who understand the pipeline best, because they have to fight harder to make a low-poly model read as charming rather than blocky. So when I say ask about LODs, I'm not ignoring style. I'm testing whether the candidate can think like a game artist, not just like a painter.

How to Conduct the Interview

So here's the practical advice. In your next interview, after the portfolio walkthrough, ask this: "Walk me through your process for a hero prop, from concept to engine. Where do you make decisions about topology, UVs, and LODs?" Listen for a few key things. Do they mention retopology? They should, because retopology rebuilds a dense sculpt into a cleaner, lower-polygon mesh with purposeful edge flow, since real-time engines can't afford millions of polygons per character (Game art pipeline, Wikipedia). Do they talk about UV mapping? They should, because UV unwrapping flattens a 3D model into 2D shells so textures can be painted (Game art pipeline, Wikipedia). Do they know why quads are preferred over triangles? Because quads are easier to edit, subdivide, and unwrap, and they give cleaner deformation for animation (Game art pipeline, Wikipedia). And do they have a plan for LODs? Even if they say "I'd use Nanite," that's fine—as long as they can explain why they'd use it and when they wouldn't.

Let me give you a concrete example of what a good answer sounds like. A candidate says: "For a hero asset, I'd start with a high-poly sculpt in ZBrush, using DynaMesh to iterate on the silhouette. Then I'd retopologize with ZRemesher to get a quad-dominant mesh, and clean up edge flow around joints manually. I'd unwrap UVs in RizomUV, making sure to use the full texture space. Then I'd bake down the high-poly detail onto the low-poly, using normal maps and an ambient occlusion map. For LODs, I'd start with the LOD0 budget from the technical artist, maybe 15,000 triangles, and then generate LOD1 at 7,500, LOD2 at 3,750, and LOD3 at 800, using decimation or retopology. I'd also check draw calls, because if I can keep the whole character in one or two materials, that's better for batching." That answer shows they understand the whole pipeline, not just one stage. Compare that to someone who says, "I just sculpt and export to the engine." That's a hobbyist, not a professional.

Comparison: The Old Way vs. The LOD-Aware Way

I know you're busy. You have a project to ship, and you just need someone who can make good art. But if you hire someone who can't handle LODs, you'll spend months optimizing their assets, or worse, you'll ship a game that runs at 20 frames per second on the average console. The U.S. Bureau of Labor Statistics says the median wage for special effects artists and animators is $99,060 a year, and employment is projected to grow 8% from 2022 to 2032 (BLS Occupational Employment and Wages). That's not a cheap mistake. You're paying professional rates for professional skills. Demand them.

Here's the single most important thing to remember: You're not hiring an artist; you're hiring a game artist. A game artist is someone who can make art that runs at 60 frames per second, loads in under 10 seconds, and doesn't break the memory budget. LODs are the most direct test of that mindset. So next time you're interviewing, skip the "What's your favorite brush?" nonsense. Ask about LODs. You'll be surprised how many portfolios crumble.

Sources

• Game art pipeline (Wikipedia) - https://en.wikipedia.org/wiki/Video_game_art_design
• Unity mobile optimization guide - https://unity.com/how-to/mobile-game-optimization-tips-part-1
• Unreal Engine documentation (Epic Games) - https://dev.epicgames.com/documentation/en-us/unreal-engine/nanite-virtualized-geometry-in-unreal-engine
• Technical artist roles (gamesindustry.biz) - https://www.gamesindustry.biz/technical-art-roles-what-they-are-and-how-to-get-one
• Stylized art longevity (Creative Bloq) - https://www.creativebloq.com/art/character-design/the-new-star-fox-shows-how-easy-it-is-to-overdesign-a-beloved-character
• BLS Occupational Employment and Wages - https://www.bls.gov/oes/current/oes271014.htm