Director, Enterprise Network Deployment & Automation

We need to output HTML fragment with sections: About the role? The posting includes description about NVIDIA, mission, etc. We need to decide sections: maybe "About the role" (intro), "Responsibilities" (What You'll Be Doing), "Requirements" (What We Need To See), "Qualifications" maybe not separate, "Skills" maybe not, "Benefits" (salary, equity, benefits), "Pay" (salary range), "Schedule" (Full time). Also "Job Category Engineering" and "Time Type Full time" maybe minor metadata. We must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out lines like "Applications for this job will be accepted at least until September 20, 2026." That's application instruction? It's a deadline; maybe considered application instruction? The instruction says remove application instructions. Likely we should remove that line. Also "NVIDIA uses AI tools in its recruiting processes." maybe boilerplate? It's about recruiting process; maybe keep? It's not EEO but could be considered boilerplate. Safer to remove lines about AI tools in recruiting, equal opportunity, etc. Also "NVIDIA is widely considered to be one of the technology world’s most desirable employers..." that's fluff but maybe keep as part of About the role? It's generic marketing; but we need preserve substantive information; not sure if it's substantive. It's more marketing fluff; but not prohibited. However we should avoid filler. Might keep as part of About the role. We need to include sections only when posting has real specific content. So we need sections: About the role (intro paragraph about NVIDIA mission and team). Responsibilities (What You'll Be Doing). Requirements (What We Need To See). Benefits (salary range, equity, benefits). Pay maybe separate? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Benefits and Pay separate, but we should avoid thin sections. Could combine Pay and Benefits into one Benefits section? But they said prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits (including salary range, equity, benefits). Schedule maybe we can note Full time in a short paragraph under About the role or separate? Could add Schedule section if we have content: "Time Type Full time". That's specific. Could be a short

under Schedule heading. But they said never emit a heading followed by filler/placeholder text. "Full time" is specific, not filler. So we could have Schedule section with

Full time

. However they also said do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So Time Type could be minor metadata; maybe we can fold into a short

under About the role or separate paragraph. But they said prefer few substantive sections; maybe we can include Schedule as a short paragraph without heading? But they require headings for sections; if we don't make a heading, it's just a paragraph. Could embed schedule in About the role paragraph. Similarly, Job Category Engineering could be minor metadata. Thus sections: About the role (intro + maybe job category and time type). Responsibilities. Requirements. Benefits (including salary range, equity, benefits). Possibly also "Qualifications" but we already have Requirements covering qualifications; we could skip Qualifications. We must not repeat job title as heading. No job title given explicitly; but we can ignore. Now craft HTML. We need to preserve all substantive information: Let's extract. Intro paragraph: "NVIDIA has been transforming computer graphics, PC gaming, and accelerated computing for more than 25 years. It’s a unique legacy of innovation that’s fueled by great technology—and amazing people. Today, we’re tapping into the unlimited potential of AI to define the next era of computing. An era in which our GPU acts as the brains of computers, robots, and self-driving cars that can understand the world. Doing what’s never been done before takes vision, innovation, and the world’s best talent. As an NVIDIAN, you’ll be immersed in a diverse, supportive environment where everyone is inspired to do their best work. Come join the team and see how you can make a lasting impact on the world!" Then maybe a sentence about Enterprise Infrastructure organization seeking Director... That's part of role description; could be in About the role or Responsibilities. Probably belongs to About the role: "NVIDIA's Enterprise Infrastructure organization is seeking a Director, Enterprise Network Deployment & Automation to own the global deployment of NVIDIA's enterprise network — across office sites, data centers, CM (contract manufacturing) facilities, the global backbone, SD-WAN, campus, and DC edge — and to lead the build-out of agentic AI and automation capabilities that scale capacity planning, design, deployment, and Day 2 change operations. Reporting to the Senior Director, Enterprise Networking, this leader will translate network architecture and strategy into repeatable, automated, and globally delivered deployment programs that keep pace with NVIDIA's growth." That's substantive. Now Responsibilities: list bullet points from "What You'll Be Doing". We'll convert each line to

. Responsibilities bullets: - Global deployment ownership: Own end-to-end network deployment execution across all site types — corporate offices, campuses, HPC data centers, CM/manufacturing facilities, labs — spanning the global backbone, SD-WAN/POP/WAN, campus, and DC edge. - Capacity planning & rollout: Build and scale a program that plans, designs, and deploys network capacity ahead of business demand, coordinating with Real Estate, Facilities, and Data Center Engineering on site timelines. - Agentic AI & automation: Lead the design and build of agentic AI and automation tooling to transform how the team plans capacity, designs configurations, delivers deployments, and manages Day 2 changes — reducing manual toil and human error. - Standardization & repeatability: Establish standardized, repeatable deployment methodologies (reference architectures, golden configs, automated validation/turn-up testing) so every new site, POP, or edge deployment follows a consistent, high-quality playbook. - Operational metrics & SLOs: Define and track deployment SLAs, automation coverage, and change-success metrics; build observability into the deployment pipeline itself, not just the steady-state network. - Day 2 change management: Manage the day-to-day execution of Day 2 network changes (moves/adds/changes, capacity augments, lifecycle refreshes) through automated, low-touch workflows with strong change governance. - Team building: Recruit, mentor, and grow a globally distributed team of deployment engineers, automation engineers, and program managers; build career paths and technical depth across regions. - Multi-functional partnership: Work closely with the Senior Director, Enterprise Networking and peer leaders across Architecture, Security, Cloud Engineering, and Site Reliability to ensure deployment plans align with the broader network strategy and roadmap. - Vendor & partner management: Manage vendor and contractor relationships for physical deployment work (cabling, hardware staging, installation partners) across a global site footprint. Now Requirements: "What We Need To See" bullet list. - Bachelor's degree in Computer Science, Electrical Engineering, or related technical field, or equivalent experience. - 13+ years of overall experience in network engineering, deployment, or infrastructure operations, with 6+ years of leadership experience managing distributed technical teams. - Hands-on depth in enterprise networking domains relevant to deployment: LAN/WLAN, SD-WAN/WAN, campus and DC edge, and global backbone connectivity. - Track record of standing up new physical sites (offices, data centers, CM facilities) end-to-end, from design through turn-up. - Direct experience building or deploying network automation and/or AI-driven tooling to reduce manual deployment and change effort at scale. - Experience managing Day 2 operations — change management, capacity augments, lifecycle refresh — for a large, geographically distributed network footprint. - Proven ability to build and scale high-performing, globally distributed engineering and deployment teams. - Strong program and vendor management skills, with experience coordinating multi-site rollouts against aggressive timelines. - Clear communication skills, able to align multi-functional partners (Real Estate, Facilities, Security, Cloud Engineering) around deployment plans and tradeoffs. Now Ways To Stand Out From The Crowd: these are desirable but not required; could be included under Requirements or a separate "Preferred Qualifications" section. Since we have no heading for Preferred Qualifications, we could incorporate them into Requirements as additional bullets, but they are "Ways To Stand Out". Might be okay to add as a subsection under Requirements? But we must not create thin sections. Could add them as part of Requirements but maybe label as "Preferred qualifications" within a

? However we need to preserve all substantive information; we can include them as bullet points under Requirements with a note "Preferred:" but that adds extra text not in original. Better to create a separate section "Preferred Qualifications" but that may be considered thin? It has several bullets; it's substantive. The instruction list of possible headings includes Qualifications, Skills. So we could have a section "Qualifications" for required, and "Preferred Qualifications" maybe not in list but we could still use

for Qualifications and include both required and preferred? Might be okay. Simplify: Have Requirements section include both required and preferred bullets, maybe with a note "Preferred:" but that adds text. Could just list them as bullets without distinction; still preserves info. The original separates them; but we can combine; still all info present. Thus Requirements bullets will include all from "What We Need To See" plus the "Ways To Stand Out" bullets. Let's list Ways To Stand Out bullets: - Experience deploying network infrastructure for HPC/AI data centers or GPU-dense compute environments (InfiniBand, Spectrum-X, RDMA/RoCE). - Background building agentic AI workflows or AI-assisted automation (e.g., AI agents for network design validation, config generation, or change execution) rather than only traditional scripted automation. - Experience with infrastructure-as-code and automation toolchains (Terraform, Ansible, Python, Netconf/YANG) applied specifically to deployment and turn-up pipelines. - Track record operating in a hyperscale or large enterprise environment supporting rapid physical expansion — new office builds, lab stand-ups, and data center deployments — on a global scale. - Familiarity with CM (contract manufacturing) facility networking requirements and constraints. Now Benefits/Pay/Salary: The posting says: "Your base salary will be determined based on your location, experience, and the pay of employees in similar positions. The base salary range is 284,000 USD - 425,500 USD. You will also be eligible for equity and benefits." Thus we have salary range and eligibility for equity and benefits. We'll create a Benefits section with that info. Could also include "equity and benefits". We'll put in

. Schedule: Full time. Could add a short paragraph under Benefits or separate Schedule section. Since we have a Schedule heading possible, we can make a Schedule section with

Full time

. That's specific. Now About the role section: combine intro paragraph + role description + maybe job category and time type? We'll include job category and time type maybe as a short paragraph after intro? But we already have Schedule section for time type; we could mention job category in About the role as a sentence: "Job Category: Engineering". But that's minor metadata; we could fold into a short

under About the role. Thus About the role will have:

NVIDIA has been transforming computer graphics, PC gaming, and accelerated computing for more than 25 years. It’s a unique legacy of innovation that’s fueled by great technology—and amazing people. Today, we’re tapping into the unlimited potential of AI to define the next era of computing. An era in which our GPU acts as the brains of computers, robots, and