Durham, NC

Salary
$94,000–$125,000from the description
Posted
Jul 27, 2026
Location
Durham, NC
Last confirmed open
Jul 29, 2026

What this job asks for AI summary

A hands-on network engineering role at a healthcare/genomics company, responsible for designing, operating, and improving hybrid network infrastructure spanning campus, laboratory, data center, and AWS cloud environments. The position involves configuring and troubleshooting Juniper/Aruba switching and routing, Palo Alto firewalls, and AWS networking services, while also developing automation to improve provisioning and operational consistency. On-site presence in Durham, NC (RTP) is required, along with participation in an on-call rotation.

Mid level · 4+ years · Durham-Chapel Hill, NC · Full-time

Quick apply — this platform usually takes a CV and a few fields.

Must have (14)
Juniper or Aruba · 3+ yrsPalo Alto Networks · 3+ yrsAWS · 2+ yrsOSPFVLANsSTPLACPVRRPPython, Ansible, Terraform or PowerShellNew Relic or SolarwindsLinuxWindowsGlobalProtectAWS Transit Gateway
Nice to have (12)
AWS Direct ConnectEVPN/VXLANAruba CXAruba CentralGitCI/CDVMware vSphereDNSDHCPActive DirectoryPKIRADIUS

“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 50 people in the Durham-Chapel Hill, NC area plausibly meet what this posting asks for (network and computer systems administrators). range 10–90

Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.

What won't set you apart
Linux75%Juniper55%Python51%Ansible51%Terraform51%AWS50%New Relic45%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $113,073 (middle half $83,507–$143,365). This posting is about at that midpoint.

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 29, 2026. It is a model, not a headcount.

Why we read it this way (6)

The role sits at the boundary between network operations (15-1244) and infrastructure software development (15-1252). The posting explicitly frames it as 'engineering-focused rather than a traditional network operations position' and requires Python/Ansible/Terraform automation development; however, the primary day-to-day work is designing, operating, and troubleshooting network infrastructure (switching, routing, firewalls, cloud networking), which aligns more closely with 15-1244. 15-1252 is noted as a genuine runner-up.

The title 'Network Engineer II' maps to a Mid-level band. The 4+ year overall experience requirement and 2–3 year per-technology requirements are consistent with a Mid-level role.

The degree requirement states 'Bachelor's degree … or equivalent practical experience,' so no hard degree gate is set.

Python, Ansible, Terraform, and PowerShell are listed together as interchangeable automation options in the required qualifications; they are emitted as a group with alternatives. However, each also appears independently in the responsibilities and preferred sections, so they are individually meaningful.

DNS and DHCP appear in the required troubleshooting list but are not named as standalone technology skills with dedicated experience requirements; they are included as preferred to reflect their presence in the posting.

The posting mentions 'AI-assisted engineering tools' in both responsibilities and preferred qualifications; this is a methodology/approach rather than a named technology and is omitted from the skills list per extraction rules.

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.

Apply

Apply on employer site ↗