Game Developer Resume Examples & Writing Guide
A game developer resume gets read when page one lists your shipped titles with platform, engine and your role, then the systems you actually built, with performance numbers attached. A portfolio or playable link near your name matters as much as the text. One page, always.
Game developer resume example (gameplay programmer, Unreal, 3 shipped titles)
This sample is for a gameplay programmer with six years and three shipped titles who works in Unreal and has console experience. The name and studios are invented. Unity and mobile developers should keep the same shape and change the engine, platform and performance targets.
Ilya Ostrowski
Gameplay Programmer
Austin, TX (open to remote) · (512) 555-0146 · ilya.ostrowski.dev@email.com · github.com/example · ilyaostrowski.example.com
Summary
Gameplay programmer with 6 years and 3 shipped titles across PC and console. Builds combat, AI and traversal systems in Unreal Engine 5 with C++ and Blueprints, and owns the performance budget for gameplay code. Cut gameplay thread time from 9.4 ms to 5.8 ms on the base console target for a 60 fps shipping build.
Experience
Gameplay Programmer · Mid-size independent studio (70 people, third-person action games)
Aug 2022–Present
- Owns the melee combat system in Unreal Engine 5: attack state machine, hit detection, cancel windows, buffering and network reconciliation, used by all 9 playable enemy archetypes.
- Cut gameplay thread time from 9.4 ms to 5.8 ms on the base console target by replacing per-tick actor queries with an event-driven registry, profiled in Unreal Insights and PIX.
- Built the enemy AI layer on behavior trees and the navigation system, including group coordination for encounters of up to 14 agents without frame spikes above 2 ms.
- Wrote 14 designer-facing tools and Blueprint nodes for encounter scripting, which cut the design team's iteration loop on a new encounter from about 40 minutes to 8.
- Took the game through first-party certification on two platforms, closing 31 of the 38 gameplay-side certification issues raised.
- Reviews 6 to 10 pull requests a week and mentors two junior programmers on profiling and memory ownership in C++.
Game Programmer · Mobile free-to-play studio (Unity, live service)
Jun 2020–Jul 2022
- Shipped and supported a live puzzle RPG in Unity with about 400,000 monthly players, building progression, inventory and live event systems in C#.
- Reduced app memory footprint by 180 MB on low-end Android devices through addressable asset groups and texture atlas rework, which cut crashes on 2 GB devices by roughly 60%.
- Cut cold start time from 11 seconds to 6 by deferring non-critical initialization and moving config loading off the main thread.
- Built the client side of the live events system and shipped 40+ timed events over two years with no rollback caused by client code.
- Instrumented gameplay analytics and worked with the data team on 12 A/B tests, one of which raised day 7 retention by 3.1 points.
Education
Bachelor of Science, Computer Science
Lone Star Technical University, 2020
Certifications
- Shipped titles: 3 (2 console and PC, 1 mobile live service)
- Ludum Dare participant, 6 jams, two entries in the top 100 overall
Skills
What a technical director or lead checks first
Games hiring is done by people who will have to code review your work. They read a resume the way they read a commit message: what did you actually change, and did it work.
- Shipped titles. Platform, engine, team size, your role, and whether you were there at ship or only in pre-production. Shipping is the single most valuable line in this industry.
- The systems you owned. Combat, AI, netcode, rendering, tools, UI, audio, backend. Studios hire for a specific hole in the team, and generic "gameplay programming" is hard to place.
- Engine depth. Unreal C++ versus Blueprint-only, Unity with the job system versus MonoBehaviour scripting, custom engine experience. Say which honestly, because it is tested.
- Something playable. A portfolio, an itch.io page, a Steam page, a GitHub repository or a two-minute video. Leads open the link before they finish the page.
“The first thing I look for is shipped titles and the second is a link I can click. If the link is a playable build or a video of a system you wrote, you have already beaten most of the stack. What I do not want is three paragraphs about a passion for games. Everyone applying has that.”
Shipped titles and the portfolio link
This is the part of a games resume that has no equivalent in other software jobs, and it is where most candidates lose ground.
- Give shipped titles their own block, near the top if you have them. Format: title, year, platforms, engine, team size, your role and how long you were on it.
- Say whether you shipped it. "Worked on" is ambiguous. "On the team from vertical slice through ship and two post-launch patches" is not.
- If a title is unannounced or under NDA, describe it generically: "unannounced third-person action title, UE5, 70-person team". Studios understand this.
- Put your portfolio, itch.io, Steam or GitHub link in the contact line, not at the bottom. It is the most-clicked item on the page.
- For each portfolio project, say what you personally wrote. On team projects and jams, name your part, because leads assume the best-looking part was somebody else's.
- A two-minute video showing a system running, with your commentary, converts better than a repository nobody has time to compile.
Game developer resume summary examples
Gameplay programmer with 6 years and 3 shipped titles on PC and console. Builds combat, AI and traversal systems in Unreal Engine 5 with C++ and Blueprints, and owns the gameplay performance budget. Cut gameplay thread time from 9.4 ms to 5.8 ms on the base console target for a 60 fps shipping build.
Unity developer with 5 years on live service mobile games reaching 400,000 monthly players. Builds progression, inventory and live event systems in C#, and works with data teams on retention experiments. Cut memory footprint by 180 MB on low-end Android and reduced crash rate on 2 GB devices by about 60%.
Engine and tools programmer with 7 years across two studios. Owns build pipeline, asset cooking and editor tooling in Unreal, and cut full cook and build time from 3 hours 40 minutes to 55 minutes. Writes editor tools that designers actually use, measured by iteration time saved rather than by feature count.
Graphics programmer with 6 years writing rendering features in HLSL and C++. Shipped a deferred lighting path and a volumetric fog system on console within a 4 ms GPU budget, and profiles with PIX and RenderDoc. Comfortable with Vulkan and DirectX 12 and with platform-specific optimization work.
Junior game programmer with a computer science degree, 6 completed game jams and one commercially released itch.io title with 9,000 downloads. Writes C++ in Unreal and C# in Unity, built an enemy AI system with behavior trees and a save system for a 4-person student project. Portfolio with playable builds and code available.
Backend engineer with 8 years in distributed systems moving into games. Built a multiplayer authoritative server in C++ with client prediction as a side project, running 32 players per instance at under 40 ms tick. Strong on networking, profiling and CI, and learning Unreal gameplay code through two shipped jam entries.
Start with an example, finish in minutes.
No sign-up to start. Download works. One-time $12 for a clean PDF, no subscription.
Game developer experience bullets, rewritten
- 1Name the system you owned, not the feature area: "the melee combat state machine", not "gameplay features".
- 2Say what you built or changed, in the engine and language the studio uses.
- 3Attach a number in the unit that matters: milliseconds, megabytes, frames per second, load seconds, crash rate, build minutes, agents on screen, players.
- 4Add the constraint that made it hard: console target, low-end device, network latency, team size, ship date.
- 5Check that a lead could ask you a follow-up question about it. If they could not, the bullet is too vague.
| Vague | Rewritten |
|---|---|
| Developed gameplay features using Unreal Engine. | Owned the melee combat system in UE5 (attack state machine, hit detection, cancel windows, buffering, network reconciliation) used by all 9 enemy archetypes. |
| Optimized game performance. | Cut gameplay thread time from 9.4 ms to 5.8 ms on the base console target by replacing per-tick actor queries with an event-driven registry, verified in Unreal Insights. |
| Worked on enemy AI. | Built the AI layer on behavior trees and navmesh, including group coordination for encounters of up to 14 agents with no frame spike above 2 ms. |
| Created tools for the design team. | Wrote 14 editor tools and Blueprint nodes for encounter scripting that cut a designer's iteration loop on a new encounter from about 40 minutes to 8. |
| Fixed bugs before release. | Closed 31 of 38 gameplay-side first-party certification issues across two platforms, taking the build through submission on schedule. |
| Reduced memory usage on mobile. | Cut app memory by 180 MB on low-end Android through addressable asset groups and texture atlas rework, reducing crashes on 2 GB devices by about 60%. |
| Implemented multiplayer features. | Implemented client prediction and server reconciliation for player movement and abilities, keeping perceived input latency under 90 ms at 120 ms round trip. |
| Worked with other departments. | Ran a weekly performance triage with art and design, publishing a per-scene budget in ms and MB that kept the shipping build inside frame budget on the minimum spec. |
Game developer skills for a resume
List them by what a studio staffs against. Be honest about depth, because technical interviews in games go straight at whatever you claim.
- Languages: C++ (say the standard you work in), C#, HLSL or GLSL, Python for tooling, and any scripting language the engine uses
- Engines: Unreal Engine (C++ and Blueprints, Gameplay Ability System, replication), Unity (job system, addressables, URP or HDRP), Godot, or in-house engines
- Domains: gameplay systems, AI, animation programming, physics, rendering, networking and netcode, UI, audio integration with Wwise or FMOD, backend and live ops, build and pipeline
- Platforms: PC, PlayStation, Xbox, Switch, iOS, Android, VR, plus first-party certification experience
- Performance: profiling with Unreal Insights, PIX, RenderDoc, Unity Profiler and Superluminal, memory budgeting, asset streaming
- Practice: Perforce, Git with LFS, code review, continuous integration, automated tests, Jira and agile production
- Math that studios actually ask about: vectors and matrices, quaternions, interpolation, collision and intersection tests
Two plain-language things belong here too, with evidence: you can take feedback in code review without friction, and you can talk to designers about what a system needs to do rather than how it is coded. Both come up in every interview loop.
Entry level game developer resume (no industry experience)
Breaking into games is competitive and the advice on forums is largely right: your portfolio does more work than your resume. But the resume still has to get you to the portfolio, so build it around finished things.
- Finished beats ambitious. One small released game with 9,000 downloads is worth more than three unfinished open-world projects.
- Game jams count as experience. List the jam, the year, your role, the team size and the result, and link the playable entry.
- Give student and personal projects the structure of a job entry: dates, engine, team size, the systems you personally wrote, and one measurable outcome such as frame time, download count or playtest feedback.
- Name the engine version and the language. "UE5.4, C++ and Blueprints" places you immediately.
- Include any adjacent professional work, especially general software engineering, QA, or tools work. Studios hire QA into programming more often than people think.
- Say what area you want. "Looking for a junior gameplay or tools programming role" is more hireable than "any position in games".
- A degree helps but is not required. Ship something, profile it, and be able to explain the tradeoffs you made.
Hollow Line (2025, itch.io, Unity, solo). Wrote all gameplay code in C#: platformer controller with coyote time and input buffering, save system, and a level editor used to author 22 levels. 9,000 downloads and a 4.6 rating from 210 ratings. Held 60 fps on a 2016 laptop through object pooling and sprite atlasing.
GMTK Game Jam 2025, 48 hours, 4-person team, Unreal Engine 5. Wrote the enemy AI and the ability system, including a behavior tree with three enemy types. Placed 87th of 6,800 entries overall.
Capstone Project, 4-person team, 8 months, Unity. Built the save and progression systems and the enemy encounter director in C#, and ran weekly profiling that kept the build above 60 fps on the department's minimum spec machines.
Format, length and the ATS question
- One page. Two only if you have ten years and many shipped titles, and even then leads read page one.
- Portfolio link in the contact line. Repeat it in the projects section if that is where the detail lives.
- Single column, plain text, no graphics on the resume itself. Save the visual work for the portfolio, because large studios screen through tracking software.
- Order the page: summary, shipped titles, experience, skills, projects, education. For entry level, move projects above experience.
- Mirror the posting's exact words: the engine and version, the language, the domain (gameplay, tools, engine, graphics, network), the platform, and the version control system.
- No photo, no date of birth. In the UK and EU a games CV follows the same conventions and photos are still not expected in this industry.
Frequently asked questions
How do I write a game developer resume?
Put a portfolio link in the contact line, list shipped titles with platform, engine, team size and your role, then write experience bullets naming the systems you owned with numbers in ms, MB, fps or players. Add a skills block that is honest about engine depth. Keep it to one page.
What skills should be on a game developer resume?
Languages (C++, C#, shader languages, Python for tools), engines with the specific subsystems you know, your domain (gameplay, AI, netcode, graphics, tools, backend), platforms and certification experience, profiling tools, and version control, which in games usually means Perforce.
How do I write an entry level game developer resume?
Build it around finished projects. List released games, game jam entries and student projects like jobs, with dates, engine, team size, the systems you wrote and one measurable result. Put projects above experience, name the area you want, and link playable builds. A finished small game beats an unfinished large one.
Do game developers need a portfolio or just a resume?
Both, but the portfolio decides it. Leads open the link before they finish reading. Make sure the portfolio says exactly what you wrote on each project, includes something playable or a short video, and loads quickly. Code on GitHub is useful only if a reviewer can understand it in five minutes.
How long should a game developer resume be?
One page. This is a strong convention in the games industry and going to two pages early in your career reads as padding. Once you have a decade and many shipped titles, a second page listing credits is acceptable, but the important material still belongs on page one.
Should I use Unity or Unreal on my resume?
Use whichever you actually know, and say at what depth. Unreal roles usually want C++ rather than Blueprint-only work, and Unity roles increasingly ask about addressables and the job system. If you know both, list both with the subsystems you have shipped in, and match the posting's engine in your headline.
How do I list an unannounced or NDA game?
Describe it generically: unannounced third-person action title, Unreal Engine 5, 70-person team, your role and dates. Studios deal with this constantly and will not penalize you. Never name a title that has not been announced, even in an interview, because leads notice.
Ready to write yours?
The builder suggests a summary from your own experience, then checks it against the job posting.
How this page was made: a first draft was written with AI assistance from cvplex's example library, then edited and fact-checked by the cvplex Careers Team. Examples are fictional composites; numbers are illustrative. Report an error via the editorial policy page.