A game developer resume has one feature that almost no other engineering resume requires: a portfolio link in the header. Studios make a yes-or-no portfolio decision before reading the rest. If you do not have a playable build, a Steam page, an itch.io link, or a YouTube demo, the resume is weaker regardless of the engine list you include.
Beyond the portfolio, game developer resumes differ from general software engineering resumes in how you quantify impact. "Improved performance" means nothing in a games context. "Reduced average frame time from 22ms to 14ms on mid-tier mobile hardware, enabling launch on the $150 Android tier" is the level of specificity studios expect.
TL;DR
- Portfolio link in the header, above experience. This is not optional for most studio roles.
- Quantify with game-specific metrics: frame time, memory budget, DAU, Day 7 retention, crash-free session rate. Not "improved performance."
- Engine specialization matters. Unity + C# and Unreal + C++ are different skill sets. Generalist framing weakens applications for senior roles.
- Live service experience (LiveOps, A/B testing, patch cadence) is a separate signal from single-player game development. List it explicitly if you have it.
How should a game developer structure their resume?
Header and portfolio
Name, email, LinkedIn, and portfolio link on the same line or immediately below your name. The portfolio link should go to a page that loads quickly and shows playable or watchable projects. If you have a GitHub with relevant game dev repositories (custom renderer, physics system, engine tools), add that link too.
For senior roles at AA or AAA studios, a portfolio without shipped titles weakens the application. "Shipped" means available to the public, not a game jam prototype that is no longer accessible.
Summary (optional but useful for specialization signals)
One to two sentences. Use this to signal your specialization: client-side rendering engineer, gameplay engineer, engine tools programmer, multiplayer systems engineer, live service engineer. Studios hire for specific slots, not generalists. If your background is primarily Unity mobile, your summary should say so.
Experience section: metrics that matter to studios
Game developer impact is measured in ways that are different from most enterprise software:
Performance metrics:
- Frame time in milliseconds on specific hardware targets (low-end Android, PlayStation 5, Nintendo Switch)
- Draw call count, overdraw rate, batch count before and after optimization
- Load time reduction in seconds
- Memory budget: heap allocation, texture memory, audio streaming footprint
Product metrics:
- DAU (daily active users), MAU (monthly active users): relevant for mobile and live service games
- Day 1, Day 7, Day 30 retention rates: standard LiveOps KPIs
- Crash-free session rate from crash reporting (Firebase Crashlytics, Datadog, Sentry)
- App store rating change after a patch
Shipping milestones:
- Platform certification (PlayStation, Xbox, Nintendo, Steam, Apple App Store, Google Play)
- Time from feature complete to release candidate
- Post-launch patch cadence
Example bullet before and after:
Before: "Optimized rendering pipeline for better performance on mobile devices."
After: "Reduced average draw calls per frame from 340 to 120 on a mid-range Snapdragon 660 device, achieving stable 60fps on the target Android hardware tier for a 2M DAU mobile title."
Engine and toolchain section
List your primary engine with the language: Unity (C#), Unreal Engine (C++), Godot (GDScript/C#), or custom engine. Secondary engines belong on the same line. Do not pad this list with engines you have opened once.
For Unreal: specify whether your work was Blueprint-heavy or native C++. These signal different roles. Blueprint-heavy experience is more common in designer-facing tools work or gameplay scripting; native C++ experience signals engine systems, performance work, or core gameplay code.
For Unity: specify whether your mobile builds used IL2CPP, and whether you have addressed garbage collection patterns (object pooling, reducing allocations in the main loop). For 2D vs. 3D, list both if relevant.
Toolchain items worth listing:
- Profiling tools: PIX, RenderDoc, Xcode Instruments, Unity Profiler, Unreal Insights
- Source control: Perforce (standard at larger studios), Git + LFS
- Build pipeline: Jenkins, Fastlane, Unity Cloud Build, Unreal Turnkey
- Crash and analytics: Firebase, GameAnalytics, Amplitude, Sentry
Industry perspective
"According to Newzoo's 2024 Global Games Market Report, mobile gaming accounts for approximately 49% of total global game revenue, a market shift that has driven sustained demand for engineers with expertise in optimization for memory-constrained hardware, battery life management, and cross-platform rendering."
— Newzoo 2024 Global Games Market Report
The implication for your resume: mobile optimization experience is not a niche qualification. It is relevant to nearly half the commercial game development market.
What game developer specializations should be listed separately?
Gameplay engineer vs. engine engineer
These are different roles with different resume signals. A gameplay engineer resume should emphasize game systems, player-facing features, and working within an existing engine. An engine engineer resume should emphasize renderer work, custom systems below the engine abstraction layer, and performance tools.
Mixing both on the same resume with equal weight dilutes the signal for both.
LiveOps and live service experience
If you have worked on a live service title (the game ran post-launch with ongoing content updates, seasonal events, and A/B tested monetization), this is a distinct and in-demand specialization. Live service work involves systems that non-live-service games do not: config-driven feature flags, server-side economy balancing, event scheduling, push notification funnels, and hotfix deployment without breaking live sessions.
State this explicitly: "Live service mobile title, 4M MAU, operational for 3+ years." This is not evident from listing "Unity" and "Firebase" without context.
Tools programmer
Tools programmers at studios build editor extensions, pipeline automation, and custom asset workflows: work that is almost entirely invisible to players but critical to production velocity. If this is your primary role, your resume should emphasize the tools you built (custom importers, procedural generation tools, animation rig editors, level validation scripts) and the team impact: "Reduced level artist export time from 12 minutes to 45 seconds."
What to leave off a game developer resume
Jam projects as primary experience: Game jam work can supplement a portfolio but should not be the top entries in your experience section for a studio role. Jams are one to seven days of work; studios hire for sustained shipped-product judgment.
Engine version numbers: Listing "Unity 2019.4" signals an outdated project. If a project was built on an older version, omit the version number unless you are specifically discussing migration work.
Non-games software experience at the top: If you have five years of enterprise software experience and two years of game development, put the game development first and adjust your summary. Studios screen for games context in the first pass.
Every language you have ever touched: C# and C++ for your target engine. Python or Lua if you have used them for game scripting or tooling. Everything else is noise unless the JD specifically asks for it.
Key takeaways
A portfolio link in the header is non-negotiable for most studio roles
Studios make a portfolio decision before reading experience. A link that goes to playable builds, video demos, or shipped product pages (not a private GitHub with unrunnable projects) is required for senior and mid-level applications.
Frame time, memory budget, and DAU replace "improved performance"
The metrics that matter to game developers are hardware-specific performance numbers, platform certification milestones, and live service KPIs. "Reduced frame time from 22ms to 14ms on mid-tier mobile hardware" is a specific claim a technical interviewer can probe. "Improved performance" is not.
Engine specialization matters more than breadth at senior levels
Unity + C# mobile and Unreal + C++ console are different career tracks. Generalist framing weakens a senior application. Pick your primary engine, state the depth (did you modify engine source code? did you write custom render pipeline code?), and only add secondary engines if genuinely relevant to the role you are applying for.
Live service experience is a separate qualification that should be stated explicitly
A live service mobile title with 4M MAU and three years of post-launch operations is a different engineering context from a single-player game shipped once. Studios with live service products screen for this experience specifically. It does not emerge from listing "Unity" and "Firebase" without context.
Frequently asked questions
Should a game developer resume include all personal projects?
Include personal projects if they demonstrate a skill not present in your professional experience, or if your professional experience is thin. A personal project with a live Steam page, App Store listing, or itch.io builds that players have downloaded is worth including. A prototype that never launched is worth including only if you can describe a specific technical problem it solved in depth.
Do I need a separate game developer portfolio if I have a GitHub?
Yes, for most studio roles. GitHub repositories contain code. A portfolio shows you can ship something that runs and is engaging to use. These are different signals. Your portfolio should have playable or watchable builds. Your GitHub can be linked separately as a code signal. Both links belong in the resume header.
How long should a game developer resume be?
One page for 0-8 years of experience. Two pages for senior engineers with deep specializations (rendering, networking, custom engine work) where a second page is needed to cover shipped titles adequately. A two-page resume that could be reduced to one without losing meaningful content signals poor editing judgment.
What is the difference between a gameplay engineer and a graphics engineer resume?
A gameplay engineer resume emphasizes game systems, player-facing feature work, tool use within an existing engine, and collaboration with designers. Metrics are player-facing: retention, session length, crash-free rate. A graphics engineer resume emphasizes renderer work, shader development, draw call optimization, platform-specific rendering constraints, and profiling tools. Metrics are technical: frame time, draw calls, GPU memory. Both are valid specializations; the resume signals for each are distinct.
Should I apply to game studios with a resume built for general software engineering roles?
Only if the specific role is a general software engineering function within a studio (DevOps, data engineering, backend infrastructure). For client-facing game engineering roles, game-specific framing (engine, platform, game-specific metrics, portfolio) is necessary. A resume optimized for fintech or web development will not read as a game developer resume to a technical hiring manager at a studio.
Bottom line
- Portfolio link in the header. Not at the bottom. Not "available on request."
- Game-specific metrics: frame time, memory budget, DAU, Day 7 retention, crash-free session rate. Replace every "improved performance" bullet with numbers.
- Lead with your engine specialization. Unity or Unreal, not both equally weighted unless the role is genuinely cross-engine.
- Live service work is a separate qualification. State it explicitly with MAU and years of operation if you have it.
For game developer roles sourced directly from studio ATS systems, browse current openings at Hire.monster/jobs. The AI match score breaks down which JD requirements your resume addresses, which helps calibrate which metrics and engine signals to emphasize in your tailored version. For applying to studios with per-job resume tailoring, see what Pro includes.