# Firaxis and Fortis Cut 500 Game Devs: Rewriting a Games Resume for SaaS

_After the Firaxis and Fortis layoffs, here is how game developers rewrite shipped titles, live ops, and NDA projects so SaaS screeners read them as relevant._

- Canonical URL: https://www.refolk.ai/candidates/blog/game-developer-resume-for-tech-jobs-live-ops
- Published: 2026-11-18
- Reading time: 10 min
- Keywords: game developer resume for tech jobs, laid off game developer jobs, game designer to product manager resume, live ops experience resume, leaving game industry career change

If you were one of the roughly 500 game developers cut by Fortis Games and Firaxis in November 2026, your games resume is about to land on SaaS postings that don't know what "shipped," "cert," or "live ops" means. The work counts. The vocabulary doesn't, and that's the part you can fix.

Fortis Games shut down on Nov. 10, 2026. Its communications director said "more than 400" people lost their jobs, and press reports put it at about 440. Eight days later, Take-Two's Firaxis (Civilization, XCOM) laid off around 60 people, about a third of the studio, two days before sibling studio Rockstar released Grand Theft Auto VI.

## Why should laid-off game developers apply outside games first?

Applying outside games first makes sense because the games market is oversupplied: Amir Satvat estimates five job seekers for every open games role worldwide. Satvat runs a network of 14 job-seeking resources through Amir Satvat's Games Community. He projects 14,259 games layoffs in 2026, and Firaxis plus Fortis account for about 3.5% of that.

GDC's November 2026 survey data says the same thing:

- 34% of respondents had been laid off in the previous 24 months (39% in the US).
- 54% of those laid off are still unemployed (59% in the US).
- 27% had sent at least 100 job applications.
- Of the people who found work after a layoff, only 68% landed in a similar field.

> **54%** Laid-off GDC respondents still unemployed
>
> The figure rises to 59% for US respondents, per GDC's November 2026 data.

One caveat. GDC says the layoff findings come from roughly 900 laid-off game workers, and that group may over-represent the people hit hardest. Treat these numbers as the bad end of a range, not a census. The wider market is slow as well. The median US unemployment spell was 11.9 weeks in October 2026, up from 9.0 in October 2019, and 27.6% of unemployed people had been looking for more than six months.

Here is why it happens. When a studio closes, hundreds of people with the same titles hit the same few open reqs in the same week. Fortis senior producer Gustavo Coronet posted publicly on LinkedIn that the studio had been "abruptly shut down," and everyone who worked alongside him went job hunting at the same moment. Outside games, far fewer people in the applicant stack share your exact profile.

What that pileup feels like is the 100th application going out and nothing coming back. When you're one of hundreds of near-identical resumes, the problem usually isn't effort. You're in a queue nobody is reading.

## Why does "live ops" hurt you outside games?

Outside games, "live ops" often points to call-center work, so as a keyword it sends recruiters to the wrong people. Live ops (live operations) means running a game after launch: event calendars, content drops, economy tuning, and the retention and monetization metrics those affect. In Refolk's index of professional profiles, only 36 US profiles have "Live Ops," "LiveOps," or "Live Operations" in their current title.

> **36** US profiles with a live-ops current title
>
> In Refolk's index. Contact-center firms show up among the top employers more often than game studios do.

Here's how the top employers in that group break down. The counts come from a 25-profile sample, so read them as directional.

| Employer group in the live-ops title sample | Profiles | Examples |
|---|---|---|
| Non-game tech | 7 | Apple (3), Disney Streaming (2), Intuit, The Meet Group |
| Contact-center firms | 6 | Liveops Inc. (4), Serenova, Arise |
| Game companies | 3 | HoYoverse (2), RallyHere |

The mechanism is literal string matching. An AI screener is the software inside an applicant tracking system that parses your resume and scores it against the posting's keywords and requirements. A recruiter who searches "LiveOps" gets Liveops, Inc. agents. Meanwhile a SaaS posting for a lifecycle or release role never uses the word at all, so your strongest experience matches nothing.

The fix:

- Spell it out on first use: "Live-service operations: release cadence, in-product event calendar, retention and monetization."
- Keep "(live ops)" in parentheses only when the employer is game-adjacent.
- Put the outcome in the bullet, not the label. "Ran weekly content releases" says less than "ran weekly releases and owned the retention dashboard used to plan them."

## Where does live-service experience transfer most directly?

Subscription and streaming companies are the best fit for live-service experience, ahead of generic SaaS. In that same sample, Apple, Disney Streaming, Intuit, and The Meet Group hold seven of the top-employer profiles with a live-ops title. These companies already have a job title for the work you did.

The reason is structural. Streaming and subscription products run on a content calendar, worry about churn between releases, and staff teams to plan the next drop. That's the live-service loop with a different product. A generic B2B SaaS company may have no seasonal calendar at all, so you'd have to explain the whole concept before the screener credits any of it.

A sensible order for your targets:

1. **Streaming and subscription consumer products**, where content cadence and churn are the core job.
2. **Live-service infrastructure companies** like RallyHere, which sit between games and backend tooling and read a game resume natively.
3. **Consumer SaaS with growth or experimentation teams**, where retention cohorts and A/B tests are daily work.
4. **General B2B SaaS**, last, and only with a fully translated resume.

Fortis was a San Francisco studio. If you're an engineer who wants to stay local, start with what's open there.

> **Engineering roles open in San Francisco** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&location=san-francisco)
>
> Live engineering postings in the city where Fortis was based.

## How do you translate game work into SaaS language?

Swap every game-specific term for the process or metric a SaaS posting actually names, and use the engine name only once. In Refolk's index, 3,417 US profiles list Unreal Engine as a skill and work at games employers. Inside games, that skill is everywhere. Outside games, "Unreal" alone won't match a backend or performance posting, but the work underneath it will.

| Game term | What the SaaS screener searches for |
|---|---|
| Soft launch | Staged rollout, beta, market test |
| D1/D7 retention | Cohort retention, activation, churn |
| Live ops | Release management, lifecycle, content calendar |
| Milestone, alpha, beta, cert | Delivery milestones, release gates, QA sign-off |
| Frame budget, perf pass | Performance profiling, latency, optimization |
| Build pipeline | CI/CD, build tooling, release engineering |

D1/D7 retention is the share of new players who come back one day and seven days after install. To a SaaS product team, that's a cohort retention curve, and it's the most transferable metric a game developer has.

### Engineers

Name the engine once, then describe the transferable layer: "C++ performance profiling," "memory and frame-time budgets," "build/CI tooling," "client-server networking." A performance-engineering posting at a streaming company is screening for profiling and latency work, not for Unreal.

### Designers moving to product management

A game designer to product manager resume should read like PM work: hypothesis, test, metric, decision. "Designed the progression system" turns into "Defined progression hypotheses, tested two variants in soft launch, shipped the one that improved [your D7 figure]." Use your real numbers. If you don't have them, describe the decision you made and what it rested on.

### Producers

Producers are delivery managers who already handle cross-functional dependencies. Lead with the scope you coordinated and the release gates you owned, written as "release management" and "cross-functional delivery." Leave out "production" and "cert."

### Analytics and live-ops staff

You ran experiments and segmented cohorts. Say "experimentation," "cohort analysis," and "monetization funnel" in the bullet itself, not just in the skills list. A term inside a bullet shows what you did with it; a skills list only shows you've heard of it.

Most people don't struggle with the mapping. They struggle with redoing it for every posting, which is the work [Refolk](/candidates) handles: it builds the resume from your own history, then rewrites the bullets in each posting's vocabulary, so a soft launch becomes a "staged rollout" for one application and an "experiment" for the next.

## How should you bullet a game that was shut down?

A killed game is evidence of product judgment, so bullet the decision, not the title. Fortis soft-launched Twilight Towers in September 2025 and later confirmed it would shut down on Nov. 16 after it failed to retain enough players. In SaaS terms, that's a staged rollout, a cohort analysis, and a data-driven kill decision.

> A game you killed for weak retention is the most PM-shaped thing on your resume. Bullet the decision.

Before:

- Worked on Twilight Towers, a mobile game.

After:

- Ran soft launch of a mobile title (Sept. 2025) in [test markets]; tracked D1/D7 cohort retention against [target]; recommended sunset when retention missed benchmark, reallocating [team] to [next project].

Here's why the rewrite works. A SaaS hiring manager has watched features ship that should have been cut. Someone who measured, compared the result to a bar, and stopped is showing the discipline most product orgs say they want. Fill the brackets with your actual figures. If you never had access to the dashboard, write the part you owned ("built the retention event tracking used in the sunset review") and don't borrow numbers you didn't produce.

## How do you bullet an unannounced, NDA-covered project?

Lead with the milestone, genre, engine, and your scope, and leave the title out entirely. According to Bloomberg, the new XCOM had development struggles and missed a significant milestone over the summer, and it hasn't been announced. Firaxis staff can't name it, and that's fine, because screeners score skills, scope, and metrics, not titles.

Usually safe to include:

- Genre and tier ("unannounced AAA strategy title")
- Engine and platform ("Unreal Engine, PC and console")
- Your team size and role ("[N]-person engineering team, tools lead")
- What you owned ("milestone build pipeline," "save-system architecture")
- Process outcomes ("cut build time by [X]"), if they reveal nothing about the game

Leave out:

- Codenames, features, characters, or anything a fan could identify
- Dates that line up with a public announcement window
- The fact that a milestone was missed, which is the studio's story to tell, not yours

An example that passes both the NDA and the parser: "Unannounced AAA strategy title (Unreal Engine): owned the milestone build pipeline for a [N]-person team; moved nightly builds to automated CI." That's "build/CI tooling" and "release engineering" in plain words, which is what a SaaS release-engineering posting screens for.

## Should you write one resume for tech or one per posting?

Write one resume per posting, because a single "tech version" of a games resume still guesses at which vocabulary each employer uses. A streaming company's lifecycle role wants "content calendar" and "churn." A SaaS growth role wants "experimentation" and "activation." A performance role wants "latency" and "profiling." Same history, three different sets of keywords.

With a median search of 11.9 weeks, a misaligned resume costs you real time. Every posting where the screener can't find the matching term is a rejection you never hear about. Before you apply, Refolk scores how well your actual history fits the posting, so you can put your effort into the streaming and live-service roles where your experience lines up, then send a tailored resume and cover letter in that employer's language.

## FAQ

### Should I remove game titles from my resume when applying to tech jobs?

No. Keep shipped, announced titles, because they prove you delivered at scale. Put them after the outcome, though, not before it. "Owned release cadence for a live-service title with [scale]" should come first, with the game's name in parentheses. The screener is matching the outcome, and a human reader still gets the credibility of the title.

### How do I write a game designer to product manager resume?

Rewrite every design bullet as hypothesis, test, metric, and decision. Systems design becomes "defined and tested hypotheses," soft launch becomes "staged rollout," and retention tuning becomes "cohort analysis and iteration." Mention any shutdown or pivot you influenced, because a data-driven kill decision is core PM work that many PM applicants can't point to.

### Is live ops experience valuable outside games?

Yes, but not under that name. In Refolk's index, only 36 US profiles hold a live-ops title, and contact-center companies like Liveops, Inc. take several of the top-employer slots. Describe the work as live-service operations, release management, and retention and monetization, and target streaming and subscription companies like Apple, Disney Streaming, and Intuit, which already use the title.

### Can I list work on an unannounced game at all?

Yes. List the genre, engine, team size, and the systems or pipelines you owned, without the title or any identifying features. Screeners score skills and scope, so "unannounced AAA strategy title, Unreal Engine, owned milestone build pipeline" gets credit without breaking your NDA. If you're unsure, check your separation agreement before you send anything.

---

_From the Refolk job search blog. More posts: https://www.refolk.ai/candidates/blog/index.md_
