You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
2K

Senior Site Reliability Engineer

  • Hybrid
  • 6+ years

Salary

Not stated

Similar roles pay $165K - 220K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company makes video games, from sports franchises to well-known titles in many genres, with studios around the world.

The team keeps the infrastructure running that connects players to game services, account platforms, CI/CD pipelines, databases and developer tools.

These systems run on AWS and on VMware data centers in several regions, and global launches and live events put heavy load on them.

Post-mortems look at systems rather than individuals, and automation is the default answer for repetitive work.

Millions of players rely on this infrastructure, and the team treats that responsibility seriously.

This is a hands-on leadership role with real ownership. You will set technical direction and work with network engineers, database administrators, systems architects and game studio developers to improve reliability from architecture review through to production.

Responsibilities

  • Build and run hybrid infrastructure across AWS and VMware vSphere, using Terraform to provision and Puppet to manage configuration.
  • Manage the full life of EC2 fleets and VMware clusters, including ESXi, vCenter, vSAN and NSX: capacity, patching, images built with Packer, AMIs, VM templates and autoscaling.
  • Design secure, resilient AWS networks using VPCs, Transit Gateway, Direct Connect, Route 53, ALB, NLB and CloudFront.
  • Run and automate F5 BIG-IP load balancers and firewalls (LTM, AFM, DNS/GTM), covering virtual servers, pools, health monitors, iRules, SSL offload and global traffic management.
  • Release game services using blue/green and canary methods, with CodeDeploy, weighted target groups, F5 pool weights and DNS-based traffic shifting.
  • Operate MySQL and PostgreSQL at scale, self-managed on VMware and EC2 and managed on Amazon RDS and Aurora.
  • Own replication, failover, backups, point-in-time recovery and disaster recovery testing.
  • Lead major-version upgrades, schema migration tooling and zero-downtime maintenance procedures.
  • Tune queries, connection pooling (ProxySQL, PgBouncer) and resource sizing for high-concurrency game workloads.
  • Build and run observability with Prometheus, Grafana, Datadog and OpenTelemetry, including database, VMware and F5 telemetry.
  • Define SLI, SLO and error budget policies, and build alerting that filters out noise.
  • Lead chaos engineering and failover drills, such as AWS Fault Injection Service, F5 HA failover and database failover, to find failures before players do.
  • Lead incident response and post-mortems, focusing on systemic fixes and making sure they are completed.
  • Remove toil through self-service provisioning, automated remediation and smarter scaling.
  • Manage server configuration at scale with Puppet, Ansible and AWS Systems Manager, including module development, Hiera data design and code promotion workflows.
  • Automate F5 configuration with AS3, iControl REST and Terraform, and keep load balancer and firewall policy as code.
  • Harden CI/CD pipelines in GitHub Actions and Jenkins.
  • Build security into the platform through secrets management (PasswordState, 1Password, AWS Secrets Manager), IAM least privilege, F5 AFM firewall policy and policy as code (OPA, AWS Config, SCPs).
  • Spread SRE practice across studios through reliability reviews, runbooks and hands-on collaboration.
  • Shape architecture decisions and write engineering RFCs that move the platform forward.

Requirements

  • 5+ years in SRE, platform engineering or equivalent infrastructure work at production scale.
  • Deep AWS experience with EC2, VPC networking, IAM, RDS/Aurora, S3, Route 53, ELB and CloudWatch.
  • Strong VMware vSphere experience with ESXi, vCenter, vSAN and/or NSX, plus bare-metal server operations.
  • Hands-on F5 BIG-IP experience with load balancers and firewalls (LTM, AFM, DNS/GTM), including iRules, SSL/TLS offload and HA pairs.
  • Production experience with MySQL and PostgreSQL, covering replication, HA and failover, backup and restore, upgrades and performance tuning.
  • Strong Terraform IaC skills and hands-on experience with Packer.
  • Deep Puppet experience with modules, Hiera, r10k or Code Manager and PuppetDB, plus Ansible and AWS Systems Manager.
  • Experience with Datadog, Prometheus, Grafana and OpenTelemetry.
  • Fluency with SLIs, SLOs and error budgets, including how to apply them inside engineering teams.
  • Production-quality code in Go, Python or TypeScript for tools, automation and internal libraries.
  • Knowledge of Linux internals, TCP/IP networking, DNS and TLS, deep enough to debug at the system level.
  • Track record leading incident response and post-mortems with systemic follow-through.
  • Nice-to-Haves: live-service game or large-scale consumer internet experience with millions of concurrent users.
  • Nice-to-Haves: database reliability engineering at scale, including sharding, read-replica fleets and Aurora Global Database or cross-region replication.
  • Nice-to-Haves: F5 automation experience (AS3, Declarative Onboarding, iControl REST) and multi-site global load balancing.
  • Nice-to-Haves: experience migrating workloads between VMware and AWS, for example with AWS Application Migration Service or VMware HCX.
  • Nice-to-Haves: FinOps and managing resources at cloud scale.
  • Nice-to-Haves: experience with AI and agentic development.
  • Nice-to-Haves: certifications such as AWS Solutions Architect, AWS Database Specialty, VMware VCP-DCV, F5 Certified Administrator, Puppet Professional or equivalent.
  • Nice-to-Haves: experience mentoring SREs or leading reliability working groups.

Conditions

Hybrid work model.

You must be legally authorized to work in the United States without current or future employer sponsorship. Visa sponsorship or assistance is not available for this role.

The company offers equal opportunity and encourages people to apply as they are.

Recruiters contact candidates only from 2K.com email accounts, never through instant messaging apps or personal email.

Where you’d work

Part of the week in the office

You can work from

  • United States

No visa sponsorship

About the company

2K

  • Industry: Gaming

Office in Austin, United States

Also hiring in Irvine, United States, United States, Montreal, Canada and 4 more places

2 of their 25 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 2 red flags

Still hiring?

13 checks

1 red flag

How crowded?

6 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Company
Tech stack
  • Python
  • Go
  • PostgreSQL
  • AWS
  • Terraform
  • Linux
  • CI/CD
  • Jenkins
  • GitHub Actions
  • Ansible
  • Prometheus
  • Grafana
  • Datadog
Seniority
Senior
Industry
Gaming
Specialty
SRE
Region
United States
Pay period
Annual
Show 7 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
SRE
Seniority
Senior
Experience
5+ years
Tech stack
  • Python
  • Go
  • PostgreSQL
  • AWS
  • Terraform
  • Linux
  • CI/CD
  • Jenkins
  • GitHub Actions
  • Ansible
  • Prometheus
  • Grafana
  • Datadog

Location

Work model
Hybrid
Region
United States
Office
  • Austin, United States
Remote from
  • United States
Visa sponsorship
Not sponsored

Compensation

Salary
Salary by agreement
Pay period
Annual

Company

Industry
Gaming

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason