Technical Project Manager - Data Center Liquid Cooling

We need to output HTML fragment with sections: About the role? Actually we have "About Fluid2Chip" description. 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. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. We have: - About Fluid2Chip: description paragraph. - Salary: note about salary ranges not reflecting pay ranges, they out-compete. - Job Summary: description. - Essential Functions: list of duties. - Position Requirements: list of requirements. - Education & Certifications: bullet list. - Physical Demands Duties: description. - Travel Requirements: description. - Benefits: list. - EEO: boilerplate (remove). - Notice To Third Party Agencies: boilerplate (remove). - The Pay Range For This Role Is 120,000 - 140,000 USD per year (Hybrid (United States)) We need to decide which sections to include. We have content for: - About the role? Could be "About Fluid2Chip" but heading "About the role" is suggested. However we have "About Fluid2Chip" which is about company. Could map to "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have: - Job Summary: could be "About the role" or "Job Summary". Probably "About the role" is appropriate. - Essential Functions: could be "Responsibilities". - Position Requirements: could be "Requirements" or "Qualifications". We have both Requirements and Education & Certifications. Could combine into "Requirements" and "Qualifications". But we need to avoid thin sections. Perhaps combine Requirements and Education & Certifications into a single "Requirements" section with lists. - Benefits: we have Benefits list. - Pay: we have Pay Range. - Schedule: not explicitly given; we have Travel Requirements (up to 75% travel). That's not schedule but travel. There's no explicit schedule (e.g., full-time, part-time). So we should not create Schedule section unless posting actually states them. It does not. So omit. - Skills: not explicitly listed separate; could be part of Requirements. Thus we can have sections: About the role (Job Summary), Responsibilities (Essential Functions), Requirements (Position Requirements + Education & Certifications), Benefits, Pay. We need to ensure we preserve all substantive information. Also include Salary note about salary ranges not reflecting pay ranges? That's somewhat meta; but we have actual pay range later. The Salary paragraph says: "Fluid2Chip recognizes salary ranges from job boards do not necessarily reflect our pay ranges. In many instances we out-compete those ranges for well-qualified candidates." This is substantive? It's about compensation but we already have actual pay range. Might be considered filler? It's not boilerplate; it's a note about salary ranges. Could be included in Pay section or as a note. Since we have actual pay range, we could include that note as a

  within Pay section. We also have Travel Requirements: could be included under Responsibilities or a separate section? Not in the list of headings. Could be part of Responsibilities (since it's about travel). But we might add a "Travel" section? Not in allowed headings but we could still use

  for any heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use

  for section headings (e.g. ...). Likely we should stick to those headings; but we could also create other headings if needed? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exhaustive? However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but to be safe we can map Travel Requirements under Responsibilities or maybe under About the role? Probably better to include a "Travel" section? But not in examples; risk of being considered not following instruction. Safer to incorporate travel details into Responsibilities as a bullet. Similarly Physical Demands Duties: could be part of Responsibilities or Requirements? It's about physical demands; could be a separate section but not in examples. Could be included under Requirements? Might be okay to add a "Physical Demands" section but not in examples; risk. Better to include under Responsibilities as a bullet. We need to preserve all substantive information, so we must include travel and physical demands somewhere. Thus we can have sections: - About the role (Job Summary) - Responsibilities (Essential Functions + Travel Requirements + Physical Demands Duties) - Requirements (Position Requirements + Education & Certifications) - Benefits - Pay (including note about salary ranges and actual range) We must not repeat job title as heading. We need to output only HTML fragment. Let's extract content. About Fluid2Chip paragraph: "Fluid2Chip is a specialized technical services practice built on decades of data center expertise. We bridge the gap between traditional construction teams and the shift to high-density liquid cooling — delivering expert commissioning, flush-and-fill, fluid chemistry, QA/QC, and system optimization services that ensure mission-critical liquid cooling infrastructure performs from day one." Job Summary paragraph: "Fluid2Chip is hiring a Technical Project Manager (Liquid Cooling) to support the delivery of advanced liquid cooling and Technology Cooling Systems (TCS) for data centers. This is not a generic project manager role. The ideal candidate brings hands-on experience with water treatment, complex fluid systems, commissioning, or high-purity environments, and has grown into a role coordinating people, process, and technical execution. You will work directly with hyperscalers, colocation providers, OEMs, and contractors to ensure liquid cooling systems are executed correctly during the most critical phases of project delivery. You will serve as the execution lead and technical authority to ensure systems are delivered safely, correctly, and on schedule." Essential Functions list (looks like sentences separated by periods but we can treat as bullet points). Let's list each: - Coordinate execution of liquid cooling and TCS projects from early engagement through commissioning. - Proactively identify execution risks, operational barriers, and change impacts and drive resolution. - Maintain project schedules, scopes, risks, and dependencies. - Serve as a technical liaison between clients, field teams, contractors, and internal leadership. - Track commissioning readiness, testing requirements, and acceptance criteria. - Translate technical issues (chemistry, cleanliness, system readiness) into project impacts. - Support field teams during critical site activities when needed. - Ensure accurate, high-quality project documentation and reporting. - Proactively escalate risks and propose mitigation strategies. - Serve as the primary client point of contact throughout execution. - Guide clients through technical decisions, milestones, and tradeoffs. - Build trusted, long term client relationships while managing expectations and driving outcomes. Travel Requirements paragraph: "Up to 75%, this may include travel to any or all 50 US states.Must be located near a major airport.Effective May 7, 2025, and in accordance with U.S. federal regulations for domestic air travel, a valid REAL ID (or an acceptable alternative, such as a passport) is required for travel associated with this position.Travel may involve transportation by car or plane depending on the destination and nature of the business need.Travel is defined as physically leaving home on behalf of business activities including but not limited to client sites, meetings with other employees, meetings for business development purposes, running errands on behalf of the business, attending industry conferences, etc." Physical Demands Duties paragraph: "Duties The following physical demands must be met by the employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee is: Frequently required to remain in a stationary position.Frequently moving through office, facility and other environments.On occasion the employee may need to move stationary items weighing up to 30 pounds." We need to preserve that text. It includes "Duties" repeated; we can keep as is. Position Requirements list: "3–10 years experience in one or more of the following:Water treatment or industrial fluid systems.Commissioning engineering or commissioning management.Complex mechanical or process systems.High-purity environments (semiconductor, electronics, pharmaceutical).Proven client-facing experience.Ability to operate independently with minimal oversight.Comfortable working in fast-paced, high-pressure project environments." Education & Certifications: "Bachelor’s degree in Engineering (Mechanical, Chemical, Electrical) or a related technical field.Equivalent hands-on experience in water treatment, commissioning, or complex fluid systems may be considered in lieu of a formal degree.PMP or equivalent project management certification is a plus, but not required." Benefits list: "Choice of comprehensive medical plans (including two PPO-style plans and a HDHP w/ HSA option). Flex spending accounts (FSA). Dental and vision plans. Comprehensive medical, dental and vision benefits extended to spouse / domestic partner and dependent children up to age 26. 401k with company match and self-directed brokerage account option. PTO including additional paid time off during the last week of the year. Company paid life insurance coverage for employees and their eligible dependents. Short and long-term disability, AD&D coverage. Professional development opportunities, tuition reimbursement, and professional licensing assistance. Paid parental leave after one year of employment. CO, CA, IL, NY, WA, and Washington DC residents only: In accordance with CO, CA, IL, NY, WA, and Washington DC law, the range provided is Fluid2Chip's reasonable estimate of the base compensation for this role. The actual amount may differ based on non-discriminatory factors such as experience, knowledge, skills, abilities, and location." Wait that last sentence about CO etc is actually part of Benefits? It seems like a legal note about pay range for certain states. It appears after benefits list but before EEO. It mentions "the range provided is Fluid2Chip's reasonable estimate of the base compensation for this role." That's about pay. So we should treat that as Pay-related note, not Benefits. Actually the Benefits section ends before that sentence. The sentence starts with "CO, CA, IL, NY, WA, and Washington DC residents only: In accordance with CO, CA, IL, NY, WA, and Washington DC law, the range provided is Fluid2Chip's reasonable estimate of the base compensation for this role. The actual amount may differ based on non-discriminatory factors such as experience, knowledge, skills, abilities, and location." Thus that belongs to Pay section. Pay Range line: "The Pay Range For This Role Is 120,0