Home >> Video Games

Qualifications for a Video Game Designer

There is no single mandatory degree or license to become a video game designer. Hiring is portfolio- and skill-based. However, studios consistently look for the following competencies.

Core Competencies (Must Demonstrate)

Area	What to Show
Systems Design	Rule sets, economies, progression, combat formulas, balance spreadsheets. Document a system you designed + iteration logic.
Level / Mission Design	Graybox layouts, pacing charts, encounter design, player guidance (affordances, signposting). Playable Unity/Unreal/Godot level.
Narrative / World Design	Quest chains, branching dialogue, lore bibles, environmental storytelling examples.
Player Psychology / UX	Onboarding flows, difficulty curves, feedback loops, retention mechanics. Usability test notes.
Technical Literacy	Scripting (C#, Lua, Blueprint, Python), version control (Git/Perforce), engine debugging, profiling. You don't code full features, but you implement/tune your designs.
Communication	Design docs (one-pagers, RFCs), Confluence/Notion wikis, pitch decks, postmortems. Clear, concise, visual.

Typical Educational Backgrounds

Bachelor's: Game Design, Computer Science, Interactive Media, HCI, Psychology, Fine Arts, Architecture. Major matters less than projects.
Specialized Programs: DigiPen, SMU Guildhall, USC Games, CMU ETC, NYU Game Center, Abertay, Breda, Cologne Game Lab — strong industry pipelines.
Self-Taught / Bootcamps: Common. Requires exceptional portfolio to compensate for no degree (visa issues for international roles).

Experience That Counts

Shipped Games: Mods, game jam entries (Global Game Jam, Ludum Dare), itch.io releases, mobile apps, student capstones. Finished > Polished.
QA / Playtest / Community Management: Entry points. Teaches production reality, bug reporting, player feedback loops.
Tools / Pipeline Work: Building design tools (Excel → JSON, Unity Editor scripts, Unreal Data Tables) shows technical chops.

Specializations (Pick One to Deepen)

Systems/Combat Designer — Math-heavy, spreadsheets, balance.
Level Designer — Spatial, pacing, scripting encounters.
Narrative Designer — Writing, branching, localization pipeline.
UI/UX Designer — Flow, accessibility, HUD, menus.
Economy / Live Ops Designer — F2P metrics, events, monetization ethics.
Technical Designer — Bridge design ↔ engineering; implements own systems.

Portfolio Essentials

3–5 complete, playable projects (WebGL, Windows build, video + context).
For each: Problem → Constraints → Solution → Iteration → Result (metrics if any).
Link source / design docs / postmortem.
Host on personal site / GitHub / itch.io / ArtStation.

Soft Skills That Get You Hired

Receiving Feedback: "Kill your darlings" — iterate, don't defend.
Cross-Discipline Empathy: Understand artist pipeline, engineer constraints, producer schedules.
Scrum / Agile Fluency: Jira, sprint planning, retrospectives.
Passion ≠ Fanboyism: Analyze games critically (mechanics, not just "fun").

Reality Check

Junior roles are scarce. Many start in QA, production, or adjacent tech.
Crunch exists. Unionize / choose studios with sustainable culture.
Lifelong learning. Engines, platforms, player expectations shift every 2–3 years.

Build small, finish often, document process, apply broadly. The portfolio is the qualification.

Video Games