Tools Programming

Tools programming means writing software for the team rather than for players: editor extensions, import and build pipelines, debugging aids and anything that shortens a production loop.

The work starts from a bottleneck someone else has. An artist waits for an import, a designer cannot see the effect of a value without a full build, a programmer has no way to inspect a running system. The tools programmer builds the thing that removes that wait, usually inside the engine editor and usually in the engine's own language.

Success is measured in time other people get back, which makes usability part of the engineering. A tool nobody adopts has failed regardless of how it is written. Pipeline work, asset validation and automated checks that catch a broken asset before it reaches the build belong to the same area.

Gameplay Programming produces what the player interacts with. Tech Art covers the same bridging work closer to the art pipeline. Tools programming serves the production itself.

Where these positions are: Frankfurt (2 positions), Munich (2 positions), Helsinki (1 position)