We’re hiring a Game Infrastructure Engineer to own the platform our Minecraft network runs on — from the bare metal up. This is a generalist systems role: a small fleet run with high standards, where everything is declarative, version-controlled, and reproducible.
What you’ll work on
The full stack below the game, wherever the next problem is:
- Container platform: the cluster the game runs on and the GitOps machinery that delivers to it
- Networking: the path from player to game server, and between services
- CI/CD: image pipelines, secrets management, local dev environments that mirror production
- Reliability: capacity planning, incident response, postmortems
Who we’re looking for
- Strong Linux fundamentals: processes, memory, storage, filesystems; able to debug a misbehaving system from first principles
- Solid networking knowledge: TCP/UDP, DNS, routing, firewalls; comfortable reading a packet capture
- Automation instinct: fluent in shell plus a scripting language; allergic to doing anything by hand twice; treats infrastructure as code and git as the source of truth
- Fluency working with AI agents: directing them through research and operations for real leverage, reviewing their output with a critical eye, and knowing when a problem deserves your own head
Nice-to-haves
- Kubernetes in production and GitOps workflows
- Declarative, reproducible OS and configuration management
- Observability stacks: metrics pipelines, dashboards, alerting, log aggregation
- Secrets management: encrypted-at-rest workflows, key rotation
- Overlay/mesh networking and edge tunneling
- CI/CD pipelines and container image build systems
- Performance engineering: JVM tuning, latency analysis, resource isolation on shared hardware
- Minecraft or game-server hosting background: understanding what tick-sensitive workloads demand of a platform
- A homelab, and opinions formed by running one