20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You'll split time between hands-on design and meetings. Mornings often review playtest notes, log bugs in Atlassian JIRA, and sketch level layouts in Adobe Photoshop or Illustrator. Afternoon work usually means building a small gameplay prototype in C# or JavaScript, or writing/update design documentation and XML/HTML specs.
You frequently touch production: talk with artists about visual style, sync with engineers about systems in Git, and iterate based on team feedback. Days vary by milestone—more prototyping near early stages, more polish and balancing near release.
Start with tools you’ll actually use: learn Git for version control, Atlassian JIRA for task tracking, and either C# (common in Unity) or JavaScript (for web or tools). Also practice Adobe Photoshop and Illustrator for quick mockups and communicating with artists.
Learn to write clear design specs in HTML or XML templates your team uses. You don’t need expert art skills, but being able to produce assets or mockups saves time and shows you can collaborate.
Use AI for fast idea generation—plot beats, item names, or rough dialogue—but always review and edit. Treat AI output as a draft, not final. Check for originality and avoid directly copying protected text.
Keep design documentation accurate: mark AI-assisted sections, confirm technical feasibility with engineers (C#/JavaScript), and run playtests to catch tone or mechanical problems. Never let AI replace stakeholder sign-off on features or monetization.
U.S. Bureau of Labor Statistics (BLS) reports for related jobs: about 113,330 employed with a median wage of $104,000 per year. The lowest tenth earn around $53,750 and the top tenth about $201,550, per BLS 2025 data.
Actual pay depends on studio size, location, and role seniority. Indie studios often pay less but may give more creative control; major studios usually pay toward the higher end and expect strong technical skills and longer production commitments.
A design strategist sits between high-level vision and practical systems: you shape the overall concept, narrative, and core mechanics, but also write specs and prototypes. Game designers focus more on specific features or levels; product managers focus on metrics, live ops, and business targets.
In practice you’ll do both creative design (level layouts, storylines, balance) and technical coordination (Git, C#/JavaScript prototypes, XML/HTML specs), and work closely with artists and producers to fulfill the game vision.
Show a small playable prototype (Unity/C# or web/JavaScript) that demonstrates a core mechanic and balancing notes from playtests. Include level layouts in Photoshop/Illustrator, sample design docs or XML/HTML specs, and JIRA-style task breakdowns.
Also show collaboration: screenshots of Git commits, links to shared assets, or notes about how you incorporated feedback from artists and engineers. Employers want concrete examples of systems you designed and iterated on.
Writing clear, actionable design documentation. You’ll constantly hand specs to engineers (C#/JavaScript) and artists (Photoshop/Illustrator). Poorly written specs cause rework and missed vision.
Good docs include exact mechanics, variables to balance, mockups (HTML/XML if used), and test steps. Combine that with regular playtesting and JIRA-tracked changes so the team can implement your vision reliably.