Technical Project Manager, GPU Infrastructure Deployment
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, application instructions, etc.
We need to parse the posting.
Key info:
- Job title: Technical Project Manager, GPU Infrastructure Deployment (but we don't repeat as heading)
- Department: Cloud,Ops
- Location: USA (Washington, D.C., Phoenix (AZ), Memphis (TN), Columbus (OH), or nearby regions)
- Work Arrangement: Remote
- Travel Requirements: Up to 25%
- Salary Range: $155K–$175K
- Role Summary: paragraph.
- How We Work At 5C: core values etc (maybe not needed? It's generic; but we could include as About the role? Actually "How We Work At 5C" is generic values; but we might include as About the role? The instruction: include a section only when posting has real, specific content for it. "How We Work At 5C" is somewhat generic but still content about company values. Could be considered "About the role" or "About the company". But we have no explicit "About the role" heading; we could create "About the role" using the Role Summary paragraph. That seems appropriate.
- What You Will Do: list of duties (many bullet-like sentences). This is responsibilities.
- What You Bring: similar to responsibilities but repeated; it's qualifications/requirements.
- What Sets You Apart: specific skills/experience.
- Why Join 5C Data Centers?: includes Career Growth, Industry Leadership, Entrepreneurial Culture, Comprehensive Rewards, Life at 5C. This could be Benefits? But we have specific benefits not listed; only "Competitive pay plus meaningful, lasting impact". That's vague. We have Salary Range already. Benefits not detailed. So we should not create Benefits section unless specific. The posting mentions "Comprehensive Rewards Competitive pay plus meaningful, lasting impact on the work you do." That's not specific benefits like health insurance etc. So we should not create Benefits section.
- Pay: we have Salary Range $155K–$175K. So we can create Pay section with that.
- Schedule: not mentioned besides Remote and Travel up to 25%. No specific schedule like full-time, hours. Not given. So we should not create Schedule section unless we have specifics. Could we infer full-time? Not given. Better to omit.
- Requirements/Qualifications: we have "What You Bring" and "What Sets You Apart". Could combine into Requirements/Qualifications and Skills. But we need to follow headings: we can have Responsibilities (Responsibilities
) with list from "What You Will Do". Then Requirements (Requirements
) maybe combine "What You Bring" and "What Sets You Apart". Or we could have Qualifications and Skills separate. But we should not create thin sections. Better to have one Requirements section that includes both.
We also need to include location, work arrangement, travel as maybe a short paragraph under About the role or separate? The instruction: Use
for prose. Could include a short paragraph after the heading "About the role" that includes role summary plus location etc. Or we could have a separate "About the role" heading with paragraph containing role summary, location, work arrangement, travel. That seems appropriate. We must not repeat job title as heading. So we will not have heading for job title. We need to output only HTML fragment, no or . Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them as lists.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the EEO statement at end, also "Ready to Apply?" and "Apply today..." and the EEO paragraph. Also remove "How We Work At 5C" maybe? It's somewhat values; but it's not boilerplate; it's specific to company culture. Could keep as part of About the role? But it's not directly about the role; it's about company. However we could incorporate into About the role? Might be considered filler? It's not generic like "commensurate with experience". It's specific: "Our core values guide how we collaborate, make decisions, support one another, and serve our customers. We're looking for people who embrace them and help us build something great." That's somewhat generic but still company-specific. Might be okay to include as part of About the role? But we already have role summary. Could add a separate section "About the Company" but not in allowed headings list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put that content under About the role as prose.
Thus About the role section will contain: Role Summary paragraph, location, work arrangement, travel, maybe core values.
We need to ensure we don't duplicate content. The "What You Will Do" and "What You Bring" are duplicated exactly; we should not duplicate content. The posting has the same block repeated under "What You Will Do" and "What You Bring". We need to preserve all substantive information but not duplicate lines. So we should include each unique piece only once. Since they are identical, we should include it once under Responsibilities (or Requirements). Probably under Responsibilities (what you will do). Then for Requirements we can include "What Sets You Apart" plus maybe any additional qualifications not already covered. The "What You Bring" is duplicate, so we skip it.
Thus we need to extract unique bullet-like sentences from "What You Will Do". Let's list them:
- Lead end-to-end project management for large-scale AI/GPU cluster deployments, including multi-rack GPU compute platforms (NVIDIA DGX and similar), InfiniBand and Ethernet GPU fabrics, and high-performance storage environments (e.g., VAST Data).
- Partner with engineering teams and managers to establish and drive consistent project tracking, milestone reporting, and status updates across the team and systems (e.g., Jira, Confluence).
- Coordinate procurement, rack-and-stack sequencing, cabling schedules, network deployment timelines, burn-in testing, cluster validation, and operational handoff.
- Coordinate with facilities engineering and datacenter operations to align MEP readiness (power distribution, cooling capacity, floor layout, containment) with deployment schedules.
- Communicate project status, risks, milestones, and dependencies to stakeholders at all levels including executive leadership.
- Prepare and present regular program reviews, steering committee updates, and ad-hoc project analyses.
- Maintain centralized project documentation and ensure consistent, accurate data.
- Contribute to improving and documenting repeatable deployment methodologies, scalable operational standards, and project management best practices.
- Track deployment KPIs (schedule variance, budget adherence, quality metrics) and drive continuous improvement through data-driven retrospectives.
That's 9 items.
Now "What Sets You Apart" bullet list:
- Experience with hyperscale cloud providers, large-scale data center deployments, or AI infrastructure programs.
- Familiarity with:
- Infrastructure-as-Code and configuration management (Ansible)
- Python, Shell, and SQL for infrastructure automation and diagnostics
- DCIM, BMS, and observability platforms for liquid-cooled environments
- NVIDIA/Mellanox networking platforms and NVLink/NVSwitch technologies
- Experience coordinating with MEP engineering teams on electrical and cooling infrastructure scheduling for large-scale deployments.
- Experience with procurement processes in infrastructure delivery contexts.
We need to format as list. The sub-items under Familiarity with could be nested list? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep as separate items. Could flatten: each bullet as separate
- . Might be okay to keep sub-bullets as separate
- under a parent? But we need to preserve all detail. Could do:
- Experience with hyperscale cloud providers, large-scale data center deployments, or AI infrastructure programs.
- Familiarity with:
- Infrastructure-as-Code and configuration management (Ansible)
- Python, Shell, and SQL for infrastructure automation and diagnostics
- DCIM, BMS, and observability platforms for liquid-cooled environments
- NVIDIA/Mellanox networking platforms and NVLink/NVSwitch technologies
- Experience coordinating with MEP engineering teams on electrical and cooling infrastructure scheduling for large-scale deployments.
- Experience with procurement processes in infrastructure delivery contexts.
That preserves detail.
Now About the role section: we need to include role summary paragraph, location, work arrangement, travel, maybe core values.
Role Summary paragraph: "We are seeking a Technical Project Manager (TPM) to drive the planning, coordination, and execution of large-scale GPU cluster infrastructure deployment programs. This role partners across multiple engineering teams to manage project schedules, track milestones, resolve blockers, and communicate status across technical teams, datacenter operations, engineering, and external vendors. The TPM operates at the intersection of program leadership and hands-on technical deployment, ensuring that end-to-end GPU cluster buildouts - spanning compute, high-speed networking fabrics, high-performance storage, power, cooling, and automation - are delivered on time, within budget, and to operational readiness standards. This includes coordinating mechanical, electrical, and plumbing (MEP) readiness with facilities engineering and datacenter operations to ensure power capacity, cooling distribution, and physical infrastructure are in place ahead of rack-and-stack. The ideal candidate brings strong technical project management expertise in hyperscale or cloud infrastructure environments, combined with a working understanding of AI/GPU deployment lifecycles and cross-functional program execution."
Location: "USA (Washington, D.C., Phoenix (AZ), Memphis (TN), Columbus (OH), or nearby regions)". Work Arrangement: "Remote". Travel Requirements: "Up to 25%". Could combine into a paragraph: "Located in USA (Washington, D.C., Phoenix (AZ), Memphis (TN), Columbus (OH), or nearby regions) with remote work arrangement and up to 25% travel."
Core values paragraph: "At 5C Our core values guide how we collaborate, make decisions, support one another, and serve our customers. We're looking for people who embrace them and help us build something great."
We could combine into About the role section: maybe two paragraphs: role summary + location/work/travel + core values.
Now Pay section: just salary range: "$155K–$175K". Could be a paragraph.
We should not create Benefits, Schedule sections.
Now we need to output HTML fragment.
Structure:
About the role
Role summary paragraph.
Location/work/travel paragraph.
Core values paragraph.
Responsibilities
- ...
...
Requirements
- Experience with hyperscale cloud providers, large-scale data center deployments, or AI infrastructure programs.
- Familiarity with:
- Infrastructure-as-Code and configuration management (Ansible)
- Python, Shell, and SQL for infrastructure automation and diagnostics
- DCIM, BMS, and observability platforms for liquid-cooled environments
- NVIDIA/Mellanox networking platforms and NVLink/NVSwitch technologies
- Experience coordinating with MEP engineering teams on electrical and cooling infrastructure scheduling for large-scale deployments.
- Experience with
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them as lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the EEO statement at end, also "Ready to Apply?" and "Apply today..." and the EEO paragraph. Also remove "How We Work At 5C" maybe? It's somewhat values; but it's not boilerplate; it's specific to company culture. Could keep as part of About the role? But it's not directly about the role; it's about company. However we could incorporate into About the role? Might be considered filler? It's not generic like "commensurate with experience". It's specific: "Our core values guide how we collaborate, make decisions, support one another, and serve our customers. We're looking for people who embrace them and help us build something great." That's somewhat generic but still company-specific. Might be okay to include as part of About the role? But we already have role summary. Could add a separate section "About the Company" but not in allowed headings list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put that content under About the role as prose. Thus About the role section will contain: Role Summary paragraph, location, work arrangement, travel, maybe core values. We need to ensure we don't duplicate content. The "What You Will Do" and "What You Bring" are duplicated exactly; we should not duplicate content. The posting has the same block repeated under "What You Will Do" and "What You Bring". We need to preserve all substantive information but not duplicate lines. So we should include each unique piece only once. Since they are identical, we should include it once under Responsibilities (or Requirements). Probably under Responsibilities (what you will do). Then for Requirements we can include "What Sets You Apart" plus maybe any additional qualifications not already covered. The "What You Bring" is duplicate, so we skip it. Thus we need to extract unique bullet-like sentences from "What You Will Do". Let's list them: - Lead end-to-end project management for large-scale AI/GPU cluster deployments, including multi-rack GPU compute platforms (NVIDIA DGX and similar), InfiniBand and Ethernet GPU fabrics, and high-performance storage environments (e.g., VAST Data). - Partner with engineering teams and managers to establish and drive consistent project tracking, milestone reporting, and status updates across the team and systems (e.g., Jira, Confluence). - Coordinate procurement, rack-and-stack sequencing, cabling schedules, network deployment timelines, burn-in testing, cluster validation, and operational handoff. - Coordinate with facilities engineering and datacenter operations to align MEP readiness (power distribution, cooling capacity, floor layout, containment) with deployment schedules. - Communicate project status, risks, milestones, and dependencies to stakeholders at all levels including executive leadership. - Prepare and present regular program reviews, steering committee updates, and ad-hoc project analyses. - Maintain centralized project documentation and ensure consistent, accurate data. - Contribute to improving and documenting repeatable deployment methodologies, scalable operational standards, and project management best practices. - Track deployment KPIs (schedule variance, budget adherence, quality metrics) and drive continuous improvement through data-driven retrospectives. That's 9 items. Now "What Sets You Apart" bullet list: - Experience with hyperscale cloud providers, large-scale data center deployments, or AI infrastructure programs. - Familiarity with: - Infrastructure-as-Code and configuration management (Ansible) - Python, Shell, and SQL for infrastructure automation and diagnostics - DCIM, BMS, and observability platforms for liquid-cooled environments - NVIDIA/Mellanox networking platforms and NVLink/NVSwitch technologies - Experience coordinating with MEP engineering teams on electrical and cooling infrastructure scheduling for large-scale deployments. - Experience with procurement processes in infrastructure delivery contexts. We need to format as list. The sub-items under Familiarity with could be nested list? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep as separate items. Could flatten: each bullet as separate
- . Might be okay to keep sub-bullets as separate
- under a parent? But we need to preserve all detail. Could do:
- Experience with hyperscale cloud providers, large-scale data center deployments, or AI infrastructure programs.
- Familiarity with:
- Infrastructure-as-Code and configuration management (Ansible)
- Python, Shell, and SQL for infrastructure automation and diagnostics
- DCIM, BMS, and observability platforms for liquid-cooled environments
- NVIDIA/Mellanox networking platforms and NVLink/NVSwitch technologies
- Experience coordinating with MEP engineering teams on electrical and cooling infrastructure scheduling for large-scale deployments.
- Experience with procurement processes in infrastructure delivery contexts.
About the role
Role summary paragraph.
Location/work/travel paragraph.
Core values paragraph.
Responsibilities
- ... ...
Requirements
- Experience with hyperscale cloud providers, large-scale data center deployments, or AI infrastructure programs.
- Familiarity with:
- Infrastructure-as-Code and configuration management (Ansible)
- Python, Shell, and SQL for infrastructure automation and diagnostics
- DCIM, BMS, and observability platforms for liquid-cooled environments
- NVIDIA/Mellanox networking platforms and NVLink/NVSwitch technologies
- Experience coordinating with MEP engineering teams on electrical and cooling infrastructure scheduling for large-scale deployments.
- Experience with