Production Operator - Night Shift

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections with real specific content. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Preserve all substantive info. We need to parse the posting. First part: "At Niagara, we’re looking for Team Members who want to be part of achieving our mission to provide our customers the highest quality most affordable bottled water. Consider Applying Here, If You Want To Work in an entrepreneurial and dynamic environment with a chance to make an impact. Develop lasting relationships with great people. Have the opportunity to build a satisfying career. We offer competitive compensation and benefits packages for our Team Members." That's generic intro; could be "About the role". It's not a heading repeated job title. So we can put that in

under About the role. Then "Production Operator - Night Shift This position is responsible for daily operations of the production floor; ensuring the shift meets established safety, quality, and production goals in compliance with all applicable legal and food safety requirements." That's description of role; could be part of About the role or Responsibilities. We'll treat as part of About the role. Then "Essential Functions" list: many bullet-like sentences. We'll put under Responsibilities as

• . Then "Qualifications" section: Minimum Qualifications: 0 Years – Experience in Field or similar manufacturing environment etc. Preferred Qualifications: 2 Years – Experience... We'll put under Requirements or Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications. Typically Requirements = minimum qualifications, Qualifications = preferred? But we can decide: Use Requirements for minimum qualifications, Qualifications for preferred? Or combine? We'll follow typical: Requirements = minimum qualifications, Qualifications = preferred qualifications and competencies? However they also have a "Competencies" section; that could be Skills. Education also separate. We need to include sections only if posting has real specific content. So we need to decide which sections to include. We have: - About the role: we have intro paragraph and description. - Responsibilities: Essential Functions list. - Requirements: Minimum Qualifications (0 years experience etc.) - Qualifications: Preferred Qualifications (2 years experience etc.) plus maybe Competencies? Could treat Competencies as Skills. - Skills: Competencies list (Lead Like an Owner, InnovACT, Find a Way, Empowered to be Great) each with bullet points. - Benefits: Benefits section described. - Pay: Not mentioned specific pay; only "competitive compensation". That's vague; we should not create Pay section unless posting actually states them. It says "We offer competitive compensation and benefits packages". That's not specific; we should not create Pay section. - Schedule: Mention "Ability to work 12 hour shifts, day or night, on a rotating 2-2-3 schedule or schedule as dictated by production demand." That's specific schedule info. So we can include Schedule section. - Education: Minimum Required: High School Diploma or GED Preferred: Associate's Degree. Could be part of Qualifications or Requirements? There's a separate Education heading in the list; we could include Education section. - Certification/License: N/A etc. Not needed. - Foreign Language: None. We need to avoid filler like "N/A". So we should not include sections that only have N/A. We need to preserve all substantive info; not invent or summarize away detail. We must remove boilerplate: lines like "Please note this job description is not designed to contain a comprehensive list..." etc. That's boilerplate; we should remove it. Also "Consider Applying Here..." maybe considered call to action; we should remove application instructions. The instruction says remove application instructions. So we should remove "Consider Applying Here, If You Want To Work..." etc? Actually that's part of intro but also a call to action. Might be considered boilerplate? It's encouraging to apply; but it's not a legal boilerplate. However it's more like a marketing line. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove explicit application instructions like "Consider Applying Here". That's an instruction to apply. So we should remove that sentence. Also "Consider Applying Here, If You Want To Work..." is basically an invitation to apply. We'll remove it. Also "We offer competitive compensation and benefits packages for our Team Members." That's not an instruction; it's a statement about benefits; we can keep. We need to keep the mission statement etc. Now let's extract substantive content: Intro: "At Niagara, we’re looking for Team Members who want to be part of achieving our mission to provide our customers the highest quality most affordable bottled water." Keep. Then after removing "Consider Applying Here..." we have: "If You Want To Work in an entrepreneurial and dynamic environment with a chance to make an impact. Develop lasting relationships with great people. Have the opportunity to build a satisfying career." That's still motivational; maybe keep as part of About the role. Then "We offer competitive compensation and benefits packages for our Team Members." Keep. Then role title: "Production Operator - Night Shift". Not a heading; we can include as a

  maybe. Then description: "This position is responsible for daily operations of the production floor; ensuring the shift meets established safety, quality, and production goals in compliance with all applicable legal and food safety requirements." Then "Essential Functions" list: we need to convert each sentence to

• . List items: - Responsible for daily activities of the production line(s), ensuring product adheres to Niagara’s standard of safety, quality, and throughput. - Accurately completes applicable quality and production reports hourly. - Physical and visual inspection of product is required to prevent non-conforming goods. - Correctly reports all quality defects to the appropriate team members and shift leadership. - Adheres to the highest standards of company and plant safety programs, guidelines, rules, and regulations. - Abides by Niagara’s Good Manufacturing Practices (GMP) and Food Safety Standards at all times. - Maintains general housekeeping in all areas of production and additional areas assigned by plant leadership. - Maintains appropriate level of raw materials as required, to ensure production lines incur minimal downtime. - Demonstrates the aptitude and skill to work in all assigned areas of production; troubleshoots minor production line issues and performs relief duties when required. - Regular and predictable attendance is an essential function of the job. - Ability to work 12 hour shifts, day or night, on a rotating 2-2-3 schedule or schedule as dictated by production demand. Note: The last item about schedule could also go to Schedule section; but it's also part of Essential Functions. We'll keep it in Responsibilities list; but we also have a Schedule section maybe separate. To avoid duplication, we could keep schedule info only in Schedule section and not duplicate in Responsibilities. However the instruction says preserve ALL substantive information; we can include it in both places? That would be duplication. Better to keep it in Schedule section and maybe remove from Responsibilities to avoid duplication. But the Essential Functions list includes that sentence; if we remove it, we lose that detail from Responsibilities. However we can keep it in Responsibilities and also have Schedule section referencing it? That would duplicate. The instruction: "Remove ... duplicated lines". So we should avoid duplication. So we need to decide where to place schedule info. Since there is a dedicated Schedule heading, we can put schedule info there and omit from Responsibilities. But then we lose the sentence from Essential Functions; but we could keep the rest of Essential Functions without that sentence. That seems acceptable: we preserve the info, just placed under Schedule. Thus Responsibilities list will exclude the schedule sentence. Now Qualifications: Minimum Qualifications: "0 Years – Experience in Field or similar manufacturing environment", "0 Years – Experience in Position", "0 Years – Experience managing people/projects experience may include a combination of work experience and education". That's a bit weird; but we keep as is. Preferred Qualifications: "2 Years – Experience in Field or similar manufacturing environment", "2 Years – Experience in Position", "2 Years – Experience managing people/projects experience may include a combination of work experience and education". We could put Minimum under Requirements heading, Preferred under Qualifications heading. Now Competencies: This is a list of competency categories each with sub-bullets. We'll put under Skills heading. Competencies text: "Lead Like an Owner Makes safety the number one priority Keeps alert for safety issues and escalates immediately Effectively prioritizes tasks based on department goals Shows respect to others and confronts interpersonal issues directly Prioritizes resolution of customer issues effectively Responds promptly and honors commitments to internal and external customers InnovACT Makes recommendations to continuously improve policies, methods, procedures, and/or products Demonstrates adaptability by reacting appropriately to unexpected changes in situations or circumstances Increases performance through greater efficiency Find a Way Seeks to develop technical knowledge through learning from other experts Understands interdepartmental impact of individual decisions and actions Seeks solutions rather than placing blame Empowered to be Great Consistently looks for ways to improve one’s self through growth and development opportunities Communicates clearly and promptly up, down, and across Communicates effectively to manage expectations" We'll convert each main competency as maybe a
• with sub-items? The instruction: Use
  • for any list of duties/requirements/benefits. For competencies, we could treat each competency as a
  • and its subpoints as nested
    • . That's acceptable. Now Education: Minimum Required: High School Diploma or GED Preferred: Associate's Degree. We'll put under Education heading. Benefits: Already have a Benefits paragraph with list. We'll put under Benefits heading. We need to ensure we don't include filler like "N/A". Benefits list includes many items; we keep them. Now we need to output HTML fragment only, no /. Use

      for each section heading. We'll structure:

      About the role

      At Niagara, we’re looking for Team Members who want to be part of achieving our mission to provide our customers the highest quality most affordable bottled water. If You Want To Work in an entrepreneurial and dynamic environment with a chance to make an impact. Develop lasting relationships with great people. Have the opportunity to build a satisfying career. We offer competitive compensation and benefits packages for our Team Members. Production Operator - Night Shift This position is responsible for daily operations of the production floor; ensuring the shift meets established safety, quality, and production goals in compliance with all applicable legal and food safety requirements.

      But we might split into multiple

      for readability. It's okay. Then

      Responsibilities

      • ... (list items except schedule)
      Then

      Requirements

      • 0 Years – Experience in Field or similar manufacturing environment
      • 0 Years – Experience in Position
      • 0 Years – Experience managing people/projects experience may include a combination of work experience and education
      Then

      Qualifications

      • 2 Years – Experience in Field or similar manufacturing environment
      • 2 Years – Experience in Position
      • 2 Years – Experience managing people/projects experience may include a combination of work experience and education
      Then

      Skills

      • Lead Like an Owner
        • Makes safety the number one priority
        • Keeps alert for safety issues and escalates immediately
        • Effectively prioritizes tasks based on department goals
        • Shows respect to others and confronts interpersonal issues directly
        • Prioritizes resolution of customer issues effectively