Reliability Engineer

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - Company Description (but this is boilerplate about the company, not about the role) - Position Summary (About the role) - Key Responsibilities (Responsibilities) - Qualifications (Requirements/Qualifications) - Additional Information (Benefits) Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's process the content: Company Description: This is about the company, not the role. The user said "Company Description" is part of the input. Should I include it? The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". Company Description is not in that list. But it's substantive information about the company. However, the instruction says "reformat a job posting into clean, well-structured semantic HTML". The job posting includes Company Description. But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The Company Description is not the job title. It's a section. But the example headings don't include "Company Description". The user might want it as a section? The rules say "include a section ONLY when the posting has real, specific content for it". The Company Description has content. But it's not about the role. However, it's part of the job posting. I think I should include it as a section, maybe "About the Company" or "Company Overview". But the example headings don't include that. The user said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That's an example list, not exhaustive. I can use other headings if they fit. But the instruction says "Prefer a few substantive sections over many thin ones." The Company Description is a paragraph. I could include it as a section with heading "About the Company" or "Company Description". However, the user might consider it boilerplate? It's not EEO/legal boilerplate; it's actual company description. I'll include it as a section. But wait: The user said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The Company Description is not that. It's part of the job posting. I'll include it. Now, Position Summary: This is "About the role". I'll use

  About the role

  and a

  for the summary. Key Responsibilities: This is a list of responsibilities. I'll use

  Responsibilities

  and
  • for each bullet. The responsibilities are grouped into three subsections: Cross-Site Coordination, Technical Oversight & Reliability Engineering, Maintenance Strategy & Standards. Each has multiple bullet points. I should preserve the structure. I could either make them as separate sub-lists or combine. Since they are grouped, I could use nested lists or separate
    for each group with a heading? But the rule says use

    for section headings. These are sub-sections within Responsibilities. I could use

    but the rule only mentions

    . The rule says "use

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

    for section headings. I think I should keep it simple: one Responsibilities section with a list of all bullet points, maybe grouped with bold text? But the rule says use

    • for any list of duties. I can include the group names as part of the list items or as separate headings? The example doesn't show subheadings. I'll include the group names as bold text within the list items, or as separate list items? Better to keep each bullet as a separate
    • and include the group name as a prefix. For example: "Cross-Site Coordination: Serves as a connective point..." But the original has multiple bullets under each group. I'll flatten them into a single list, but preserve the grouping by including the group name in each bullet. That might be messy. Alternatively, I can create three separate
      lists, each preceded by a

      ? But the rule says use

      for section headings. It doesn't say I cannot use

      . However, to be safe, I'll use

      for main sections only. I'll make Responsibilities one section with a single

      containing all bullet points, each bullet starting with the group name in bold. Let's see the responsibilities: Cross-Site Coordination: - Serves as a connective point across sites, building relationships with site maintenance supervisors and creating visibility into best practices across the network, partnering with functions like procurement, IT, etc. to drive long-term solutions. - Builds a culture of continuous improvement and cross-site best practice sharing, supporting Harsco Environmental’ s internal initiatives. - Compiles and communicates lessons learned, vendor performance data, and component life data (i.e., OEE, MTBF / MTTR, downtime) across the site network. Technical Oversight & Reliability Engineering: - Assesses site equipment condition and maintenance practices to identify existing or potential reliability and performance gaps, working with site supervisors to develop corrective measures and following up to ensure measures have been implemented. - Leads root cause analysis for significant or recurring equipment maintenance needs across the network, translating findings into actionable corrective and preventive measures, and driving actions through to closure. - Assists site maintenance supervisors in understanding root cause analysis methodology, including guidance on conducting investigations and managing corrective and preventive action plans. - Maintains reliability files and records, including failure history, RCA documentation, and PM standards. Maintenance Strategy & Standards: - Develops and standardizes preventive maintenance strategies across sites and asset classes, grounded in failure history and duty cycle. - Defines technical specifications and standards for major components and equipment, recommending other safeguards to prevent recurring failures and unplanned downtime. - Provides technical sourcing support to procurement as needed, including specification input at time of equipment purchase. - Provides insights for equipment lifecycle decisions, including repair versus replace, refurbish versus new, and in-house versus OEM service. - Develops and maintains a network-wide condition monitoring strategy, including tool coordination, ownership, and scale-up planning. I'll create a single
      with each bullet as an
      • . I'll include the group name as a bold prefix. Qualifications: This is a list of qualifications. I'll use

        Qualifications

        and
        • for each bullet. Additional Information: This mentions benefits. It says "We offer competitive benefits, including health insurance, life insurance and disability plans, as well as a 401k with company matching." That's specific benefits. Also includes EEO statement which is boilerplate. I should include the benefits but remove the EEO boilerplate. The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So I'll keep the benefits sentence, but not the EEO sentence. Also the Disclaimer is boilerplate. Remove. Now, the Qualifications section includes "Bachelor's degree...", "5+ years...", "Passport is required...", "Experience with root cause analysis...", "Knowledge of maintenance...", "Strong analytical...", "Experience with CMMS...", "Bilingual in Spanish is a plus". All are specific. Also note: The Qualifications section says "Will also consider 5+ years of relatable engineering experience within an industrial environment" as alternative to degree. That's part of the same bullet? Actually it's a separate line. I'll treat each line as a bullet. Now, the Position Summary is a paragraph. I'll put it in

          . Company Description is a paragraph. I'll put it in

          under a heading "Company Overview" or "About the Company". I'll use

          Company Overview

          . But the rule says "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't include Company Overview. However, it's a section with real content. I'll include it. Now, the output should be only HTML fragment. No markdown code fences. Let's structure:

          Company Overview

          Harsco Environmental is the premier provider of material processing and environmental services to the global steel and metals industries. Our onsite mill services and resource recovery services offer sustainable solutions that maximize environmental benefit and return valuable raw material into production. We also have developed a range of by-products for specialized applications across industry, construction and agriculture, which utilize Harsco’s expertise in mineral materials.

          About the role

          The Reliability Engineer is responsible for improving equipment reliability, reducing downtime, and driving continuous improvement initiatives across steel production and environmental systems. This role leads root cause failure analyses, develops and implements corrective actions, and works closely with operations, maintenance, and engineering teams to enhance asset performance, safety, and environmental compliance.

          Responsibilities

          • Cross-Site Coordination: Serves as a connective point across sites, building relationships with site maintenance supervisors and creating visibility into best practices across the network, partnering with functions like procurement, IT, etc. to drive long-term solutions.
          • Cross-Site Coordination: Builds a culture of continuous improvement and cross-site best practice sharing, supporting Harsco Environmental’ s internal initiatives.
          • Cross-Site Coordination: Compiles and communicates lessons learned, vendor performance data, and component life data (i.e., OEE, MTBF / MTTR, downtime) across the site network.
          • Technical Oversight & Reliability Engineering: Assesses site equipment condition and maintenance practices to identify existing or potential reliability and performance gaps, working with site supervisors to develop corrective measures and following up to ensure measures have been implemented.
          • Technical Oversight & Reliability Engineering: Leads root cause analysis for significant or recurring equipment maintenance needs across the network, translating findings into actionable corrective and preventive measures, and driving actions through to closure.
          • Technical Oversight & Reliability Engineering: Assists site maintenance supervisors in understanding root cause analysis methodology, including guidance on conducting investigations and managing corrective and preventive action plans.
          • Technical Oversight & Reliability Engineering: Maintains reliability files and records, including failure history, RCA documentation, and PM standards.
          • Maintenance Strategy & Standards: Develops and standardizes preventive maintenance strategies across sites and asset classes, grounded in failure history and duty cycle.
          • Maintenance Strategy & Standards: Defines technical specifications and standards