Where to find a game UI/UX designer: every channel, compared

Before you start looking

Two decisions make every channel work better, and skipping them is why searches go badly.

• Know which role you need. UI artist, UX designer, or a generalist who does both. They cluster in different places, and asking for the wrong one produces a confusing shortlist. The distinction is broken down in how to hire a game UI/UX designer.
• Have a rough screen list and a budget range. Not to publish everywhere, but so you can answer instantly when someone asks. Designers deprioritise enquiries that cannot answer those two questions.

The channels at a glance

Freelance marketplaces

Upwork, Fiverr and similar platforms are where most first-time clients start, and for good reason: verifiable work history, contracts, escrow and dispute resolution built in. The trade-off is signal-to-noise, which you manage with filters rather than hope.

• Search for the specialism, not the category. "Game UI designer" and "game UX designer" return very different lists from "UI designer", which is dominated by app and web work.
• Filter on job success and earnings history first, then look at portfolios. History is the part that is hard to fake.
• Read the client feedback, not just the score. Look for repeat clients and long contracts. Both mean somebody was easy to work with.
• Invite people rather than only posting. The strongest freelancers are often busy and not scanning the board. A direct invitation with a real brief gets a much better response rate.
• Check whether the portfolio is game work. Plenty of excellent product designers list game UI because it is a searched term.

Fiverr's model is different: fixed packages you buy rather than a brief you post. That suits small, well-defined jobs, a single screen or an icon set, and suits full UI systems poorly, because the scoping conversation that a real project needs does not fit the format.

Portfolio platforms

ArtStation, Behance and Dribbble are where the work lives rather than where the hiring happens. You will find stronger visual quality here than anywhere else, and you have to do more of the work yourself.

• Search by the artefact, not the job title. "Game UI kit", "game HUD", "main menu", "inventory UI" surface people who have actually made those things.
• Look for a case study, not a gallery. A post that explains a decision tells you far more than ten that show a result.
• Check the dates. A beautiful portfolio last updated three years ago usually means they have a full-time job now.
• Approach directly and specifically. These platforms have no hiring workflow, so your first message is doing all the work. There is a template further down.

Games-industry job boards

Boards such as Hitmarker, Work With Indies and GameJobs.co, plus the community-maintained job lists that circulate in the industry, are aimed at people who work in games specifically. That focus is their strength and their limit: they are built around roles and contracts more than one-off projects.

• Best for longer engagements: a contract of several months, or a part-time ongoing role.
• Expect a slower cycle. Two to four weeks from posting to shortlist is normal.
• Your post matters more here, because it is competing with studio postings. Writing one is covered in how to write a game UI job post.
• You will reach people currently employed, which is a different and often more experienced pool than the marketplaces.

LinkedIn

Good for finding senior people with shipped credits, poor for speed. Most of the strongest candidates are working and are not actively looking, which means you are making an approach rather than filling a vacancy.

• Search job titles plus a genre or engine: "game UI designer Unity", "UX designer mobile games".
• Look at who worked on games you admire. Credits are more searchable here than anywhere else.
• Keep the first message short and specific. Long paragraphs about your vision get ignored. Project, platform, scope, budget range, timeline. Five lines.
• Expect a slow reply, and do not read silence as disinterest. It usually means busy.

Communities and Discords

Reddit communities such as r/gamedev, r/INAT and r/gameDevClassifieds, plus the many game development Discord servers, are where indies actually talk. The quality range is enormous and there is no vetting at all, which makes references and a paid test more important here than anywhere else.

1. Read the rules before posting. Most of these spaces have strict formats for paid work versus revenue-share, and posts that ignore them get removed.
2. Say the budget. In community spaces, a post without one is assumed to be unpaid or exploitative, and the good people scroll past.
3. Never post revenue-share as if it were payment. It is a legitimate arrangement between founders and an insult when offered as a fee.
4. Ask for recommendations, not just applicants. "Who have you worked with and would hire again?" is the highest-value question you can ask in a community.
5. Take the conversation to a contract quickly. Community goodwill is not a substitute for milestones and a written scope.

Referrals: the highest hit rate of any channel

Ask five developers you know who they have worked with. It takes an afternoon and produces better candidates than a week of searching, because somebody has already absorbed the risk of finding out whether that person delivers.

The reason people skip it is that they ask badly. "Do you know any UI designers?" gets a vague answer. Ask this instead:

Outsourcing studios and B2B directories

Art and UI outsourcing studios sell capacity: several people, a producer, and a process. B2B directories such as Clutch list them with verified client reviews, which is useful vetting you do not get elsewhere.

Expect higher rates, minimum engagement sizes, and a sales process before anyone designs anything. Worth it for large volume or when procurement requires a company; usually overhead for a project under about thirty screens. The full comparison is in freelance, studio, or asset store, and the money side in game development outsourcing costs.

The message that gets a reply

Whichever channel you use, the first message decides your response rate. Good designers get a lot of vague enquiries and answer the specific ones. Keep it to six lines.

1. 01

   What the game is

   One sentence, plus a link to a build, trailer or screenshots. Something to look at beats any amount of description.

2. 02

   What you need designed

   "Main menu, settings, pause, results and a HUD, around 12 screens." A rough number beats "the UI".

3. 03

   Platform and inputs

   PC, console, mobile, VR, and which inputs must be supported. This changes the work more than anything else.

4. 04

   Timeline

   The real deadline and what it is tied to. A demo, a festival, a publisher milestone.

5. 05

   Budget range

   A range is fine. Withholding it does not get a lower price, it gets a slower conversation and fewer replies.

6. 06

   Why them

   One line referencing something specific in their work. It is the difference between a message and a mass mail, and it is obvious which one you sent.

A two-week plan

1. Day 1. Write your screen list and settle a budget range. Ask five contacts the referral question.
2. Day 2. Post on one marketplace and one games job board. Do not spray.
3. Days 2 – 4. Search ArtStation and Behance for the artefacts you need, and send five specific direct messages.
4. Days 5 – 7. Shortlist three to five people on evidence: full flows, unglamorous screens, written reasoning.
5. Days 8 – 10. Short calls. Ask what they would push back on and what the smallest useful first delivery would be.
6. Days 11 – 12. One paid test task, two to four hours, at their rate, on work adjacent to yours.
7. Days 13 – 14. Agree scope, revision rounds, delivery format and file ownership in writing. Start.

Two weeks is realistic and worth protecting. The teams that regret a hire almost always compressed this into two days.