What should a game developer CV show in 2026?

What should a game developer CV show in 2026?

A game developer CV in 2026 needs three things a text prompt can't fake: named shipped titles with your exact scope on each, deep ownership of one engine or pipeline area, and numbers that only come from production — frame time, memory budgets, build times, retention. The timing matters. On 7 October 2026, Google Labs began testing Playground, an experimental platform where you describe a game in plain language and get a playable browser version back, with Gemini handling generation, Nano Banana the imagery and Lyria the audio. Published games get ratings and leaderboards, and Google has signalled a Unity Spark integration for stronger 3D. The consequence for your application is blunt: a playable thing behind a link no longer proves you can build one.

Hiring conditions make that gap expensive. GDC's 2026 State of the Game Industry report, built on responses from more than 2,300 professionals, found roughly one in three US developers had been laid off within the previous two years, and 28% globally. Confirmed layoffs passed 10,000 by August, with Epic cutting more than 1,000 roles in March and Microsoft's July reduction sweeping across Xbox and four divested studios. Respondents pointed at restructuring, budget cuts and cancelled projects. The practical effect on your CV is simple: every opening competes against experienced people who already have credits, and entry-level postings routinely draw more than 200 applicants. You're not being compared to nothing. You're being compared to someone who shipped.

So the job of the document has changed. A game developer CV used to work as a project index — here are eight things I made, please look. That version now reads like output rather than evidence, because generating eight playable things takes an afternoon and a weekly token allowance. What survives screening is a document organised around delivery: titles released, platforms certified, systems you personally owned, bugs you closed under a performance budget, decisions you made when the budget wouldn't hold. Here's my blunt opinion — halve your project count and triple the detail on what's left. Three projects you can explain down to the profiler trace beat eight you can only gesture at, every single time.

Does a portfolio still beat a CV for game dev roles?

Your portfolio still decides whether a studio wants you, but your CV decides whether anyone opens the portfolio. Those are two different jobs and they need two separate documents. Portfolio links appear as a requirement in roughly 60% of analysed game developer postings, and for junior and indie roles a playable, well-documented portfolio genuinely outweighs a degree. Here's the catch almost nobody plans for: most studios funnel applications through an applicant tracking system first, and that system reads your CV file — not your itch.io page, not your showreel, not your devlog. If the file parses badly, or carries none of the engine and system terms the advert lists, the portfolio never gets clicked at all.

Treat the portfolio as a craft exhibit with a strict running order. A hiring manager should land on a 60 to 90 second annotated gameplay reel with your strongest footage inside the first ten seconds, then reach a playable build within about three minutes of arriving. One hero project leads: finished, polished, optimised — small is completely fine, unfinished is not. Two to four supporting projects follow to prove the hero wasn't luck, ideally across different genres and different technical problems. Each needs a short case study naming your role, the problem you solved, and a build or repo link. Recruiters check itch.io and GitHub more often than anything else you put in front of them.

The division of labour between the two is worth being deliberate about. Your CV carries scope, ownership and numbers: team size, platforms certified, frame-time wins, retention movement, years in a given engine, the profilers you actually drive. The portfolio carries taste and craft: feel, readability, polish, and the reasoning behind a system. Repeat yourself as little as possible across them. And resist the urge to list every game jam you've entered — jams prove you can start something under pressure, which is useful once, not six times. One summarising line about jam participation, plus one jam project you genuinely finished and shipped, says far more than a scrolling wall of prototypes.

How do you write AI-assisted game projects honestly?

Name the tool, name the stage, and name what you did yourself. Vague phrasing like "AI-assisted" is worse than saying nothing, because it invites the reviewer to assume the worst version. Write which model or tool you used, where in the pipeline it sat — concepting, base textures, boilerplate, test generation, dialogue variants — and what the human layer was: retopology, UVs, rig compatibility, LODs, refactors, profiling, the review pass that caught the bad output. Art directors and engineering leads have become good at spotting generated work, so quietly passing it off as hand-authored now carries more risk than admitting it. Specific disclosure reads as confidence. Evasion reads as a liability waiting to surface mid-production.

There's a commercial reason studios care, not just a cultural one. Under US copyright law, work made for hire assumes a human author, so assets a contractor generated may not vest the way the contract assumes. Steam rewrote its AI disclosure requirements in January 2026, and EU disclosure obligations take effect on 2 August 2026. A hire who can't account for where a shipped asset came from becomes someone else's problem on a submission checklist. That's exactly why provenance belongs on your CV as a competence rather than an apology: version history kept, source files retained, generated output reviewed before it entered the build. Say you work that way and you've answered a question leads are quietly anxious about.

At bullet level, the pattern that works puts the judgement first and the tool second. "Generated first-pass barter dialogue variants with an LLM, hand-edited every shipped line for voice and length, cut writing time on 40 vendor NPCs by about half" tells a lead you can drive a tool. "Used AI" tells them nothing. The same logic applies to code: assistants that write tests, scaffold systems or review diffs are now ordinary production tools, and writing AI-assisted engineering work up as evidence is a skill worth getting right. Keep a few pieces that are demonstrably fully hand-authored too — some studios and clients still apply stricter policies, and you want an answer ready.

Which game programmer CV keywords do studio filters match?

Studio tracking systems match the literal strings in the job advert: engine names, language names, platform names, system names and the job title itself. There's no clever synonym layer doing you favours. If the posting says "Unreal Engine 5" and your CV only says "UE5", assume the match fails — write both, once each. The same goes for "C++" versus "CPP", "Nintendo Switch" versus "Switch", and "gameplay programmer" versus whatever creative internal title your last studio gave you. Mirror the advert's vocabulary in your skills block and inside at least one bullet, because a term that appears only in a list looks like a claim, while the same term attached to a shipped system looks like experience.

Specialism language does more work than breadth language. "Physics programmer", "tools developer", "graphics programmer", "netcode engineer" — these land instantly with both a filter and a human, where "game developer with a passion for games" lands nowhere. Pick the one strength you want to be hired for and let it anchor the top third of the page, even if you're genuinely a generalist. Then group the rest honestly, separating engines from languages from systems from pipeline tools, so a reader scanning for one capability finds it in two seconds. Naming your profiler matters too: Unreal Insights, RenderDoc and PIX signal that you've optimised real builds rather than read about optimisation.

Formatting is the other half of passing that first screen, and it's where strong candidates lose. Single column, standard headings ("Experience", "Skills", "Education"), no icons, no text boxes, no two-column layouts, no skills rendered as rating bars a parser reads as nothing. Game CVs suffer badly here because developers build beautiful documents, and a two-column design with a sidebar of engine logos can arrive at the recruiter as a jumble. Export to PDF, then check what the extracted text actually looks like. If you want the mechanics in detail, this walkthrough of what a technical CV has to clear on the first screen covers the parsing traps specifically.

How do you show scope and ownership on each shipped title?

Give every shipped title its own header line carrying title, platform, engine, team size, your role and the system you owned — then three bullets underneath. That one line answers the question a lead silently asks about every credit: how big was this, and which part was actually yours? "Contributed to combat" is unreadable. "Owned melee hit detection and the parry window across PS5, Xbox Series X and PC, team of 14" is a hiring signal. Scope beats studio prestige here, and I'll defend that: owning one system end to end on a mid-size release reads stronger than being one of ninety names in a AAA credits roll with no stated remit. Leads hire for the remit.

Then pair your bullets so each title shows an engine number, a player number and a scope number. The engine one lives in milliseconds, not vibes — "pulled frame time from 19.4 ms to 16.2 ms in performance mode via Unreal Insights traces, LOD authoring and draw-call batching" is checkable. The player one uses the cohort metrics the industry actually runs on: D1, D7, D30 retention, DAU, ARPU. Keep those credible. Median D1 retention sits around 22% with top titles above 40%, and median D7 under 4%, so "+40% retention" reads as noise while "D7 from 6.1% to 7.4% across a 200,000-player cohort, measured against a control group" reads as real work.

Unannounced and cancelled projects need a plan, not a gap. Write the shape without the secret: "unannounced third-person action title, PS5 and PC, team of 60 — owned traversal and camera collision" respects the NDA and still proves scope. Cancelled work counts too; say what shipped internally, which milestone you hit, what you learned when the plug came out. A cancellation after two years of systems work is a credit, not an embarrassment. Once the structure is there, run the file through a free AI CV analysis to see how it scores on ATS compatibility, clarity and impact, or build it from scratch in the CV builder and tailor it to one specific job advert.

Frequently asked questions