Python

The glue language of game production: tooling, content pipelines, data work and automation around the engine.

Python rarely ships inside a game and is everywhere around one. It drives content pipelines and exporters, editor and DCC tooling in Maya, Blender or Houdini, build and release automation, telemetry and analytics jobs, and the small scripts that turn a two-hour manual task into one command.

In data roles it is the working language for pulling events out of a warehouse, joining them to SQL queries and turning the result into something a team can act on. In AI and machine learning work it is the default, which is why it appears in postings for AI development next to model and inference tooling.

Expect it as a secondary requirement in most engineering and data roles rather than as the thing someone is hired to write all day. Where Python is the main language, the job is usually tools, services or data, not gameplay.

Where these positions are: Barcelona (10 positions), Paris (10 positions), London (6 positions), Bucharest (3 positions), Belgrade (2 positions), Berlin (2 positions), Katowice (2 positions), Munich (2 positions), Nicosia (2 positions), Annecy (1 position), Bremen (1 position), Cologne (1 position), Dublin (1 position), Guildford (1 position), Hamburg (1 position), Helsinki (1 position), Limassol (1 position), Lleida (1 position), Lyon (1 position), Manchester (1 position), Prague (1 position), Stockholm (1 position), Warsaw (1 position)