Technical Project Manager - Data Center Infrastructure/Cabling

We need to output HTML fragment with sections: About the role? The posting includes "Position Overview:" and "Key Responsibilities:" and "Required Qualifications:" and "Preferred Qualifications:" and "Benefits and Perks:" plus maybe "Pay, Schedule"? Not present. Also "Tier 2 PM26 Benefits and Perks:" is a heading but we treat as Benefits. Also there is mention of full-time salaried position, full benefits, paid time off, paid training, performance-based bonuses. Also mention of travel 50% and relocation assistance. That could be under Schedule? Not exactly schedule. There's no explicit pay or schedule details. So we should not create Pay or Schedule sections unless stated. Benefits we have details. So sections: About the role (maybe from Position Overview?), Responsibilities, Requirements (maybe combine Required and Preferred?), Qualifications? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have Position Overview (could be About the role). Key Responsibilities (Responsibilities). Required Qualifications (Requirements). Preferred Qualifications (maybe Skills? Or Qualifications?). Benefits and Perks (Benefits). Also there is mention of full-time salaried, full benefits, paid time off, paid training, performance-based bonuses, travel 50%, relocation assistance. Those could be part of Benefits or maybe Schedule? Travel is not schedule. Could be under Benefits? Might be better to include under Benefits as additional perks. Or we could create a separate "Schedule" if we had schedule info (like full-time). But schedule is not detailed; we have full-time. Could we create Schedule section with "Full-time"? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time, salaried position. That's schedule info (full-time). So we could include Schedule section with "Full-time". However they said "prefer a few substantive sections over many thin ones." Might be okay to include Schedule with just full-time. But also they said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Full-time is not filler; it's specific. So we could include Schedule. Pay: they mention salaried position, performance-based bonuses, but no specific salary numbers. That's vague; "salaried" is not a number. Might be considered filler? The instruction: never create Pay section unless posting actually states them. It does state salaried position and performance-based bonuses, but no numbers. Is that enough? Likely they want actual pay details like salary range or hourly rate. Since not provided, we should omit Pay section. Benefits: we have details, so include Benefits. Also there is mention of "Tier 2 PM26 Benefits and Perks:" heading; we can treat as Benefits. Now we need to output HTML fragment with

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. Let's extract content: About the role (Position Overview): "As a Technical Project Manager, you will manage large scale cabling infrastructure deployments for major AI and hyperscale data centers across the U.S. This position will focus on planning, coordination, documentation, reporting, and overall project delivery. You will work closely with clients, project teams, leadership, vendors, and subcontractors to ensure infrastructure deployments are completed safely, accurately, on schedule, and within budget. The ideal candidate has experience managing AI infrastructure, data center cabling, low-voltage, network infrastructure, or other IT infrastructure for large-scale deployments. This is a full-time, salaried position, full benefits, paid time off, paid training, and performance-based bonuses. Candidates may be based in another approved location if they are comfortable with approximately 50% travel. Relocation assistance may also be available for candidates interested in living near the project site." We could split some of that into Schedule (full-time, 50% travel, relocation assistance) but we can keep in About the role. Responsibilities (Key Responsibilities): List items: - Manage data center cabling and infrastructure projects from planning through closeout - Create and maintain project schedules, budgets, milestones, risk logs, and resource plans - Coordinate with clients, field teams, subcontractors, vendors, and internal stakeholders - Track project progress, identify risks, and resolve schedule or deployment issues - Manage RFIs, change orders, submittals, status reports, and closeout documentation - Track materials, equipment readiness, labor, project costs, and change orders - Lead client and internal project meetings and provide clear status updates - Partner with Superintendents and Foremen to ensure field work meets project requirements - Support QA/QC, testing, commissioning, turnover, and project closeout Requirements (Required Qualifications): - 5+ years of project management experience supporting data centers, structured cabling, low-voltage, network infrastructure, server or compute deployments, or similar technology infrastructure projects - Experience managing multiple teams, vendors, locations, or concurrent projects - Experience managing schedules, budgets, risks, documentation, and client expectations - Strong organizational, communication, and customer-facing skills - Proficiency with Excel and project management, scheduling, or reporting platforms Preferred Qualifications (maybe Skills or Qualifications): - Experience with AI or hyperscale data center infrastructure deployments - Knowledge of structured cabling, fiber, copper, racks, cabinets, containment, and cable pathways - Experience working within a PMO or structured project delivery team Benefits and Perks: List: - Comprehensive Medical, Dental, and Vision coverage - Health Savings Account (HSA) and Flexible Spending Account (FSA) options - 401(k) plan with a dollar-for-dollar company match at 3% up to an annual maximum of $5k. - Complimentary ClassPass membership to support your health and wellness goals - Generous Paid Time Off (PTO) - Company-paid holidays - Cellphone Reimbursement Program - Floating Holiday to celebrate a day that is meaningful to you - Pre-tax commuter benefits, where applicable - Employee wellness programs, events, and team-building activities - Employee referral program Also mention full benefits, paid time off, paid training, performance-based bonuses already in About the role; but we can keep them there. We also have note about interviews may be recorded; that's boilerplate? It's about hiring process; maybe we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The interview recording note is not exactly those categories but could be considered procedural; but it's not a boilerplate like EEO. However it's still part of posting; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The interview recording note is not exactly those; but it's part of hiring process. Might be considered legal? It's about recording for internal purposes. Could be considered legal boilerplate. Safer to remove it. Also the company description paragraph after benefits is likely boilerplate; we should remove as it's not required for job details? It's about company overview; could be considered boilerplate but it's substantive about Align. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview is not explicitly listed; but it's not a section heading we have. Might be considered filler? It's not duplicated. Could keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company overview if it's substantive. However they also say prefer a few substantive sections over many thin ones. Adding a company overview section would be extra; but we don't have a heading for it. Could we incorporate into About the role? Might be too much. The company overview is generic; maybe we can omit as it's not directly about the role. The instruction: remove duplicated lines, and application instructions. Company overview is not duplicated. But it's not about the role; still could be considered substantive. However typical job posting reformatting often drops the company description. The instruction didn't explicitly say to remove company overview, but they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Company overview is not that. I'd lean to keep it as a paragraph maybe under an "About Align" heading? But we don't have a heading for that in allowed list. Could we add a heading like "About the company"? Not in list. 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 list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings; we should not create other headings. So we should not add a heading for company overview. Therefore we should omit company overview text, as we cannot put it without a heading. Could we embed it in About the role as extra paragraph? That would be mixing content; but About the role is for role overview. Adding company description there might be okay but could deviate. Safer to omit it, as we cannot create a heading for it and we shouldn't add random paragraphs without heading? The instruction didn't forbid paragraphs without heading; we can have

  anywhere. But we need to use headings for sections; we can have paragraphs under headings. We could add a paragraph under About the role that includes company overview; but that would be mixing. I'd rather follow the instruction to only include sections with headings from the list, and put content under those headings. So we will omit company overview. Also we have "To support a fair, consistent, and high-quality hiring experience, some interviews may be recorded..." That's likely legal boilerplate; remove. Now we need to output HTML fragment. Structure:

  About the role

  ... (the position overview paragraph)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  maybe for Preferred Qualifications? Or we could use Qualifications for Required and Skills for Preferred. The instruction list includes Qualifications and Skills. We have Required Qualifications and Preferred Qualifications. Could map Required to Requirements, Preferred to Skills. Or we could have Requirements and Qualifications. But we already used Requirements for Required. We could use Qualifications for Preferred. Or we could combine both under Requirements and Skills. Let's decide: Use

  Requirements

  for Required Qualifications. Use

  Skills

  for Preferred Qualifications. That seems reasonable. Then Benefits:

  Benefits

  • ...
  ...
  We also might need Schedule section for full-time, 50% travel, relocation assistance. Could add Schedule heading with those details. But we already have full-time etc in About the role. If we create Schedule, we would duplicate. Better to keep in About the role. The instruction says prefer few substantive sections over many thin ones. So we keep About the role includes schedule info. Thus final HTML:

  About the role

  As a Technical Project Manager, you will manage large scale cabling infrastructure deployments for major AI and hyperscale data centers across the U.S. This position will focus on planning, coordination, documentation, reporting, and overall project delivery. You will work closely with clients, project teams, leadership, vendors, and subcontractors to ensure infrastructure deployments are