Data Center Operation Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes Company Overview, Job Overview, Key Responsibilities, Required Skills, Required Experience, Preferred Certifications, Physical Requirements, Compensation, Benefits? There's a line: "We also offer comprehensive benefits options which vary depending on role, location, and employment type." That's vague; not specific benefits. According to rules: do NOT create Benefits section unless posting actually states them. It says "We also offer comprehensive benefits options which vary depending on role, location, and employment type." That's not specific; we should not create Benefits section because it's not specific details. Similarly Pay: we have "Estimated Pay Range: $49.00 - $75.00 USD". That's specific enough to create Pay section. Schedule: not mentioned. So we include Pay. We need headings: About the role? The posting includes Company Overview and Job Overview. Could combine into About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (company overview + job overview), Responsibilities (Key Responsibilities), Requirements (maybe Required Skills + Required Experience?), Qualifications? They didn't separate qualifications; we could combine Required Skills and Required Experience under Requirements? But they said prefer a few substantive sections over many thin ones. Could have sections: About the role, Responsibilities, Requirements (including skills and experience), Preferred Certifications, Physical Requirements, Pay. However Preferred Certifications maybe part of Requirements. But we can keep separate if substantive. Let's decide: We'll have About the role, Responsibilities, Requirements (skills+experience), Preferred Certifications, Physical Requirements, Pay. We must not repeat job title as heading. No Job ID. Remove boilerplate: diversity statement, EEO, fraud notice, etc. Also remove "Company Overview" heading? We'll embed content in About the role. We need to preserve all substantive information. So include company overview description, job overview description, responsibilities list, required skills list, required experience list, preferred certifications list, physical requirements list, compensation. We must use

• for any list of duties/requirements/benefits. For prose use

  . For headings use

  . We need to ensure we don't include filler like "commensurate with experience". Not present. Let's extract content. Company Overview paragraph: "Milestone Technologies is a global IT managed services firm that partners with organizations to scale their technology, infrastructure and services to drive specific business outcomes such as digital transformation, innovation, and operational agility. Milestone is focused on building an employee-first, performance-based culture and for over 25 years, we have a demonstrated history of supporting category-defining enterprise clients that are growing ahead of the market. The company specializes in providing solutions across Application Services and Consulting, Digital Product Engineering, Digital Workplace Services, Private Cloud Services, AI/Automation, and ServiceNow. Milestone culture is built to provide a collaborative, inclusive environment that supports employees and empowers them to reach their full potential. Our seasoned professionals deliver services based on Milestone’s best practices and service delivery framework. By leveraging our vast knowledge base to execute initiatives, we deliver both short-term and long-term value to our clients and apply continuous service improvement to deliver transformational benefits to IT. With Intelligent Automation, Milestone helps businesses further accelerate their IT transformation. The result is a sharper focus on business objectives and a dramatic improvement in employee productivity. Through our key technology partnerships and our people-first approach, Milestone continues to deliver industry-leading innovation to our clients. With more than 3,000 employees serving over 200 companies worldwide, we are following our mission of revolutionizing the way IT is deployed." Job Overview: "Job Overview The Senior Data Center Operations Engineer plays a critical, hands-on role in supporting the build-out and long-term operation of a high-performance, enterprise-scale data center environment. This position is designed for an experienced engineer with deep expertise in server hardware troubleshooting, Linux systems, and data center operations. You will contribute during the initial build and deployment phase, supporting infrastructure bring-up, validation, and hardware readiness. As the environment transitions into steady-state operations, you will take ownership of ongoing reliability, advanced troubleshooting, and continuous improvement initiatives. This role requires a strong operator mindset—someone who thrives in high-availability environments and takes pride in resolving complex issues at their root. You will serve as a technical escalation point, working closely with engineering and infrastructure teams to maintain system stability and performance. You will collaborate with cross-functional teams, making clear and professional communication in English (written and verbal) essential for success in this role. This role offers continuity across both deployment and operational phases, providing a strong foundation for long-term technical growth within a critical infrastructure program." We can combine these two into About the role section. Responsibilities: list under Key Responsibilities with subheadings? The posting has subheadings: Advanced Hardware Troubleshooting & Repair, Linux Systems & Platform Support, Data Center Operations Support, Collaboration & Mentorship. Each has bullet points. We need to output a

  • for any list of duties/requirements/benefits. Should we flatten all bullet points into a single list? Probably we can keep subheadings as

    ? But only

    allowed for section headings. Could we keep subheadings as or just include them in

    text? The instruction: Use

    • for any list of duties/requirements/benefits, and

      for prose. It doesn't forbid other headings inside list items. But to be safe, we can keep each bullet as

    • and include the subheading text as part of the
    • maybe preceded by a dash. However we risk losing structure. Could we make separate sections for each responsibility category? That would be many thin sections, which they advise against. Better to have one Responsibilities section with a
      containing all bullet points, preserving the subheadings as part of the
      • text. Let's extract bullet points: Advanced Hardware Troubleshooting & Repair: - Diagnose and resolve complex hardware failures across server platforms (motherboards, CPUs, memory, storage) - Perform component-level repairs and replacements on servers and data center hardware - Execute break/fix processes with a focus on minimizing downtime and meeting SLAs - Conduct root cause analysis (RCA) of hardware failures and recommend preventative actions - Identify recurring failure trends and contribute to tooling and process improvements - Perform such other duties and responsibilities as may be reasonably be assigned from time to time Linux Systems & Platform Support: - Utilize Linux command-line tools for system monitoring, diagnostics, and troubleshooting - Support provisioning and deployment of servers across various Linux distributions (RHEL, Ubuntu, etc.) - Troubleshoot boot-level and OS-level issues in production environments - Collaborate with engineering teams to resolve complex issues involving hardware/software interaction Data Center Operations Support: - Support hardware installation, structured cabling, and infrastructure validation - Maintain accurate inventory of spare parts, assets, and retired equipment - Document all repairs, changes, and configurations in ITSM/DCIM systems - Ensure adherence to data center safety, security, and operational protocols - Act as a technical escalation point for complex infrastructure issues - Participate in on-call rotation supporting 24x7 operations Collaboration & Mentorship: - Provide guidance and training to technicians on hardware troubleshooting best practices - Collaborate with network, storage, and infrastructure teams to resolve cross-functional issues - Contribute to knowledge sharing, documentation, and operational excellence initiatives Required Skills: - Strong English communication skills (written and verbal) are required for coordination with cross-functional teams - Expert-level knowledge of server hardware architecture and component-level troubleshooting - Strong proficiency with Linux systems and command-line diagnostics - Solid understanding of networking fundamentals and hardware (switches, routers, firewalls) - Experience working within structured operational environments (SOPs, SLAs, ticketing systems) - Familiarity with ITSM/DCIM tools (ServiceNow, Jira, or similar) - Experience with structured cabling and fiber optic connectivity - Strong analytical and problem-solving skills with attention to detail - Ability to operate effectively in high-pressure, high-availability environments - Strong organizational and documentation skills Required Experience: - 5+ years of experience in data center operations or similar infrastructure environments - Significant hands-on experience with server hardware troubleshooting and repair - Minimum of 2 years of experience working with Linux operating systems in production environments - Experience supporting enterprise server platforms and infrastructure environments - Demonstrated experience performing root cause analysis and resolving complex hardware issues - Experience working within ticketing systems and operational workflows - Exposure to data center build-outs, deployments, or infrastructure upgrades (preferred) Preferred Certifications: - CompTIA A+, Server+, or Linux+ LPI certification or equivalent - Vendor-specific hardware certifications Physical Requirements: - Ability to lift and move equipment up to 50 lbs - Ability to work in a temperature-controlled environment with moderate noise levels - Ability to perform physical tasks such as standing, walking, bending, and kneeling for extended periods Compensation: - Estimated Pay Range: $49.00 - $75.00 USD - Also note: "We also offer comprehensive benefits options which vary depending on role, location, and employment type." Not specific, so we skip Benefits section. - Also note about compensation details: "The Talent Acquisition Partner can share more details about compensation or benefits for the role during the interview process. Exact compensation and offers of employment are dependent on circumstances of each case and will be determined based on job-related knowledge, skills, experience, licenses or certifications, and location." This is somewhat generic; we could include as prose under Pay section? It's about compensation details. Might be okay to include as

        under Pay. We must not create Benefits section. Now produce HTML. Structure:

        About the role

        Company overview paragraph.

        Job overview paragraph.

        Responsibilities

        • ... (each bullet)
        ...

        Requirements

        Maybe split into Skills and Experience? Could combine but might be long. Could have two subsections? But they said prefer few sections. Could have Requirements with two
        lists: one for Skills, one for Experience. But that is still one section with multiple lists. That's fine. We'll do:

        Requirements

        Skills

        but h4 not allowed? Only h3 for section headings. Could use inside

        or just include as part of list with preceding text. Simpler: have two

        under Requirements, each preceded by a

        describing. But the instruction: Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could also have Skills as a separate heading. But they said prefer few sections. However we already have About the role, Responsibilities, Requirements, Preferred Certifications, Physical Requirements, Pay. That's six sections. That's okay. We could keep Skills and Experience separate under Requirements? Actually they listed Skills and Experience as separate headings in the posting. We could make separate sections: Skills and Experience. But that would increase sections. However they said prefer a few substantive sections over many thin ones. Skills and Experience are both substantive; maybe we keep them as separate sections: Skills and Experience. Then we also have Preferred Certifications, Physical Requirements, Pay. That's many sections (About the role, Responsibilities, Skills, Experience, Preferred Certifications, Physical Requirements, Pay) = 7 sections. Might be okay but maybe too many. However they said "Prefer a few substantive sections over many thin ones." These are substantive. Could be okay. Alternatively combine Skills and Experience into Requirements with two lists. That reduces sections. I'll go with Requirements containing two

        lists: one for Skills, one for Experience, each preceded by a <