DataCenter Operations Manager
Catapult Federal Services · Dallas, TX · 3 wk ago
ManagementFull-time
We need to output HTML fragment with sections for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: role description, responsibilities (many bullet-like paragraphs), requirements (experience, knowledge), preferred experience, certifications, etc. No explicit Benefits, Pay, Schedule mentioned. So we should not include those sections. We need to use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent. Remove boilerplate like location line? The posting starts with "IT Dallas, TX Direct Hire Sep 24, 2026 Manager, Data Center IT Operations". That's metadata; we can fold minor metadata into a short
or drop it. Probably include a short
with location and date? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a
for location and date.
We need sections: About the role (maybe a summary), Responsibilities, Requirements, Qualifications, Skills? The posting includes responsibilities, requirements (experience), preferred experience, certifications, etc. Could combine Requirements and Qualifications? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include those with real content.
We have About the role: we can use the first paragraph: "This role is responsible for keeping Compass Datacenters’ internal IT environments running once facilities are live and in production. That covers the servers, networking, storage, and security infrastructure that supports our operations—not customer colocation environments."
Responsibilities: many bullet points. We'll create a
- list.
Requirements: the "8+ years in IT infrastructure roles..." etc. That's required experience.
Qualifications: maybe the certifications and preferred experience? Could treat as Qualifications.
Skills: maybe the technical skills list? Could be separate.
But we must not create thin sections. Let's see if we have enough content for each.
About the role: we have a paragraph.
Responsibilities: many items.
Requirements: we have the 8+ years etc.
Qualifications: we have certifications and preferred experience.
Skills: we have technical skills like Windows Server, VMware/Nutanix, networking fundamentals, security ops, etc. Might overlap with requirements. Could combine but we need to follow instruction: prefer a few substantive sections over many thin ones. Maybe we can combine Requirements and Qualifications into one section? But headings are predefined; we can omit sections if no real content. So we could have About the role, Responsibilities, Requirements (covering both required and preferred), Skills (maybe not needed if covered). But we need to decide.
Let's extract content:
About the role: first sentence.
Responsibilities: list items:
- Manage the team that handles day-to-day administration, monitoring, patching, and incident response across all production sites.
- When something breaks at 2 AM, your team is the one that gets the call.
- When we need to plan capacity for the next round of site launches, you’re the one building that plan.
- This is a hands-on leadership role—you need to be close enough to the technology to make good calls, and experienced enough as a manager to build and run a reliable team.
- Production Infrastructure Operations
- Server and compute: Oversee administration of Windows Server, VMware/Nutanix virtualization clusters, and associated storage environments across all production sites.
- Network operations: Own the health and performance of the production network—switches, routers, firewalls, load balancers, and WAN connectivity. Coordinate with the design team on changes and upgrades.
- Monitoring and alerting: Make sure monitoring tools are configured, thresholds are tuned, and alerts go to the right people. Reduce noise so the team can focus on what matters.
- Directory and identity services: Manage Active Directory, DNS, DHCP, and identity/access management across the environment.
- Backup and recovery: Own the backup strategy and make sure restores actually work. Run periodic recovery tests—don’t wait for a real disaster to find out.
- Security Operations
- Incident triage: Serve as the escalation point for security alerts from EDR/MDR tools. Make sure threats are investigated, contained, and resolved—not just acknowledged.
- Patching and vulnerability management: Run the patching cycle across servers, network gear, and endpoints. Track vulnerabilities, prioritize based on actual risk, and close them out on a schedule.
- Firewall and access control: Ensure firewall rules, WAF configurations, and access policies stay current and hardened. Clean up stale rules regularly.
- Compliance alignment: Work within established security frameworks (NIST, CIS, or whatever Compass adopts) and support audit and compliance activities as needed.
- Planning and Lifecycle Management
- Capacity planning: Track utilization across compute, storage, and network resources. Forecast needs based on site launch schedules and growth.
- Lifecycle management: Maintain a hardware and software lifecycle plan. Know what’s approaching end-of-life, what needs to be refreshed, and when.
- Budget ownership: Own the IT operations budget. Track spend against forecast, manage renewals, and make the case for capital when it’s needed.
- Site onboarding: Receive new sites from the construction/design team after commissioning. Validate that systems are built to standard and ready for production support.
- Team and Vendor Management
- Direct management: Lead a team of systems and network administrators. Set clear expectations, run regular 1:1s, do real performance reviews, and invest in developing your people.
- On-call and coverage: Build and maintain an on-call rotation that provides 24/7 coverage without burning the team out.
- Vendor relationships: Manage relationships with hardware, software, and support vendors. Own contract renewals, escalations, and service-level accountability.
- Incident management: Run the incident response process for major outages. Lead root cause analysis after the fact and make sure corrective actions actually get implemented.
Requirements: "8+ years in IT infrastructure roles, with at least 3 years directly managing a team. Strong working knowledge of Windows Server, Active Directory, DNS, and Group Policy. Experience with VMware vSphere or Nutanix, including cluster management, resource allocation, and troubleshooting. Solid networking fundamentals—routing, switching, VLANs, firewall administration. You don’t need to be a CCIE, but you need to be dangerous enough to troubleshoot production issues. Hands-on security operations experience: EDR/MDR triage, vulnerability management, patching cycles, and IAM administration. Experience managing IT operations across multiple sites or locations. Track record of running an on-call rotation and managing incident response for production environments."
Preferred Experience: "Experience in datacenter or critical infrastructure environments. Familiarity with BMS/OT systems from an operational monitoring perspective. Relevant certifications: MCSE, VCP, CCNA/CCNP, Security+, or similar. Experience with ITIL-based service management processes. Familiarity with infrastructure-as-code or automation tools (PowerShell, Ansible, Terraform)."
We could treat Preferred Experience as Qualifications.
Skills: maybe the technical skills list overlapped with requirements; but we could create a Skills section summarizing the technical competencies: Windows Server, AD, DNS, Group Policy, VMware vSphere/Nutanix, networking, security ops, etc. However that may duplicate.
Given instruction to prefer few substantive sections, we could have About the role, Responsibilities, Requirements (including both required and preferred), and maybe Skills (if we think it's distinct). But we could also combine Requirements and Qualifications into one section called Requirements (since they are both about qualifications). The heading list includes both Requirements and Qualifications; we can omit Qualifications if we think it's not distinct enough. But we need to ensure we don't miss content. We could put preferred experience and certifications under Qualifications.
Thus sections: About the role, Responsibilities, Requirements, Qualifications.
We'll not include Skills, Benefits, Pay, Schedule.
Now format:
Location: Dallas, TX. Posted: Sep 24, 2026. Role: Manager, Data Center IT Operations.
About the role
This role is responsible for keeping Compass Datacenters’ internal IT environments running once facilities are live and in production. That covers the servers, networking, storage, and security infrastructure that supports our operations—not customer colocation environments.
Responsibilities
- Manage the team that handles day-to-day administration, monitoring, patching, and incident response across all production sites.
- When something breaks at 2 AM, your team is the one that gets the call.
- When we need to plan capacity for the next round of site launches, you’re the one building that plan.
- This is a hands‑on leadership role—you need to be close enough to the technology to make good calls, and experienced enough as a manager to build and run a reliable team.
- Production Infrastructure Operations
- Server and compute: Oversee administration of Windows Server, VMware/Nutanix virtualization clusters, and associated storage environments across all production sites.
- Network operations: Own the health and performance of the production network—switches, routers, firewalls, load balancers, and WAN connectivity. Coordinate with the design team on changes and upgrades.
- Monitoring and alerting: Make sure monitoring tools are configured, thresholds are tuned, and alerts go to the right people. Reduce noise so the team can focus on what matters.
- Directory and identity services: Manage Active Directory, DNS, DHCP, and identity/access management across the environment.
- Backup and recovery: Own the backup strategy and make sure restores actually work. Run periodic recovery tests—don’t wait for a real disaster to find out.
- Security Operations
- Incident triage: Serve as the escalation point for security alerts from EDR/MDR tools. Make sure threats are investigated, contained, and resolved—not just acknowledged.
- Patching and vulnerability management: Run the patching cycle across servers, network gear, and endpoints. Track vulnerabilities, prioritize based on actual risk, and close them out on a schedule.
- Firewall and access control: Ensure firewall rules, WAF configurations, and access policies stay current and hardened. Clean up stale rules regularly.
- Compliance alignment: Work within established security frameworks (NIST, CIS, or whatever Compass adopts) and support audit and compliance activities as needed.
- Planning and Lifecycle Management
- Capacity planning: Track utilization across compute, storage, and network resources. Forecast needs based on site launch schedules and growth.
- Lifecycle management: Maintain a hardware and software lifecycle plan. Know what’s approaching end‑of‑life, what needs to be refreshed, and when.
- Budget ownership: Own the IT operations budget. Track spend against forecast, manage renewals, and make the case for capital when it’s needed.
- Site onboarding: Receive new sites from the construction/design team after commissioning. Validate that systems are built to standard and ready for production support.
- Team and Vendor Management
- Direct management: Lead a team of systems and network administrators. Set clear expectations, run regular 1:1s, do real performance reviews, and invest in developing your people.
- On‑call and coverage: Build and maintain an on‑call rotation that provides 24/7 coverage without burning the team out.
- Vendor relationships: Manage relationships
for prose. We need to preserve all substantive information, not invent. Remove boilerplate like location line? The posting starts with "IT Dallas, TX Direct Hire Sep 24, 2026 Manager, Data Center IT Operations". That's metadata; we can fold minor metadata into a short
or drop it. Probably include a short
with location and date? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a
for location and date. We need sections: About the role (maybe a summary), Responsibilities, Requirements, Qualifications, Skills? The posting includes responsibilities, requirements (experience), preferred experience, certifications, etc. Could combine Requirements and Qualifications? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include those with real content. We have About the role: we can use the first paragraph: "This role is responsible for keeping Compass Datacenters’ internal IT environments running once facilities are live and in production. That covers the servers, networking, storage, and security infrastructure that supports our operations—not customer colocation environments." Responsibilities: many bullet points. We'll create a
- list.
Requirements: the "8+ years in IT infrastructure roles..." etc. That's required experience.
Qualifications: maybe the certifications and preferred experience? Could treat as Qualifications.
Skills: maybe the technical skills list? Could be separate.
But we must not create thin sections. Let's see if we have enough content for each.
About the role: we have a paragraph.
Responsibilities: many items.
Requirements: we have the 8+ years etc.
Qualifications: we have certifications and preferred experience.
Skills: we have technical skills like Windows Server, VMware/Nutanix, networking fundamentals, security ops, etc. Might overlap with requirements. Could combine but we need to follow instruction: prefer a few substantive sections over many thin ones. Maybe we can combine Requirements and Qualifications into one section? But headings are predefined; we can omit sections if no real content. So we could have About the role, Responsibilities, Requirements (covering both required and preferred), Skills (maybe not needed if covered). But we need to decide.
Let's extract content:
About the role: first sentence.
Responsibilities: list items:
- Manage the team that handles day-to-day administration, monitoring, patching, and incident response across all production sites.
- When something breaks at 2 AM, your team is the one that gets the call.
- When we need to plan capacity for the next round of site launches, you’re the one building that plan.
- This is a hands-on leadership role—you need to be close enough to the technology to make good calls, and experienced enough as a manager to build and run a reliable team.
- Production Infrastructure Operations
- Server and compute: Oversee administration of Windows Server, VMware/Nutanix virtualization clusters, and associated storage environments across all production sites.
- Network operations: Own the health and performance of the production network—switches, routers, firewalls, load balancers, and WAN connectivity. Coordinate with the design team on changes and upgrades.
- Monitoring and alerting: Make sure monitoring tools are configured, thresholds are tuned, and alerts go to the right people. Reduce noise so the team can focus on what matters.
- Directory and identity services: Manage Active Directory, DNS, DHCP, and identity/access management across the environment.
- Backup and recovery: Own the backup strategy and make sure restores actually work. Run periodic recovery tests—don’t wait for a real disaster to find out.
- Security Operations
- Incident triage: Serve as the escalation point for security alerts from EDR/MDR tools. Make sure threats are investigated, contained, and resolved—not just acknowledged.
- Patching and vulnerability management: Run the patching cycle across servers, network gear, and endpoints. Track vulnerabilities, prioritize based on actual risk, and close them out on a schedule.
- Firewall and access control: Ensure firewall rules, WAF configurations, and access policies stay current and hardened. Clean up stale rules regularly.
- Compliance alignment: Work within established security frameworks (NIST, CIS, or whatever Compass adopts) and support audit and compliance activities as needed.
- Planning and Lifecycle Management
- Capacity planning: Track utilization across compute, storage, and network resources. Forecast needs based on site launch schedules and growth.
- Lifecycle management: Maintain a hardware and software lifecycle plan. Know what’s approaching end-of-life, what needs to be refreshed, and when.
- Budget ownership: Own the IT operations budget. Track spend against forecast, manage renewals, and make the case for capital when it’s needed.
- Site onboarding: Receive new sites from the construction/design team after commissioning. Validate that systems are built to standard and ready for production support.
- Team and Vendor Management
- Direct management: Lead a team of systems and network administrators. Set clear expectations, run regular 1:1s, do real performance reviews, and invest in developing your people.
- On-call and coverage: Build and maintain an on-call rotation that provides 24/7 coverage without burning the team out.
- Vendor relationships: Manage relationships with hardware, software, and support vendors. Own contract renewals, escalations, and service-level accountability.
- Incident management: Run the incident response process for major outages. Lead root cause analysis after the fact and make sure corrective actions actually get implemented.
Requirements: "8+ years in IT infrastructure roles, with at least 3 years directly managing a team. Strong working knowledge of Windows Server, Active Directory, DNS, and Group Policy. Experience with VMware vSphere or Nutanix, including cluster management, resource allocation, and troubleshooting. Solid networking fundamentals—routing, switching, VLANs, firewall administration. You don’t need to be a CCIE, but you need to be dangerous enough to troubleshoot production issues. Hands-on security operations experience: EDR/MDR triage, vulnerability management, patching cycles, and IAM administration. Experience managing IT operations across multiple sites or locations. Track record of running an on-call rotation and managing incident response for production environments."
Preferred Experience: "Experience in datacenter or critical infrastructure environments. Familiarity with BMS/OT systems from an operational monitoring perspective. Relevant certifications: MCSE, VCP, CCNA/CCNP, Security+, or similar. Experience with ITIL-based service management processes. Familiarity with infrastructure-as-code or automation tools (PowerShell, Ansible, Terraform)."
We could treat Preferred Experience as Qualifications.
Skills: maybe the technical skills list overlapped with requirements; but we could create a Skills section summarizing the technical competencies: Windows Server, AD, DNS, Group Policy, VMware vSphere/Nutanix, networking, security ops, etc. However that may duplicate.
Given instruction to prefer few substantive sections, we could have About the role, Responsibilities, Requirements (including both required and preferred), and maybe Skills (if we think it's distinct). But we could also combine Requirements and Qualifications into one section called Requirements (since they are both about qualifications). The heading list includes both Requirements and Qualifications; we can omit Qualifications if we think it's not distinct enough. But we need to ensure we don't miss content. We could put preferred experience and certifications under Qualifications.
Thus sections: About the role, Responsibilities, Requirements, Qualifications.
We'll not include Skills, Benefits, Pay, Schedule.
Now format:
Location: Dallas, TX. Posted: Sep 24, 2026. Role: Manager, Data Center IT Operations.
About the role
This role is responsible for keeping Compass Datacenters’ internal IT environments running once facilities are live and in production. That covers the servers, networking, storage, and security infrastructure that supports our operations—not customer colocation environments.
Responsibilities
- Manage the team that handles day-to-day administration, monitoring, patching, and incident response across all production sites.
- When something breaks at 2 AM, your team is the one that gets the call.
- When we need to plan capacity for the next round of site launches, you’re the one building that plan.
- This is a hands‑on leadership role—you need to be close enough to the technology to make good calls, and experienced enough as a manager to build and run a reliable team.
- Production Infrastructure Operations
- Server and compute: Oversee administration of Windows Server, VMware/Nutanix virtualization clusters, and associated storage environments across all production sites.
- Network operations: Own the health and performance of the production network—switches, routers, firewalls, load balancers, and WAN connectivity. Coordinate with the design team on changes and upgrades.
- Monitoring and alerting: Make sure monitoring tools are configured, thresholds are tuned, and alerts go to the right people. Reduce noise so the team can focus on what matters.
- Directory and identity services: Manage Active Directory, DNS, DHCP, and identity/access management across the environment.
- Backup and recovery: Own the backup strategy and make sure restores actually work. Run periodic recovery tests—don’t wait for a real disaster to find out.
- Security Operations
- Incident triage: Serve as the escalation point for security alerts from EDR/MDR tools. Make sure threats are investigated, contained, and resolved—not just acknowledged.
- Patching and vulnerability management: Run the patching cycle across servers, network gear, and endpoints. Track vulnerabilities, prioritize based on actual risk, and close them out on a schedule.
- Firewall and access control: Ensure firewall rules, WAF configurations, and access policies stay current and hardened. Clean up stale rules regularly.
- Compliance alignment: Work within established security frameworks (NIST, CIS, or whatever Compass adopts) and support audit and compliance activities as needed.
- Planning and Lifecycle Management
- Capacity planning: Track utilization across compute, storage, and network resources. Forecast needs based on site launch schedules and growth.
- Lifecycle management: Maintain a hardware and software lifecycle plan. Know what’s approaching end‑of‑life, what needs to be refreshed, and when.
- Budget ownership: Own the IT operations budget. Track spend against forecast, manage renewals, and make the case for capital when it’s needed.
- Site onboarding: Receive new sites from the construction/design team after commissioning. Validate that systems are built to standard and ready for production support.
- Team and Vendor Management
- Direct management: Lead a team of systems and network administrators. Set clear expectations, run regular 1:1s, do real performance reviews, and invest in developing your people.
- On‑call and coverage: Build and maintain an on‑call rotation that provides 24/7 coverage without burning the team out.
- Vendor relationships: Manage relationships