Skip to content
Design & Creative

Junior Game Designer Resume Example

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

Choose Your Level

Select experience level to see tailored resume template

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.

Switch between levels for specific recommendations

Key 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
  • Combat Systems Design
  • Faction Balance
  • Telemetry-Driven Iteration
  • Balance Patch Cadence
  • Playtest Synthesis
  • Mentorship
  • Tableau
  • Looker
  • deltaDNA
  • Mixpanel
  • Houdini-Driven Layouts
  • Substance
  • Cross-Team Standards Authorship
  • Live-Ops Calendar Design
  • Item Economy Design
  • Cohort Balance Reviews
  • ARPDAU Modeling
  • Retention Strategy
  • Cross-Pod Standards
  • Mentorship to Senior Promotions
  • GDD Review Templates
  • AppsFlyer
  • Adjust
  • Whale Cohort Analysis
  • Pricing A/B
  • Faction Shake-Up Design
  • Difficulty Rebanding
  • Narrative Branch Coverage
  • Design Org Scaling
  • Multi-Year Design Roadmaps
  • Studio Standards Authorship
  • Designer Career Ladder
  • Hiring Rubric Design
  • Promotion Calibration
  • Studio Head Partnership
  • Live-Ops Strategy
  • Director of Production Partnership
  • Budget Negotiation
  • Multi-Region Org Design
  • Designer Compensation Design
  • Cross-Project Standard Adoption
  • Board Communication
  • Industry Vertical Strategy
  • Studio Reorg Planning

Level Up Your Resume

Salary Ranges (US)

Junior
$65,000 - $95,000
Middle
$95,000 - $150,000
Senior
$150,000 - $220,000
Lead
$200,000 - $320,000

Career Progression

The game designer career arc compounds because the skill graph (design intent + iteration mechanics + telemetry literacy + cross-discipline navigation) only grows with each shipped season, balance patch, and live-ops cycle. Most strong designers reach senior in five to seven years and lead in nine to twelve, often pivoting from level design or systems design into broader live-ops or economy work, then into design lead or director-of-design roles. Common entry routes: game-jam portfolio plus modding scene, CS or humanities degree plus game-design coursework, narrative writing plus interactive scripting, or systems-engineering pivots. Studios value subspecialty depth at junior and mid level, then breadth across systems / level / combat / narrative / economy / live-ops at senior and lead.

  1. JuniorMiddle2-4 years

    Ship at least one full feature or content arc (multiplayer mode, mission set, faction kit) end-to-end with playtest and telemetry evidence. Run a sustained weekly playtest cadence with synthesized actionable changes. Author a Confluence-grade GDD that survived senior review. Translate at least one telemetry funnel into a measured design change.

    • Combat Systems Design
    • Faction Balance
    • Telemetry-Driven Iteration
    • Cross-Discipline Collaboration
  2. MiddleSenior2-4 years

    Own at least one balance-critical system end-to-end across multiple patch cycles. Lead one explicit kill on a system or content cut before launch. Author a design doc adopted as a studio template by other mission or systems designers. Influence one balance-patch cadence or content cadence at the team level. Mentor at least one junior designer to ship their own playtests with synthesis.

    • Live-Ops Calendar Design
    • Item Economy Modeling
    • Cohort Balance Reviews
    • Cross-Pod Standards Authorship
  3. SeniorLead3-5 years

    Architect a live-ops calendar or economy redesign that compounded retention or ARPDAU across multiple quarters. Establish a studio-wide KPI (playtest insight close rate, narrative branch coverage, faction win-rate variance) adopted across pods. Mentor at least one designer to senior promotion. Influence a build-vs-buy or partnership decision on telemetry or content tooling. Author or co-author a designer career ladder.

    • Design Org Scaling
    • Multi-Year Design Roadmaps
    • Studio Standards Authorship
    • Executive Partnership

Strong game designers also pivot into product management for free-to-play and live-service titles, into creative director roles at studios that fuse design lead and director-of-design, into UX research where playtest synthesis pays off directly, or into game-design consulting and executive coaching for live-ops cohorts. A common late-career move is founding an indie studio or a game-design tooling startup (paper-prototyping platforms, telemetry-to-design pipelines, narrative authoring tools).

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.

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.