Game Design - UX Designer (Games)

What Game UX Designers Actually Do (Day-to-Day Reality)

 

In-Game: The Moment-to-Moment Stuff

When game UX designers work on in-game experiences, they’re obsessing over:

HUDs that don’t clutter.

That health bar. The minimap. Objective markers. Ammo counters. All visible, but nothing gets in the way of gameplay. It sounds simple. It’s not.

I watched a UX designer at Riot spend three weeks on where to place a champion’s passive ability indicator. Three. Weeks. Why? Because if it’s in the wrong spot, competitive players miss crucial information in 100ms moments. That’s the difference between a kill and getting destroyed.

Menus that don’t suck.

Pause menus. Inventory systems. Character sheets. Quick-access wheels. The friction here is invisible, until it ruins a session.

Feedback that makes you feel things.

When you land a hit, something should pop. Screen shake, a satisfying sound, controller rumble, all coordinated. Feels great? You keep playing. Feels janky? You’re already leaving the game.

Onboarding that doesn’t bore or overwhelm.

Teaching new players without drowning them. Progressive disclosure is the magic word here. Teach them one thing at a time, build their confidence, then layer complexity.

A game UX designer does this by constantly asking: “What’s the player thinking right now? What do they actually need to know?” Not what’s on some design doc. What’s real.

Around-Game: Everything Else

Outside actual gameplay, there’s a whole ecosystem:

Progression systems.

Battle passes. Seasonal rewards. Level-up triggers. Achievement tracking. Players spend massive time here, sometimes more time than playing. Make it feel rewarding, not like work.

The shop.

In-game cosmetics. Pricing presentation. Bundle design. This is where UX design intersects revenue. Get it wrong and players feel exploited. Get it right and they want to spend money. It’s an art.

Social features.

Friends lists. Parties. Clans. Matchmaking queues. Social friction kills games faster than bad design kills it.

Account systems.

Sign-in flows. Cross-game accounts. Save management. Boring? Yes. Matters? Absolutely. One confusing sign-up screen and you’ve lost 30% of new players.

Live service content.

Limited-time events. Seasonal drops. New features rolling in constantly. Every integration point is a potential disaster if UX design isn’t solid.

How It Shifts Through Development

Prototype stage:

Rapid wireframes. Clickable mockups. Rough sketches. Goal: “Does this concept make sense to a human?”

Pre-production:

Deep research. Player personas. Information architecture. “How do we build this thing systematically?”

Production:

Detailed wireframes. Constant playtests. Iteration loops. Handoff to UI artists who make it pretty. “Does this feel right yet?”

Post-launch/Live service:

Monitoring real player behavior. Data analysis. Updates based on actual usage. “What broke? What surprised us? What works?”

A Real Day, Not the Highlight Reel

9:15 AM:

Grab coffee. Check Slack. Three messages from programmers asking “Why did we design it this way?” They always do.

10:00 AM:

Playtest with real players. You’re watching five people struggle with the economy system. Specifically: pricing isn’t clear. Everyone’s confused at the same spot. Note it.

11:30 AM:

Sketching three different solutions. Which is clearest? Which matches the art direction? Which won’t break technically? None are perfect, all suck in different ways.

1:00 PM:

Meeting with game designer, who says, “This scope is massive,” tech lead, who says, “We can’t do that in the timeframe,” and UI artist, who says, “Can you make it fit the sci-fi aesthetic?”

You propose your three solutions. Everyone shoots them down for different reasons. Welcome to game UX design.

2:30 PM:

Building a prototype in Figma. Controller mapping so you can test if the flow feels right. Not just looks right, feels right. There’s a difference.

4:00 PM:

Analyzing player telemetry. Engagement metrics. Drop-off points. Some players are bailing at the customization screen. Why? Is it a design issue or just confusing wording? Dig deeper.

5:30 PM:

Iterating based on all the feedback and data. Tomorrow you’ll playtest it again. This loop never stops. Ever.

This isn’t theoretical work. It’s collaborative, data-driven, and real.

Skills You Need, and What Actually Matters

Tools Matter Less Than You Think

Everyone assumes technical skills are the gatekeeper. They’re really not.

Figma.

Industry standard. Learn it. Most game UX designers use controller mapping features specifically for games. But here’s the truth: Figma is just a pencil. Anyone can learn a pencil in a week.

Unity or Unreal.

Don’t code. Just understand how UI lives in these engines. What’s possible? What’s expensive? What’ll make programmers cry? Three weeks of poking around teaches you enough.

Adobe stuff.

Photoshop, Illustrator. Nice to have. Not required. A strong UX designer without these still beats someone with every tool but no thinking.

Prototyping basics.

Figma flows. Interactive prototypes. Clickable mockups. These matter more than any fancy tool.

The dirty secret? Mastering tools is easy. Thinking like a UX designer is hard. Most people get that backward.

The Soft Skills, Honestly, These Are Everything

Problem-solving that isn’t boring.

Can you approach a design problem from five angles? Can you propose three completely different solutions? Can you explain why each one has tradeoffs?

Most people propose one thing and defend it like their life depends on it. Game UX designers are comfortable throwing ideas away.

Talking to people who speak different languages.

You spend half your time explaining designs to game designers, who think systems, programmers, who think constraints, and artists, who think aesthetics. Can you translate? Can you speak their language?

A UX designer who can’t communicate designs clearly might as well not exist.

Adaptability that doesn’t break your spirit.

Features get cut. Requirements pivot. New data comes in and blows up your assumptions. Some designers grip their original concept like it’s their baby. Those people burn out or get fired.

Real game UX designers adapt without ego death.

Genuine empathy for players, not the corporate kind.

Developers live inside their game. They know every secret. A new player is lost. Can you actually imagine the experience through fresh eyes? Not “what does the UX guide say,” but what does this person actually think when they see your design?

This is harder than it sounds. Most people can’t do it.

Storytelling, not just presenting.

Showing your portfolio isn’t “here’s my case study.” It’s: “Here’s the problem players faced. Here’s why it mattered. Here’s how I thought about it. Here’s what I tried. Here’s what I learned.”

The best UX designers tell stories.

Game-Specific Knowledge, You Can’t Fake This

Game design principles.

Not design theory. Actual game loops. Progression curves. Difficulty pacing. You don’t need to design games, but you need to speak the language.

Player psychology.

Different players want different things. Achievement hunters. Explorers. Competitors. Social players. What motivates each? How do you teach? What frustrates them?

Accessibility standards.

Colorblind modes. Subtitle options. Remappable controls. Difficulty options. This isn’t a nice-to-have. Modern AAA design requires it.

Common systems.

Loot tables. Economy design. Progression mechanics. You should recognize these patterns without thinking.

How to Actually Get This Job (Not the Generic Version)

If You’re Starting From Zero

Months 1–2: Lay the Foundation

1. Take an online UX fundamentals course, such as Coursera, IDF, or CareerFoundry. Don’t overthink it. Finish it.

2. Read The Design of Everyday Things by Don Norman. One book. Seriously.

3. Play five games from different genres. While playing, don’t just vibe. Analyze. “Why’d they design that way? What sucks? What’s clever?”

Months 2–4: Get Specific

1. Learn Figma. Free tier. YouTube tutorials. Mess around. The tool matters less than understanding flow.

2. Watch GDC talks. “Intro to Game Design” from Game Maker’s Toolkit is gold.

3. Analyze three to five games from a UX lens. Write case studies. “Why This Menu System Works” or “What That Game Got Wrong.” Actually write them.

Months 4–6: Ship Something

1. Enter a game jam. Itch.io hosts monthly ones. Build something. Finish it. Even if it’s rough, you shipped.

2. Create two to three case studies analyzing real games’ UX problems. Propose solutions. Show your thinking.

3. Build a simple game concept in Figma with full UX flow. Make it feel polished in Figma.

Months 6+: Get Serious

1. Build a portfolio website. Make it sharp.

2. Join game dev Discord communities, such as IDGA Games User Research, Design Buddies, and Funsmith Club. Introduce yourself.

3. Reach out to one or two junior designers on LinkedIn. Ask for portfolio feedback. Most will ignore you. Some won’t.

4. Start applying. Junior roles. Internships. Don’t wait until you’re “ready.”

If You’re Jumping From Traditional UX

You already understand UX fundamentals. Your gap is game-specific knowledge. Close it fast.

Accelerated Path, 3–4 Months

1. Game immersion: play 10+ games seriously. Write three to five game UX case studies.

2. Game design crash course: take one course or read one book. Fill the gaps.

3. Engine literacy: spend two to three weeks exploring Unity or Unreal. Don’t learn programming. Understand UI implementation. How does UX live in these engines?

4. Portfolio evolution: take your best two to three traditional UX projects. Reframe them with game language. Add two to three game-specific projects or case studies.

5. Strategic applications: your UX background is valuable. Target studios open to career switchers. Emphasize how your cross-platform or consumer experience translates.

The advantage? You already think like a designer. You just need gaming context.

Building a Portfolio That Lands Interviews

Your portfolio is everything. Here’s what works:

One Solid Case Study

Deep dive. Show your process, not just the result.

What was the problem?

Be specific. “Players were confused” is vague. “23% of new players abandoned the game in the customization screen because...” is better.

How’d you approach it?

• Show three iterations that reveal your thinking.
• Include the final solution with reasoning.
• Add prototype screenshots.
• Explain what you learned.
• Competitive Analysis
• Pick a game’s system, such as inventory, shop, or progression.
• What works?
• What could improve?
• Create two to three redesign proposals.
• Explain why each one has tradeoffs.

Real Project

Game jam results. Personal project. Collaborative work. Anything real beats theoretical.

Accessibility Analysis

Pick a game. Propose accessibility improvements. This shows you understand inclusive design.

Portfolio Don’ts

Unfinished work, because it looks amateur.

Over-explaining obvious things.

Showing ten projects instead of three to four great ones.

Stolen credit, because studios check.

Game Jams, Why They Matter

Game jams aren’t just networking. They’re proof.

You ship things under pressure.

You iterate fast.

You collaborate with strangers.

You handle feedback.

You produce real work.

Itch.io hosts hundreds. Game Camp is a longer format with mentorship.

After a jam:

1. Document your process.

2. Write a postmortem explaining what worked and what didn’t.

3. Add it to your portfolio.

Studios see game jam projects and think: “This person actually makes things.”

Networking, How You Actually Get Hired

Your portfolio gets you an interview. Your network gets you the interview in the first place.

Discord Communities

IDGA Games User Research: industry professionals discussing UX.

Design Buddies: peer feedback and growth.

Funsmith Club: mentorship and networking.

LinkedIn Strategy

1. Follow 20–30 game UX designers at studios you admire.

2. Engage with their posts using real comments, not generic praise.

3. DM two to three per month asking for 15-minute feedback on your work.

4. Most ignore you. Some don’t. That’s fine.

Conferences and Events

GDC: expensive, but worth it for serious candidates.

Local meetups: usually free and surprisingly valuable.

Reddit, especially r/gamedev.

TIGSource forums.

Real talk: your first industry connection often leads to your first opportunity. Someone mentions you to someone. That’s hiring.

Getting Hired, The Actual Process

Landing Your First Position

Where to Look

LinkedIn Jobs

Glassdoor

GameDev.jobs

Unity Jobs

IDGA Job Board

Studio websites directly, since many only post there

Recruiters, especially those who specialize in game design

Don’t wait until you’re 100% ready. Apply at 50%.

What to Include

1. Resume: one page. Relevant skills. Mention games you’ve logged serious hours in. Yes, this matters.

2. Portfolio link: this is everything. It should be live and mobile-responsive.

3. Cover letter: three to four paragraphs. Show you understand that specific studio and that specific game.

Example:

“I’ve played 150+ hours of Valorant and noticed a specific UX opportunity around player onboarding and match preparation. That’s why I’m excited about this role. I know what strong UX design in competitive games needs to feel like.”

Tips

Customize each cover letter. Generic ones get deleted.

Apply to slightly lower-level roles if the studio is your dream.

Include portfolio URLs and GitHub if relevant.

The Interview Structure

Round 1: Recruiter Screen, 30 Minutes

Basic conversation. Timeline. Communication vibe. Usually painless.

Round 2: Design Interview, 60–90 Minutes

Often a Zoom call with a game UX designer from the team. They might ask:

“Tell me about a game you love and a UX problem in it.”

Or:

“Design a shop system for this game genre.”

You’ll share your screen. Sketch. Prototype on the fly. They’re assessing whether you can think, communicate, and understand games.

Round 3: Portfolio and Team Interview, 60 Minutes

Present your case study. Expect questions from the hiring manager.

“Why this choice?”

“What would you change?”

“How do you handle feedback?”

This is also a culture fit assessment.

Sometimes: Fourth Round With a Take-Home Design Challenge

Some studios include a take-home challenge. Keep your process clear, explain your decisions, and don’t overbuild the thing into a tiny cathedral.

Questions You’ll Get, and How to Answer

“Tell me about a game you love and one you’d redesign.”

They want proof you think critically.

Answer by picking a specific game. Name something that works brilliantly and explain why. Then pick one system you’d improve. Propose two to three alternatives with reasoning. Show process, not just conclusion.

“Design a progression system for a competitive multiplayer game.”

They want holistic thinking and player psychology.

Answer by asking clarifying questions first.

Who is the player base?

What is the business model?

What platforms are involved?

Then move through research, personas, requirements, multiple concepts, and iteration.

“Walk me through iterating on a design based on feedback.”

They want proof you handle criticism without ego death.

Answer with a real story. What was the feedback? Why was it hard? How did the design evolve? What did you learn?

Most designers fail this by sounding defensive.

“What would you do differently now?”

They want self-reflection.

Answer honestly without self-flagellation.

Example:

“My first portfolio project over-designed the customization flow. Now I’d cut 40% of the options and use progressive disclosure.”

“How’d you handle a feature being cut?”

They want realistic temperament.

Answer:

“I’d understand why, contribute to the pivot discussion, and move on. Attachment to my idea only slows the team down.”

Negotiating Your Offer

When the offer comes, you have leverage. Use it.

Areas to Negotiate

Base salary: ask for the top 15% above their initial offer. Expect to meet in the middle.

Sign-on bonus: $5k–$15k is reasonable for junior roles.

Remote work: even two to three days remote can improve life significantly.

Equity or stock: if it is a startup or smaller studio, negotiate explicitly.

Professional development budget: $1k–$2k per year for conferences and courses.

Don’t Fight Hard On

PTO, because it is usually fixed.

Health insurance, because it is often standard.

Junior job title, because accepting it can still get you into the studio.

Script

“I’m excited about this. The salary of $X is below market for this role and my experience. Based on the data I’ve seen, I’d like $X plus 15%. I’m also interested in remote flexibility and a professional development budget. What flexibility exists?”

They’ll accept, counter, or hold. Then you decide whether it’s worth it.

The Real Talk, This Job Isn’t for Everyone

The Downsides Nobody Mentions

Crunch Culture Is Real

End-of-project crunches happen. Some studios normalize 60-hour weeks. Others have healthy boundaries. Research the studio before applying. Check Glassdoor, ask current employees, and trust your gut.

High Change Rate

You design something perfect. Requirements change. Data suggests a different approach. Art direction pivots. Can you stay flexible, or does this wreck you? Real UX designers adapt without attachment.

Rapid Iteration, Never “Done”

There’s rarely a final design. You’re constantly iterating. If you want polished work that stays untouched forever, gaming isn’t for you.

Budget Constraints, Indie Reality

You’ll design amazing features that get cut. That’s normal. Sometimes it hurts.

Public Criticism

Your designs are visible. Players will hate them. You’ll read angry Reddit threads about systems you obsessed over. Thick skin required.

Job Instability

The 2023–2024 layoffs proved even AAA isn’t safe. Budget cuts happen. Projects get cancelled. Always have a backup plan.

Career Paths, Choose Your Adventure

Individual Contributor Track, Most Common

Junior to Mid-level to Senior to Lead Designer.

You own bigger projects. Mentor juniors. Influence studio vision. Stay hands-on and creative. This is the path many people love.

Management Track

Senior to UX Manager to UX Director.

This requires different skills: people management, strategy, and politics. Less design work. More bureaucracy. It can be fulfilling or soul-crushing depending on studio culture.

Specialization Track

Become an expert in live service, accessibility, or VR/AR.

Specialists command premiums. They are often more stable because fewer people have these skills.

Cross-Discipline Track

Transition to creative director, product management, your own studio, or indie work.

Creative director requires strong game design knowledge.

Product management lets you leverage your UX background.

Starting your own studio gives you control, but also risk.

Long-Term: Is This Sustainable?

Burnout risk is real. Deadline pressure plus creative criticism plus job instability creates burnout conditions. Some studios are toxic. Some are healthy.

Protect Yourself

1. Choose your studio carefully. Research the culture.

2. Set boundaries early. Sixty-hour weeks in year one won’t magically improve.

3. Diversify income through freelance work, side projects, or savings.

4. Monitor your energy. Dread is a signal.

5. Know your limits. You can crunch for a launch, not indefinitely.

6. Invest in transferable skills. They make you valuable across industries.

Is it sustainable long-term? Yes, if you’re intentional about studio choice and boundaries. Some designers have 15+ year careers. Some burn out in three. The difference is usually self-protection, not talent.

Real Questions People Ask, Honest Answers

Do I Actually Need a Degree?

No.

Most game UX designers have degrees, but plenty don’t. What matters is demonstrated skill and results. A strong portfolio beats credentials.

If you have time, a degree provides structure and networking.

If you’re in a hurry, self-teach, build a portfolio, and ship real work. You may have less credential advantage, but a stellar portfolio can outweigh that.

Is Game UX Actually in Demand?

Honest answer: it’s recovering, not booming.

In 2024, UX design postings grew 15% from post-layoff lows. Competition is moderate. Doable, but not easy.

Highest Demand

Live service games, because they always need iteration.

Mobile gaming, because it is growing.

AAA studios, because they are selective but still hiring.

VR/AR companies, because they need specialists.

Lower Demand

Indie studios, because they rarely hire dedicated UX.

Declining franchises, because there are fewer jobs.

Bottom line: you can get hired. It requires hustle, but the job exists.

Timeline: How Long Until Employment?

From zero to first offer: typically four to twelve months.

Speed Factors

Existing UX experience can cut the timeline to three to four months.

A strong portfolio can make it three to six months.

Solid networking can shorten the path to two to three months if you are connected.

Slow Factors

Complete beginner with no portfolio: six to twelve months.

Unrealistic salary expectations: twelve or more months.

Geographic or visa constraints: longer timeline.

Reality: some get hired in two months. Some take eighteen. The average is six to nine months.

Should I Learn Unity or Unreal?

Do you need to? No.

Should you? Yes, for competitiveness.

Which one? Unity is more accessible. Unreal is more powerful. Learning UI implementation in either one shows initiative and makes you more hireable.

Time investment: three to four weeks to understand UI basics. Not months.

What If I Have Zero Design Background?

Good news: absolutely doable.

Bad news: it takes longer than it would for someone with a design foundation.

Path

1. UX fundamentals through an online course, four to six weeks.

2. Game-specific knowledge through game study, two to three months.

3. Portfolio projects, three to six months.

Total timeline: five to nine months, compared to three to four months for experienced designers.

You’re not behind. You’re starting further back. Many successful designers took exactly this path.

Your Next Move, Start Today

You’ve read this far. That puts you ahead of 90% of casual browser traffic.

Next 48 Hours

Today, Next Two Hours

1. Play a game you love for 30 minutes. Find one moment where the UX was confusing or frustrating. Write it down.

2. Join a community. Discord. IDGA Games User Research or Design Buddies. Introduce yourself.

This Week

1. Decide: casual learning or serious? If serious, block eight to ten hours per week for six months.

2. Take one free UX course. Interaction Design Foundation has solid free content.

3. Download one game from each genre: RPG, FPS, puzzle, and strategy. Play one to two hours each.

This Month

1. Learn Figma through five to six YouTube tutorials. Mess around.

2. Write your first analysis: 500 words on one game system. Post it for feedback.

3. Research game jams starting in two to three months. Mark your calendar.

Next Three Months

1. Participate in a game jam.

2. Create two to three portfolio case studies.

3. Build a portfolio website.

4. Connect with five game UX designers on LinkedIn.

Months 4–6

1. Create two to three more portfolio projects.

2. Start applying to junior or intern roles.

3. Attend one game dev event.

4. Deepen your early connections.

The point: you don’t need to know everything. Start moving. Each step reveals the next one.