Field Project Manager - Data Center Liquid Cooling

We need to output HTML fragment with sections: About the role? Actually the posting includes Position Overview, Responsibilities, etc. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading only if there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Interview Process? That's maybe not required but it's part of posting; but not listed as a section heading we must include only if content exists. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide which sections have content. We have: - Position Overview: description about Align, role. Could map to "About the role". That's substantive. - Key Responsibilities: list of duties. That's "Responsibilities". - Required Qualifications: list. That's "Requirements" or "Qualifications". The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. Probably combine? But they said prefer a few substantive sections over many thin ones. Could use "Qualifications" to cover both required and preferred? But we have both Required and Preferred Qualifications. Could make a "Qualifications" section containing both required and preferred. Or separate "Requirements" and "Preferred Qualifications"? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications as possible headings. We could put Required Qualifications under "Requirements" and Preferred Qualifications under "Qualifications". That seems reasonable. - Skills: Not explicitly listed but could be inferred from qualifications. However we should not create a Skills section unless posting actually states them. The posting does not have a separate "Skills" bullet list; skills are embedded in qualifications. So we should not add a Skills section. - Benefits: There's a "Benefits & Perks" section with list. So we create Benefits heading. - Pay: There's "Compensation: $170,000–$210,000 annually (commensurate with experience) plus benefits, project bonuses, paid travel, and training opportunities." That's specific pay range. So we create Pay heading. - Schedule: There's "Travel: Approximately 50% nationwide." That's about travel, not schedule. There's no explicit schedule (e.g., full-time, hours). So we should not create Schedule heading unless there is schedule info. There's none. So omit Schedule. We also have "About Align" at end describing company. That could be considered "About the role"? Actually "About the role" is about the position; we already used Position Overview for that. The "About Align" is company description; could be considered "About the role"? Might be redundant. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The "About Align" is not metadata; it's company overview. Could be placed under "About the role"? But we already have Position Overview which describes role and company. The "About Align" is more about the company. Could we include it under "About the role" as additional paragraph? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. If we put it under "About the role", we would be adding content beyond the Position Overview. That's okay as long as we don't create a heading that is not warranted. The heading "About the role" is warranted because we have Position Overview content. We can add the About Align paragraph under same heading as additional paragraph. That would preserve all info. Alternatively we could create a separate heading "About Align" but that's not in the allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. So we will put company description under About the role. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to output only HTML fragment, no /, no markdown. We'll produce sections in logical order: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience" in Pay heading? Actually Pay section should include the compensation text. The phrase "commensurate with experience" is part of the compensation description; it's not filler; it's specific. So we can include it. We must not include sections with only filler/placeholder text. All sections have real content. Now we need to extract content. About the role: Combine Position Overview and About Align. Position Overview text: "Align is a leader in data center white-space design and deployment, managing projects from conceptual design through execution nationwide. Our expertise includes layouts, overhead support systems, power distribution, mechanical distribution, conduit pathways, and structured cabling infrastructure. We are seeking an experienced Data Center Liquid Cooling Project Manager to lead planning, estimating, coordination, and execution of advanced cooling infrastructure for hyperscale and AI data center white-space fit-outs. This role requires strong technical expertise and project management experience overseeing liquid cooling systems from design through commissioning and turnover. The ideal candidate has experience managing liquid cooling projects in hyperscale, AI, colocation, or other mission-critical environments and can effectively coordinate engineers, manufacturers, contractors, commissioning agents, operators, and construction teams. Experience with broader data center MEP systems, electrical distribution, structured cabling, and telecommunications infrastructure is a plus." About Align text: "Align is a premier provider of technology infrastructure solutions, specializing in data center, cloud, cybersecurity, managed IT, and digital infrastructure services. For more than 30 years, Align has helped clients design, deploy, and support innovative technology solutions across financial services, healthcare, life sciences, retail, media, telecommunications, and technology sectors. Learn more at www.align.com" We should preserve the "Learn more at www.align.com" as prose. Now Responsibilities: list of duties under Key Responsibilities with subheadings: Project Management, Design & Technical Coordination, Construction Oversight, Testing & Commissioning, Vendor & Subcontractor Management, MEP Coordination. Each has bullet points. We need to output a

  • for any list of duties/requirements/benefits. Should we preserve subheadings? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

    • for any list of duties/requirements/benefits, and

      for prose. It doesn't say we cannot have headings inside the section; but we only allowed to use

      for section headings. Subheadings like "Project Management" could be formatted as

      Project Management

      or maybe as

      but we should avoid creating extra headings not in list. Probably we can treat them as prose bolded. But we need to preserve all substantive information; we can include them as

      Project Management

      then a

      for the bullets under that. Similarly for each subsection. Thus Responsibilities section will have

      Responsibilities

      then a series of

      Subheading

      followed by
      • ... items. Now Requirements: Required Qualifications list. We need to output as
        • each item. Required Qualifications bullet points: - 7+ years of project, construction, or technical management experience in data centers, mission-critical facilities, mechanical construction, or MEP construction. - Proven experience managing liquid cooling projects in hyperscale, AI, or other high-density data center environments. - Strong knowledge of direct-to-chip cooling, rear-door heat exchangers, CDUs, manifolds, piping, pumps, heat exchangers, filtration, controls, and related systems. - Experience overseeing installation, flushing, testing, commissioning, and turnover activities. - Ability to interpret mechanical drawings, specifications, submittals, schematics, and construction documents. - Experience coordinating subcontractors, manufacturers, commissioning agents, and multiple trades. - Strong understanding of data center white-space construction and supporting IT infrastructure. - Demonstrated project management skills covering scope, schedule, budget, quality, risk, and documentation. - Ability to travel approximately 50% across the United States. Now Qualifications: Preferred Qualifications list. Preferred Qualifications bullet points: - Experience with hyperscale, AI, NVIDIA GPU, or other high-density compute environments. - Experience with CDUs, liquid-to-liquid heat exchangers, facility water systems, secondary cooling loops, rack manifolds, quick disconnects, direct-to-chip systems, and rear-door heat exchangers. - Experience with liquid cooling commissioning and integrated systems testing. - Experience working for a data center general contractor, mechanical contractor, equipment manufacturer, or specialty liquid cooling contractor. - Knowledge of data center electrical distribution, structured cabling, and telecommunications infrastructure. - Experience with Procore or similar construction management platforms. - PMP certification or equivalent preferred. - Engineering degree or PE license is a plus. Now Benefits: Benefits & Perks list. Items: - Medical, Dental, and Vision coverage - HSA and FSA options - 401(k) with dollar-for-dollar company match at 3% (up to $5,000 annually) - Complimentary ClassPass membership - Generous PTO and paid holidays - Floating holiday - Cell phone reimbursement - Pre-tax commuter benefits (where applicable) - Employee wellness programs and team-building events - Employee referral program Now Pay: Compensation line. "Compensation: $170,000–$210,000 annually (commensurate with experience) plus benefits, project bonuses, paid travel, and training opportunities." We should output as

          maybe. Now we need to ensure we don't include any boilerplate like Interview Process, etc. Also we should not include "Learn more at www.align.com" maybe it's okay as prose. Now we need to output only HTML fragment. Let's craft. We'll start with

          About the role

          then

          Position Overview paragraph(s) and About Align paragraph(s). We need to preserve line breaks? Use

          for each paragraph. Paragraph 1: "Align is a leader in data center white-space design and deployment, managing projects from conceptual design through execution nationwide. Our expertise includes layouts, overhead support systems, power distribution, mechanical distribution, conduit pathways, and structured cabling infrastructure." Paragraph 2: "We are seeking an experienced Data Center Liquid Cooling Project Manager to lead planning, estimating, coordination, and execution of advanced cooling infrastructure for hyperscale and AI data center white-space fit-outs. This role requires strong technical expertise and project management experience overseeing liquid cooling systems from design through commissioning and turnover." Paragraph 3: "The ideal candidate has experience managing liquid cooling projects in hyperscale, AI, colocation, or other mission-critical environments and can effectively coordinate engineers, manufacturers, contractors, commissioning agents, operators, and construction teams." Paragraph 4: "Experience with broader data center MEP systems, electrical distribution, structured cabling, and telecommunications infrastructure is a plus." Paragraph 5 (About Align): "Align is a premier provider of technology infrastructure solutions, specializing in data center, cloud, cybersecurity, managed IT, and digital infrastructure services. For more than 30 years, Align has helped clients design