Senior DevOps Engineer

We are hiring Senior DevOps Engineers with two areas of primary focus. CI/CD is the most urgent need, followed by general platform and IaC. Kubernetes and containers are a strong third area. You do not need to be equally deep in everything, but you must be genuinely senior and current in at least one of the two primary areas and capable in the other., * 8+ years in DevOps, platform, SRE, or build/release engineering, including current hands-on work (in your present or most recent role) and a minimum of 4 consecutive years of hands-on work with the core tools below. \n

• Jenkins at depth: declarative pipelines, shared libraries, plugin management, controller/agent design, and troubleshooting. \n

• Terraform and/or OpenTofu at depth: module design, remote state and locking, multi-account and multi-region patterns, safe refactoring and imports. \n

• Linux administration and open-source tooling fluency. \n

• Solid AWS experience in a multi-account, multi-region environment, including IAM, VPC and networking, and Well-Architected principles. \n

• Hands-on experience with Kubernetes (EKS or equivalent) and Helm. \n

• Experience with Ansible and Packer (or comparable tools) for building and maintaining immutable images. \n

• Experience building artifact and dependency workflows with Nexus or a comparable repository manager (Artifactory, for example). \n

• Practical experience with build and test automation for JVM-based projects (Maven, JUnit) and with integrating quality and security scanning (SonarQube or similar) into pipelines. \n

• Experience with Git-based workflows, branching and promotion strategies, and repository platform administration (GitHub and/or Bitbucket). \n

• A security-first mindset, demonstrated through concrete examples in pipelines, IaC, and cloud access design. \n

• Experience building self-service capabilities (templates, modules, golden paths) that multiple teams consume. \n

• Strong written and verbal communication, and the ability to work effectively with a distributed team. \n

Our Interactive division delivers online games to players worldwide. Many development and QA teams support that business: platform services teams and multiple game studios, each often running several projects in parallel. We are modernizing and standardizing how all of them build, test, and deploy software and infrastructure.

\n

\n

You will join the central Cloud & DevOps Platform team, which owns the standards, architecture, implementation, and ongoing improvement of our CI/CD, infrastructure, and Infrastructure as Code (IaC). The team’s mission is twofold. We govern and operate the centralized foundation that promotes software to stage and production environments across the globe, spanning AWS, other cloud and hosting providers, and bare metal. We also give dev and QA teams safe, standards-compliant self-service for their own pipelines, environments, and infrastructure.

\n, n \n

• Design, build, and run Jenkins-based pipelines at scale, including reusable shared libraries and pipeline templates that dev/QA teams consume without hand-writing pipelines from scratch. \n

• Define and enforce pipeline standards: branching and promotion models, quality gates, test stages, artifact versioning, and what blocks a release versus what only warns. \n

• Operate and evolve our artifact strategy on Sonatype Nexus, including binary and media assets (images, audio) alongside code artifacts. \n

• Execute the migration of repositories and pipelines from Bitbucket to GitHub, including GitHub-hosted app runners, with minimal disruption to active teams. \n

• Integrate and tune build and test tooling: Maven, JUnit, JMeter, Selenium, SonarQube. \n

• Introduce new capabilities: database change management with Liquibase, secrets management with HashiCorp Vault (open source), and CI/CD health and delivery metrics. \n

• Support game studios who run their own Jenkins servers against their dev/test environments while consuming our centralized tooling (artifact repository, scanning, and so on). \n

\n

Platform, Cloud, and IaC

\n \n

• Build and maintain a library of Terraform/OpenTofu modules and Terragrunt configurations that let teams self-serve dev and QA infrastructure within guardrails. \n

• Practice a shift-left, immutable, ephemeral approach. Build golden images with Packer and Ansible and provision environments from code rather than modifying them in place. \n

• Work within a multi-account, multi-region AWS environment built on AWS Organizations and a custom landing zone. This includes account vending, cross-account access patterns, and network and IAM standards. \n

• Contribute to infrastructure that spans AWS, other providers, and bare-metal hosting, including servers that are managed over SSH only. \n

• Help evolve those environments from VM-based deployments toward container clusters. \n

\n

Containers and Kubernetes

\n \n

• Deploy and operate Kubernetes workloads on EKS and on bare-metal and provider-hosted clusters, managed centrally with Rancher. \n

• Run AWS-only supporting workloads (automation, observability, internal tooling) on ECS with Fargate and help define when each platform is the right choice. \n

• Package and deploy applications with Helm using push-based delivery pipelines. \n

\n

Security (a first-class concern in everything above)

\n \n

• Build security into pipelines and IaC from the start: static analysis (SonarQube, with Snyk on the roadmap), dynamic testing (StackHawk), and IaC policy scanning (Checkov and/or tfsec as policy-as-code is introduced). \n

• Apply least-privilege IAM design, secrets hygiene, and image and artifact integrity practices across CI/CD and infrastructure. \n

• Reduce shared-credential risk, such as replacing shared SSH keys with scoped, auditable access models, without breaking existing automation. \n

\n

Team and Standards

\n \n

• Contribute to governance and architecture standards, including multi-account strategy, naming, tagging, and DNS and network conventions. \n

• Write clear documentation and runbooks so that other teams can adopt standards on their own. \n

• Participate in design and code reviews as part of the team’s normal delivery process. \n

• Collaborate with dev and QA leads across studios and platform teams to understand their needs and balance self-service with compliance. \n

\n

\n, n

• Terragrunt experience managing many environment and account combinations. \n

• Rancher or other multi-cluster Kubernetes management, and Kubernetes on bare metal or non-AWS infrastructure. \n

• ECS/Fargate experience. \n

• Bitbucket to GitHub migration experience, including GitHub Actions or app-runner hosting. \n

• HashiCorp Vault and Liquibase experience. \n

• Performance and functional test tooling (JMeter, Selenium) in pipelines. \n

• Experience with Snyk, StackHawk, Checkov, tfsec, or similar security tooling. \n

• CI/CD delivery metrics experience (DORA-style measures). \n

• Experience designing or operating hybrid environments that combine public cloud with third-party hosting or bare metal. \n

• Experience in regulated, compliance-driven environments (PCI, SOC 2, or similar). \n

• Experience in online gaming, gambling, or other regulated real-money gaming. Regulated-industry or compliance exposure in other domains counts. \n

• GitOps tooling (ArgoCD or Flux) experience. It is not a current focus for us, but it is a likely future direction. \n

• Experience contributing to an internal developer platform or portal. \n

• Relevant certifications (AWS Solutions Architect, Terraform Associate, CKA, or similar). They are helpful but not a substitute for hands-on depth. \n

\n

\n