Was this sample helpful? Rate it!
Average: 4.9 (17 votes)
Contents
What Matters Most
Why This Game Developer Resume Works
How to Write a Game Developer Resume That Gets Interviews
What to Include in a Game Developer Resume
Game Developer Resume Summary Examples
Game Developer Work Experience Examples
Top Game Developer Skills
Certifications for a Game Developer
Common Game Developer Resume Mistakes
Game Developer Resume FAQs
Summary
Game developer with eight years building games in Unity and Unreal for indie and mid-size studios in Prague. Turns designs into playable, performant games — gameplay code, tools and the optimisation that keeps a game running smoothly across devices. Shipped several titles across mobile and PC, including one that hit a strong launch and steady player numbers. Implements gameplay systems and mechanics, builds tools for designers, optimises performance, and fixes the bugs that stand between a build and a release. Practical, collaborative and genuinely enthusiastic about the games he helps build. Looking for a game-developer or gameplay-engineer role with a studio building games people love to play.
Work Experience
Game Developer
Vltava Games, Prague, Czech Republic
Apr 2017 – Present
- Build games in Unity and Unreal, turning designs into playable, performant titles across mobile and PC platforms.
- Shipped several titles, including one that hit a strong launch and held steady player numbers afterwards.
- Implement gameplay systems and mechanics from design docs, writing clean code that designers can tune and build on.
- Build tools and editor extensions for designers and artists, speeding up the whole team's workflow and iteration.
- Optimise performance across devices, profiling and fixing the bottlenecks that keep a game from running smoothly.
- Hunt and fix the bugs that stand between a build and release, getting games stable and shippable under deadline.
Junior Game Programmer
Bohemia Indie Studio, Prague, Czech Republic
Jul 2015 – Mar 2017
- Implemented gameplay features and fixed bugs on indie games in Unity, learning game programming on real shipped titles.
- Worked with designers and artists to build and iterate features, learning how a game comes together end to end.
- Learned gameplay programming, engines and optimisation on the job across nearly two years.
- Gained the Unreal certificate and earned the move into a broader game-developer role of my own.
Education
BSc in Computer Science (Games), Computer Science
Czech Technical University in Prague
Sep 2011 – Jun 2015
- Degree in computer science with a games focus covering programming, graphics and game engines, with projects. The study built strong programming and engine fundamentals. It led directly into game development.
Certificate in Unreal & Game Optimisation, Game Development
Game Dev Academy
Jan 2017 – Jun 2017
- Certificate covering Unreal Engine, gameplay programming and performance optimisation, with hands-on projects. It broadened engine skills and deepened optimisation technique. It supported shipping performant, stable games across multiple platforms.
Certifications
Unreal & Game Optimisation Certificate
Game Dev Academy
Jun 2017 – Present
- Certificate covering Unreal Engine, gameplay programming and performance optimisation to a recognised standard. It broadened engine skills and deepened optimisation and supports shipping performant games across platforms.
Highlights
Shipped titles that held players
- Shipped several titles including one that hit a strong launch and held steady player numbers afterwards. Actually shipping games that find and keep an audience is the achievement that matters most in game development.
Tools that speed the team
- Builds tools and editor extensions that speed up the whole team's iteration, not just his own work. Good internal tools quietly multiply how fast designers and artists can build the game.
Mobile Title Launch
Mobile Title Launch
Jan 2021 – Nov 2021
- Built gameplay systems, tools and optimisation for a mobile title from production through to launch, profiling and fixing performance across devices, which shipped to a strong launch and steady ongoing player numbers.
Languages
- Czech — Native or Bilingual Proficiency
- English (UK) — Full Professional Proficiency
Technical Skills
- Unity
- Unreal Engine
- C# & C++
- Gameplay Programming
- Performance Optimisation
- Tools Development
- Debugging & Profiling
- Multiplatform (Mobile/PC)
- Version Control (Git/Perforce)
- Shipping Titles
Personal Skills
- Problem Solving
- Passion for Games
- Collaboration
- Pragmatism
- Persistence
Activities & Interests
- Ice Hockey
- Snow Boarding
- Cleaning
- Online Shop
- Climbing
What Matters Most
Before the section-by-section detail, here is what actually decides whether a studio calls you back:
- Put the engine and language in your opening line. Unity with C#, Unreal with C++, or both, because recruiters filter on engine before they read a single bullet.
- Shipped titles outrank listed skills. Name the game, the platform it launched on, what you personally owned on it, and roughly when it went live.
- Quantify optimisation in milliseconds and frames, not adjectives. Going from 22 ms to 14 ms per frame on a 2018 Android baseline device is a fact a lead can check.
- Say which gameplay systems you built. Combat, inventory, AI navigation, netcode and progression are separate specialisms, and most openings exist to fill one specific gap.
- Count your tools and editor work. A custom inspector or build script that saves designers a round trip reads as senior thinking at any mid-size studio.
- Link a portfolio with a playable build or captured footage. A game programmer resume with nothing to play or watch loses to one that has both.
Why This Game Developer Resume Works
The sample above is a mid-career gameplay programmer at a Prague studio, and its structure does several things worth copying.
- The summary names both engines and both languages in the first line, so an Unreal-only or Unity-only screener knows within a second whether to keep reading.
- Shipping is treated as the headline achievement rather than a footnote. A launch that held its player numbers afterwards tells a producer the code survived contact with real players, not just QA.
- The bullets separate four different jobs a game programmer does: gameplay systems, designer-facing tools, profiling and optimisation, and release bug work. Studios hire against those categories.
- Tooling gets its own Highlight instead of hiding inside a work bullet. Editor extensions that speed up designers and artists are the clearest evidence a programmer thinks about the whole production, not only their own tasks.
- The junior role is kept short and framed as the run-up to a broader developer title, which keeps the reading weight on the eight years of shipped work.
- A named project entry gives one title a start and end date, so the launch is anchored in time rather than floating in the summary.
How to Write a Game Developer Resume That Gets Interviews
Game studios read resumes differently from other software employers. Work through these five moves in order:
Lead with your engine, your language and your shipped count
Open the summary with the stack a studio filters on: "Gameplay programmer, six years in Unity and C#, three shipped mobile titles." Engine and language are the first filter on almost every game programming posting, and a shipped count answers the second question before it is asked. Save the descriptive career narrative for later in the line.
Build the experience section around systems you owned, not features you touched
Write each bullet against a named system: the melee combat state machine, the save and load layer, the matchmaking flow, the enemy navigation. Ownership of a system is what a lead can interview you on for forty minutes. "Worked on gameplay features" gives them nothing to ask about and gets skipped.
Turn performance work into numbers a technical lead trusts
Frame budget is the currency. Give the before and after in milliseconds or frames per second, name the platform, and name the tool you profiled with: Unity Profiler, Unreal Insights, RenderDoc, Xcode Instruments. "Cut CPU frame time from 21 ms to 13 ms on a Snapdragon 660 reference device, restoring 60 fps in combat" reads as real work; "improved performance" reads as filler.
Give designers and artists a line of their own
Studios quietly value programmers who unblock other disciplines. Devote at least one bullet to editor tooling, build automation or data-driven tuning: a level-loading tool, a scriptable-object tuning table, a nightly build pipeline. State how much iteration time it saved and who it saved it for.
Make the portfolio link do work the resume cannot
Put the link near the top with the contact details, and make sure what sits behind it is playable or watchable within seconds: a WebGL build, a store link, or a two-minute capture with a short note on what you wrote. Hiring leads open the portfolio before the interview and decide what to test you on from it.
Extra tips
Most gameplay leads open the portfolio before the resume and look for one thing: something running.
Put the playable link in the header, not in a projects section three quarters of the way down.
What to Include in a Game Developer Resume
Beyond the standard blocks, a game programming resume carries a few sections that other software resumes do not:
If you have shipped work but no clean way to present it, drafting the layout is often the slow part. You can lay out the shipped-titles table, portfolio links and system ownership properly with the free online resume builder and spend your time on the wording instead.
A shipped titles block: game name, platforms, engine, your role, and launch year. Three lines here beat a paragraph of adjectives.
Engine and tooling list split from general programming skills, so Unity, Unreal, Perforce, Jenkins and Houdini are not buried next to generic language names.
Genre or platform context. Mobile free-to-play, console action, VR and simulation hire for different instincts about memory, input and session length.
Team scale and production stage, such as a team of nine through vertical slice to launch. Studios want to know whether you have lived through certification and post-launch patching.
A portfolio, itch.io page or public repository, plus a short note stating exactly which parts of the project were yours.
Game jams and personal projects if you are early career, treated as real entries with the engine, the scope and what you built named.
Game Developer Resume Summary Examples
These summaries cover angles the sample does not: a first studio job, a mobile free-to-play specialist and a console-side senior. Adapt the shape, not the words.
Entry-level resume summary example
Junior gameplay programmer with a computer science degree and two shipped game jam titles built in Unity and C#. Comfortable implementing gameplay features from a design brief, including a third-person camera rig, an inventory system backed by scriptable objects, and enemy behaviour driven by a simple state machine. Built a WebGL prototype that reached 4,000 plays on itch.io in its first month and used the player drop-off data to rework the tutorial's first ninety seconds. Familiar with Git, Unity Profiler and the basics of build pipelines from running releases solo. Looking for a junior gameplay role in a studio where a graduate programmer gets real systems to own and a senior close enough to learn from.
Mid-level resume summary example
Mobile game developer with five years in Unity and C# building free-to-play titles for Android and iOS, two of them live and earning. Owns gameplay systems end to end, from a progression and economy layer tuned through remote config to an ad-mediation integration that survived three SDK migrations. Cut cold start time from 9.2 seconds to 4.1 on a 2019 mid-tier Android reference device by reworking addressable loading and deferring analytics initialisation. Works closely with live-ops designers, shipping tuning changes weekly without client updates. Seeking a mid-level gameplay or live-ops engineering role at a studio running mobile titles with a long tail rather than a launch spike.
Senior-level resume summary example
Senior gameplay engineer with eleven years in Unreal Engine and C++ across four shipped console and PC titles, including two through full platform certification on PlayStation and Xbox. Specialises in combat and animation systems, owning the ability framework, hit reaction blending and the animation notify pipeline on a third-person action title that reviewed strongly for feel. Rebuilt the ability system's replication to hold combat under 120 ms of simulated latency, cutting desync complaints in playtests by roughly two thirds. Mentors three gameplay programmers and runs the studio's code review standard for gameplay modules. Looking for a principal or lead gameplay role on a project with real combat depth.
Game Developer Work Experience Examples
Each set below is written for a different corner of game programming. Take the one closest to your work and rebuild it around your own systems and numbers:
Gameplay programmer, mobile free-to-play
- Built the progression and reward economy for a live puzzle title in Unity and C#, wiring difficulty curves to remote config so live-ops designers could retune pacing weekly without shipping a new client build.
- Cut cold start time from 9.2 to 4.1 seconds on a mid-tier Android reference device by reworking addressable asset loading and deferring analytics init, lifting day-one retention by four percentage points.
- Implemented an offline-first save layer with conflict resolution across two devices, ending a class of lost-progress support tickets that had accounted for roughly a third of the game's inbox each week.
- Integrated and maintained ad mediation and in-app purchase SDKs through three vendor migrations, keeping revenue reporting intact and holding crash-free sessions above 99.4 percent across the transitions.
- Profiled combat scenes with the Unity Profiler and Frame Debugger, batching draw calls from 340 to 90 per frame and restoring a stable 60 fps on the studio's 2018 baseline handset.
Gameplay and systems programmer, console or PC
- Owned the ability and status-effect framework for a third-person action title in Unreal Engine and C++, supporting 40 abilities authored by designers in data assets rather than code, cutting new-ability turnaround to a day.
- Rebuilt hit registration and animation blending for melee combat, tuning root motion and notify windows with the combat designer until playtesters stopped reporting the attacks as floaty in blind sessions.
- Reworked ability replication to hold combat readable at 120 ms of simulated latency, using client prediction and server reconciliation, which cut desync reports in internal multiplayer playtests by around two thirds.
- Drove the title through platform certification on PlayStation and Xbox, clearing 61 submission issues across two passes and getting the build through first-party approval ahead of the announced launch date.
- Cut memory on the streaming level path by 380 MB by auditing texture budgets and retiring duplicated material instances, bringing the build back inside the console memory ceiling before certification.
Tools and engine programmer
- Built a Unity editor tool that let designers author and preview enemy encounter waves in the scene view, removing a round trip through the programming team and cutting encounter iteration from hours to minutes.
- Automated nightly builds for three platforms in Jenkins with Perforce triggers and smoke tests, so a broken submit was caught within twenty minutes rather than surfacing at the next morning's playtest.
- Wrote an asset validation pass that failed the build on oversized textures and missing collision, cutting art-related build breaks from several a week to under one a month across a team of twenty-six.
- Extended the animation import pipeline to auto-generate notify tracks from naming conventions, saving animators an estimated six hours a week of manual setup on a title with 900 authored clips.
- Instrumented the game with a custom in-build profiler overlay showing frame time, draw calls and GC allocations, letting designers catch their own performance regressions before code review picked them up.
Top Game Developer Skills
Studios screen against a short list of engine and systems skills, then check the rest in the technical interview. Mirror the wording in the job ad where it is honest:
Hard skills
- Unity
- Unreal Engine
- C++
- C#
- Gameplay programming
- Physics and collision
- Animation systems and state machines
- AI and pathfinding (navmesh, behaviour trees)
- Multiplayer networking and replication
- Performance profiling (Unity Profiler, Unreal Insights)
- Frame budget and memory optimisation
- Shaders and rendering basics (HLSL)
- Editor tooling and custom inspectors
- Build pipelines and CI (Jenkins, TeamCity)
- Version control for games (Perforce, Git LFS)
- Mobile and console platform SDKs
- Game math (vectors, quaternions, interpolation)
- Data-driven design and scripting
- Debugging and crash triage
- Platform certification and submission
Soft skills:
- Working with designers
- Iteration under deadline
- Playtest feedback handling
- Pragmatic scoping
- Persistence on hard bugs
- Cross-discipline communication
Certifications for a Game Developer
Certificates carry less weight here than in most engineering fields, since a playable build settles the question faster. They are still worth listing when you are moving engines or coming in without shipped credits:
-
Unity Certified Professional: Programmer
— Unity Optional. Most useful for self-taught developers proving Unity and C# fundamentals without shipped titles behind them.
-
Unity Certified Expert: Programmer
— Unity Optional senior-level credential covering optimisation and architecture; only meaningful once you already have production experience.
-
Unreal Engine Certified Professional
— Epic Games Optional. Worth listing when you are moving from Unity to Unreal and need something on paper before your first Unreal credit.
-
Certified ScrumMaster
— Scrum Alliance Optional, and only relevant if you run sprints for a gameplay pod. Never list it in place of engine skills.
Common Game Developer Resume Mistakes
These are the errors that get game programming resumes rejected before the portfolio is ever opened:
- Listing games without saying what you wrote. A credit on a title tells a lead nothing until you name the systems you owned on it.
- Hiding the engine. If a screener has to reach the skills block to find out whether you use Unity or Unreal, half of them will not get there.
- Describing optimisation without numbers. "Optimised performance" is unverifiable; frame times, draw calls, memory in megabytes and a named target device are not.
- Padding with unfinished personal projects. One completed small game with a link beats five prototypes that stop at a main menu.
- Treating tools and pipeline work as too unglamorous to mention, when it is often the strongest evidence of production maturity on the page.
- Leaving off platform experience. Mobile thermal throttling, console certification and VR frame budgets are different disciplines, and studios recruit for the one they ship on.
- Sending a portfolio link that opens a repository with no README. A hiring lead gives it about a minute before deciding what to test you on.
Game Developer Resume FAQs
The questions candidates most often ask when writing a game developer resume:
Lead with an engine and a language: Unity with C#, or Unreal with C++. Follow with the gameplay areas you have actually built, such as animation, AI, physics or netcode, then profiling and optimisation tools, and version control for games such as Perforce or Git LFS. Fifteen to twenty concrete technical skills is enough.
Yes, and it is often read before the resume itself. Link a playable build, a store page or a short capture, and state in one line which systems in it you wrote. A game programming application with nothing playable behind the link is at a real disadvantage against one that has it.
One page for the first five years, two once you have several shipped titles worth detailing. Studios will read two pages when the second page is shipped credits and systems ownership; they will not read two pages of skill lists and coursework.
Yes if you are early career, and treat them as real entries. Name the jam, the engine, the team size, the scope you delivered in the time limit, and link the build. Once you have two or three shipped commercial titles, drop the jams and keep the space for those.
Put whichever one the job ad names first, and list both if you genuinely work in both. Mobile and smaller-team studios skew heavily to Unity and C#; console and AAA work skews to Unreal and C++. Claiming both when you have only shipped in one gets exposed in the first technical call.
Replace shipped credits with finished projects. One complete small game, a modding contribution with a download count, or an open-source engine tool with users all demonstrate you can carry work to a finish. State the engine, the scope, and exactly which parts of the code were yours.
Include it only if the repositories are presentable. A pinned project with a README, a clear architecture note and readable commit history helps; a wall of half-finished tutorial forks does not. If the best work is under NDA, link the portfolio instead and describe the systems generically.
Get Started With Our
Free Resume Creator today!
Free sign-up. No credit card required.
