Skip to content
Design & CreativeSenior

Senior Game Designer Resume Example

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

Senior Salary Range (US)

$150,000 - $220,000

Why This Resume Works

Verbs signaling design ownership at scale

Architected, Drove, Established, Pioneered, Designed, Built, Shipped, Mentored. Senior designers stop using verbs of execution and adopt verbs of organizational leverage.

Numbers proving live-ops, retention, and ARPDAU lift

22 million MAU, 11 percent ARPDAU lift, D30 retention 1.8 points above baseline, 240 levels over 18 months. Senior numbers should make hiring panels stop scrolling.

Live-ops outcomes tied to cohort and economy work

Not 'ran live-ops' but 'held D30 retention 1.8 points above the franchise baseline through a faction shake-up'. Senior designers connect economy and content decisions to retention curves.

Cross-team and cross-studio influence

Now adopted across 3 studio teams, used by 12 designers across the live-ops pod, mentored 4 designers with 2 promoted to senior. Seniors prove they multiply through people, not just patches.

Frameworks owned by name, not vibes

Live-ops calendar, item economy redesign, cohort balance reviews, GDD review template, playtest insight close rate KPI. Senior designers name the design systems they architect, not just the tools they use.

Essential Skills

  • 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
  • deltaDNA
  • Whale Cohort Analysis
  • Pricing A/B
  • Faction Shake-Up Design
  • Difficulty Rebanding
  • Narrative Branch Coverage

Level Up Your Resume

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 Senior Game Designer Resume

  1. Open with live-ops or economy systems you architected, not content you authored. 'Architected the live-ops calendar for a 22-million MAU mobile strategy title with content updates shipping on a 2-week cadence and ARPDAU lift of 11 percent across 3 quarters' is the senior shape.
  2. Quantify retention, ARPDAU, and cohort variance in tandem. D30 retention 1.8 points above the franchise baseline, ARPDAU lift of 14 percent on the segmented whale cohort, faction win-rate variance under 1 percent. Senior designers carry all three lenses.
  3. Show frameworks that outlived a single project. Playtest insight close rate KPI, GDD review template, cohort balance review process. Seniors author design systems, not just designs.
  4. Document mentee outcomes, not mentorship intent. 'Mentored 4 designers with 2 promoted to senior within 14 months' is the only mentorship sentence worth writing on a senior resume.
  5. Reference cross-cohort and cross-team adoption. 'Used by 12 designers across the live-ops pod' or 'now adopted across 3 studio teams' proves your work compounds beyond your immediate scope, the core senior signal.

Common Resume Mistakes for Senior Game Designer

  1. Reading as a strong mid-level IC instead of an org-shaping senior

Why it hurts: Senior CVs focused on personal level shipping or single-feature ownership without cross-team adoption, mentorship outcomes, or KPI authorship signal you have not made the leap to leverage.

How to fix: Add bullets on standards you authored, frameworks adopted by other pods, KPIs you established, and mentees you promoted. Two such bullets per role rewrite the seniority signal.

  1. No live-ops, economy, or cohort lens

Why it hurts: Senior designers in modern studios are expected to think in cohorts, calendars, and economies, even on single-player projects. CVs without this lens look mid-level no matter the years.

How to fix: Include at least one live-ops calendar, economy redesign, or cohort balance review per role with the retention or ARPDAU lift it produced.

  1. Telemetry stack missing or stuck on basic tools

Why it hurts: Senior designers without Tableau, Looker, deltaDNA, or comparable cohort-tooling references read as junior power-users of Mixpanel and nothing more. Studios filter these CVs out for live-service roles.

How to fix: Name the dashboards you built, the cohort segments you defined, and the KPI you established, with the tooling that supports each call.

Quick Resume Tips for Senior Game Designer

  1. Open each role with a system you architected. Live-ops calendar, item economy redesign, cohort balance review process.
  2. Quantify three axes per role. Retention, ARPDAU, faction balance variance.
  3. Drop a standard or KPI bullet per role. Playtest insight close rate KPI, GDD review template, cohort balance review.
  4. Document mentee outcomes. 'Mentored 4 designers with 2 promoted to senior'.
  5. Reference cross-pod adoption. Used by 12 designers across the live-ops pod, now adopted across 3 studio teams.

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.

Three artifacts: a 12-month live-ops calendar with seasonal arcs, content drop cadence, and faction-balance windows aligned with patch cycles; a cohort attribution model that segments whales, dolphins, and minnows and predicts ARPDAU response per content drop; and a playtest insight close rate KPI that catches design misses before they ship. The hardest part is admitting when content cadence has to slip to protect retention, instead of slipping retention to keep the calendar.

Recommended Certifications

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:

  • How would you architect a live-ops calendar for a 20-million MAU mobile title?
  • Walk me through an item economy redesign and the retention impact you measured
  • Describe a cohort balance review that changed your live-ops cadence
  • How do you operationalize a playtest insight close rate KPI without slowing the team?
  • Tell me about a senior-level call you made on monetization that pushed back on growth
  • How do you mentor mid-level designers through ambiguous live-service work?
Updated: