Perforce

Game projects version gigabytes of uncompressed art, audio and engine data, and that is why Perforce is still standard where Git struggles. Working with it means understanding workspaces and streams, exclusive checkouts on binary files, branching and integration between mainline and release branches, and what a bad submit does to everyone else's build.

Postings naming Perforce usually expect it as everyday fluency rather than expertise: artists, designers, programmers and QA all submit into the same depot. Administration — triggers, typemaps, proxies for remote sites — appears in tools, build and IT roles instead.

Git is common for tooling, backend services and smaller projects, and plenty of studios run both. Knowing why the two coexist, and which one a given asset belongs in, is part of the skill.