Wastewater Operator

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. Rules: - 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 - Do NOT repeat the job title as a heading (the page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, let me parse the job posting content: 1. Introductory marketing text about Inframark 2. "Why Work for Inframark?" - benefits mentioned: attractive salary package, generous benefits package with health, dental, life insurance, 401(k), paid time off, sick leave, holidays, wellness plan 3. JOB FUNCTION/PURPOSE: Wastewater Operator responsible for operation and maintenance of equipment in wastewater treatment facilities. Salary range $23-$27/hr depending on experience. Wastewater Operator license preferred or ability to obtain. 4. Responsibilities: list of duties 5. Qualifications: list of qualifications 6. Education/Experience: High School Diploma or GED 7. Licenses/Certifications: Valid Driver's License (CDL preferred), Water/Wastewater Operator's License specific to state and site-specific requirements, other licenses may vary 8. Technical: Ability to follow manual & operating instructions, basic proficiency with Microsoft Office & internet, basic knowledge of water/wastewater operations 9. Communication: Communicates clearly & professionally, contributes to positive customer experience, willing to help others, maintains composure 10. Problem Solving & Quality: Pays attention to detail, identifies & solves problems, escalates issues, checks work for quality 11. Managing for Results: Works well with supervision, takes projects to completion, follows policies & SOPs, manages multiple tasks 12. Leadership & Initiative: Demonstrates positive attitude, acts in accordance with company vision/mission/values, takes accountability, willing to take on additional assignments 13. PHYSICAL DEMANDS: lift 50-60 pounds, load/unload/move large equipment/tools, access confined spaces, continuously walk and climb stairs and ladders 14. Background screening, drug testing, driving record review 15. EEO statement (boilerplate - remove) 16. "Learn more about us at Operations and Maintenance - Inframark" (navigation - remove) Now, I need to structure this into sections with h3 headings. Let me think about appropriate sections: - About the role (or Job Purpose) - from JOB FUNCTION/PURPOSE - Responsibilities - from Responsibilities list - Qualifications - from Qualifications list - Education & Experience - from Education/Experience - Licenses & Certifications - from Licenses/Certifications - Technical Skills - from Technical - Communication Skills - from Communication - Problem Solving & Quality - from Problem Solving & Quality - Managing for Results - from Managing for Results - Leadership & Initiative - from Leadership & Initiative - Physical Demands - from PHYSICAL DEMANDS - Benefits - from "Why Work for Inframark?" section (has specific benefits listed) - Pay - salary range is given ($23-$27/hr) - Schedule - mentions "Willing to work all shifts, including weekends, holidays, evening and 24-hour emergency on call" appears twice But the rule says: "Prefer a few substantive sections over many thin ones." Some of these are quite thin (e.g., Technical, Communication, Problem Solving, Managing for Results, Leadership & Initiative are each just a few bullet points). However, they are distinct categories in the posting. The rule says include a section ONLY when the posting has real, specific content for it. These do have specific content. But maybe I can group some? The posting separates them into distinct competency areas. I think I should keep them as separate sections because they are explicitly labeled in the posting. But wait: the rule says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't require me to use exactly those headings; those are examples. I should use headings that match the content. Also, the introductory marketing text ("Join Inframark: Leading the Way in Water Management...") is prose about the company. Should I include an "About the Company" section? The rule says "Preserve ALL substantive information". But it's marketing fluff. However, it does describe the company's mission. I could include a brief "About Inframark" section with a paragraph. But the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is not exactly boilerplate; it's company description. But it's not core job info. The user said "Preserve ALL substantive information". I'll include it as a short paragraph under an "About Inframark" heading? But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". That's about job title. Company description might be okay. However, the example headings don't include "About the Company". I'll include it as a

  at the top maybe without a heading? But the rule says use

  for section headings. I could do an

  About Inframark

  then

  . But the rule says "Prefer a few substantive sections over many thin ones." This is thin. Maybe I'll fold it into a brief intro paragraph before the first heading? But the output should be HTML fragment with sections. I think I'll include a short "About Inframark" section with the prose. Now, the "Why Work for Inframark?" section includes benefits and salary mention. But salary is also in JOB FUNCTION/PURPOSE. I'll create a Benefits section with the benefits list, and a Pay section with the salary range. Schedule: The posting mentions shift requirements in Responsibilities and Qualifications. I'll create a Schedule section with that info. Now, let's structure: 1. About Inframark (prose) 2. Job Purpose (prose + salary) 3. Responsibilities (list) 4. Qualifications (list) 5. Education & Experience (list or prose) 6. Licenses & Certifications (list) 7. Technical Skills (list) 8. Communication Skills (list) 9. Problem Solving & Quality (list) 10. Managing for Results (list) 11. Leadership & Initiative (list) 12. Physical Demands (list) 13. Benefits (list) 14. Pay (prose) 15. Schedule (prose) But many of these are very thin. The rule says "never emit a heading followed by filler/placeholder text". These are not filler; they are actual content from the posting. However, the rule also says "Prefer a few substantive sections over many thin ones." Perhaps I can group the competency areas (Technical, Communication, Problem Solving, Managing for Results, Leadership & Initiative) under a "Competencies" or "Skills & Attributes" section with sub-lists? But the rule says use

  • for any list. I could make a section "Skills & Competencies" and then have subheadings? But the rule says only

    for section headings. No subheadings. So maybe keep them separate. Alternatively, I could combine them into one "Qualifications & Competencies" section with multiple lists? But the posting separates them. I think I'll keep them as separate sections because they are distinct in the source. But let's check the rule: "Include a section ONLY when the posting has real, specific content for it". Each of these has specific bullet points. So they qualify. Now, the EEO statement and background screening info: "To support a safe and secure workplace, all offers of employment are contingent upon the successful completion of background screening, drug testing, and driving record review where applicable." This is a condition of employment. I could include a "Pre-Employment Requirements" section. But it's a single sentence. Might be thin. Could fold into a paragraph at the end. But the rule says preserve substantive information. I'll include a "Pre-Employment Requirements" section with a paragraph. Also, the "Learn more about us at Operations and Maintenance - Inframark" is navigation, remove. Now, let's write the HTML. I'll start with an

    About Inframark

    and a

    for the intro prose. Then

    Job Purpose

    with a

    for the purpose and salary. Then

    Responsibilities

    with
    • for each bullet. Then

      Qualifications

      with
      • . Then

        Education & Experience

        with
        • (just one item). Then

          Licenses & Certifications

          with
          • . Then

            Technical Skills

            with
            • . Then

              Communication Skills

              with
              • . Then

                Problem Solving & Quality

                with
                • . Then

                  Managing for Results

                  with
                  • . Then

                    Leadership & Initiative

                    with
                    • . Then

                      Physical Demands

                      with
                      • . Then

                        Benefits

                        with
                        • from the "Why Work for Inframark?" section. Then

                          Pay

                          with

                          for salary range. Then

                          Schedule

                          with

                          for shift requirements. Then

                          Pre-Employment Requirements

                          with

                          for background screening, drug testing, driving record. I need to ensure I don't duplicate the shift requirement in both Responsibilities and Qualifications. The posting has it in both. I'll include it in Schedule section and maybe not duplicate in Responsibilities? But the Responsibilities list includes "Willing to work all shifts, including weekends, holidays, evening and 24-hour emergency on call." That's a responsibility? Actually it's a requirement. I'll keep it in Responsibilities as it appears there, and also mention in Schedule. But that duplicates. The rule says preserve ALL substantive information. Duplication in source is okay? I'll keep as in source: include in Responsibilities list and also in Schedule section. But that's redundant. Maybe I'll include in Responsibilities and not create a separate Schedule section? But the rule says create Schedule section if posting states them. The posting states shift requirements. I'll create a Schedule section summarizing the shift requirements, and keep the bullet in Responsibilities as it appears. Now, let's write the HTML. Note: The salary range is given in Job Purpose: "Salary range is $23-$27/hr depending on level of experience." I'll put that in Pay section. Benefits: "We offer an attractive salary package, including a generous benefits package with health, dental, and life insurance, 401