Janitor

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting. Posting content: - "Janitor Who We Are? Trojan Storage is the best self-storage operator in the business with over 40+ locations in the U.S today! Simply put, we have the best people in the workplace with our amazing culture, healthy benefits, and growth opportunities." That's about the company; could be "About the role"? Actually "Who We Are?" is about the company. Could map to "About the role"? Usually "About the role" is description of role. But we have "Your Role:" later. So we could have "About the role" maybe summarizing the role description. But we need to avoid filler. We have "Your Role: Do you have a knack for keeping spaces clean? Look no further! We are looking for a motivated Janitor who keeps our stores in tip-top condition and makes our customers feel right at home, in a safe and clean environment." That's role description. We have "Your Benefits:" list. We have "Your Responsibilities:" list. We have "Qualifications:" list. We also have "Basic technical skills..." etc. That could be Skills. We have schedule info: "Flexible Part/Full-Time schedule between 9:30AM to 5:30PM (weekends 10AM – 4PM) 30-35 hrs. per week". That's schedule. Pay: Not mentioned. So we should NOT include Pay section because no specific pay. Benefits: list given. Schedule: we have schedule info. Requirements: maybe same as Qualifications? Usually Requirements separate. But we have Qualifications section; we could treat that as Requirements. But we need to decide which headings to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which are present. We have: - About the role: maybe we can combine "Who We Are?" and "Your Role:" into About the role. But we need to avoid filler. The "Who We Are?" is about company; could be considered About the role? Might be okay. - Responsibilities: present. - Requirements: maybe we can treat Qualifications as Requirements. But we also have Qualifications heading itself. Could we have both Requirements and Qualifications? Might be redundant. Better to pick one: Qualifications is more specific. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using both Requirements and Qualifications if content distinct. But we have qualifications list; we could treat that as Qualifications. Requirements could be things like driver's license, ability to lift, etc. That's also qualifications. Might be overlapping. Safer to include Qualifications only, and maybe Requirements omitted. - Skills: we have "Basic technical skills such as restarting a computer, checking internet connectivity, troubleshooting printers, operating a phone/tablet, and other office systems." plus "Excellent communication and interpersonal skills." plus "Strong customer service skills". That's skills. - Benefits: list. - Schedule: schedule info. - Pay: none -> omit. We need to preserve all substantive information. So we need to include all details from the posting, except boilerplate (EEO, etc). Also remove duplicated lines, cookie/navigation/legal etc. The posting includes EEO statement at end; we must remove that. Also remove "Andasol Management Inc. is an equal opportunity employer..." etc. Also remove "Apply today to join one of the fastest growing self-storage operators in the business!" maybe that's application instruction? It's a call to apply; we should remove application instructions. The instruction says remove application instructions. So we should remove that line. Also remove "Andasol does not discriminate..." etc. Also remove contact email for accommodation? That's part of EEO? It's also maybe considered boilerplate; we should remove. Thus final HTML will have sections:

About the role

with paragraph(s) containing company description and role description.

Responsibilities

with

• list.

  Qualifications

  with
  • list (including driver's license, physical abilities, weekend availability, etc.)

    Skills

    with
    • list (technical skills, communication, customer service)

      Benefits

      with
      • list (flexible schedule, sick time, referral program, employee discount store discounted storage, education assistance program, employee assistance program, work/life balance, growth opportunities, mileage reimbursement, and much more…). Need to preserve each bullet as given.

        Schedule

        with

        containing schedule details. We must not repeat job title as heading. The job title is "Janitor". Not used as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment. Let's extract details precisely. Company description: "Trojan Storage is the best self-storage operator in the business with over 40+ locations in the U.S today! Simply put, we have the best people in the workplace with our amazing culture, healthy benefits, and growth opportunities." Role description: "Do you have a knack for keeping spaces clean? Look no further! We are looking for a motivated Janitor who keeps our stores in tip-top condition and makes our customers feel right at home, in a safe and clean environment." Combine into About the role paragraph(s). Could be two paragraphs. Responsibilities list: from "Your Responsibilities:": - Cleaning offices, restrooms, and common areas such as corridors, driveways, loading areas, storage units, gutters, maintaining high levels of curb appeal. - Dispose of debris and abandoned goods as directed. - Conduct daily storage unit inspections and ensure spaces are ready to rent. - Report maintenance needs, safety concerns, and any equipment failures to their direct report. - Directing customers to their units and self-storage kiosks/sales areas and delivering great customer experiences. - Basic troubleshooting of on-site systems such as gate & access control and general technology components for customer service. - Performs safe best practices when fulfilling daily tasks and utilizing onsite equipment. Note: Some items start with verb forms; keep as is. Qualifications list: from "Qualifications:": - Valid driver’s license, insurance, and working transportation required to travel between properties or conduct other work-related business. - Ability to stand, sit, crawl, bend, climb, or balance on a ladder, and transport/lift/move up to 45 lbs. - Ability to spend 50% of time in outdoor environments, climbing stairs and opening large doors. - Weekend availability and ability to work independently. - Basic technical skills such as restarting a computer, checking internet connectivity, troubleshooting printers, operating a phone/tablet, and other office systems. - Excellent communication and interpersonal skills. - Strong customer service skills with a passion for helping others. But note that "Basic technical skills..." etc could also be considered Skills. However they appear under Qualifications. We could split: keep technical skills under Skills, and communication/interpersonal/customer service also under Skills. But Qualifications would then contain driver's license, physical abilities, weekend availability. However the instruction says preserve all substantive information; we can categorize as we like as long as we don't lose info. Let's decide to put driver's license, physical abilities, weekend availability under Qualifications, and put technical skills, communication, customer service under Skills. That seems logical. Thus Qualifications list: - Valid driver’s license, insurance, and working transportation required to travel between properties or conduct other work-related business. - Ability to stand, sit, crawl, bend, climb, or balance on a ladder, and transport/lift/move up to 45 lbs. - Ability to spend 50% of time in outdoor environments, climbing stairs and opening large doors. - Weekend availability and ability to work independently. Skills list: - Basic technical skills such as restarting a computer, checking internet connectivity, troubleshooting printers, operating a phone/tablet, and other office systems. - Excellent communication and interpersonal skills. - Strong customer service skills with a passion for helping others. Benefits list: from "Your Benefits:": - Flexible Part/Full-Time schedule between 9:30AM to 5:30PM (weekends 10AM – 4PM) 30-35 hrs. per week - Sick Time Available - Referral Program - Employee Discount Store Discounted Storage - Education Assistance Program - Employee Assistance Program - Work/Life Balance - Growth Opportunities - Mileage Reimbursement - And Much More… Note: The first bullet includes schedule info; but we also have a separate Schedule section. Might duplicate. The instruction says we should not duplicate. We have schedule info also in Benefits. We could either keep schedule under Benefits and not have separate Schedule, or we could split schedule info out. The posting says "Your Benefits: Flexible Part/Full-Time schedule between 9:30AM to 5:30PM (weekends 10AM – 4PM) 30-35 hrs. per week | Sick Time Available | Referral Program | Employee Discount Store Discounted Storage | Education Assistance Program | Employee Assistance Program Work/Life Balance | Growth Opportunities | Mileage Reimbursement | And Much More…" Thus the first benefit includes schedule. We could keep schedule as part of Benefits and not create separate Schedule section. But the instruction says we should include a Schedule section only if posting actually states them. It does state schedule, but it's within Benefits. We could still create a Schedule section with that detail, but then we would be duplicating the schedule info (also in Benefits). To avoid duplication, we could either move schedule detail to Schedule section and remove from Benefits, or keep schedule in Benefits and not have Schedule section. Which is better? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we keep schedule inside Benefits and not create a separate Schedule section, to avoid thin section. However the schedule is quite specific; but it's already in Benefits. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule, but it's inside Benefits. If we create a Schedule section, we would be stating it again, which is duplication but not invented. However we must not duplicate lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines refers to duplicated content in the source; we should not duplicate content that appears multiple times in the source. The source only mentions schedule once (in Benefits). If we create a Schedule section, we would be repeating that content, which is duplication of content (though not present twice in source). The instruction likely means don't output duplicate lines that appear multiple times in the source; but creating a new section with same content is not a duplicate line from source, but it's still repeating the info. Might be okay but they said "Prefer a few substantive sections over many thin ones." So better to keep schedule within Benefits and not create a separate Schedule section. Thus we will have Benefits section with the list including schedule bullet. We need to ensure we don't include Pay section. Now we need to output HTML fragment. Structure:

        About the role

        Trojan Storage is the best self-storage operator in the business with over 40+ locations in the U.S today! Simply put, we have the best people in the workplace with our amazing culture, healthy benefits, and growth opportunities.

        Do you have a knack for keeping spaces clean? Look no further! We are looking for a motivated Janitor who keeps our stores in tip-top condition and makes our customers feel right at home, in a safe and clean environment.

        Respons