Skip to content
Design & CreativeJunior

Junior Game Designer Resume Example

Professional Junior Game Designer resume example. Get hired faster with our ATS-optimized template.

JuniorMiddleSeniorLead

Junior Salary Range (US)

$65,000 - $95,000

Why This Resume Works

Strong verbs open every bullet

Designed, Authored, Ran, Shipped, Translated. Even at junior level, your verbs must show you drove design decisions, not just took notes during playtests.

Numbers tied to playtest and telemetry, not vibes

D1 retention 2.1 points above the seasonal cohort baseline, 31 actionable layout changes, 18 percent session-length lift. Junior designers who quantify playtest output separate themselves from juniors who just attended sessions.

Outcomes connect design intent to player behavior

Not 'designed levels' but 'lifted average session length on the affected levels by 18 percent'. Recruiters need to see that your design choices moved a metric, not just shipped to gold.

Cross-discipline collaboration even as junior

Senior level designer, narrative lead, telemetry analyst. Junior designers who name the partners around them get pulled into bigger design loops faster than those who write in 'I' alone.

Real design tools, not buzzwords

Unreal Editor with Blueprints scripting, Roblox Studio with Lua, Twine, Amplitude funnels, Confluence GDDs. Naming the actual design tooling proves you have hands on the right surface, not just a syllabus.

Essential Skills

  • Level Design
  • Encounter Pacing
  • GDD Authoring
  • Playtest Facilitation
  • MDA Framework
  • Paper Prototyping
  • Unreal Editor
  • Blueprints Scripting
  • Roblox Studio
  • Lua Scripting
  • Unity Editor
  • Twine
  • Articy:Draft
  • Amplitude
  • GameAnalytics
  • Confluence

Level Up Your Resume

Get Roasted

Brutal AI feedback on your resume

Roast My Resume →

Tailored Resume & Cover Letter

Customize for specific job postings

Tailor My Resume →

AI Resume Builder

Edit with AI suggestions

Open dashboard →

Game designer resume templates and examples for every career stage. Whether you are running your first weekly playtest as a junior level designer, owning combat balance for a live-service shooter at mid-level, architecting a live-ops calendar for a 20-million MAU mobile title at senior level, or leading a 20-designer studio org at lead level, your resume must prove you turn design intent into measurable player outcomes. Hiring managers at Riot, Bungie, Naughty Dog, Insomniac, Supercell, King, Niantic, Roblox, Larian, Blizzard, Ubisoft, Mediatonic and the Russian studios behind Pixonic, Playrix, MyTona, Owlcat, and Saber Interactive scan for shipped levels with playtest evidence, balance work tied to win-rate variance, retention deltas vs cohort baseline, ARPDAU lift on live-service work, and content-update velocity. This guide covers junior level designer through design lead resume strategies with real engines (Unreal, Unity, Roblox Studio), real telemetry stacks (Tableau, Looker, Amplitude, deltaDNA, GameAnalytics), and real frameworks (MDA, GDD authoring, paper prototyping, faction balance, item economy). Game design is not game development, the role owns design intent and iteration based on playtest plus telemetry, not engine code.

Best Practices for Junior Game Designer Resume

  1. Open every bullet with a design action plus a player outcome. Replace 'designed levels' with 'shipped 4 multiplayer party-game levels with D1 retention 2.1 points above the seasonal cohort baseline'. Junior designers who attach metric deltas to their work separate from juniors who only attended sessions.
  2. Quantify playtest output, not playtest attendance. Number of attendees per session, actionable layout changes captured per milestone, telemetry funnels translated into geometry edits. The bar is the synthesis you delivered, not the meetings you sat in.
  3. Show real design tooling, not buzzwords. Unreal Editor with Blueprints scripting, Roblox Studio with Lua, Twine narrative branches, Articy:Draft graphs, Confluence GDDs, Amplitude funnels. Naming the actual surface proves you are hands-on, not coursework-deep.
  4. Reference the senior or lead you partnered with. 'Reviewed alongside the senior level designer' or 'co-designed with the narrative lead' lands harder than first-person solo phrasing and signals you understand the design discipline pipeline.
  5. Lead with shipped or playable artifacts, not coursework. A Roblox map with 240k plays, a game-jam Twine narrative with 12 endings, a personal Unreal level with a public build link beat any GPA bullet at the top of a junior CV.

Common Resume Mistakes for Junior Game Designer

  1. 'Designed levels' or 'created content' without metric or playtest reference

Why it hurts: Generic phrasing tells recruiters nothing about your judgment, intent, or how design decisions landed with players. Junior designers who write this way look interchangeable with anyone who took a game-design elective.

How to fix: Re-frame each bullet as 'design action plus playtest synthesis plus measured outcome'. Pin a number on retention, session length, or actionable changes captured.

  1. 'Used Unity' or 'used Unreal' without a system or pipeline reference

Why it hurts: Tool-only mentions read like a tutorial completion list. The role expects you to use Unreal Editor with Blueprints scripting or Unity Editor with ScriptableObjects to ship something measurable.

How to fix: Pair each tool with the system you authored on it (encounter pacing layout, branching dialogue tree, faction balance spreadsheet) and the player metric it moved.

  1. No reference to playtest cadence or telemetry

Why it hurts: Game design is iterative. A junior CV without weekly playtest evidence or any telemetry tool reference looks like a writer or wireframer who never closed a feedback loop.

How to fix: Anchor at least one bullet with playtest cadence (weekly, biweekly, attendees per session) and one with a telemetry tool (Amplitude, GameAnalytics, Mixpanel) translated into a design change.

Quick Resume Tips for Junior Game Designer

  1. Lead with shipped or playable artifacts. A Roblox map with public play count, a Twine narrative with branch count, an Unreal level with a build link.
  2. Pin a number to every bullet. D1 retention vs cohort, attendees per playtest, layout changes captured per milestone.
  3. Use the with-whom format for collaboration. 'Reviewed alongside the senior level designer' lands harder than 'helped a team'.
  4. Pair every tool with a system you built on it. Unreal Editor with Blueprints scripting plus encounter pacing, Roblox Studio with Lua plus modular hazard kits.
  5. Show one weekly playtest cadence. Weekly playtest with attendees per session and actionable changes captured proves you closed feedback loops.

Frequently Asked Questions

A game developer is the engineer who writes the code that makes the game run: gameplay programmers, engine programmers, network programmers, tools programmers. A game designer owns the design intent and the iteration loop: what the player does, why it feels good, how systems balance, what the level pacing looks like, how the live-ops calendar plays. Designers work in Unreal Editor with Blueprints scripting, Unity Editor with ScriptableObjects, Roblox Studio with Lua, plus Twine, Articy:Draft, Confluence, and a telemetry stack like Tableau, Amplitude, or deltaDNA. They are graded on retention deltas, ARPDAU lift, win-rate variance, and content-update velocity, not on lines of C++ shipped.

Common subspecialties: level designer (geometry, encounter pacing), systems designer (combat math, ability kits, faction balance), combat designer (combat feel, hit reactions, ability tuning), narrative designer (branching dialogue, quest structure, faction reputation), economy designer (item rarity curves, ARPDAU modeling, whale cohort tuning), live-ops designer (seasonal content cadence, calendar design, cohort balance reviews), mission designer (objective design, mission pacing). Most resumes anchor to one or two of these and show fluency in the rest. Senior and lead resumes show subspecialty breadth via the standards they authored across them.

Lead with D1, D7, and D30 retention deltas vs cohort baseline, ARPDAU lift on live-service work, faction or class win-rate variance for balance work, average mission completion rate or session length lift for level work, content-update velocity (levels per quarter, balance patches per cycle), and playtest insight close rate (actionable changes captured per session). Pair them with one team metric (designers mentored, designers promoted) at senior and lead level. Five to seven numbers across these axes outperform any wall of prose.

Yes, but in scripting tools, not in production C++. The bar is fluency in Unreal Blueprints scripting, Unity ScriptableObjects, Roblox Lua, and ideally enough Python to wrangle telemetry pulls or balance simulations. Narrative designers write Twine and Articy:Draft graphs. Systems designers maintain spreadsheets in Google Sheets and balance simulations in Python or in-engine. Designers who refuse any scripting fall behind, designers who write production-quality C++ have likely picked the wrong role and would be happier as gameplay engineers.

One end-to-end design artifact: a Confluence-grade GDD for a multiplayer level or single-player encounter, a playable build (Unreal, Unity, or Roblox) with a public link, a one-page playtest report covering attendees, actionable changes captured, and a metric you moved (D1 retention, session length, completion rate), and a short telemetry funnel translation showing how Amplitude or GameAnalytics data led to a geometry or pacing edit. That artifact signals all four junior muscles in twenty minutes of review.

Yes, and most strong junior designers come through a mix of CS or humanities degree, game-jam shipping, modding scene experience (Roblox, Source, GMod, Dota Workshop), and a portfolio with weekly playtest evidence. Backgrounds that convert well: software engineering (especially with scripting and telemetry comfort), narrative writing, systems thinking domains like operations research, and tabletop game design. The bar is shipped artifacts and playtest evidence, not the school name.

Recommended Certifications

Unreal Authorized Instructor

Epic Games

junior

Unity Certified Programmer

Unity Technologies

junior

GDC Vault Subscription (Design Track)

Game Developers Conference

junior

Interview Preparation

Game designer loops blend a portfolio walkthrough with three discipline-specific stations: a take-home design test (write a one-page GDD or balance proposal for a fictional level, faction, or live-ops drop), a live whiteboard or scripting exercise (sketch combat encounter pacing, faction balance spreadsheet, or branching narrative graph), and a playtest synthesis role-play where you defend a design call against pushback from a simulated lead or producer. Senior loops add a live-ops calendar review and a cohort balance memo. Lead loops add a design org structure conversation and an executive partnership simulation.

Common Questions

Common questions:

  • Walk me through a level you shipped and the playtest change that improved it most
  • Sketch encounter pacing for a 3-minute multiplayer round on a whiteboard
  • How did you translate Amplitude or GameAnalytics data into a layout edit?
  • Tell me about a Confluence GDD you authored and the lead feedback you absorbed
  • What is your weekly playtest cadence and how do you synthesize 12 attendees into actionable changes?
  • Describe the moment your design intent collided with a player behavior and how you adjusted
Updated:
Use this template