Large Venue Route Service Technician | $22-$25/hr + Monthly Bonus | 4-Day Workweek

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". So we need to parse the description. Let's extract sections: - About the role: description of position, team-based, etc. Could be a paragraph. - Responsibilities: list of duties (What You'll Do). That's a list. - Requirements: list of requirements (What We're Looking For). Also maybe Preferred Experience. - Qualifications: maybe combine with Requirements? But we can have separate sections if content. - Skills: maybe not explicit; could be part of requirements. - Benefits: list of benefits (Why Join Advanced Fryer Solutions? includes pay, bonus, etc). Also includes Paid Training, Comprehensive Benefits Package, Work Boots, etc. - Pay: $22-$25/hr Starting Pay + Monthly Bonus, $500 New Hire Bonus After 90 Days. - Schedule: Full-Time Four 10-hour shifts per week, Overnight and early morning hours, Typical start times between 12:00 AM and 3:00 AM, Weekends off, Three days off each week, Consistent full-time schedule. We need to avoid filler like "commensurate with experience". Not present. We need to remove duplicated lines: e.g., "Working overnight and early morning hours" appears both in Before You Apply and maybe elsewhere; we should keep only once? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines: we should not repeat same info multiple times? It says remove duplicated lines. So we should deduplicate. We need to remove application instructions: "Ready to Join the AFS Team? If you value ... apply today." Also "Join a company that values reliability..." and "Advanced Fryer Solutions is an Equal Opportunity Employer." Those are boilerplate/application instructions/EOE. Remove them. Also remove "Before You Apply" heading? It's not a standard heading; we can incorporate its content into Requirements or maybe a separate section like "Is this role for you?" but we only output standard headings. Probably we incorporate that content into Requirements or maybe a "Qualifications" section. Since it's about fit, we can treat as part of Requirements. We need to output only HTML fragment, no /, no markdown fences. Let's craft sections:

  About the role

  Full-Time Overnight Position in West Chester, OH with weekends off and a company vehicle during shift. Advanced Fryer Solutions (AFS) seeks dependable, hardworking, and motivated Large Venue Service Technicians to join the growing West Chester team. This hands‑on, team‑based position serves large customers throughout Greater Cincinnati and Northern Kentucky, including universities, stadiums, entertainment venues, healthcare facilities, and other high‑volume commercial kitchen operations. Technicians work together as a team, traveling in a company box truck to perform fryer oil filtration, preventative maintenance, oil management services, and other specialized kitchen maintenance.

  That seems good.

  Responsibilities

  • Service commercial kitchen fryers and oil management systems
  • Perform fryer oil filtration and preventative maintenance
  • Safely remove and transport used cooking oil
  • Operate specialized filtration and cleaning equipment
  • Travel in a company box truck with another technician
  • Service universities, stadiums, healthcare facilities, entertainment venues, and other large‑volume customers
  • Complete service documentation using company mobile applications
  • Build positive customer relationships
  • Follow all company safety policies and procedures
  • Maintain company equipment and vehicles in a clean, professional condition
  • Represent AFS professionally at all customer locations

  Requirements

  • Reliable attendance and strong work ethic
  • Ability to work overnight and early morning schedules
  • Strong teamwork and communication skills
  • Customer‑focused attitude
  • Valid driver's license with a good driving record
  • High School Diploma or GED
  • Ability to lift, push, pull, and carry up to 45 pounds
  • Comfortable working around used cooking oil, grease, and commercial kitchen equipment
  • Comfortable using smartphones and mobile applications
  • Strong attention to detail
  • Ability to reliably commute to the West Chester, OH facility
  • Ability to pass a background check and drug screen
  Optionally include Preferred Experience as a subsection? Could be under Requirements or Qualifications. Since we have "Preferred Experience (Not Required)" we could put under a

  Preferred Experience

  but not a standard heading; maybe we can incorporate into Requirements as a note. But instruction: use headings only for standard sections; we could add a

  Preferred Experience

  if we want, but it's not in the list. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map Preferred Experience into Requirements or Qualifications. Let's put under Requirements as a note: maybe a

  Preferred experience (not required): route service or delivery experience, box truck driving experience, restaurant/food service/commercial cleaning experience, equipment maintenance/mechanical aptitude, facilities/field service experience.

  But we need to use
  • for any list. So we could make a list under Requirements for required, and then a separate

    Preferred Experience

    not allowed? Might be okay to add but risk violating instruction. Safer to incorporate into Requirements as a

    with list? The instruction: "Use

    • for any list of duties/requirements/benefits". So if we have a list of preferred experience, we should use
      • . So we could add a

        Preferred Experience

        but it's not in the allowed headings list. However the instruction says: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive? It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings if they are relevant, but the examples are given. Safer to stick to those headings. So we can incorporate preferred experience into Requirements or Qualifications. We could have a

        Qualifications

        that includes both required and preferred. But we already have Requirements. Maybe we can have Qualifications for education/certifications, and Requirements for skills/experience. However the posting doesn't separate clearly. Let's just have Requirements covering both required and preferred, with a note. Thus:

        Requirements

        • Reliable attendance and strong work ethic
        • Ability to work overnight and early morning schedules
        • Strong teamwork and communication skills
        • Customer‑focused attitude
        • Valid driver's license with a good driving record
        • High School Diploma or GED
        • Ability to lift, push, pull, and carry up to 45 pounds
        • Comfortable working around used cooking oil, grease, and commercial kitchen equipment
        • Comfortable using smartphones and mobile applications
        • Strong attention to detail
        • Ability to reliably commute to the West Chester, OH facility
        • Ability to pass a background check and drug screen

        Preferred experience (not required): route service or delivery experience, box truck driving experience, restaurant, food service, or commercial cleaning experience, equipment maintenance or mechanical aptitude, facilities or field service experience.

        Now Benefits: we need to list benefits from "Why Join Advanced Fryer Solutions?" includes: $22-$25/hr Starting Pay + Monthly Bonus, $500 New Hire Bonus After Successful Completion of 90 Days, 4-Day Workweek with Weekends Off, Company Vehicle During Work Hours, Paid Training and Advancement Opportunities, Comprehensive Benefits Package Including Medical, Dental, Vision, Life Insurance, Short-Term Disability, PTO, Paid Holidays, and IRA with Company Match, Work Boots and Uniforms Provided, Stable, Growing Company. We need separate sections for Pay, Schedule, Benefits. So we should extract Pay and Schedule into their own sections, and Benefits for the rest. Pay: $22-$25/hr Starting Pay + Monthly Bonus, $500 New Hire Bonus After Successful Completion of 90 Days. Schedule: Full-Time Four 10-hour shifts per week, Overnight and early morning hours, Typical start times between 12:00 AM and 3:00 AM, Weekends off, Three days off each week, Consistent full-time schedule. Benefits: 4-Day Workweek with Weekends Off (but that's also schedule; we already have schedule; maybe we should not duplicate. Since schedule section already covers 4-day workweek and weekends off, we should not repeat in Benefits. So Benefits: Company Vehicle During Work Hours, Paid Training and Advancement Opportunities, Comprehensive Benefits Package Including Medical, Dental, Vision, Life Insurance, Short-Term Disability, PTO, Paid Holidays, and IRA with Company Match, Work Boots and Uniforms Provided, Stable, Growing Company. Also note: "Stable, Growing Company" is a bit vague but it's substantive. We need to avoid filler like "not specified". Not present. Now we need to ensure we don't duplicate content: The schedule section includes "Four 10-hour shifts per week", "Overnight and early morning hours", "Typical start times between 12:00 AM and 3:00 AM", "Weekends off", "Three days off each week", "Consistent full-time schedule". The Benefits section should not repeat those. Now we need to output HTML fragment with sections in logical order: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Or maybe Benefits before Pay? The order not specified; we can choose. Let's produce:

        About the role

        ...

        Responsibilities

        ...

        Requirements

        ...

        Preferred experience (not required): ...

        Benefits

        ...

        Pay

        $22‑$25/hr starting pay + monthly bonus; $500 new hire bonus after successful completion of 90 days.

        Schedule

        ...
        Make sure to use proper hyphen encoding? Use plain hyphen. Now check for any leftover boilerplate: removed "Before You Apply", "At AFS, we hire individuals who demonstrate our core values..." etc. Also removed "Why Join Advanced Fryer Solutions?" heading; we incorporated its content into Benefits/Pay/Schedule. Check for duplicated lines: Ensure we didn't repeat "Weekends off" etc. In Benefits