Principal Data Center Facilities Engineer

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: - Job Description (intro paragraph) – could be considered "About the role"? The instruction: do NOT repeat the job title as a heading. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (intro). Then Responsibilities (list). Then Requirements? The posting has Minimum Qualifications and Preferred Qualifications. Could combine into Requirements? Or separate Qualifications and Skills? The posting includes Required Skills, Preferred Qualifications, etc. We need to decide sections. We have: - About the role: intro paragraph(s) describing role. - Responsibilities: multiple bullet points grouped under headings: Global Reliability and Risk Management, Incident Escalation and Corrective Action, Facility Audits and Operational Assurance, Engineering Standards and Technical Governance, Design and Platform Reliability, Knowledge Sharing, Additional Responsibilities As Needed (Colocation Provider Management). We could combine all responsibilities into a single

• list, but we need to preserve all substantive information. Could keep subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid additional headings inside? Probably we should stick to those headings only. So we can have a single Responsibilities section with a list of all responsibilities (maybe grouped but still list items). We'll need to extract each responsibility bullet. - Requirements: could be Minimum Qualifications? Or we could have Requirements (minimum) and Qualifications (preferred). But we have both Minimum Qualifications and Preferred Qualifications. Also there is a "Qualifications Disclaimer" which is boilerplate (should be removed). Also there is "Range and benefit information provided..." which includes Pay and Benefits. So we need Pay and Benefits sections if they have specific content. Pay: The posting says "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $102,300 - $209,500 per year. May be eligible for bonus and equity." That's specific pay range. So we should include a Pay section with that info. Benefits: The posting lists many benefits: medical, dental, vision, etc. Also vacation accrual details, holidays, sick leave, parental leave, etc. So we should include Benefits section with that content. Schedule: Not mentioned. So we should not include Schedule. Skills: There's "Required Skills" and "Preferred Qualifications" includes skills. We could have a Skills section for Required Skills. Also maybe a Qualifications section for Minimum and Preferred Qualifications. But we need to avoid duplication. Let's think: The instruction list includes Requirements, Qualifications, Skills as possible headings. We need to decide which to use. We have: - Minimum Qualifications (education/experience) - Preferred Qualifications (more experience, specific experiences) - Required Skills (troubleshoot, respond to incidents) - Also there are many skill-like items in Preferred Qualifications (experience evaluating reliability risk, leading RCA, deep expertise, ability to translate findings, experience with O&M of building systems, etc.) We could treat Minimum Qualifications as "Requirements". Preferred Qualifications as "Qualifications". Required Skills as "Skills". That seems logical. We must not include headings with filler text. All have real content. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Qualifications Disclaimer" (the paragraph about US based roles immunization etc.) That's boilerplate legal; remove. Also remove "The role will generally accept applications for at least three calendar days..." (application instructions). Remove "As part of Oracle's onboarding process..." (biometric info) maybe also boilerplate? It's about onboarding requirement; could be considered legal; but it's not EEO. Might be considered boilerplate; but it's specific to Oracle's onboarding. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The biometric info is legal/onboarding requirement; could be considered legal boilerplate; safer to remove. Also remove "About Us" section? That's marketing; not required but could be considered boilerplate? It's not EEO but it's generic company description. Might be considered boilerplate; but it's not explicitly listed to remove. However it's not substantive job content; it's about Oracle. Probably we should remove it as it's not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Us is not substantive to the role; it's generic marketing. Likely we should remove it. Also remove "Oracle is an Equal Employment Opportunity Employer..." etc. That's EEO boilerplate; remove. Thus final HTML will have sections:

  About the role

  ... (intro paragraph(s) from job description)

  Responsibilities

  • ... each responsibility bullet

  Requirements

  ... Minimum Qualifications text

  Qualifications

  ... Preferred Qualifications text

  Skills

  ... Required Skills text

  Pay

  ... Pay range info

  Benefits

  • ... each benefit item
  We must not include Schedule. Now we need to extract the exact text, preserving all substantive information, not inventing or summarizing away detail. We must keep the details as they appear, but we can format as list items. Let's extract. Intro paragraph(s): The job description starts: "Provides global facility engineering expertise to improve the reliability and resilience of Oracle’s colocation data center portfolio. The role identifies systemic risk through incident reviews, colocation facility audits, design-deviation reviews, and engineering analysis; guides mitigations to closure; and translates operational learning into colocation standards and policies. Working across Data Center Operations, Facility Engineering, Design, Construction, Commissioning, Energy, and colocation providers, this engineer provides electrical and mechanical facility engineering expertise for mission-critical colocation infrastructure. The role supports incident escalation, validates corrective and preventive actions, evaluates recurring equipment and provider risks, and develops technical guidance that can be applied across Oracle’s global colocation portfolio." That's one paragraph (maybe two sentences). We'll keep as

  . Now Responsibilities: There are headings within responsibilities: Global Reliability and Risk Management, Incident Escalation and Corrective Action, Facility Audits and Operational Assurance, Engineering Standards and Technical Governance, Design and Platform Reliability, Knowledge Sharing, Additional Responsibilities As Needed (Colocation Provider Management). We need to extract each bullet under those headings. Let's list them: Under Global Reliability and Risk Management: - Review colocation data center design deviations identified through formal design-review processes and track approved mitigations through implementation and validation. - Analyze recurring critical-infrastructure failures, provider-performance trends, and site-level events to identify risks that may affect other facilities in the colocation portfolio. - Assess reliability risks associated with aging infrastructure, including exposure to loss of utility, cooling, generation, electrical distribution, and other critical systems. - Develop technical findings and recommendations that prioritize risk reduction and support informed engineering decisions. - Partner with colocation providers and internal engineering teams to address equipment, design, and maintenance risks that recur across colocation sites. Under Incident Escalation and Corrective Action: - Provide engineering support during significant data center infrastructure incidents and abnormal operating events. - Participate in root-cause analysis and post-incident reviews; identify lessons learned and validate corrective and preventive action plans. - Track CAPA and RCA action items to completion, escalating barriers and overdue actions when needed. - Confirm that approved remediation resolves the identified risk and determine whether similar conditions exist elsewhere in the colocation portfolio. Under Facility Audits and Operational Assurance: - Lead or support facility engineering audits, including engagement with mechanical, electrical, operations, and colocation-provider stakeholders. - Assess operations and maintenance maturity against established standards and identify gaps that could affect reliability. - Evaluate critical maintenance practices, including equipment lifecycle management, battery replacement practices, control-system settings, and maintenance standards. - Support technical assessments of high-risk facilities and recommend remediation plans with clear ownership and completion criteria. Under Engineering Standards and Technical Governance: - Develop, review, and maintain facility engineering standards, operating policies, and technical guidance based on fleet experience and industry practices. - Provide technical guidance for items such as CDU firmware releases, valve settings, maintenance standards, battery replacement policies, and liquid-cooling requirements. - Partner with the Energy team on coordination between onsite generation and data center short-circuit coordination studies. - Monitor applicable industry and technology developments, including liquid-cooling guidance, and recommend appropriate actions for Oracle facilities. - Represent Reliability Engineering in design reviews, technical working groups, and change reviews involving material impact to critical infrastructure. Under Design and Platform Reliability: - Provide facility engineering input for new rack platforms, liquid-cooling deployments, and infrastructure changes that may affect colocation reliability. - Participate in design and commissioning reviews to identify operational and reliability risks before turnover. - Review technical reports, simulations, and engineering documentation as needed to support reliability recommendations. Under Knowledge Sharing: - Share incident learning, audit findings, and technical guidance with regional Facility Engineering and Data Center Operations teams. - Act as an electrical or mechanical subject matter expert and support the development of technical capability across the organization. - Mentor junior engineers and contribute to training materials, procedures, and engineering playbooks. Under Additional Responsibilities As Needed (Colocation Provider Management): - Provide technical input for colocation-provider contract administration, including statements of work, change orders, cost forecasts, and other engineering documentation. - Coordinate with colocation providers and internal stakeholders on contractor scheduling, site access, and work execution in accordance with Oracle safety and operating expectations. - Support assessment of resource readiness for critical infrastructure work, including spare parts, generator fuel, water, consumables, and other provider-managed resources. - Review provider performance and maintenance-execution trends; escalate material gaps that could affect reliability across the colocation portfolio. We'll put all these as

• items in a single
  . Now Requirements (Minimum Qualifications): "8 years of experience in operating data center critical infrastructure, critical facility operations, or a related field. OR Bachelor’s degree in Electrical Engineering, Mechanical Engineering, Industrial Engineering, Process Engineering, or a related field and 6 years of experience in operating data center critical infrastructure, critical facility operations, or a related field." We'll keep as

  . Qualifications (Preferred Qualifications): "12 years of experience in operating data center critical infrastructure, critical facility operations, or a related field. OR Bachelor’s degree in Electrical Engineering, Mechanical Engineering, Industrial Engineering, Process Engineering, or a related field and 8 years of experience in operating data center critical infrastructure, critical facility operations, or a related field. Experience evaluating reliability risk across multiple colocation data centers, regions, or colocation providers. Experience leading or supporting root-cause analysis, CAPA, facility audits, or operations-and-maintenance maturity assessments. Deep electrical or mechanical expertise in critical infrastructure, including power, cooling, controls, generators, UPS, batteries, and fire and life-safety systems. Ability to translate technical findings into standards, policies, and actionable remediation plans. Experience working with operation and maintenance of building systems, uninterruptible power supplies, generators, cooling, building automation, and fire and life-safety systems." We'll keep as

  (maybe multiple sentences). Could also break into

  but not required. We'll keep as

  . Skills (Required Skills): "Demonstrated ability to troubleshoot and resolve complex technical issues across multiple technology domains. Demonstrated ability