Site Lead, Data Center Operations

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job description. First, we need to decide which sections to include. The posting includes: - Job Description (intro paragraph) describing role: "Manages operations for a moderately complex data center..." That's about the role. Could be "About the role". We'll put that as

About the role

with

containing that paragraph. - Responsibilities: The posting has a "Responsibilities" heading with subheadings: Key Responsibilities, Data Center Site Portfolio Management, Performance Monitoring and Analysis, Issue Management and Automation, Data Center Expansion Support, Installation and Maintenance, Core Responsibilities (Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement). So we need to extract responsibilities content. We'll put under

Responsibilities

with

• items for each bullet/duty. Must preserve all substantive info. We need to avoid duplication. The content includes many sentences; we can break into list items. - Qualifications: There's a "Qualifications" section with a disclaimer about US based roles, immunization, drug testing. Then "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $74,100 - $148,300 per year. May be eligible for bonus and equity." Then details about Oracle US offers a comprehensive benefits package (list). Also mentions role will accept applications for at least three calendar days, onboarding process identity verification, accommodations, etc. Also "About Us" section. We need to separate Qualifications (requirements) vs Benefits vs Pay vs Schedule. The posting includes: - Qualifications: The disclaimer about immunization/occupational health mandates, drug testing requirements. That's a qualification? It's more like a requirement. Also maybe they didn't list explicit qualifications like education/experience. So we might have a Qualifications section with that disclaimer. - Pay: The hiring range $74,100 - $148,300 per year, may be eligible for bonus and equity. That's pay info. - Benefits: The comprehensive benefits package list. - Schedule: Not mentioned explicitly. No schedule info. So we should not create Schedule section. - Skills: Not explicitly listed. Could infer but we should not invent. So omit Skills. - About the role: we have intro paragraph. - Responsibilities: as above. - Qualifications: include disclaimer and maybe note about US-based employees identity verification? That's more about onboarding, but could be considered qualification? Might be better to put under Qualifications? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They gave Requirements as an example but we don't have explicit Requirements section; we have Qualifications. We'll follow the given list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can omit sections lacking content. They said "include a section ONLY when the posting has real, specific content for it". So we need to decide if we have content for Requirements. The posting didn't have a separate "Requirements" heading; but we could treat the disclaimer as qualification. Might be better to put under Qualifications. We'll not create Requirements if no explicit content. Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits. Possibly also "About Us" but not in list; we should not add extra headings not in list. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those. The "About Us" is not in list; we could incorporate that into About the role? But it's more about company. Could be omitted as not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit About Us, we lose substantive info about company mission. However, the instruction about sections only applies to those headings; we could still include a

  about company under About the role or maybe as a separate

  without heading? The instruction says output ONLY the HTML fragment; we can include paragraphs not under headings? It didn't forbid. It says 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. So we can have prose paragraphs not under headings? Probably yes, but better to structure with headings for each major chunk. The "About Us" could be a separate

    after About the role, but we could also put it under About the role heading as additional prose. That would preserve info. Thus:

    About the role

    Manages operations for a moderately complex data center, monitoring key metrics, addressing routine issues like capacity and cooling, and recommending improvements aligned with industry best practices. Provides support for escalated technical problems, optimizes automation and monitoring tools, documents processes and incident responses, and contributes to continuous improvement projects. Supports new region builds and expansions, collaborates with project teams, and oversees installations, repairs, inventory, and logistics—leading component upgrades and advising on data center purchases and deployments.

    Then responsibilities: we need to list bullet points. Let's extract each duty. From responsibilities section: Key Responsibilities - Data Center Site Portfolio Management: Typically one data center of moderate complexity. - Performance Monitoring and Analysis: Independently monitors and analyzes data center operations, providing insights and recommendations based on metrics. Analyzes and resolves routine issues (e.g., physical capacity, power capacity, cooling capacity). Partners across functions and regions to identify, measure, and improve processes in alignment with industry best practices (e.g., Lean, Six Sigma), contribute to improvement projects, and support alignment with strategic objectives. - Issue Management and Automation: Provides support for escalated complex technical issues. Triages and/or escalates issues and optimizes the use of automation, scheduling, and monitoring tools to proactively mitigate potential problems. Identifies, documents, and reviews issues, processes, and solutions, ensuring the data center knowledge base is continually updated. Executes incident or crisis management protocols in alignment with business continuity plans. Performs Root Cause Analysis (RCA) following crises or incidents, and updates documentation to capture process improvements. - Data Center Expansion Support: Independently supports new region builds and expansion activities, both onsite and remotely. Acts as a liaison with project teams and data center engineering, supporting timelines and capacity needs are proactively managed for expansion projects and site builds. Collaborates closely with project teams on significant aspects of expansion projects and site builds to deliver high standards. - Installation and Maintenance: Oversees installations, repairs, inventory management, and logistics tasks for data centers. Leads efforts to replace and upgrade components. Evaluates and recommends purchases or upgrades for data centers. Plans and oversees rack deployments, installation. - Core Responsibilities - 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: Collaborates across teams to align on expectations and achieve shared objectives. Builds and maintains a comprehensive understanding of business, stakeholder, and/or customer needs to build and support effective partnerships. Actively listens to diverse perspectives and asks questions to ensure understanding of others. - Problem Solving: Independently identifies and addresses standard and non-standard issues in accordance with standard practices, escalating more complex issues as appropriate. Analyzes data and/or information from multiple sources to troubleshoot standard and non-standard errors. Contributes to knowledge sharing and best practices. - Continuous Learning: Embraces continuous learning by actively seeking to build knowledge and new skills and/or tools and staying current with industry trends and best practices. Seeks out and leverages feedback and training to improve skills. Contributes to a culture of continuous learning and knowledge sharing with team members. - Continuous Improvement: Develops ideas and recommends updates to increase the efficiency and effectiveness of processes, protocols, and workflows within a team. Seeks input from team members on alternative approaches and methods for improving work. We need to put these as
    • . Could combine some sentences into one li each. Ensure we preserve all substantive info; we can break into multiple li for clarity but not required. We'll create li for each bullet point as above. Now Qualifications: includes disclaimer: "Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." Also maybe mention "Range and benefit information provided in this posting are specific to the stated locations only US:" but that's pay/benefit. Also mention "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." That's more about application process, which we should remove per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop that line about application period. Also "As part of Oracle's onboarding process and consistent with applicable law, US-based employees are required to complete identity verification, which involves the collection and processing of their biometric information. Accommodations to this requirement may be granted following an individualized assessment." That's also onboarding/legal; maybe we should drop as it's legal/boilerplate? It's not EEO but it's about onboarding; might be considered legal. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is about onboarding identity verification; could be considered legal. Safer to drop. Thus Qualifications section will contain only the disclaimer about immunization/occupational health mandates and drug testing requirements. Possibly also note that it's US based roles; we keep that. Thus:

      Qualifications

      Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements.

      Now Pay: hiring range $74,100 - $148,300 per year, may be eligible for bonus and equity. Thus:

      Pay

      Hiring range in USD from $74,100 to $148,300 per year. May be eligible for bonus and equity.

      Now Benefits: list of benefits. We need to use
      • for list of benefits. Benefits list: - Medical, dental, and vision insurance, including expert medical opinion - Short term disability and long term disability - Life insurance and AD&D - Supplemental life insurance (Employee/Spouse/Child) - Health care and dependent care Flexible Spending Accounts - Pre-tax commuter and parking benefits - 401(k) Savings and Investment Plan with company match - Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation. - 11