Sony took a ~$765M impairment on Bungie across two tranches (about $204M in Q2 FY2025 and $565M in Q4 FY2025 tied to Marathon's March 5, 2026 launch), then cut more of the Destiny 2 team in June. Epic Games followed with 1,000+ layoffs on March 24, 2026. If you shipped a live-service title in the last five years, the studio-to-studio search you're about to run is the wrong search. The resume rewrite is the whole game.
Why the 2026 game industry layoffs are a positioning problem, not a skills problem
The people getting cut are exactly the people defense sim, robotics sim, and AI training companies are trying to hire. The gap is how the resume reads, not what the resume proves.
Over 20,000 games roles have been cut across 2023 to 2026, roughly 720 at Bungie alone since Sony's 2022 acquisition (with a 292-worker Bellevue figure on the Washington State WARN filing), and Epic's ~20% cut leaves the company at about 4,000 employees. Epic said the quiet part loud in the same breath: core Unreal Engine teams were deliberately spared. The cuts concentrated on Fortnite live-ops, mode teams (Rocket Racing, Festival), designers, and artists. The market is being flooded with senior people who build real-time content pipelines on top of Unreal, which is precisely what Anduril, Blue Origin, and the RL environment shops need.
The underlying metric behind Epic's cut tells you not to wait this out. Fortnite's average monthly hours on PlayStation dropped from 21 in February 2025 to 16 in February 2026, a 24% collapse in one year. Live-service engagement is not mean-reverting on your job-search timeline.
Bungie, Epic, and the long tail of studio closures have pushed live-service talent into the market faster than studios can absorb it.
The 3,193-to-3 arbitrage hiding in Unreal Engine defense jobs
There are three orders of magnitude more Unreal-fluent US game developers than there are people positioned for defense simulation work, and that gap is a resume rewrite, not a training program.
In Refolk's index of professional profiles, US Unreal Engine talent breaks down like this:
| Segment | US professionals with Unreal Engine | Ratio to games |
|---|---|---|
| Computer Games industry (baseline) | 3,193 | 1:1 |
| Robotics simulation keyword | 12 | 266:1 |
| Defense simulation keyword | 3 | 1,064:1 |
That is not a demand shortage. Anduril, Blue Origin's Autonomy & Robotics group, Bedrock Robotics, and Pittsburgh's National Robotics Engineering Center all show up in the same index as active employers of Unreal-fluent simulation engineers. The bottleneck is that when a recruiter searches "defense simulation Unreal" on any professional network, three people come back. Be the fourth.
The mechanism is boring: hiring searches are keyword-scoped and industry-scoped. If your headline still says "Senior Gameplay Engineer, Destiny 2" and your industry tag still says "Computer Games," you are invisible to the roles that would actually take you. Pasting the Anduril or Blue Origin JD into Refolk and getting your Bungie or Epic bullets rewritten in the vocabulary the JD is scored against is the specific work that closes the gap.
The Anduril tell: "Game Developer" is already the job title
Do not strip "game" from your resume. Anduril's actual posted title is "Game Developer, Sensor Simulation," and the JD asks for 2+ years of C++ and Unreal Engine with a predicted salary band of $138K to $252K.
The Sensor Simulation team builds synthetic imagery for software-in-the-loop and hardware-in-the-loop integration tests, ML training data generation, and operator training environments. The stated goal is a pipeline so realistic that flight-test engineers can't tell synthetic frames from real ones. That is a game-engine problem dressed as a defense problem. The buyers know it. They wrote "Game Developer" into the requisition on purpose.
What this means for your bullets:
- Keep "Unreal Engine 5" front and center. It is the keyword the JD indexes on.
- Keep "shipped title" language. It proves you finished something under a deadline, which government primes rarely see from pure-research candidates.
- Recast entertainment metrics (DAU, retention, ARPPU) as capability metrics (frame determinism, sensor fidelity, scenario throughput).
- Name the engine version, the render pipeline (Lumen, Nanite), and any Niagara or Chaos work. Sim teams care about the same subsystems for different reasons.
The defense buyer wrote Game Developer into the requisition on purpose. Do not talk them out of it.
The RL environment pivot that out-earns AAA
Reinforcement learning environment engineers, the people who build deterministic training worlds for AI agents, are now paying above senior game industry comp. Mechanize reportedly offered $500K salaries for full-time environment engineers. Mercor raised a $350M Series C at a $10B valuation in October 2025 and reportedly hit ~$2B annualized revenue by June 2026, on the back of RL environments and domain-expert training data. Surge AI (roughly $1.2B in 2024 revenue with 110 employees) sells RLHF and RL environments to Anthropic, OpenAI, Microsoft, and Meta.
Every one of those companies is a shipped-live-service game away from having what it needs, and does not know it.
The translation table
Take one bullet from your last game and rewrite it. Keep the numbers, swap the frame:
- "Designed daily challenge system with 42% D7 retention lift" becomes "Built verifiable-reward task generator with deterministic scoring across 30-day agent evaluation windows."
- "Owned quest state machine across 3 seasons of live content" becomes "Owned finite-state task graph for long-horizon agent training, versioned across content drops."
- "Tuned enemy AI behavior trees for boss encounters" becomes "Authored behavior-tree opponents for curriculum learning, with difficulty scaling as reward shaping."
- "Instrumented player telemetry pipeline, 900M events/day" becomes "Instrumented rollout telemetry at 900M events/day for offline policy evaluation."
The primitives are the same. Reward loops, state machines, telemetry, deterministic replay. RL environment shops call them by their formal names because that is what their customers (frontier labs) call them. Your job is to meet them in their vocabulary.
Transferable skills game dev candidates undersell
The five capabilities defense sim, robotics sim, and RL environment teams want most are ones every shipped live-service dev already has and almost none list correctly.
- Deterministic simulation. Replays, netcode rollback, seeded RNG. In defense this is "repeatable scenario execution." In RL it is "reproducible rollouts."
- Real-time content pipelines. Hotfix cadence, asset streaming, LiveOps deploys. Robotics sim teams ship new environments to fleets on the same cadence you shipped weekly Fortnite modes.
- Physics and sensor modeling. Vehicle handling, projectile ballistics, hit registration. This is the on-ramp to sensor simulation and vehicle-in-the-loop work.
- Telemetry at scale. Event schemas, funnel analysis, A/B pipelines. Frontier labs call this "eval infrastructure" and pay differently for it.
- Toolchain authorship. Custom editors, Blueprint frameworks, in-engine debugging UIs. Sim teams buy engineers who can build the tools their non-engineers use, because that is most of the actual cost of a sim program.
None of these need retraining. All of them need renaming.
The three-vertical target list
Do not spray. Pick three verticals, name a handful of employers in each, and tune the resume once per vertical rather than once per posting.
| Vertical | Named employers from the research | What they want on page one |
|---|---|---|
| Defense simulation | Anduril, Blue Origin (Autonomy & Robotics, Seattle) | C++, Unreal, SITL/HITL, sensor pipelines |
| Robotics simulation | Bedrock Robotics, National Robotics Engineering Center (Pittsburgh) | Physics fidelity, synthetic data generation, sim-to-real |
| RL environments / AI training | Mercor, Surge AI, Mechanize | Deterministic rewards, task graphs, eval infra, RLHF tooling |
Scoring each posting for fit before you tailor is the difference between 30 sprayed applications and 8 real ones. That triage step is what Refolk is built for.
What Marathon's failure teaches about resume framing
Marathon's aesthetic and gunplay drew praise on preview; hardcore extraction mechanics made onboarding brutal, and the launch did not save the impairment math. The lesson for the resume is the same lesson Bungie learned in public: lead with what the buyer's world cares about, not with what your last world cared about.
Defense and robotics buyers do not care about MAU, ARPPU, or Twitch peaks. They care about:
- Systems engineering rigor (interface docs, versioned APIs, ICDs)
- Sensor and physics fidelity (frame-accurate, unit-correct, validated against real captures)
- Determinism and reproducibility (scenario X gives result Y, every time)
- Security posture (ITAR-adjacent language, clearance-eligible status if it applies)
Frontier lab and RL environment buyers care about a slightly different list:
- Reward-signal design (dense vs sparse, gameable vs verifiable)
- Task generation at scale (procedural, parameterized, curriculum-shaped)
- Evaluation infrastructure (offline, online, human-in-the-loop)
- Domain fidelity for the specific vertical they are training against
Your Bungie or Epic history has evidence for every bullet in both lists. The rewrite is choosing which evidence to surface for which buyer.
FAQ
Should I hide that I worked in games on a defense resume?
No. Anduril's live requisition is literally titled "Game Developer, Sensor Simulation," and the JD asks for Unreal and C++. Defense sim buyers explicitly want game-engine fluency because game engines are what they use to generate synthetic sensor data and training scenarios. Keep the studio names, keep the shipped titles, keep the Unreal versions. Change the outcome framing (from entertainment metrics to capability metrics) and change the industry tag on your profile.
How do I get an interview for RL environment work without ML on my resume?
Frontier labs and RL environment shops (Mercor, Surge AI, Mechanize) are buying reward-loop design, deterministic simulation, and task-graph authoring, not gradient descent. If you built quests, seasons, or daily challenges, you built RL environments and did not know it. Rewrite three bullets in that vocabulary (verifiable reward, curriculum, rollout telemetry) and apply. The 3,193-to-single-digit ratio in Refolk's index means the pool of correctly positioned candidates is small enough that a real portfolio clears the first filter.
What if I only have Unity experience, not Unreal?
For defense sim roles that specify Unreal, be honest and lead with the engine-agnostic skills: real-time rendering, physics tuning, scenario authoring, tool-chain building. The Anduril posting names Unreal specifically, but Blue Origin's Simulation Engineer III listing and most robotics sim postings surfaced in Refolk's index care more about the underlying capability than a specific engine.
Is it worth waiting for the game studios to bounce back?
The Fortnite hours-per-user metric fell 24% year over year on PlayStation, Bungie took a $765M impairment on the back of Destiny 2 and Marathon underperformance, and 20,000+ industry cuts have already landed since 2023. Nothing in that data set suggests studio hiring returns to 2022 levels on a timeline that helps you pay rent. The adjacent industries are hiring now, at higher comp bands, against a talent pool that has not figured out how to describe itself yet. Move.