Rust
Rust in game companies: tools, services and engine-adjacent code where memory safety and predictable performance both matter.
Rust appears in game job postings away from the game client. Backend services, asset pipelines, build and deployment tooling, network daemons and the occasional engine component are the usual ground, and WebAssembly builds show up where a tool has to run in a browser. The attraction named in briefs is the combination of C++-level performance with a compiler that rejects whole classes of memory bugs.
Requirements name ownership and borrowing, async runtimes such as Tokio, cargo and the crate ecosystem, and the FFI boundary to existing C++ code - few studios rewrite, most add. Docker, CI and cloud deployment come along with the service work.
The word is also an ambiguous one in this industry, which is why this tag is only given where the context names the language rather than the survival game. For the engine side of a title, C++ remains the requirement that postings actually spell out.
Open positions for Rust (1)
