Data Center Facilities Development Manager
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. 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
8. Prefer a few substantive sections over many thin ones
9. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting has:
- A general description paragraph at the top
- "Responsibilities" section with subsections:
- Key Responsibilities (with sub-subsections: Construction Project Management-Project Planning and Execution, Construction Project Management-Project Integration and Quality Assurance, Risk and Problem Management, Stakeholder and Vendor Management, Design Coordination and Improvement)
- Core Responsibilities (with sub-subsections: Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement)
- "Qualifications" section (but it's mostly disclaimer, pay range, benefits, career level, about us, EEO)
I need to structure this properly. The "Qualifications" section in the posting is actually a mix of disclaimer, pay, benefits, career level, company info, and EEO. The actual qualifications/requirements for the role aren't explicitly listed as a separate "Requirements" or "Qualifications" section with bullet points. The responsibilities are detailed.
I should create sections for:
- About the role (the initial description paragraph)
- Responsibilities (with the detailed responsibilities)
- Pay (since it states a specific range: $91,400 - $187,000 per year, plus bonus and equity)
- Benefits (since it lists a comprehensive benefits package)
- Maybe Career Level (IC3) as a small note
But the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state pay range and benefits, so I can include them.
I should remove the EEO boilerplate, the "About Us" marketing text, the accommodation contact info, the application timeline note, etc.
Also, the "Qualifications" heading in the posting is misleading because it's not really qualifications. I should not use "Qualifications" as a heading if there are no actual qualifications listed. Instead, I'll use "Pay" and "Benefits" for those sections.
Let me structure:
1.
About the role
with the initial paragraph
2. Responsibilities
with the detailed responsibilities organized. Since there are many sub-items, I'll use nested lists or separate lists for each sub-section. The rules say use - for any list of duties/requirements/benefits. I can have multiple
under the Responsibilities heading, each preceded by a bold label or just list items. But the rules say use for section headings, not for sub-sections. So I'll keep Responsibilities as one and then use for the list of responsibilities. However, the responsibilities are grouped into categories. I could either flatten them into one big list, or use labels within list items. The instruction: "Use - for any list of duties/requirements/benefits". It doesn't forbid using bold labels inside list items. I think it's okay to have list items that start with a bold category.
Alternatively, I could create separate
for each sub-category? But the rules say use for section headings like "Responsibilities", not for sub-sections. So I'll keep one Responsibilities section.
I'll create a list where each item is a responsibility, grouped by the sub-categories. I'll include all the bullet points from the posting.
Similarly, for Pay and Benefits, I'll use - for benefits list.
Now, let's write the HTML.
First, the initial description: "Assists in managing the construction of data centers by colocation providers, ensuring adherence to timelines, budgets, and quality standards. Supports the creation, review, and maintenance of documentation, including design review, commissioning, and problem-solving papers. Implements quality control processes to ensure all construction activities meet design specifications and industry standards. Conducts regular site walks and assists in the startup and commissioning phases of major data center projects. Identifies gaps in risk identification and mitigation and recommends standard corrective actions. Serves as the primary point of contact between the company and colocation providers. Assists in the selection, negotiation, and management of contracts with external vendors, contractors, and suppliers, ensuring contract compliance and performance and construction activities align with the approved design plans and specifications. Assists in overseeing the installation of power, cooling, networking, and structured cabling systems."
That's a paragraph, so
.
Then Responsibilities: I'll create a
with many - . Each li can be a responsibility statement. I'll include all from Key Responsibilities and Core Responsibilities.
Key Responsibilities subsections:
- Construction Project Management-Project Planning and Execution: 4 bullet points (but they are written as sentences). I'll list each as a separate li.
- Construction Project Management-Project Integration and Quality Assurance: 4 bullet points.
- Risk and Problem Management: 3 bullet points.
- Stakeholder and Vendor Management: 3 bullet points.
- Design Coordination and Improvement: 3 bullet points.
Core Responsibilities subsections:
- Planning & Execution: 2 bullet points.
- Collaboration & Partnership: 3 bullet points.
- Problem Solving: 3 bullet points.
- Continuous Learning: 3 bullet points.
- Continuous Improvement: 2 bullet points.
That's a lot. I'll combine them into one list, but maybe group with bold labels. However, the rules don't specify how to handle sub-categories. I think it's fine to have a flat list of all responsibilities. But to preserve structure, I could use nested lists: outer list for categories, inner list for items. But the rule says "Use
- for any list of duties/requirements/benefits". Nested lists are still ul/li. I'll do nested: each category as a li with a strong label and then a nested ul of items. That might be more semantic.
But the instruction: "Use
- for any list of duties/requirements/benefits, and
for prose." It doesn't forbid nested lists. I'll do nested for clarity.
Similarly for Benefits: it's a list of benefits, so
- .
Pay: it's a range and mention of bonus and equity. I'll put as a
or a list? Since it's a single piece of info, maybe a
. But the rule says use
- for any list. Pay is not a list, so
is fine.
Career Level: IC3, I can include in a small
maybe under a "Details" section? But the rules say prefer a few substantive sections. I could include career level in a
at the end or in the About the role. But the posting has "Career Level - IC3" as a line. I'll include it as a
maybe after Responsibilities or in a "Details" section. However, the rules say include a section ONLY when the posting has real, specific content for it. Career level is a minor metadata. I'll fold it into a short
maybe at the end of the fragment.
But the rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Career level is similar minor metadata. I'll include it in a
at the end.
Now, let's write the HTML.
I'll start with
About the role
...initial description...
Responsibilities
- Construction Project Management – Project Planning and Execution
- Assists in managing the construction of data centers by colocation providers, ensuring adherence to timelines, budgets, and quality standards.
- Supports in developing and maintaining project schedules, working closely with colocation providers to ensure timely delivery of milestones.
- Assists in creating and managing project budgets, ensuring efficient use of resources and cost-effective project delivery.
- Supports the creation, review, and maintenance of documentation, including design review, commissioning, and problem-solving papers, ensuring standards are upheld, documents are managed effectively, and materials are suitable for their intended purpose.
- Construction Project Management – Project Integration and Quality Assurance
- Implements and oversees quality control processes to ensure all construction activities meet design specifications and industry standards.
- Assists in the coordination and integration of tenant fit out projects by following established procedures and providing support during design, construction, and commissioning phases.
- Conducts regular site walks to ensure schedule, coordination, and quality throughout the life of the project.
- Assists in the startup and commissioning phases of major data center projects, ensuring that all systems are operational and meet design specifications.
- Risk and Problem Management
- Evaluates the risk profiles associated with timely project delivery.
- Identifies gaps in risk identification and mitigation and recommends standard corrective actions.
- Implements mitigation strategies for major construction project risks to ensure project success.
- Stakeholder and Vendor Management
- Serves as the primary point of contact between the company and colocation providers, facilitating clear and effective communication.
- Develops and maintains key relationships to effectively support internal and external stakeholders.
- Assists in the selection, negotiation, and management of contracts with external vendors, contractors, and suppliers, ensuring contract compliance and performance.
- Design Coordination and Improvement
- Collaborates with design teams to ensure that construction activities align with the approved design plans and specifications.
- Provides ongoing colocation provider evaluation input for continuous improvement.
- Assists in overseeing the installation of power, cooling, networking, and structured cabling systems.
- Planning & Execution
- Independently manages work, monitoring timelines and deliverables to ensure projects or initiatives stay on track and meet requirements.
- Proactively prioritizes work and adapts to resource or timeline shifts, suggesting adjustments to maintain project efficiency.
- Collaboration & Partnership
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. 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 8. Prefer a few substantive sections over many thin ones 9. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - A general description paragraph at the top - "Responsibilities" section with subsections: - Key Responsibilities (with sub-subsections: Construction Project Management-Project Planning and Execution, Construction Project Management-Project Integration and Quality Assurance, Risk and Problem Management, Stakeholder and Vendor Management, Design Coordination and Improvement) - Core Responsibilities (with sub-subsections: Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement) - "Qualifications" section (but it's mostly disclaimer, pay range, benefits, career level, about us, EEO) I need to structure this properly. The "Qualifications" section in the posting is actually a mix of disclaimer, pay, benefits, career level, company info, and EEO. The actual qualifications/requirements for the role aren't explicitly listed as a separate "Requirements" or "Qualifications" section with bullet points. The responsibilities are detailed. I should create sections for: - About the role (the initial description paragraph) - Responsibilities (with the detailed responsibilities) - Pay (since it states a specific range: $91,400 - $187,000 per year, plus bonus and equity) - Benefits (since it lists a comprehensive benefits package) - Maybe Career Level (IC3) as a small note But the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state pay range and benefits, so I can include them. I should remove the EEO boilerplate, the "About Us" marketing text, the accommodation contact info, the application timeline note, etc. Also, the "Qualifications" heading in the posting is misleading because it's not really qualifications. I should not use "Qualifications" as a heading if there are no actual qualifications listed. Instead, I'll use "Pay" and "Benefits" for those sections. Let me structure: 1.
About the role
with the initial paragraph 2.Responsibilities
with the detailed responsibilities organized. Since there are many sub-items, I'll use nested lists or separate lists for each sub-section. The rules say use- for any list of duties/requirements/benefits. I can have multiple
- under the Responsibilities heading, each preceded by a bold label or just list items. But the rules say use
- for any list of duties/requirements/benefits". It doesn't forbid using bold labels inside list items. I think it's okay to have list items that start with a bold category.
Alternatively, I could create separate
for each sub-category? But the rules say use
for section headings like "Responsibilities", not for sub-sections. So I'll keep one Responsibilities section. I'll create a list where each item is a responsibility, grouped by the sub-categories. I'll include all the bullet points from the posting. Similarly, for Pay and Benefits, I'll use
- for benefits list.
Now, let's write the HTML.
First, the initial description: "Assists in managing the construction of data centers by colocation providers, ensuring adherence to timelines, budgets, and quality standards. Supports the creation, review, and maintenance of documentation, including design review, commissioning, and problem-solving papers. Implements quality control processes to ensure all construction activities meet design specifications and industry standards. Conducts regular site walks and assists in the startup and commissioning phases of major data center projects. Identifies gaps in risk identification and mitigation and recommends standard corrective actions. Serves as the primary point of contact between the company and colocation providers. Assists in the selection, negotiation, and management of contracts with external vendors, contractors, and suppliers, ensuring contract compliance and performance and construction activities align with the approved design plans and specifications. Assists in overseeing the installation of power, cooling, networking, and structured cabling systems."
That's a paragraph, so
. Then Responsibilities: I'll create a
- with many
- . Each li can be a responsibility statement. I'll include all from Key Responsibilities and Core Responsibilities.
Key Responsibilities subsections:
- Construction Project Management-Project Planning and Execution: 4 bullet points (but they are written as sentences). I'll list each as a separate li.
- Construction Project Management-Project Integration and Quality Assurance: 4 bullet points.
- Risk and Problem Management: 3 bullet points.
- Stakeholder and Vendor Management: 3 bullet points.
- Design Coordination and Improvement: 3 bullet points.
Core Responsibilities subsections:
- Planning & Execution: 2 bullet points.
- Collaboration & Partnership: 3 bullet points.
- Problem Solving: 3 bullet points.
- Continuous Learning: 3 bullet points.
- Continuous Improvement: 2 bullet points.
That's a lot. I'll combine them into one list, but maybe group with bold labels. However, the rules don't specify how to handle sub-categories. I think it's fine to have a flat list of all responsibilities. But to preserve structure, I could use nested lists: outer list for categories, inner list for items. But the rule says "Use
- for any list of duties/requirements/benefits". Nested lists are still ul/li. I'll do nested: each category as a li with a strong label and then a nested ul of items. That might be more semantic.
But the instruction: "Use
- for any list of duties/requirements/benefits, and
for prose." It doesn't forbid nested lists. I'll do nested for clarity. Similarly for Benefits: it's a list of benefits, so
- .
Pay: it's a range and mention of bonus and equity. I'll put as a
or a list? Since it's a single piece of info, maybe a
. But the rule says use
- for any list. Pay is not a list, so
is fine. Career Level: IC3, I can include in a small
maybe under a "Details" section? But the rules say prefer a few substantive sections. I could include career level in a
at the end or in the About the role. But the posting has "Career Level - IC3" as a line. I'll include it as a
maybe after Responsibilities or in a "Details" section. However, the rules say include a section ONLY when the posting has real, specific content for it. Career level is a minor metadata. I'll fold it into a short
maybe at the end of the fragment. But the rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Career level is similar minor metadata. I'll include it in a
at the end. Now, let's write the HTML. I'll start with
About the role
...initial description...
Responsibilities
- Construction Project Management – Project Planning and Execution
- Assists in managing the construction of data centers by colocation providers, ensuring adherence to timelines, budgets, and quality standards.
- Supports in developing and maintaining project schedules, working closely with colocation providers to ensure timely delivery of milestones.
- Assists in creating and managing project budgets, ensuring efficient use of resources and cost-effective project delivery.
- Supports the creation, review, and maintenance of documentation, including design review, commissioning, and problem-solving papers, ensuring standards are upheld, documents are managed effectively, and materials are suitable for their intended purpose.
- Construction Project Management – Project Integration and Quality Assurance
- Implements and oversees quality control processes to ensure all construction activities meet design specifications and industry standards.
- Assists in the coordination and integration of tenant fit out projects by following established procedures and providing support during design, construction, and commissioning phases.
- Conducts regular site walks to ensure schedule, coordination, and quality throughout the life of the project.
- Assists in the startup and commissioning phases of major data center projects, ensuring that all systems are operational and meet design specifications.
- Risk and Problem Management
- Evaluates the risk profiles associated with timely project delivery.
- Identifies gaps in risk identification and mitigation and recommends standard corrective actions.
- Implements mitigation strategies for major construction project risks to ensure project success.
- Stakeholder and Vendor Management
- Serves as the primary point of contact between the company and colocation providers, facilitating clear and effective communication.
- Develops and maintains key relationships to effectively support internal and external stakeholders.
- Assists in the selection, negotiation, and management of contracts with external vendors, contractors, and suppliers, ensuring contract compliance and performance.
- Design Coordination and Improvement
- Collaborates with design teams to ensure that construction activities align with the approved design plans and specifications.
- Provides ongoing colocation provider evaluation input for continuous improvement.
- Assists in overseeing the installation of power, cooling, networking, and structured cabling systems.
- Planning & Execution
- Independently manages work, monitoring timelines and deliverables to ensure projects or initiatives stay on track and meet requirements.
- Proactively prioritizes work and adapts to resource or timeline shifts, suggesting adjustments to maintain project efficiency.
- Collaboration & Partnership
- Construction Project Management – Project Planning and Execution
- for any list. Pay is not a list, so
- .
Pay: it's a range and mention of bonus and equity. I'll put as a
- for any list of duties/requirements/benefits, and
- for any list of duties/requirements/benefits". Nested lists are still ul/li. I'll do nested: each category as a li with a strong label and then a nested ul of items. That might be more semantic.
But the instruction: "Use
- . Each li can be a responsibility statement. I'll include all from Key Responsibilities and Core Responsibilities.
Key Responsibilities subsections:
- Construction Project Management-Project Planning and Execution: 4 bullet points (but they are written as sentences). I'll list each as a separate li.
- Construction Project Management-Project Integration and Quality Assurance: 4 bullet points.
- Risk and Problem Management: 3 bullet points.
- Stakeholder and Vendor Management: 3 bullet points.
- Design Coordination and Improvement: 3 bullet points.
Core Responsibilities subsections:
- Planning & Execution: 2 bullet points.
- Collaboration & Partnership: 3 bullet points.
- Problem Solving: 3 bullet points.
- Continuous Learning: 3 bullet points.
- Continuous Improvement: 2 bullet points.
That's a lot. I'll combine them into one list, but maybe group with bold labels. However, the rules don't specify how to handle sub-categories. I think it's fine to have a flat list of all responsibilities. But to preserve structure, I could use nested lists: outer list for categories, inner list for items. But the rule says "Use
- for benefits list.
Now, let's write the HTML.
First, the initial description: "Assists in managing the construction of data centers by colocation providers, ensuring adherence to timelines, budgets, and quality standards. Supports the creation, review, and maintenance of documentation, including design review, commissioning, and problem-solving papers. Implements quality control processes to ensure all construction activities meet design specifications and industry standards. Conducts regular site walks and assists in the startup and commissioning phases of major data center projects. Identifies gaps in risk identification and mitigation and recommends standard corrective actions. Serves as the primary point of contact between the company and colocation providers. Assists in the selection, negotiation, and management of contracts with external vendors, contractors, and suppliers, ensuring contract compliance and performance and construction activities align with the approved design plans and specifications. Assists in overseeing the installation of power, cooling, networking, and structured cabling systems."
That's a paragraph, so
for section headings, not for sub-sections. So I'll keep Responsibilities as one
and then use
- for the list of responsibilities. However, the responsibilities are grouped into categories. I could either flatten them into one big list, or use labels within list items. The instruction: "Use
- for any list of duties/requirements/benefits". It doesn't forbid using bold labels inside list items. I think it's okay to have list items that start with a bold category.
Alternatively, I could create separate