Lead Cleaner

We need to output HTML fragment only, with sections as needed. Must include headings using

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO etc. Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Pay: $17.00 per hour. Also includes Benefit Information: ABM offers a comprehensive benefits package. For information about ABM’s benefits, visit ABM Employee Benefits | Front Line Team Members. So we have Pay and Benefits content. Schedule? Not mentioned. So we should not create Schedule section. Skills? Not explicit; maybe we can infer but we should not invent. So we may not include Skills unless there is explicit content. Qualifications? There's a Qualifications section with Required and Preferred. So include Qualifications. Responsibilities section present. About the role? The initial paragraph describes role; we could put that under About the role. Also there is "About Us" which is company description; maybe not needed as per headings list; but we could include as About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About the role" could contain the initial description of role. "Responsibilities" list. "Qualifications" list (Required and Preferred). "Benefits" from benefit info. "Pay" from pay line. "Requirements" maybe not separate; we have qualifications required and preferred; could put under Qualifications. There's no separate Requirements section besides qualifications. Could we include Requirements as a heading? The posting has "Qualifications Required:" and "Preferred:" So we could treat that as Qualifications. The instruction says we can include sections only when posting has real specific content. So we include About the role, Responsibilities, Qualifications, Benefits, Pay. Not Requirements, Skills, Schedule. We must not repeat job title as heading. The job title is "Lead" maybe? Not needed. We must not put Job ID/requisition numbers as headings; none present. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities list, qualifications, benefits, pay, about role. We need to use

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

  for prose. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About the role: The initial paragraph(s) before Responsibilities: "We are looking for a reliable and experienced Lead to ensure all facility operations follow policies and procedures. They coordinate daily operations by delegating job assignments and providing guidance. A Lead provides supervision at an assigned location when the Manager is not present. The Shift Leader demonstrates established standards to keep the buildings/facilities clean and safe for all workers and customers. This role involves operating specialized equipment, handling cleaning chemicals, and supporting general janitorial duties as needed." Also there is "A good job for someone just entering the workforce or returning to the workforce with limited experience and education. ABM is a military and veteran friendly employer, veterans and candidates with military experience encouraged to apply." That seems like additional info about role suitability; could be included in About the role or maybe separate but we can include in About the role as prose. Also there is "About Us" paragraph describing ABM; that's company info, not role. Should we include? The instruction says preserve ALL substantive information; but we should not include boilerplate like About Us? It's not boilerplate; it's substantive about company. However the headings list does not have a specific "About the company". Could we include it under About the role? Might be stretching. But we could include as a separate paragraph under About the role? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It doesn't say we cannot add other headings, but likely they expect only those headings. Safer to stick to those headings. The About Us content could be omitted? But instruction says preserve ALL substantive information; do not invent or summarize away detail. If we omit About Us, we lose substantive info about company. However maybe they consider that as boilerplate? It's not navigation/legal/EEO etc. It's company description. Might be considered substantive. But there is no heading for About the company; we could incorporate it into About the role as extra prose, though it's not about the role but about the company. Might be okay. Alternatively we could create a heading "About the company" but not in list; risk. Better to include under About the role as additional prose. Now Responsibilities: list items after "Responsibilities". Let's extract: - Any additional certifications, trainings needed by site type. - Follow assigned work schedules, route cards as directed. - Report any barriers. - Provides leadership and direction to team members. - Provides open communication between field employees and management, monitors and documents client communications. - Assists with making daily and weekly work schedules - Oversee and perform cleaning operations in assigned building - Takes care of keys and access cards for the property - Reports damaged, broken and out of work features/items - Oversee and perform additional service requests (tag job) in assigned building - Oversees quality of jobs and confirms completion with Area Manager. - Provides training for all new hires assigned to the building in accordance with onboarding procedures. - Completes and validates any time records for regular or subcontractor employees. - Checks supplies, equipment, and chemicals weekly. - Miscellaneous duties as assigned. Note there is also line "Any additional certifications, trainings needed by site type." Might be a responsibility. We need to output as

  • each. Now Qualifications: Required and Preferred. Required: - Must be 18 years of age or older - A high school diploma, GED, or college degree is not required Preferred: - 1 year of similar work experience - 1 year of customer service experience - 1 year of lead or supervisory experience - Valid Driver’s license We need to output as list; maybe separate Required and Preferred? Could combine but better to separate with headings? Not required; we can just list all qualifications as
    • . But we might lose distinction. However instruction says preserve ALL substantive information; we can keep the distinction by adding a note in prose? Could do

      Required:

      ...

      Preferred:

      ... That's acceptable. Now Benefits: "ABM offers a comprehensive benefits package. For information about ABM’s benefits, visit ABM Employee Benefits | Front Line Team Members". That's the benefit info. We'll output as

      ABM offers a comprehensive benefits package. For information about ABM’s benefits, visit ABM Employee Benefits | Front Line Team Members

      . Pay: "Pay: $17.00 per hour The pay listed is the hourly range or the hourly rate for this position. A specific offer will vary based on applicant’s experience, skills, abilities, geographic location, and alignment with market data". We'll output as

      Pay: $17.00 per hour. The pay listed is the hourly range or the hourly rate for this position. A specific offer will vary based on applicant’s experience, skills, abilities, geographic location, and alignment with market data.

      Now About the role: combine the initial paragraphs plus the "A good job for someone just entering..." plus maybe About Us? Let's include the initial description and the good job statement. We'll omit About Us to avoid risk. But we might lose substantive info about ABM. However the instruction says preserve ALL substantive information; but maybe they consider About Us as boilerplate? It's not navigation/legal/EEO etc. It's company overview. Might be considered substantive. However there is no heading for About the company; we could still include as a paragraph under About the role, but it's not about the role. Might be okay. Let's include it: "ABM (NYSE: ABM) is one of the world’s largest providers of integrated facility, engineering, and infrastructure solutions. Every day, our over 100,000 team members deliver essential services that make spaces cleaner, safer, and efficient, enhancing the overall occupant experience. ABM serves a wide range of market sectors including commercial real estate, aviation, education, mission critical, and manufacturing and distribution. With over $8 billion in annual revenue and a blue-chip client base, ABM delivers innovative technologies and sustainable solutions that enhance facilities and empower clients to achieve their goals. Committed to creating smarter, more connected spaces, ABM is investing in the future to meet evolving challenges and build a healthier, thriving world. ABM: Driving possibility, together." That's a lot; but it's substantive. We'll include as prose under About the role. Now we must not include EEO etc. The posting includes EEO statements at end; we must remove them. Also remove "ABM directs all applicants to apply at www.abm.com/careers . ABM does not accept unsolicited resumes or submissions outside of this portal. Applicants should submit their application by clicking Apply Now. For more information, visit www.abm.com". That's application instructions; remove. Also remove "ABM participates in the U.S. Department of Homeland Security E-Verify program..." etc. That's legal/EEO; remove. Also remove "ABM is a military-friendly company..." etc? That's maybe not EEO but still about military-friendly; could be considered substantive? It's about veteran friendly. Might be considered part of About the role? The earlier "ABM is a military and veteran friendly employer, veterans and candidates with military experience encouraged to apply." That's already in About the role. The later military-friendly paragraph is more detailed; we could keep as part of About the role? It's not boilerplate; it's substantive about veteran support. Might be okay to keep. However it's near the end with other legal stuff; but we can keep if not EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The military-friendly statement is not EEO; it's a positive statement. Might be okay to keep. But to be safe, we could keep it as part of About the role. But we must also remove duplicated lines. There's no duplication. Now produce HTML. Structure:

      About the role

      ... (combined paragraphs)

      Responsibilities

      • ...
      ...

      Qualifications

      Required:

      • Must be 18 years of age or older
      • A high school diploma, GED, or college degree is not required

      Preferred:

      • 1 year of similar work experience
      • 1 year of customer service experience
      • 1 year of lead or supervisory experience
      • Valid Driver’s license

      Benefits

      ABM offers a comprehensive benefits package. For information about ABM’s benefits, visit ABM Employee Benefits | Front Line Team Members

      Pay

      Pay: $17.00 per hour. The pay listed is the hourly range or the hourly rate for this position. A specific offer will vary based on applicant’s experience, skills, abilities, geographic location, and alignment with market data.

      We should