Lead Network Engineer
Take-Two Interactive Software, Inc. · Austin, TX
—
Jul 22, 2026
Austin, TX
Jul 23, 2026
What this job asks for AI summary
A senior-level network engineering role focused on leading a global transition from traditional perimeter-based networking to Zero Trust Architecture and Infrastructure as Code. Day-to-day work spans designing and operating ZTNA and SASE solutions, building network automation pipelines with Python, Ansible, and Terraform, managing Palo Alto firewalls, Arista switches, F5 load balancers, and cloud networking on AWS and GCP, while mentoring junior engineers. Suits a seasoned network engineer with strong automation and cloud credentials.
Senior level · 8+ years · New York-Newark-Jersey City, NY-NJ-PA · Bachelor's required · 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 60 people in the New York-Newark-Jersey City, NY-NJ-PA area plausibly meet what this posting asks for (network and computer systems administrators). range 15–90
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 $122,015 (middle half $98,091–$145,542).
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 (9)
SOC classification is a genuine judgment call: the role's primary work spans network infrastructure operations (15-1244) and security architecture (Zero Trust, SASE, microsegmentation — 15-1212). The infrastructure operations and engineering framing ('Lead Network Engineer', managing physical/virtual network devices, cloud topologies, wireless) narrowly wins, but the security-architecture scope is substantial.
The title 'Lead Network Engineer' carries no standard seniority level word, so the title states no level. The 8+ years requirement and scope (mentorship, global architecture ownership) support a Senior classification.
Checkmk is listed in the requirements section but framed with 'familiarity with' — treated as preferred rather than a hard gate.
Netbox/Nautobot appear as illustrative examples ('for example Netbox, or Nautobot') in the responsibilities narrative rather than as a hard requirement — treated as preferred.
Python, Ansible, and Terraform are listed together as interchangeable examples in the requirements section ('e.g., Python, Ansible, Terraform'); however, all three are also called out individually and repeatedly throughout the responsibilities, suggesting all three are genuinely expected. They are captured as separate required skills.
AWS and GCP are listed together as examples of public cloud platforms; both are captured as required given the explicit cloud networking depth demanded.
Industry certifications (PCNSE, CCIE, CCNP, Meraki) are described as 'highly desirable' — not captured as hard-gate skills.
No compensation range is stated in the posting.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): Zero Trust Architecture.
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.