Critical Facilities Maintenance Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting does not mention pay, schedule, benefits explicitly. So we should not include those sections. We need sections: About the role (maybe "About The Role Of CFM Engineer" but we need heading

About the role

. Also maybe "About The Critical Facilities Maintenance (CFM) Team" could be a section? Could be "About the team" but not in list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also include other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use others? Probably we should stick to those. However we have content about team, about 5C, what you'll be contributing (which is responsibilities). We can map: About the role -> includes description of role. Responsibilities -> list of duties. Requirements/Qualifications -> qualifications. Skills -> maybe key competencies. Benefits -> none. Pay -> none. Schedule -> none. We need to preserve all substantive info. So we need to extract responsibilities list, qualifications list, skills list. Let's parse. From posting: About The Role Of CFM Engineer: description: role at heart of site operations team, driving seamless performance of all electrical, mechanical, fire/life safety systems supporting >20MW critical IT capacity 24/7. Responsibilities include planning/executing preventative maintenance, handling repairs, responding to emergencies, under guidance of CFM Chief Engineer and Facility Manager. Also go-to expert for general facility management tasks from building inspections to maintaining pristine work environment. Opportunity to lead small-to-medium scale projects from start to finish - collaborating with external teams such as engineering, controls, logistics, construction to bring projects to life. Role includes procuring quotes, drafting procedures, ensuring work executed with highest standards of safety, security, integrity for customers. As primary liaison with vendors and service providers, guarantee adherence to safety and environmental protocols, while ensuring 5C receives exceptional service. About The Critical Facilities Maintenance (CFM) Team: description of team, maintaining power delivery, cooling, building infrastructure. Opportunity to lead and manage maintenance and repair of equipment including list. Also support growth through new installations and capital projects. Team works alongside diverse team members. About 5C: description of company. What You'll Be Contributing: bullet list of contributions grouped under headings: Critical Infrastructure Operations, Maintenance & Technical Execution, Incident Response & Reliability, Compliance, Documentation & Reporting, Team Support & Knowledge Sharing. Each with sub-bullets. Required What Sets You Apart (Qualifications): list of qualifications. Preferred: list of preferred experience. Key Competencies: list. We need to output sections: About the role (maybe combine About the role, About the team, About 5C? But we can put all descriptive prose under About the role heading? Might be too much but okay. Could also have separate sections but not in allowed list. Probably better to stick to allowed headings: About the role (includes role description, team, company). Responsibilities (list of duties). Requirements (maybe qualifications). Qualifications (maybe preferred?). Skills (key competencies). But we need to avoid duplication. We could do:

About the role

... description of role, team, company ...

Responsibilities

• ... list from "What You'll Be Contributing" sections ...

Requirements

• ... from Required What Sets You Apart (Qualifications) ...

Skills

• ... from Key Competencies ...

We could also include Preferred as part of Requirements? But maybe we can include a separate section "Preferred qualifications" but not in allowed list. Could incorporate into Requirements as separate list? Might be okay to include both required and preferred under Requirements heading, but we need to preserve all info. Could split:

Required Qualifications

and

Preferred Qualifications

but those are not in allowed list but maybe acceptable as they are still headings. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g.)". It might be okay to use other headings as long as they are

. Safer to stick to those examples. Could treat "Qualifications" as heading for both required and preferred, but we need to differentiate. Could have

Qualifications

and inside have two

lists: one for required, one for preferred. That would preserve info. Similarly Skills heading for key competencies. Thus:

About the role

...

Responsibilities

...

Qualifications

... required ...
... preferred ...

Skills

... key competencies ...
We must not include empty sections. Ensure no filler. Now extract content. About the role paragraph: combine role description, team description, company description. Must preserve all substantive info. Let's craft a concise paragraph but not omit details. We need to include: role at heart of site operations team, driving seamless performance of all electrical, mechanical, fire/life safety systems supporting >20MW critical IT capacity 24/7. Responsibilities include planning/executing preventative maintenance, handling repairs, responding to emergencies, under guidance of CFM Chief Engineer and Facility Manager. Also go-to expert for general facility management tasks from building inspections to maintaining pristine work environment. Opportunity to lead small-to-medium scale projects from start to finish - collaborating with external teams such as engineering, controls, logistics, construction to bring projects to life. Role includes procuring quotes, drafting procedures, ensuring work executed with highest standards of safety, security, integrity for customers. As primary liaison with vendors and service providers, guarantee adherence to safety and environmental protocols, while ensuring 5C receives exceptional service. Team: Critical Facilities Maintenance (CFM) is comprised of onsite team members that maintain power delivery, cooling and general building infrastructure on behalf of customers ensuring services available without interruption on continuous (24/7) basis. As member, you will have opportunity to lead and manage maintenance and repair of equipment including Electrical Switchgear, Uninterruptable Power Supplies, Transformers, Batteries, Generators, Chillers, Air Handlers, Fire/Life Safety Equipment and more! Additionally, CFM will also support 5C's growth through support of new installations and capital projects. The CFM team will work alongside diverse team members including controls engineers, project managers, business development, logistics, construction, and security personnel to accomplish 5C's ambitious growth strategy. About 5C: 5C is an industry-leading data center and cloud services provider serving hyper scalers, cloud providers, and enterprise customers. Built on a foundation of exceptional talent and backed by strong investors, the company specializes in fast deployment of state-of-the-art data centers. With a focus on sustainable and energy-efficient solutions, 5C is committed to innovation and customization, meeting the unique needs of each client. We can combine into a paragraph or multiple paragraphs. Use

for prose. Could have multiple

under same heading? Probably okay. Now Responsibilities: from "What You'll Be Contributing" sections. List items: - Critical Infrastructure Operations: * Independently operate and monitor critical electrical and mechanical systems, including: UPS systems, battery plants, PDU/RPP, switchgear, Generators, ATS/STS equipment, CRAH/CRAC units, chillers, cooling towers, pumps, valves, BMS, EPMS, SCADA, leak detection, and fire-life-safety systems * Perform advanced troubleshooting and assist in diagnosing root causes for system issues. * Escalate complex or high-risk issues to Lead/Chief Engineers as appropriate. - Maintenance & Technical Execution: * Perform complex preventive, corrective, and emergency maintenance activities with minimal supervision. * Execute MOPs, SOPs, and EOPs with strong accuracy and adherence to safety standards. * Provide input on procedure improvements, redlines, and documentation updates. * Assist in coordinating vendor activities, ensuring work is performed safely and in alignment with operational requirements. - Incident Response & Reliability: * Support incident response activities under the direction of a Lead or Chief Engineer. * Assist in gathering data for post-incident reviews and reliability analysis. * Identify trends in system performance and communicate observations to site leadership for optimization. - Compliance, Documentation & Reporting: * Ensure work is performed in accordance with OSHA, NFPA, and internal safety policies. * Ensure compliance with safety standards, environmental regulations, and internal audit requirements. * Maintain detailed shift logs, equipment records, maintenance notes, and technical documentation. * Support internal and external audit requirements (ISO, SOC2, environmental compliance). - Team Support & Knowledge Sharing: * Share technical knowledge, best practices, and troubleshooting techniques. * Support a collaborative team environment focused on safety, reliability, and continuous improvement. We need to flatten into

• items. Could keep sub-bullets as separate
• but maintain meaning. Now Qualifications (Required): list: - Relevant technical degree, military training, or formal certifications - Strong working knowledge of critical electrical and mechanical systems, including: UPS, switchgear, generators, electrical distribution; Chillers, CRAH/CRAC, pumps, cooling towers, and chilled-water systems - Ability to read electrical one-lines, mechanical schematics, wiring diagrams, and control sequences. - Proficiency executing MOPs, SOPs, and EOPs in a live critical environment. - Demonstrated advanced troubleshooting skills. - Ability to work onsite in a 24/7 critical environment (shifts vary by location). - Strong documentation and communication skills. - Ability to perform physical work (lifting, ladder use, confined spaces) safely and reliably. Preferred: list: - Preferred Experience: 2–4 years of hands-on experience in data centers, critical facilities, industrial plants, mechanical/electrical infrastructure or related industry experience. - Ability to independently perform routine and moderately complex maintenance tasks. - Understanding of critical systems (CRAC/CRAH, UPS, generators, PDUs). - Experience executing MOPs/SOPs with minimal supervision. - Early-stage experience troubleshooting non-complex issues. - Experience coordinating with vendors or contractors. - Technical diploma, trade certificate, or coursework in HVAC, electrical, mechanical, or industrial maintenance. - Experience with BMS/EPMS/SCADA systems. - OEM training (Liebert, Schneider, Cummins, Caterpillar, Trane). - Exposure to liquid cooling for AI/GPU environments. Now Skills (Key Competencies): - Technical depth in power and cooling systems - Strong problem-solving and analytical skills - Ability to work independently while supporting team collaboration - Excellent communication and documentation habits - High attention to safety and operational discipline - Professionalism, reliability, and accountability Now produce HTML. We must not include any extra text outside HTML. No markdown fences. Let's craft. We'll have:

  About the role

  ...

  ...