Director, Network and Data Center Services
Yale University · New Haven, CT · 1 mo ago
OTHR$165k–$248k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes introductory paragraph about Yale and role. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We have content for About the role (intro paragraph). Responsibilities: there is a list of responsibilities under "Key Responsibilities" with subheadings but we can treat as list items. Requirements: maybe "Key Qualifications" and "Required Education and Experience". Skills: "Required Skills And Abilities" and "Skills and Abilities". Benefits: none given. Pay: we have Salary Range $165,000.00 - $247,500.00. Schedule: we have Time Type Full time, Duration Type Staff, Work Model Hybrid. That's schedule info. So we can include Pay and Schedule sections.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, background check, health requirements, posting disclaimer, etc. Also remove duplicated lines.
We need to preserve all substantive information. So we need to include the intro paragraph about Yale and role. Then responsibilities list. Then qualifications (key qualifications + required education/experience). Then skills (required skills and abilities). Then pay (salary range). Then schedule (full time, hybrid). Possibly also include "Work Model Hybrid". Also maybe include "Duration Type Staff". We'll put schedule details.
We must use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We have content for About the role (intro paragraph). Responsibilities: there is a list of responsibilities under "Key Responsibilities" with subheadings but we can treat as list items. Requirements: maybe "Key Qualifications" and "Required Education and Experience". Skills: "Required Skills And Abilities" and "Skills and Abilities". Benefits: none given. Pay: we have Salary Range $165,000.00 - $247,500.00. Schedule: we have Time Type Full time, Duration Type Staff, Work Model Hybrid. That's schedule info. So we can include Pay and Schedule sections.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, background check, health requirements, posting disclaimer, etc. Also remove duplicated lines.
We need to preserve all substantive information. So we need to include the intro paragraph about Yale and role. Then responsibilities list. Then qualifications (key qualifications + required education/experience). Then skills (required skills and abilities). Then pay (salary range). Then schedule (full time, hybrid). Possibly also include "Work Model Hybrid". Also maybe include "Duration Type Staff". We'll put schedule details.
We must use - for any list of duties/requirements/benefits. For prose use
. For headings use
.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
Let's extract content.
Intro: "Working at Yale means contributing to a better tomorrow. Whether you are a current resident of our New Haven-based community, eligible for opportunities through the New Haven Hiring Initiative, or a newcomer, interested in exploring all that Yale has to offer, your talents and contributions are welcome. Discover your opportunities at Yale! Yale ITS is seeking a senior technical leader to lead Network Engineering, Network Operations, and Data Center Services—responsible for the design, reliability, and evolution of Yale’s campus‑wide communication and hosting infrastructure. This role combines engineering authority, operational accountability, and transformation leadership, with responsibility for: A software-defined campus networkA mandate to improve network operations through automation, observability, and disciplineTwo capacity‑constrained, at‑risk on‑prem data centers, a nearby co-lo and a cloud interconnection co-lo This leader will drive end‑to‑end ownership of core network infrastructure, ensuring Yale’s network and data center platforms are resilient, scalable, and operationally excellent."
We need to keep that as prose. Could split into paragraphs but okay.
Responsibilities: Under "Key Responsibilities" there are bullet-like paragraphs. We'll extract each bullet as list item.
List items:
- Network Strategy, Engineering & Transformation
- Manage the architecture, engineering, and lifecycle management of Yale’s software-defined campus network
- Define standards for: performance, resiliency, segmentation, and security
- Drive modernization toward automated, code-defined network operations and integrated observability and telemetry
- Network Operations Transformation
- Own 24x7 network operations, including availability, performance, and incident response
- Lead transformation of network operations tooling transitioning from LogicMonitor / Cisco-native tools → next-gen platforms (e.g., Datadog)
- Establish disciplined operational practices around monitoring, alerting, escalation, and incident management
- Improve key metrics and publish live network data for ITS leadership: MTTR, uptime, latency, incident recurrence
- Data Center Strategy & Execution
- Own the end-to-end roadmap for Yale’s data centers, addressing: Capacity constraints; Operational risk; Lack of appropriate resiliency and DR capability
- Define and execute a multi-year strategy across: On-prem, colo, and cloud integration; Improved resiliency; Scalable capacity to support research and enterprise growth
- Resiliency & Reliability Engineering
- Embed resiliency by design across network and data center services by eliminating single points of failure and ensure network failover and recovery capabilities are validated
- Drive alignment with Disaster Recovery (RTO/RPO) targets
- Network Automation Champion
- Champion automation across infrastructure operations: Network automation; Data center workflows; Configuration and lifecycle management
- Partner with Automation Engineering to shift toward Infrastructure as Code an reduce manual intervention and operational risk
- Observability & Tooling Integration
- Build a unified observability model across networks, data centers, and facilities/campus operations
- Ensure monitoring tools provide end to end network visibility with actionable alerts integrated with incident management
- Team Leadership & Culture
- Lead and develop network engineering, operations, and data center teams while building a culture of ownership and accountability, engineering rigor, and an automation-first mindset
- Improve team capabilities in software-defined networking, automation and observability, and modern operations practices
- Cross-Functional Collaboration & Influence
- Work closely with core infrastructure engineering, TechOps, and Information security
- Navigate a federated organization, influencing without direct authority
- Align network and data center strategy with broader IT Stability initiatives, faculty and research needs.
We could flatten but okay.
Qualifications: "Key Qualifications" list:
- Proven leadership of large scale network and infrastructure environments (campus or enterprise, with hybrid cloud environments)
- Deep technical expertise in: Enterprise networking (LAN/WAN, SDN, campus networks, large Cisco implementation); Data center infrastructure (power, cooling, compute integration); Observability and monitoring platforms
- Experience leading 24x7 network operations environments and major transformation initiatives (tooling, architecture, operating model)
- Strong understanding of resiliency engineering, DR design and ITSM processes (incident, change, problem management)
Then "Leadership Capabilities" list:
- Technical authority with credibility across engineering and operations
- Execution-focused leader with strong delivery discipline
- Ability to hold teams accountable while developing talent
- Strong communicator translating complexity into clear direction
- Proven ability to influence across organizational boundaries
Then "Success criteria for the ideal candidate are a highly available, observable resilient network, reduced risk of our data center fabric, predictable metric-drive network ops, reduced toil and increased automation. A team that reduce toil while embracing automation and exhibit a strong engineering culture." That's prose.
Then "Required Education and Experience": Bachelor’s Degree in related field and 10 years of related experience or the equivalent combination of education and experience.
We can combine qualifications and required education into a Requirements section? The instruction says use headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Requirements and Qualifications separate. We could put qualifications under Qualifications heading, and required education/experience under Requirements heading. Or we could merge but better to follow headings.
Thus:
Requirements
with
Bachelor’s Degree in related field and 10 years of related experience or the equivalent combination of education and experience.
Qualifications
with - ... items ...
plus maybe the leadership capabilities list also under Qualifications? Could be separate but we can include all qualification items.
Skills: "Required Skills And Abilities" and "Skills and Abilities" (duplicate). We'll combine.
List:
- Comprehensive analytical, critical thinking and problem-solving skills.
- Comprehensive interpersonal, written, communication, presentation, and organizational skills.
- Expert ability to run meetings with senior leaders/stakeholders.
- Proven ability to lead and manage large staff.
- Proven ability to manage multiple/complex projects, meeting deadlines and budget.
We should not duplicate.
Pay: Salary Range $165,000.00 - $247,500.00.
Schedule: Time Type Full time, Duration Type Staff, Work Model Hybrid.
We'll output as Full time, Staff, Hybrid work model.
maybe.
Now ensure we don't include any boilerplate like background check, health requirements, posting disclaimer, EEO, etc.
Let's craft HTML.
We'll start with About the role
... intro ...
Then Responsibilities
with list items. Each responsibility could be a - containing maybe sublist? But spec says use
- for any list of duties/requirements/benefits. It didn't forbid nested lists but we can keep flat. Could include sub-bullets as separate
- but might lose hierarchy. Could embed sub-points within same
- using commas or semicolons. Simpler: each main heading as
- with sub-points as sentences inside same
- . That satisfies list.
Thus each
- will contain the heading and its details.
Let's craft.
Responsibilities items:
- Network Strategy, Engineering & Transformation: Manage the architecture, engineering, and lifecycle management of Yale’s software-defined campus network; define standards for performance, resiliency, segmentation, and security; drive modernization toward automated, code-defined network operations and integrated observability and telemetry.
- Network Operations Transformation: Own 24x7 network operations, including availability, performance, and incident response; lead transformation of network operations tooling transitioning from LogicMonitor / Cisco-native tools → next-gen platforms (e.g., Datadog); establish disciplined operational practices around monitoring, alerting, escalation, and incident management; improve key metrics and publish live network data for ITS leadership: MTTR, uptime, latency, incident recurrence.
- Data Center Strategy & Execution: Own the end-to-end roadmap for Yale’s data centers, addressing capacity constraints, operational risk, and lack of appropriate resiliency and DR capability; define and execute a multi-year strategy across on-prem, colo, and cloud integration; improved resiliency; scalable capacity to support research and enterprise growth.
- Resiliency & Reliability Engineering: Embed resiliency by design across network and data center services by eliminating single points of failure and ensure network failover and recovery capabilities are validated; drive alignment with Disaster Recovery (RTO/RPO) targets.
- Network Automation Champion: Champion automation across infrastructure operations: network automation, data center workflows, configuration and lifecycle management; partner with Automation Engineering to shift toward Infrastructure as Code to reduce manual intervention and operational risk.
- Observability & Tooling Integration: Build a unified observability model across networks, data centers, and facilities/campus operations; ensure monitoring tools provide end‑to‑end network visibility with actionable alerts integrated with incident management.
- Team Leadership & Culture: Lead and develop network engineering, operations, and data center teams while building a culture of ownership and accountability, engineering rigor, and an automation‑first mindset; improve team capabilities in software‑defined networking, automation and observability, and modern operations practices.
- Cross‑Functional Collaboration & Influence: Work closely with core infrastructure engineering, TechOps, and Information security; navigate a federated organization, influencing without direct authority; align network and data center strategy with broader IT Stability initiatives, faculty and research needs.
Now Qualifications items:
- Proven leadership of large scale network and infrastructure environments (campus or enterprise, with hybrid cloud environments).
- Deep technical expertise in enterprise networking (LAN/WAN, SDN, campus networks, large Cisco implementation); data center infrastructure (power, cooling, compute integration); observability and monitoring platforms.
- Experience leading 24x7 network operations environments and major transformation initiatives (tooling, architecture, operating model).
- Strong understanding of resiliency engineering, DR design and ITSM processes (incident, change, problem management).
- Technical authority with credibility across engineering and operations.
- Execution‑focused leader with strong delivery discipline.
- Ability to hold teams accountable while developing talent.
- Strong communicator translating complexity into clear
. For headings use
.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
Let's extract content.
Intro: "Working at Yale means contributing to a better tomorrow. Whether you are a current resident of our New Haven-based community, eligible for opportunities through the New Haven Hiring Initiative, or a newcomer, interested in exploring all that Yale has to offer, your talents and contributions are welcome. Discover your opportunities at Yale! Yale ITS is seeking a senior technical leader to lead Network Engineering, Network Operations, and Data Center Services—responsible for the design, reliability, and evolution of Yale’s campus‑wide communication and hosting infrastructure. This role combines engineering authority, operational accountability, and transformation leadership, with responsibility for: A software-defined campus networkA mandate to improve network operations through automation, observability, and disciplineTwo capacity‑constrained, at‑risk on‑prem data centers, a nearby co-lo and a cloud interconnection co-lo This leader will drive end‑to‑end ownership of core network infrastructure, ensuring Yale’s network and data center platforms are resilient, scalable, and operationally excellent."
We need to keep that as prose. Could split into paragraphs but okay.
Responsibilities: Under "Key Responsibilities" there are bullet-like paragraphs. We'll extract each bullet as list item.
List items:
- Network Strategy, Engineering & Transformation
- Manage the architecture, engineering, and lifecycle management of Yale’s software-defined campus network
- Define standards for: performance, resiliency, segmentation, and security
- Drive modernization toward automated, code-defined network operations and integrated observability and telemetry
- Network Operations Transformation
- Own 24x7 network operations, including availability, performance, and incident response
- Lead transformation of network operations tooling transitioning from LogicMonitor / Cisco-native tools → next-gen platforms (e.g., Datadog)
- Establish disciplined operational practices around monitoring, alerting, escalation, and incident management
- Improve key metrics and publish live network data for ITS leadership: MTTR, uptime, latency, incident recurrence
- Data Center Strategy & Execution
- Own the end-to-end roadmap for Yale’s data centers, addressing: Capacity constraints; Operational risk; Lack of appropriate resiliency and DR capability
- Define and execute a multi-year strategy across: On-prem, colo, and cloud integration; Improved resiliency; Scalable capacity to support research and enterprise growth
- Resiliency & Reliability Engineering
- Embed resiliency by design across network and data center services by eliminating single points of failure and ensure network failover and recovery capabilities are validated
- Drive alignment with Disaster Recovery (RTO/RPO) targets
- Network Automation Champion
- Champion automation across infrastructure operations: Network automation; Data center workflows; Configuration and lifecycle management
- Partner with Automation Engineering to shift toward Infrastructure as Code an reduce manual intervention and operational risk
- Observability & Tooling Integration
- Build a unified observability model across networks, data centers, and facilities/campus operations
- Ensure monitoring tools provide end to end network visibility with actionable alerts integrated with incident management
- Team Leadership & Culture
- Lead and develop network engineering, operations, and data center teams while building a culture of ownership and accountability, engineering rigor, and an automation-first mindset
- Improve team capabilities in software-defined networking, automation and observability, and modern operations practices
- Cross-Functional Collaboration & Influence
- Work closely with core infrastructure engineering, TechOps, and Information security
- Navigate a federated organization, influencing without direct authority
- Align network and data center strategy with broader IT Stability initiatives, faculty and research needs.
We could flatten but okay.
Qualifications: "Key Qualifications" list:
- Proven leadership of large scale network and infrastructure environments (campus or enterprise, with hybrid cloud environments)
- Deep technical expertise in: Enterprise networking (LAN/WAN, SDN, campus networks, large Cisco implementation); Data center infrastructure (power, cooling, compute integration); Observability and monitoring platforms
- Experience leading 24x7 network operations environments and major transformation initiatives (tooling, architecture, operating model)
- Strong understanding of resiliency engineering, DR design and ITSM processes (incident, change, problem management)
Then "Leadership Capabilities" list:
- Technical authority with credibility across engineering and operations
- Execution-focused leader with strong delivery discipline
- Ability to hold teams accountable while developing talent
- Strong communicator translating complexity into clear direction
- Proven ability to influence across organizational boundaries
Then "Success criteria for the ideal candidate are a highly available, observable resilient network, reduced risk of our data center fabric, predictable metric-drive network ops, reduced toil and increased automation. A team that reduce toil while embracing automation and exhibit a strong engineering culture." That's prose.
Then "Required Education and Experience": Bachelor’s Degree in related field and 10 years of related experience or the equivalent combination of education and experience.
We can combine qualifications and required education into a Requirements section? The instruction says use headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Requirements and Qualifications separate. We could put qualifications under Qualifications heading, and required education/experience under Requirements heading. Or we could merge but better to follow headings.
Thus:
Requirements
with
Bachelor’s Degree in related field and 10 years of related experience or the equivalent combination of education and experience.
Qualifications
with- ... items ...
Full time, Staff, Hybrid work model.
maybe. Now ensure we don't include any boilerplate like background check, health requirements, posting disclaimer, EEO, etc. Let's craft HTML. We'll start withAbout the role
... intro ...
ThenResponsibilities
- with list items. Each responsibility could be a
- containing maybe sublist? But spec says use
- for any list of duties/requirements/benefits. It didn't forbid nested lists but we can keep flat. Could include sub-bullets as separate
- but might lose hierarchy. Could embed sub-points within same
- using commas or semicolons. Simpler: each main heading as
- with sub-points as sentences inside same
- . That satisfies list. Thus each
- will contain the heading and its details. Let's craft. Responsibilities items:
- Network Strategy, Engineering & Transformation: Manage the architecture, engineering, and lifecycle management of Yale’s software-defined campus network; define standards for performance, resiliency, segmentation, and security; drive modernization toward automated, code-defined network operations and integrated observability and telemetry.
- Network Operations Transformation: Own 24x7 network operations, including availability, performance, and incident response; lead transformation of network operations tooling transitioning from LogicMonitor / Cisco-native tools → next-gen platforms (e.g., Datadog); establish disciplined operational practices around monitoring, alerting, escalation, and incident management; improve key metrics and publish live network data for ITS leadership: MTTR, uptime, latency, incident recurrence.
- Data Center Strategy & Execution: Own the end-to-end roadmap for Yale’s data centers, addressing capacity constraints, operational risk, and lack of appropriate resiliency and DR capability; define and execute a multi-year strategy across on-prem, colo, and cloud integration; improved resiliency; scalable capacity to support research and enterprise growth.
- Resiliency & Reliability Engineering: Embed resiliency by design across network and data center services by eliminating single points of failure and ensure network failover and recovery capabilities are validated; drive alignment with Disaster Recovery (RTO/RPO) targets.
- Network Automation Champion: Champion automation across infrastructure operations: network automation, data center workflows, configuration and lifecycle management; partner with Automation Engineering to shift toward Infrastructure as Code to reduce manual intervention and operational risk.
- Observability & Tooling Integration: Build a unified observability model across networks, data centers, and facilities/campus operations; ensure monitoring tools provide end‑to‑end network visibility with actionable alerts integrated with incident management.
- Team Leadership & Culture: Lead and develop network engineering, operations, and data center teams while building a culture of ownership and accountability, engineering rigor, and an automation‑first mindset; improve team capabilities in software‑defined networking, automation and observability, and modern operations practices.
- Cross‑Functional Collaboration & Influence: Work closely with core infrastructure engineering, TechOps, and Information security; navigate a federated organization, influencing without direct authority; align network and data center strategy with broader IT Stability initiatives, faculty and research needs. Now Qualifications items:
- Proven leadership of large scale network and infrastructure environments (campus or enterprise, with hybrid cloud environments).
- Deep technical expertise in enterprise networking (LAN/WAN, SDN, campus networks, large Cisco implementation); data center infrastructure (power, cooling, compute integration); observability and monitoring platforms.
- Experience leading 24x7 network operations environments and major transformation initiatives (tooling, architecture, operating model).
- Strong understanding of resiliency engineering, DR design and ITSM processes (incident, change, problem management).
- Technical authority with credibility across engineering and operations.
- Execution‑focused leader with strong delivery discipline.
- Ability to hold teams accountable while developing talent.
- Strong communicator translating complexity into clear