Equipment Operator

We need to output HTML fragment with sections: About the role? Actually we have sections: About Ceres Environmental Operations (maybe "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have content: About Ceres Environmental Operations (company description). That could be "About the role"? Actually "About the role" is generic; but we can use "About the role" heading and put description of role? The posting includes "What We Are Looking For" and "Duties And Responsibilities". Also "Required Qualifications", "Desired Qualifications". Also "What To Expect" includes schedule info (overnight shifts, extended hours, weekends, holidays, overtime). Also "Why Join CEO?" includes benefits (collaborative culture, opportunities, chance to make difference). No explicit pay or benefits details besides "competitive pay". So we may include Pay section only if posting actually states them: It says "We offer competitive pay". That's a statement about pay but not specific amount. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive pay" and schedule details. So we can include Pay section with that statement? It says "competitive pay" is a statement; it's not placeholder like "commensurate with experience". It's actual content. So we can include Pay section with that sentence. Benefits: "We Offer A collaborative, mission-driven culture. Opportunities for professional growth and advancement. The chance to make a lasting difference for communities across the U.S." That's benefits. So we can include Benefits section. Schedule: "What To Expect This is a weather-dependent role that requires flexibility and reliability. Expect overnight shifts, extended hours, weekends, holidays, and overtime during snow events." So schedule section. We need to avoid repeating job title as heading. No Job ID. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, Work Authorization, etc. Also remove duplicated lines. We need to decide which sections to include: About the role (maybe company overview), Responsibilities (duties), Requirements (maybe required qualifications), Qualifications (maybe desired qualifications?), Skills? Could combine. But we should prefer few substantive sections over many thin ones. However we need to capture all info. Could have sections: About the role (company description), Responsibilities (duties), Requirements (required qualifications), Qualifications (desired qualifications), Benefits, Pay, Schedule. That's many sections but each has substantive content. The instruction: "Prefer a few substantive sections over many thin ones." But we need to include all info; we can combine some. For example, we could have "Responsibilities" and "Requirements" covering duties and qualifications. "Benefits" and "Pay" and "Schedule" separate. "About the role" could be company overview. That's 6 sections. Might be okay. We must not create sections with filler like "not specified". All sections have content. Now we need to extract content precisely. Let's parse: About Ceres Environmental Operations (company description): "Ceres Environmental Operations (CEO) is a leader in crisis management, rapid response, and disaster recovery, committed to rebuilding stronger, safer communities. We specialize in emergency response, environmental services, planning, and consulting, including debris removal, blue roofs, logistics, debris management, demolition, recycling, forest management, and coastal and marine restoration. As a licensed general contractor, we offer unparalleled expertise to restore stability where it’s needed most. Driven by Purpose, Powered by People At CEO, we believe you’re more than just an employee; you’re part of a team with a purpose and a meaningful mission. Every team member plays a vital role in restoring hope, helping communities recover and rebuild. We value initiative, respect diversity, and give our people the freedom to lead. We offer competitive pay, travel opportunities, and a culture built on resilience and teamwork. If you show up with compassion, share the commitment, react with urgency, and deliver solutions, you’ll fit right in. We don’t just respond to challenges; we rise to them." That's a lot. We'll keep as prose under About the role. Responsibilities (Duties And Responsibilities): list: - Load end dump trailers with snow to be removed from site - Use wheel loader to manipulate and transport snow - Use a skid steer to clear snow with either a bucket or broom in high traffic areas - Plow large parking lots with wheel loader or skid - Always adhere to stringent safety standards - Communicate effectively - Other duties may be assigned. - Light Maintenance We need to preserve all. So we can make

  • each. Requirements (Required Qualifications): list: - High school diploma or general education degree (GED) - Must have a minimum of one year’s experience operating a wheel loader or skid steer - Must have valid state issued driver's license with no restrictions - Reliable transportation to downtown Minneapolis in inclement weather - Able to read and comprehend instructions, short correspondence, site maps, and memos - Maintain detailed job timesheet - Ability to be alert and aware overnight - Willing to always observe safety and security procedures; use equipment and materials properly - Is consistently at work and on time - Dependable and able to commit to long hours of work with short notice, when necessary and typically overnight, and multiple nights in a row We'll put as
    • . Desired Qualifications: list: - Experience working with snow removal - Willing to work overtime and in all weather conditions We could put under Qualifications section or separate. Could combine required and desired under Qualifications with subheadings? But instruction says use

      for section headings; we could have a single Qualifications section and inside we could have two

      with headings? But we cannot add extra headings besides

      . Could use

      to label "Required Qualifications:" and then list. But better to have separate sections: Requirements and Qualifications (desired). However we already used Requirements for required qualifications; we can use Qualifications for desired qualifications. That's fine. Benefits: from "Why Join CEO?" and "We Offer": "A collaborative, mission-driven culture. Opportunities for professional growth and advancement. The chance to make a lasting difference for communities across the U.S." We can make

      • each. Pay: "We offer competitive pay, travel opportunities, and a culture built on resilience and teamwork." Actually that sentence includes pay and travel opportunities and culture. Travel opportunities could be benefit. But we already have benefits. We could extract pay: "competitive pay". Also travel opportunities maybe benefit. But we can put Pay section with "competitive pay". Also maybe mention travel opportunities as benefit. But to avoid duplication, we could put Pay: "competitive pay". And Benefits: collaborative culture, professional growth, chance to make difference, travel opportunities. However travel opportunities already mentioned in the earlier paragraph under About CEO. We'll include it in Benefits. Schedule: from What To Expect: "This is a weather-dependent role that requires flexibility and reliability. Expect overnight shifts, extended hours, weekends, holidays, and overtime during snow events. You'll operate heavy equipment in cold, challenging weather conditions while following strict safety procedures to help keep roads and parking areas safe." We can put schedule as
        • each item: overnight shifts, extended hours, weekends, holidays, overtime during snow events. Also maybe mention operating heavy equipment in cold, challenging weather conditions; but that's more work environment. Could be part of schedule or work environment. But we don't have a Work Environment section; we could include under Schedule or maybe under Responsibilities? Better to include under Schedule as "operate heavy equipment in cold, challenging weather conditions". Also "follow strict safety procedures". But those are more about work environment. However we have no separate section; we could add to Schedule or maybe to Responsibilities? But schedule section should reflect timing expectations. The instruction: only create Schedule section if posting actually states them. It does state schedule expectations. We'll include the schedule items; we can also include the weather condition as part of schedule? Might be okay. We must not invent or summarize away detail. So we need to keep the exact phrases. Let's extract exact sentences: From What To Expect: "This is a weather-dependent role that requires flexibility and reliability. Expect overnight shifts, extended hours, weekends, holidays, and overtime during snow events. You'll operate heavy equipment in cold, challenging weather conditions while following strict safety procedures to help keep roads and parking areas safe." We'll keep that as prose under Schedule? Or we could break into list but preserve detail. The instruction: Use
          • for any list of duties/requirements/benefits. For schedule, it's a list of expectations; we could make list. But we also have a sentence about operating heavy equipment etc. That's not a list item but could be separate

            . We'll do:

            This is a weather-dependent role that requires flexibility and reliability.

            then
            • overnight shifts
            • extended hours
            • weekends
            • holidays
            • overtime during snow events
            then

            You'll operate heavy equipment in cold, challenging weather conditions while following strict safety procedures to help keep roads and parking areas safe.

            That preserves all. Now Benefits: from "Why Join CEO?" and "We Offer". Let's extract: "Why Join CEO? At CEO, you won’t just have a job, you’ll have a mission. Your work will directly impact the speed and strength of community recovery after disasters. We Offer A collaborative, mission-driven culture. Opportunities for professional growth and advancement.The chance to make a lasting difference for communities across the U.S." We need to preserve all substantive information. So we can have:

            At CEO, you won’t just have a job, you’ll have a mission. Your work will directly impact the speed and strength of community recovery after disasters.

            Then benefits list:
            • A collaborative, mission-driven culture
            • Opportunities for professional growth and advancement
            • The chance to make a lasting difference for communities across the U.S.
            Also travel opportunities mentioned earlier in About CEO: "We offer competitive pay, travel opportunities, and a culture built on resilience and teamwork." That's part of About the role section maybe. We'll keep travel opportunities in About the role paragraph (since it's part of company description). But we could also add to Benefits. However to avoid duplication, we can keep it in About the role. Pay: "We offer competitive pay, travel opportunities, and a culture built on resilience and teamwork." Actually that sentence includes pay and travel opportunities and culture. We already used travel opportunities in About the role. For Pay section we can just have "competitive pay". But we need to preserve all substantive information; we cannot drop travel opportunities if we only put it in Pay. Better to keep travel opportunities in About the role (since it's part of company description). Pay section can just be "competitive pay". That's okay. Now About the role: we need to include company description but not repeat job title. We'll include the paragraph(s) from About Ceres Environmental Operations and also maybe the "Driven by Purpose, Powered by People" part. We'll keep as prose. We must ensure we don't include boilerplate like EEO, Work Authorization, etc. Remove those. Now produce HTML fragment. Structure:

            About the role

            ... (company description)

            Responsibilities

            • ...
            ...

            Requirements

            • ...
            ...

            Qualifications

            • ...
            ...