Middle Game Designer Resume Example
Professional Middle Game Designer resume example. Get hired faster with our ATS-optimized template.
Middle Salary Range (US)
$95,000 - $150,000
Why This Resume Works
Verbs that prove you own design end-to-end
Designed, Killed, Led, Shipped, Authored, Mentored, Translated. Mid-level designers drive intent and iteration, not just author docs. Your verbs should show you closed loops, not opened tickets.
Metrics tied to retention, balance, and shipping cadence
0.4 percent win-rate variance, 12 levels in 9 months, 47 actionable changes per quarter. Mid-level designers who lead with these numbers get senior-loop interviews.
Design choices linked to player and team outcomes
Not 'balanced abilities' but 'killed grenade-spam meta in MP via a single cooldown change with 0.4 percent win-rate variance'. The cause-and-effect format proves you understand what design buys.
Ownership beyond your own backlog
Mentored 2 designers, led the combat playtest cadence, co-authored faction balance spreadsheets with the lead systems designer. Mid-level is where ownership stops being a single bullet and becomes a habit.
Frameworks and telemetry stack named explicitly
Tableau dashboards, Amplitude funnels, Looker session-length data, Houdini-driven layouts, MDA framework. At mid-level, recruiters look for fluency in the working surface, not the abstract one.
Essential Skills
- Combat Systems Design
- Faction Balance
- Telemetry-Driven Iteration
- Balance Patch Cadence
- Playtest Synthesis
- GDD Authoring
- Mentorship
- Tableau
- Looker
- Amplitude
- deltaDNA
- Mixpanel
- Houdini-Driven Layouts
- Substance
- Articy:Draft
- Cross-Team Standards Authorship
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 Game Designer Resume
- Lead each role with a balance or retention metric, not a content count. 'Killed grenade-spam meta in MP via a single cooldown change with 0.4 percent win-rate variance across 3 patches' beats 'balanced abilities'. Mid-level designers prove judgment, not throughput.
- Show one explicit balance call or kill per role. A meta you killed, a system you cut before launch, a content cadence you defended. The kill clause is the seniority signal that separates mid from senior-IC.
- Quantify across three lenses: shipping cadence, balance variance, retention. Shipped 12 levels in 9 months, win-rate variance held under 1.2 percent across PvP modes, average mission completion rate up 9 percent after pacing edits. Three lens metrics outperform any wall of prose.
- Name the telemetry stack you actually use. Tableau dashboards, Looker session-length data, Amplitude funnels, deltaDNA event tracking. Recruiters at Riot, Bungie, and Supercell read tooling specifics as proof you can plug in on day one.
- Mention mentorship and cross-team adoption, not just personal output. 'Mentored 2 junior designers' and 'design doc adopted by 3 mission designers as the studio combat template' show you operate beyond your own backlog.
Common Resume Mistakes for Game Designer
- No explicit balance call or PoC kill
Why it hurts: Mid-level designers who only ship features without showing one balance decision or system they cut read as senior-junior, not mid. Riot, Bungie, and Supercell hiring panels read kill discipline as the seniority signal.
How to fix: Pick one meta you killed via a balance change, one system you cut before launch, or one content cadence you defended against scope creep, and document it with the criterion that triggered the call.
- 'Used Unity' or 'used Unreal' as a skills-list bullet
Why it hurts: At mid-level, listing the engine without naming the system you authored on it signals you ride along on someone else's design. The bar is naming faction balance spreadsheets, ECS-style ScriptableObjects, Blueprints behavior trees, or whatever you actually shaped.
How to fix: Replace 'used Unity' with 'authored faction balance spreadsheets in Google Sheets and ScriptableObjects in Unity for a roster of 12 abilities'.
- No retention or ARPDAU lens, only shipping count
Why it hurts: Mid-level CVs that count levels shipped or features delivered without retention or ARPDAU deltas read as production-tracking, not design judgment. Hiring managers downgrade them in calibration.
How to fix: Add at least one bullet per role tying your design output to a retention or ARPDAU number against a baseline. Even rough deltas beat raw counts.
Quick Resume Tips for Game Designer
- Open each role with a balance or retention metric. Win-rate variance, mission completion rate, retention delta vs baseline.
- Show one explicit kill per role. A meta you killed, a system you cut, a content cadence you defended.
- Quantify across three lenses. Shipping cadence, balance variance, retention or ARPDAU.
- Name the telemetry stack. Tableau, Looker, Amplitude, deltaDNA, GameAnalytics.
- Reference cross-team adoption. Design doc adopted by 3 mission designers, Confluence templates picked up by encounter team.
Frequently Asked Questions
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:
- Describe a meta you killed via a balance change and the win-rate variance before and after
- Walk me through a combat encounter design doc that became a studio template
- How do you decide when to cut a system before launch vs ship and patch?
- Tell me about a time you mentored a junior designer through their first balance call
- How do you partner with combat or systems engineers without designing in their lane?
- Describe a content cadence you defended against scope creep and the trade you negotiated