Cloud Services (AWS/Azure/GCP)

Cloud work in games means operating the services a live title depends on. Compute and container orchestration, managed databases and caches, object storage for patches and user content, networking and load balancing, secrets, logging and metrics, and infrastructure described as code so an environment can be rebuilt instead of remembered.

Two things make it game-specific. Load is spiky: a launch, a sale or a patch can move traffic by an order of magnitude within the hour, so autoscaling and capacity planning are design decisions rather than settings. And cost is a product constraint, because a service that scales well and bills badly still fails.

Postings pair cloud skills with server administration, CI/CD, Python for automation and database work. A backend developer writes the services; cloud work is about the platform they run on and the pipeline that puts them there.