The specific signals an experienced game developer hiring panel grades on during the eight-second scan.

• Shipped titles named with platform + role

  'Gameplay programmer on Phantom Halo: Echo (PS5/PC, 2024, 1.4M units)' beats 'game developer.' Shipped + role + platform is the first scan.

• Engine + language depth

  Unity (C#) or Unreal (C++ + Blueprint). Name the engine + the language with version (Unreal 5.4 + C++17).

• Programmer track (gameplay / engine / tools / graphics)

  Game-dev sub-specializes. Naming the track signals seniority; conflating tracks reads as junior.

• Performance optimization in frame budgets

  ms per frame, frame rate at target spec, GPU draw calls. The game-dev quantification.

• Source control + build pipeline named

  Perforce (P4), Git LFS, Unreal build farm, Unity Cloud Build. Tooling fluency.

• Portfolio / itch.io / Steam link

  Game-dev portfolio is the load-bearing credential. Link to playable builds.

1. 1

   Open with shipped titles + role + platform

   A senior gameplay programmer summary names shipped titles: 'Gameplay programmer on Phantom Halo: Echo (PS5/PC, 2024, 1.4M units) and Iron Drift Saga (Switch/PC, 2022, 280k units). 6 years on Unreal 5 + C++; specialized in player-controller + combat.' Indie/mobile: 'Solo Unity developer; shipped 4 Steam titles (combined 18k Wishlists, 2 Steam Featured) + 2 mobile titles (1.4M downloads).' Entry: 'CS grad with 3 game-jam top-50 finishes (Ludum Dare 56, GMTK Jam 2023, Global Game Jam 2024) + a Steam release (Wishlists 1,200, post-demo).'

   Shipped + role + engine + platform is the first scan.

2. 2

   Quantify in frame budgets and metrics that scale matter

   ms per frame at target FPS (60 FPS = 16.67ms; 120 FPS = 8.33ms). Tick cost per subsystem (player-controller, AI, animation, physics). Draw calls. Memory budgets per region. Open-world chunk-streaming hitch frequency. Network bandwidth per replication group.

   The specific numbers to favor: • ms per subsystem tick (before/after). • Frame-rate target hit-rate at target platform (e.g., 99.8% above 58 FPS on PS5). • Memory budget (MB) per region or per subsystem. • Build size (GB) after compression. • Load time (cold + transition). • Multiplayer replication bandwidth (KB/sec/player).

3. 3

   Name engine subsystems precisely

   Unreal subsystems: GameInstance, GameMode, PlayerController, Character, BehaviorTree, NavMesh, LandscapeStreaming, UMG, World Partition, Niagara, Chaos. Unity subsystems: ScriptableObjects, Job System, Burst Compiler, Addressables, URP/HDRP, Visual Effect Graph, ECS / DOTS, Cinemachine.

   Named subsystems parse as game-dev-vocabulary signal.

4. 4

   Surface specialty + cross-discipline collaboration

   Game dev is heavily cross-functional. Name design + art + audio + production partner counts. Concrete bullets: 'partnered with 2 designers + 1 animator on the combat-feedback iteration; 14 vertical-slice playtests across Q2 2024.'

   Specialty work surfaces seniority: combat-AI, character-controller tuning, replication / networking, save/load systems, accessibility-feature engineering (subtitle systems, color-blind support, ergonomic controls).

5. 5

   Close with portfolio / OSS / community signal

   Game jam placements (Ludum Dare, GMTK Jam, Global Game Jam — overall rank + jam scale). itch.io / Steam releases with Wishlist or sales context. GDC talks (any track). Engine source PRs (Unreal source, Godot). Technical blog posts that gained traction.

Each follows the [verb] [object] [number] structure hiring managers grade against. Copy them as a starting point, swap in your own numbers, and read the annotation to understand why each one works.

• Optimization

  Cut combat-AI tick cost from 2.8ms to 0.9ms per frame on PS5 (target 16.67ms total budget at 60 FPS) by replacing per-frame line-traces with a sweep-cached spatial hash + bucket-deferred AI updates.

  Why it works: ms before/after with frame-budget context, platform, two interventions.

• Gameplay system

  Owned the player-controller system on Phantom Halo: Echo (Unreal 5 + C++); shipped 14 movement abilities + 8 combat states with frame-perfect input buffering; partnered with 2 designers + 1 animator on combat-feedback iteration across Q2 2024.

  Why it works: System owned, engine + language, ability counts, input-buffering detail, partner count.

• Engine work

  Built a custom Unreal subsystem for streaming-friendly LOD swaps on a 144 km² open-world tile-streamed map; cut hitch frequency at chunk boundaries from 14/hour to under 1/hour on PS5 + Series X.

  Why it works: Engine sub-system, map scale, metric before/after, target platforms.

• Shipped titles

  Shipped 2 AAA titles (Phantom Halo: Echo + Iron Drift Saga) and 4 indie titles (3 Steam, 1 Itch.io); combined unit sales: 1.68M; combined Metacritic 81/100. Game-jam wins: Ludum Dare 56 (22/1,800) + GMTK Jam 2023 (14/6,800).

  Why it works: AAA + indie counts, platforms, unit-sales aggregate, Metacritic, game-jam placements.

• Networking

  Authored the multiplayer-replication backbone for Phantom Halo: Echo's 16-player Battle Royale mode (Unreal 5 + custom relevancy + bandwidth-tiered prop replication); peak bandwidth 38 KB/sec/player at 95th-percentile match density.

  Why it works: Replication architecture, player-count scope, bandwidth metric at percentile context.

• Load time

  Cut Phantom Halo: Echo cold-load time from 38 seconds to 9 seconds on PS5 by overlapping asset-decompression with shader-cache warm-up + decoupling first-frame-render from world-init.

  Why it works: Cold-load before/after, platform, two interventions.

• Accessibility

  Authored the team's accessibility-feature suite (subtitle customization, color-blind mode, button-remapping, hold-to-press toggle, ergonomic input curve); shipped to 100% of players post-launch via a Day-1 patch.

  Why it works: Five accessibility features, scope (100%), patch context.

• Pipeline

  Migrated team from Perforce single-stream to streams-based Perforce workflow over 6 weeks; merge-conflict frequency fell from ~8/week to ~1/week across the 38-engineer team.

  Why it works: Migration scope, team size, merge-conflict outcome.

• Mentorship

  Mentored 2 junior gameplay programmers on player-controller + combat-state work; both shipped sole-owner mechanic features (one wall-run, one parry-counter) before the team's vertical-slice milestone.

  Why it works: Mentee count, specific feature deliverables tied to milestone.

• Speaking

  GDC 2024 talk (programming track) — 'Frame-perfect input buffering at 60 FPS without sacrificing animation tween quality' (50 minutes, 420 in-room + 8,400 GDC Vault views).

  Why it works: Named conference, track, talk title, attendance + view metrics.

• Open source

  Open-sourced UE5-CharacterMotionAnalyzer — a profiling tool for character-controller tick costs (Unreal 5 plugin, 380 GitHub stars, used by 4 named indie studios per their public devlogs).

  Why it works: Tool name, scope, stars, named-studio usage.

• Entry-level

  Shipped Echoflow — a solo Unity 6 puzzle game on Steam — as a CS-grad portfolio project; 4,800 Wishlists post-demo + Steam Next Fest featured in October 2024.

  Why it works: For an entry candidate, a real shipped Steam title with wishlists + Next Fest feature is high-leverage.

Same intent, two phrasings. Read why the right column lands on the keep-pile and the wrong column doesn't.

Patterns our writers see most often when reviewing game developer resumes — each one disqualifies candidates faster than weak experience does.

• Mistake

  Generic 'game developer' without shipped titles.

  Fix

  Lead with shipped titles. Even one indie title with player counts beats vague experience claims.

• Mistake

  Listing both Unity and Unreal as equal depth.

  Fix

  Pick the engine you ship in. Multi-engine claims invite scrutiny in technical interviews.

• Mistake

  Optimization claims without frame budgets.

  Fix

  Frame-rate target + ms per subsystem is the game-dev quantification.

• Mistake

  No portfolio link.

  Fix

  Game dev portfolio (itch.io, Steam, dedicated portfolio site) is load-bearing. Link in the header.

• Mistake

  Not naming the track.

  Fix

  Gameplay / engine / tools / graphics — sub-specializing. Name your track.

• Mistake

  Two-page resume below tech-lead level.

  Fix

  One page until tech-lead / engineering-director work justifies more.

• Mistake

  Listing every engine you've touched.

  Fix

  Depth in one engine beats breadth across five. Hiring leads grade on shipped engine experience.

• Mistake

  Hiding game jam placements.

  Fix

  Game jam placements (especially Ludum Dare + GMTK Jam top finishes) are credible portfolio. Surface them.

Strong verbs lead strong bullets. Replace generic openers (worked on, helped with, was responsible for) with the specific verb that matches what you actually did.

ATS pipelines weight your Skills section as a structured list. Include 15-25 of the items below if they match your experience — not soft skills.