The phrase "game UI/UX designer" describes at least three different jobs, and most studios write a job description that mixes all three, hire whoever is best at the one they mentioned first, and then wonder why the other two are not getting done.
This covers what the roles actually are, how to tell them apart in a portfolio, whether you should hire at all, and the interview questions that reveal something.
The Three Jobs Hiding in One Job Title
UI artist. Makes it look good. Icons, HUD elements, menu art, visual systems, motion. This is a craft discipline with a high skill ceiling and it is the most visible of the three, which is why it dominates portfolios and job specs. A good one transforms how your game feels. They will not tell you the screen should not exist.
UI designer. Decides layout, hierarchy, states, and behaviour. Where things go, what happens when you press them, what the empty state looks like, how it survives a 40-character item name in German. This is the least glamorous of the three and the one that determines whether the interface actually functions.
UX designer. Decides what appears, when, and whether at all. Sequencing, onboarding, cognitive load, information architecture. This person's best work is invisible and produces no portfolio pieces, which makes them the hardest to hire and the easiest to undervalue.
Most studios need all three and can afford one. The failure is not choosing, writing a spec that describes all three, and hiring the artist because the artist's work photographs. Then the studio has a beautiful interface with the same structural problems and concludes that design did not help.
The distinction between the last two is not academic and we break it down properly in our guides to game UI design and game UX design. The short version: if the fix is a colour, it is UI. If the fix is what appears when, it is UX.
Work Out Which One You Need
Diagnose before you post the role.
Your interface looks dated but performs fine. You need a UI artist. This is a real problem and the cheapest of the three to solve.
Your interface is confusing but the structure is right. You need a UI designer. Symptoms: players cannot find things that exist, controller navigation is awkward, the inventory is a known joke internally.
A number is bad and nobody can explain it. You need a UX designer, and hiring either of the other two will cost you six months. Symptoms: first-session drop-off, activation below expectation, a store that underconverts against traffic that is fine.
You have all three problems. Hire the UX designer first, because they will tell you which of the other two to hire next and in what order. This is unintuitive and it is right.
Reading a Games Design Portfolio
Portfolios select for the photogenic, which correlates weakly with the interface working. A screenshot is judged at leisure for two seconds. An interface is judged under pressure over hundreds of hours. Those evaluations disagree constantly.
What to look for instead:
The before. A candidate showing only finished screens is showing you their art. One who shows what was there before and explains what was wrong with it is showing you their thinking, which is the thing you are actually hiring.
A constraint. Every real project has one. A budget, a legacy system, a stakeholder who would not move, a platform requirement. Portfolio pieces with no constraints are student work or fiction.
Something they removed. This is the single best signal in the discipline. Ask what they took out and why. Candidates who have only ever added things have never done the hard part.
Outcomes, if any exist. Not every designer has access to numbers and it is unfair to require them. But a candidate who knows what happened after their work shipped is a candidate who cared, and that is rarer than it should be.
Range. If every piece in the portfolio has the same visual language, you are looking at someone with a style rather than a practice. Fine if their style is your game. A problem if it is not, because they will apply it anyway.
The Interview Questions That Reveal Something
"What would you remove from our interface?" Give them the build and half an hour. This is the fastest test in the discipline and almost nobody uses it. UI artists will talk about hierarchy and polish. A UX person will have structural opinions immediately, because removal is what they think about.
"Tell me about a time research changed your mind." The answer separates people who do research from people who present it. If nothing ever changed, there was no research.
Claudia Mérigo, a UX researcher on our team, described a gaming project where the interviews revealed the client had misunderstood their own users entirely. The product had been designed for casual gamers. The people who would actually use it were professional gamers, and those two audiences have completely different behaviours, needs, and expectations. The research redirected the whole product. That is what a real answer sounds like.
"How do you handle controller navigation?" A technical screen that separates people who have shipped games from people who have shipped software. The right answer is that focus order, wrap behaviour, and default selection are design deliverables, specified in the file, not left to engineering. Someone who has never thought about it will not understand the question.
"What text size do you use on console?" Microsoft's Xbox Accessibility Guidelines publish minimums by platform and resolution, and they are larger than most designers guess. A candidate who has shipped console knows these exist. One who has not will say they will make it look good on a TV.
"What is on the accessibility baseline?" The Game Accessibility Guidelines basic tier is genuinely basic, and most shipped games still fail parts of it. Remappable controls, text size options, subtitle backgrounds, never using colour as the only carrier of meaning. A candidate who cannot name anything on it is going to hand you a compliance problem and a store-listing problem, since platform holders now surface this.
"How do you handle a 40-character item name in German?" Localisation inflates UI strings 30 to 40% into German and worse elsewhere. The answer you want involves pseudo-localisation before translations exist. The answer you will usually get is "flexible components," which is a way of saying they have not hit this yet.
"What happens when the producer disagrees with you?" The most revealing question here. A designer who always defers is a pair of hands. If you are hiring judgement and they fold under pressure, you will never receive the judgement.
Writing the Job Description So It Attracts the Right Person
Once you know which of the three you need, the spec has to say so, and most do the opposite.
The generic version, "seeking a UI/UX designer to create beautiful, intuitive interfaces for our game," describes all three jobs and commits to none. It attracts artists, because artists read "beautiful" and apply. Your UX candidates read it and correctly conclude the role is decorative.
What changes the applicant pool is naming the problem rather than the deliverables. "Our first-session drop-off is 62% and we do not know why. You will find out and fix it" is a spec that a UX designer reads and gets excited about, and that a UI artist self-selects out of. That is the filter working.
Two other things worth putting in writing. Say where the role sits, because a designer reporting into art has a different job than one reporting into product regardless of the title, and good candidates know to ask. And say what authority the role carries. A designer who can remove things is a different hire than one who receives a spec, and the second is much easier to fill and much less useful when the problem is structural.
In-House Versus Outsourcing
The trade is not really cost. It is authority.
An outsourced designer, however good, cannot tell your VP of Product that the onboarding is the problem. They are a supplier. They have no standing, no context on your politics, and no ability to lose that argument and stay in the room afterwards. That is not a criticism of outsourcing, it is the structure.
Which produces a clean decision rule. Outsource production. Hire direction.
If you know what needs building and need it built, outsourcing is efficient and frequently excellent. Published rates for game UX designers run from roughly $25 an hour to well over $100, and that spread is a category gradient rather than a quality one. The bottom is art production in a low-cost region. The top is a team with product and research capability.
If you do not know what needs building, outsourcing will give you a well-executed version of your current assumptions. That is the expensive failure, because it looks like progress for six months.
The middle path that actually works for a lot of studios: one senior person in-house with authority, plus outsourced capacity underneath them. You are buying judgement once and hands as needed. Trying to buy judgement by the hour from a vendor with no standing in your org is the thing that does not work, and we cover how to evaluate vendors in our guide to choosing a game UI/UX design company.
The Case for One Senior Person Over Three Juniors
Studios facing a design gap often reach for headcount, because headcount is a legible answer to a resourcing question. It is frequently the wrong shape.
The core problem in game interfaces is not production capacity. It is that nobody is empowered to remove things.
Eric Lee Smith, a game designer with award-winning titles behind him, described the dynamic to us on our Visionaries podcast as a law of development: the longer a product is in development, the more complicated it becomes. He offered it as simply true rather than as a criticism, and that framing is exactly why headcount does not fix it. Three more designers do not reduce complexity. They increase throughput, and throughput is how complexity got here.
What changes the outcome is one person with enough seniority to tell the economy designer their currency is not going on the HUD, and enough standing to survive that conversation. That is a hiring decision about level, not volume, and it is usually cheaper than the alternative.
The reason it matters is the thing underneath all of it. Sidney Rhoads, a product designer on our team, described it in a conversation about psychology in UX design: cognitive load is what you are almost always trying to decrease, because too much stimulus or choice at once fatigues people and slows everything down. Your player's capacity is fixed. Your team's output is not. Somebody senior has to hold that line, and juniors structurally cannot.
What Good Looks Like When You Get It Right
Buildbox is a no-code game creation platform used by millions, backed by a former Riot Games CTO. Genuinely powerful product. The original interface presented all of that power the moment a user signed in, and people got lost and left before making anything. The value was real and invisible.
The work that fixed it was not production. It was a single decision: identify the meaningful first success and move everything else later. First-success completion improved 41%.
That decision required someone who could look at a feature-rich product and say most of this is not going on the first screen. No amount of design capacity produces that. One person with judgement and standing does.
Final Thoughts: Hire the Discipline, Not the Title
The mistake underneath most bad design hires in games is treating "UI/UX designer" as one thing. It is three, and the market's habit of bundling them means you will get whichever one the candidate is best at, regardless of which one you needed.
So decide first. If your interface is ugly, hire an artist and enjoy the improvement. If it is confusing, hire a UI designer. If a number is bad and nobody can explain it, hire a UX designer, pay for seniority, and give them the authority to remove things. That last one is the hardest hire, the least legible portfolio, and by a distance the most valuable when the problem is genuinely product-shaped.
Then ask the removal question. Half an hour with your build, one question, and you will know within minutes which of the three you are talking to.
Not Sure Whether You Need a Hire or a Partner
If you have a design gap and are unsure of its shape, we can help you work that out, including the outcome where the answer is to hire rather than engage us. Wandr has designed for game creation platforms, real-money gaming products, esports tools, and character systems. See how our game UI/UX design team works, or send us the product and we will come back with what we would fix first and who should do it.
