21 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You usually start by reviewing JIRA tickets and the level design board, then open the game editor to tweak a level or prototype a mechanic in C# or JavaScript. Expect cycles of building geometry, placing enemies/objects, and running a 20–30 minute playtest to check pacing and balance.
Afternoon is meetings: sync with artists about textures in Photoshop/Illustrator, coordinate with gameplay programmers via Git, and update the design spec or XML/HTML UI mockups. End by logging results in JIRA and writing notes for the next iteration.
You’ll commonly use a game editor (Unreal, Unity) plus text/code editors for C#, JavaScript, XML and HTML for UI or menu work. Source control like Git is used daily to save scenes and scripts.
For art and documentation you’ll see Adobe Photoshop and Illustrator files, and JIRA for task tracking. Design documents often live as simple markdown, XML, or shared docs linked from JIRA.
Use AI for small, explicit tasks: generate level layout ideas, write drafts of dialogue, or produce placeholder textures. Always mark AI output as draft, review it yourself, and get artist or narrative sign-off before it goes into the game.
Never let AI change code, push to Git, or alter the live level without a human code review. Keep original sources and document where AI was used in the design notes and JIRA tasks.
The Bureau of Labor Statistics reports 113,330 people employed in related occupations, with a median wage of $104,000 per year. The lowest tenth earn about $53,750 and the top tenth about $201,550, per BLS data.
Expect pay to vary by studio size, location, and your role (junior vs. lead). Big-city AAA studios usually pay above the median; indies often pay less but may offer other benefits.
Learn a game engine (Unity or Unreal) and make small levels—focus on player flow, challenge placement, and pacing. Practice scripting simple mechanics in C# (Unity) or Blueprints/C++ (Unreal) and learn Git for version control.
Build a small portfolio of 3 playable levels with notes: design goals, what you tested, and what you changed. Include screenshots from Photoshop/Illustrator for any UI mockups and link to a short design doc.
A level designer focuses on play spaces: layout, enemy placement, pacing, and how the player experiences a level. They script gameplay and balance encounters and often write the level’s part of the design document.
Game designers set core mechanics and systems (global rules, economy, combat). Environment artists create the visual assets and materials in tools like Photoshop and Illustrator. Level designers sit between both: they need design sense and some scripting skills.
Playtesting and iterating: run short, focused playtests and change only one thing per test. Collect quantitative (time to objective, deaths) and qualitative (player comments) data, then update the level and retest.
This skill ties to many tasks: balancing gameplay, documenting changes in JIRA, and communicating results to artists and programmers so the next build improves predictably.