Cloud Systems Engineer II at Take-Two Interactive Software, Inc.
Austin, TX
—
Jul 23, 2026
Austin, TX
Jul 25, 2026
What this job asks for AI summary
A cloud infrastructure role focused on designing, deploying, and maintaining scalable systems across AWS and GCP. Day-to-day work centers on managing infrastructure-as-code with Terraform, building CI/CD pipelines via GitHub Actions, and writing Python automation tooling. The position also involves mentoring junior engineers, participating in on-call rotations, and collaborating with development, security, and networking teams. Suits engineers with strong cloud-native and Linux backgrounds.
Senior level · New York-Newark-Jersey City, NY-NJ-PA · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 510 people in the New York-Newark-Jersey City, NY-NJ-PA area plausibly meet what this posting asks for (software developers). range 190–660
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $170,499 (middle half $133,523–$210,499).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
This role sits at the boundary between software development (writing Terraform modules, Python automation, CI/CD pipelines) and infrastructure/systems administration (cloud ops, on-call, networking). It was classified as Software Developers (15-1252) because the JD emphasizes writing and shipping code — Terraform IaC, Python tooling, CI/CD pipelines — over merely operating existing systems. 15-1244 is a genuine runner-up given the strong infrastructure operations and on-call responsibilities.
The AWS sub-services (EC2, ECS/EKS, RDS, EBS, S3, Lambda, IAM, VPC) are explicitly enumerated under the 'What You Bring' requirements section and are treated as hard gates alongside the parent AWS requirement.
Ansible and Puppet are listed together under 'Great to Have' as interchangeable configuration management options; Ansible is the primary name with Puppet in alternatives.
Datadog, Grafana, Prometheus, and CheckMK are listed together under 'Great to Have' as interchangeable observability stack options.
AWS Transit Gateway and PrivateLink appear under 'Great to Have' as examples of advanced networking patterns; GCP VPC peering was omitted as a separate skill since it is a sub-feature of GCP rather than a distinct named tool.
No compensation range is stated in the posting.
The title 'Cloud Systems Engineer' carries no explicit seniority level word, so advertised seniority is Unspecified. However, the scope — mentoring junior/mid engineers, leading CI/CD design, architecting for high availability, driving post-incident reviews — supports a Senior classification.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.