DevOps & SRE Jobs in iGaming

DevOps and SRE work in iGaming is defined by one fact: the platform can never be down when the match is on. Live betting means real-time load that spikes around big fixtures, so engineers plan capacity for Champions League nights, the Grand National, and the Super Bowl rather than average traffic. Kubernetes, Terraform, and heavy observability stacks are standard.

Multi-jurisdiction infrastructure adds a twist rarely seen elsewhere, since some regulators require in-country hosting or data residency, forcing hybrid setups across cloud regions and licensed data centers. Teams run 24/7 on-call rotations, chaos-test failover, and treat deployment freezes around major sporting events as normal practice. Salary context lives on the salaries page.

Open DevOps & SRE roles

No open roles here right now. New jobs land daily.

Browse all open roles →

Frequently asked questions

Why is uptime such an obsession in iGaming?
Downtime during a major fixture is direct, unrecoverable revenue loss and a player trust hit, because bets not placed in that window are gone. SLAs with B2B clients and regulator expectations add contractual and legal pressure on top.
What does multi-jurisdiction infrastructure mean in practice?
Regulated markets can require local hosting, data residency, or regulator access to specific systems. SREs end up operating the same platform across multiple cloud regions and in-country data centers, with per-market routing and compliance controls baked into the infrastructure.
How is capacity planning done for betting platforms?
Around the sporting calendar. Teams model load for known peaks like tournament finals and big race days, pre-scale ahead of kickoff, and load test settlement and wallet paths specifically, since those are the components that buckle first.