Game developer CVs face a problem that almost no other software engineering role has: the hiring manager wants to play your games before they decide. No amount of CV content substitutes for a working, playable build that demonstrates what you can ship. But the portfolio only gets opened if the CV passes the initial screen — and game studio CVs get screened by the same ATS systems that other engineering roles use. Which means the game developer who lists "Unity, Unreal Engine, Godot, GameMaker, C++, C#, Python, Lua, JavaScript, DirectX, Vulkan, OpenGL" as skills has communicated that they have surface familiarity with everything and depth in nothing, and will be filtered ahead of candidates who list three things they genuinely know at engine level. The second failure is the absent portfolio link: a game developer CV with no GitHub, itch.io, Steam page, or App Store link is asking studios to take the claims at face value without any evidence. They will search for your work online regardless — if they find nothing, that absence is information. This guide covers the engine keywords, specialization signals, performance evidence, and bullet structure that make a game developer CV worth opening.

What Game Studio Job Descriptions Require in 2026

Game developer JDs split sharply by specialization and engine. Applying without matching on both is the most common filter failure.

Gameplay programmer: Owns the feel of the game — player movement, physics interactions, camera systems, ability and combat mechanics, input handling, and the systems that make the game responsive and satisfying to play. The most common type of games JD. Requires: primary engine (Unity C# or Unreal C++/Blueprint), proficiency with the engine's physics and character systems, 3D math (vectors, matrices, quaternions), and a portfolio of responsive, polished-feeling mechanics. Performance matters but is secondary to feel.

Engine/systems programmer: Works below the gameplay layer — memory allocators, asset pipelines, build systems, runtime architecture, threading models, streaming systems. Requires: C++ depth (memory model, templates, SIMD), data-oriented design (ECS, DOD), profiling tools (PIX, RenderDoc, Unreal Insights), and ideally experience modifying engine internals rather than just using them.

Graphics programmer: Specializes in the rendering pipeline — custom shaders (HLSL, GLSL), DirectX 12/Vulkan/Metal, lighting models, post-processing effects, performance optimization at GPU level. Very scarce, very well-compensated. Requires: strong mathematics (linear algebra, matrix operations), GPU architecture understanding (rasterization pipeline, tile-based rendering, memory bandwidth), and a portfolio of visual systems.

Tools programmer: Builds the internal tools that other developers use — editor extensions, pipeline automation, import/export workflows, content validation, procedural generation tools. Requires: engine editor API knowledge (Unity Editor scripting, Unreal Editor Utilities), data serialization, and the ability to design tools that non-engineers use without frustration.

Core requirements across all game developer JDs: engine proficiency in the studio's primary engine (Unity or Unreal — most JDs are one or the other, rarely both); version control (Git for indie/small studios, Perforce for AAA); shipped titles or credits on shipped projects; and the ability to profile and optimize — every studio cares about frame rate and memory budgets.

Game developer salaries in 2026: £35K–£60K UK (junior–mid); £55K–£90K for senior. Graphics and engine programmers command premiums. US: $85K–$140K; senior at AAA studios $120K–$180K.

ATS Keywords for a Game Developer Resume

Game studio ATS filtering uses engine names, language names, and rendering API terms as primary signals. "Game development" as a generic string is weaker than specific engine and language names.

Essential ATS terms for a game developer resume:

  • Title variants: Game Developer, Game Programmer, Gameplay Engineer, Gameplay Programmer, Engine Programmer, Graphics Programmer, Tools Programmer, Senior Game Developer, Technical Artist (adjacent)
  • Engines: Unity, Unreal Engine, Unreal Engine 5, UE5, Godot, GameMaker Studio, Lumberyard, custom engine
  • Languages: C++, C#, Python, HLSL, GLSL, Blueprint, Lua, JavaScript (web games), ShaderLab
  • Graphics APIs: DirectX, DirectX 12, Vulkan, OpenGL, Metal, WebGL, Shader Graph, HDRP, URP
  • Systems: ECS, entity component system, data-oriented design, DOD, physics simulation, collision detection, pathfinding, A*, behavior trees, finite state machines, FSM
  • Math: 3D math, linear algebra, vectors, matrices, quaternions, interpolation, procedural generation
  • Performance: profiling, optimization, frame rate, frame time, memory management, garbage collection, GPU profiling, RenderDoc, PIX, Unreal Insights, VTune
  • Platform: PC, console, PlayStation, Xbox, Nintendo Switch, mobile, iOS, Android, platform certification
  • Tools: Git, Perforce, version control, CI/CD, Jenkins, build pipeline
  • Long-tail phrases: game developer resume examples, how to write a game developer resume, Unity developer resume, Unreal developer resume, gameplay programmer cv, game programmer resume, indie game developer cv

Placement: Your primary engine (Unity or Unreal) and language (C++ or C#) in the headline — this is the primary fork that determines whether a JD-specific filter keeps or removes your application. Specialization in the headline if you have one: "Gameplay Programmer | Unity · C# · Performance Optimization". Portfolio/GitHub/itch.io link in the header alongside your name — mandatory.

Game Developer CV Structure and Bullets That Prove Shipping Capability

Section order:

  1. Header — name, portfolio URL or itch.io/Steam profile, GitHub, LinkedIn, location
  2. Headline — "Gameplay Programmer | Unity · C# · 3D Math · Physics · Performance Optimization"
  3. Skills — Engine / Languages / Graphics APIs / Systems / Performance / Tools / Platforms
  4. Shipped Titles or Projects — one section dedicated to shipped games: title, platform, your role, player count or rating if available. This is the most important section for candidates with shipped credits.
  5. Experience — professional studio experience with performance-aware, outcome-led bullets
  6. Education — CS, game dev, or related degree; bottom; jam participation worth noting if recent and notable

Two pages for 5+ years. Keep the Skills section tight — three to five items per category, depth over breadth. Portfolio link earns more than a sixth skills column.

Three elements make a game developer bullet convincing: the system built and its scope (what game, what mechanic, what engine), the implementation approach (what technique or architecture decision), and the measurable performance or player impact. Three examples:

  • Shipped a roguelike dungeon crawler in Unity (C#) to Steam as sole developer — 12,000 downloads and 78% Overwhelmingly Positive review score; implemented procedural dungeon generation using a BSP tree algorithm and optimized for 60fps on Intel HD 4000 minimum-spec hardware; final build shipped at 180MB
  • Built core movement, camera, and interaction systems for a first-person puzzle game in Unreal Engine 5 using a data-driven ECS approach — profiled and reduced average frame time from 22ms to 11ms on the PC high-spec target, enabling the title to pass first-party console certification on its first submission
  • Replaced A* pathfinding with a hierarchical flow field solution for an RTS supporting up to 300 simultaneous AI agents — reduced AI pathfinding CPU budget from 18% to 2.3% of frame time; unit cap doubled while the game maintained its target framerate on minimum-spec hardware

Game developer interviews include technical screens (implement a specific algorithm, profile and fix this performance issue, explain how you'd design a component system) and portfolio walkthroughs. Your CV's shipped title evidence and performance numbers determine whether the technical screen focuses on fundamentals or on deeper system design.

Three Game Developer CV Mistakes That Signal a Hobbyist to Studio Recruiters

Too many engines and languages, too little depth signal. A skills section listing Unity, Unreal, Godot, GameMaker, C++, C#, Python, Lua, JavaScript, and DirectX tells a studio recruiter one thing: this candidate has opened tutorials for many things and shipped none of them in a professional context. Studios — particularly AAA studios hiring senior roles — are not looking for breadth. They are looking for the candidate who knows Unity so well they understand the garbage collector's impact on frame timing, or who knows Unreal well enough to write a custom Gameplay Ability System task without referencing the documentation. Pick your primary engine, name it first and feature it most heavily, and reserve the secondary list for tools you have genuinely used in shipped or near-shipped projects.

No playable portfolio link. A game developer who does not link to playable work on their CV is asking studios to evaluate claims without evidence. This is particularly damaging in a field where the norm is a detailed portfolio and hiring managers will search for your name + engine on itch.io, GitHub, and the App Store regardless of what you include. If the search turns up nothing — or nothing that matches the claims on your CV — that gap is noted. A single shipped jam entry on itch.io, a free mobile game with 1,000 downloads, or a polished GitHub repo with a playable WebGL build outweighs a clean CV with impressive bullet points and no work to show. Ship something before your next job search begins, and link to it in the first two lines of your CV.

Generic engineering bullets with no game-specific performance evidence. "Implemented gameplay systems and optimised performance" describes two weeks of work on any game project, anywhere. What system, in what engine, using what approach, with what measurable result? Performance numbers are the most credible evidence on a game developer CV because they are hard to fabricate and immediately meaningful to a studio engineer reading the application: frame time reduced from 22ms to 11ms, memory reduced from 380MB to 210MB, AI CPU budget reduced from 18% to 2.3% of frame time, loading time reduced from 14 seconds to 3 seconds. Pick the highest-impact performance win from each role and put the before-and-after number in the bullet.

If you are applying to game developer or gameplay programmer roles and want your CV rebuilt around the specific engine, performance, and shipping experience requirements in a target job description, Resumegpt generates your game developer CV from your work history in under 60 seconds — engine depth evidenced, shipped titles foregrounded, performance wins measured, ATS-optimised, and exported as a PDF ready to submit.