Start with the player experience problem — what friction, confusion, or inefficiency existed? Describe the design choices you made, what you tested or iterated on, and what shipped. Interviewers want to hear how you think, not just what you made.

Describe how you define base elements (color palette, typography, icon style, component sizing) and document them in a way the team can follow. The goal is a system that scales — where new screens feel native without you reviewing every pixel.

Start with player state questions: what information does the player need, when, and at what urgency level? Persistent elements need different treatment than contextual alerts. Then discuss spatial anchoring, contrast against gameplay backgrounds, and motion that signals without distracting.

Be specific: Unreal’s UMG/Widget Blueprints, Unity’s UI Toolkit or uGUI, Coherent GT, Scaleform, custom engines. Describe the workflow from design to in-engine — do you implement yourself or hand off? TDs prefer UI artists who can at minimum test and adjust their own work in-engine.

Motion should serve function: confirming actions, directing attention, communicating state changes. It hurts when it’s slow (adds latency to player feedback), excessive (trains players to ignore it), or decorative without purpose. Describe a specific decision you made to add or cut UI animation.

Cover the basics: never rely on color alone to convey information (add shape, label, or pattern). Support text scaling. Provide high contrast mode. If you’ve shipped accessibility features, describe the process — player feedback, testing with users, iterating on defaults. If you haven’t, describe how you’d approach it.

Be honest. Studios want to know you can advocate for your design rationale while ultimately respecting the decision authority of the director. The red flag is either capitulating with no pushback (no design conviction) or being immovable (poor collaboration). Show you can disagree professionally.

Cover anchoring and safe zones, scalable layouts, dynamic sizing, and testing across target displays. Mention any specific tools or workflows you use for multi-resolution testing. Console UI has strict safe zone and font size requirements — if you have console experience, describe that workflow.

UI breaks on localization because German and Russian are significantly longer than English. Design for text expansion (plan for 40% longer strings), use flexible containers, avoid fixed-width text fields, and test key strings early. If you have shipped a localized title, describe specific design accommodations you made.

Describe your starting point — silhouette-first design, reference gathering, establishing the visual grammar (line weight, corner radius, perspective style). Explain how you test readability at small sizes and against different background scenarios. Consistency comes from the system, not just individual icon decisions.

Describe how you document your reasoning — annotations, design rationale docs, presentations. The goal is that a programmer or producer can understand why a design choice was made without asking you. This is especially important for decisions that look simple but have complex reasoning behind them.

Be practical. Describe how you triage: what must be fully polished at launch (first-session UI, tutorial screens), what can ship at MVP quality, and what gets cut. Studios want UI artists who can prioritize, not just ones who obsess over every pixel regardless of time.

Studios want to see shipped UI from real games or strong personal projects. They look for UX thinking (not just visual polish), motion and animation work, consistency across a design system, and — increasingly — evidence that you can implement your own work in-engine. Show the process: wireframes and iterations, not just the final screen.

Not necessarily, but the more you can implement in-engine (UMG in Unreal, UI Toolkit in Unity), the more employable you are. At minimum, you should be able to test and adjust your own designs in-engine without relying on a programmer. Blueprint or basic scripting skills are a significant advantage.

A UI art test typically involves redesigning an existing game UI or designing a system (inventory, HUD, settings) from a brief. You’ll have 3-5 days and are expected to deliver mockups with clear design rationale. Some studios ask you to implement the design in-engine. Always ask whether the test is compensated.

UI artist salaries vary by seniority and studio size. Junior UI artists earn $45K-$65K, mid-level $65K-$90K, senior $85K-$120K, and lead UI artists $110K-$150K at major studios. Salaries at AAA studios are higher than indie. ArtBlast includes salary data on UI artist job listings where disclosed.

In game studios, UI artist and UX designer roles often overlap. UI artists typically own the visual design, motion, and asset production. UX designers own the interaction architecture, user flows, and usability testing. At smaller studios, one person does both. At AAA studios, the roles are usually separate, with UI artists working to UX specs.