Pest Control Technician - $1,500 Sign-On Bonus

We need to output HTML fragment with sections: Benefits, About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Benefits: "Benefits Start Day 1 for Full-Time Colleagues - No Waiting Period! For more information about our benefits, see below! ... We are proud to be a member of the Rentokil family..." Then later: "All Full-Time Colleagues qualify for the following and Part-Time Colleagues qualify for most benefits after they meet certain criteria. Click here to read more about our Total Rewards Program which includes: Professional and Personal Growth ... Health and Wellness ... Savings and Retirement ... Work-Long ... Work-Life Balance ..." Also "$1,500 Sign-On Bonus". So we have benefits info. - About the role: The description: "What do our Pest Control Technicians do? The primary purpose of this role is to perform our industry leading pest management services for residential customers. You will be responsible for identifying and eliminating pests from residential properties by conducting thorough inspections, determining the type of pest infestation, applying appropriate treatments like pesticides and traps, and providing preventative measures to prevent future infestations, all while adhering to safety regulations and communicating with clients about pest control solutions." That's a prose description. - Responsibilities: List after "Responsibilities Include But Are Not Limited To The Following" then bullet list items. - Essential Job Functions: Another list (maybe part of responsibilities? Could be separate but we can treat as part of responsibilities or maybe as "Requirements"? Actually essential job functions are more like physical demands; could be part of "Requirements" or "Qualifications". But we have sections: Requirements, Qualifications, Skills. We need to decide where to put them. - "What do you need?" list: Clean shaven face, high school diploma or GED, valid driver's license, licenses/certificates as required, available to work Monday-Friday and weekends as needed, open to learning, solid reading writing verbal communication skills, basic math skills, customer-facing experience preferred. That's qualifications/requirements. - Also "Why Choose Us?" includes benefits details again; but we already have benefits. - Pay: Not mentioned except sign-on bonus $1,500. That's pay? Could be considered Pay section: sign-on bonus. The posting does not give salary range. It mentions "$1,500 Sign-On Bonus". That is specific pay info. So we can include a Pay section with that detail. - Schedule: Not explicitly given except "Available to work Monday-Friday and weekends as needed". That's schedule info. So we can include Schedule section. - Benefits: Already have. Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3) maybe combine qualifications and skills? Could separate Qualifications (education/license) and Skills (communication, math, customer-facing). But we have limited content; better to combine into Requirements (or Qualifications). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We need to avoid filler. We'll include About the role, Responsibilities, Requirements (covering education, license, availability, learning, communication, math, customer-facing), Benefits, Pay, Schedule. Possibly also Qualifications? But we can put education/license under Requirements. Skills could be communication, math, customer-facing. But we already have those in Requirements. To avoid duplication, we could split: Requirements: education, license, availability. Skills: communication, math, customer-facing. Qualifications maybe not needed. Let's decide. We have: Clean shaven face (safety), high school diploma or GED; related experience/training; valid driver's license; licenses/certificates as required; available to work Monday-Friday and weekends as needed; open to learning; solid reading, writing, verbal communication skills; basic math skills; customer-facing experience preferred. We can categorize: - Requirements (mandatory): Clean shaven face, high school diploma or GED, valid driver's license, licenses/certificates as required, available to work Monday-Friday and weekends as needed. - Qualifications (preferred): related experience/training, open to learning, customer-facing experience preferred. - Skills: solid reading, writing, verbal communication skills; basic math skills. But we have limited sections; we can include Requirements, Qualifications, Skills. That would be three sections. However we need to avoid thin sections; but each has substantive content. Let's see: Requirements: Clean shaven face, high school diploma or GED, valid driver's license, licenses/certificates as required, available to work Monday-Friday and weekends as needed. Qualifications: related experience and/or training; or equivalent combination of education and experience; open to learning and becoming knowledgeable in all areas of pest control; customer-facing experience preferred. Skills: Solid reading, writing, and verbal communication skills; Basic math skills — you’ll need to be able to follow instructions for mixing on product labels. That seems reasonable. Now Benefits: We have details: Benefits start day 1 for full-time colleagues, no waiting period. $1,500 sign-on bonus. Also mention of Total Rewards Program: Professional and Personal Growth (multiple avenues to grow your career, training and development programs available, tuition reimbursement benefits for FT colleagues). Health and Wellness: Health benefits including Medical, Dental, Vision, Disability, and Life Insurance plus much more; full-time colleagues eligible to begin enrollment immediately upon hire with benefits starting on day 1. Savings and Retirement: 401(k) retirement plan with company-matching contributions. Work-Life Balance: Vacation days & sick days, company-paid holidays & floating holidays, company mindset that prioritizes health, safety, and flexibility. We should include all that as bullet list under Benefits. Pay: $1,500 Sign-On Bonus (maybe also mention competitive pay and performance incentives but not specific). We'll include the sign-on bonus. Schedule: Available to work Monday-Friday and weekends as needed. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include job title heading, no Job ID, no boilerplate, no navigation, no EEO, etc. Remove duplicated lines. We need to preserve all substantive information; do not invent or summarize away detail. Let's craft. First, About the role: prose paragraph. Second, Responsibilities: list items from "Responsibilities Include But Are Not Limited To The Following". The list includes: - Conduct thorough inspections of client properties to identify signs of pest infestations, damage, and entry points - Apply approved pest control products, including chemicals, baits, and traps, to effectively eliminate pests while adhering to safety standards - Educate customers on pest prevention methods and the importance of maintaining a pest-free environment. Provide advice on how to reduce the risk of future infestations. - Build relationships with customers, schedule and confirm their appointments, help with sales to current customers, and expand our product to new customers - Ensure that all pest control equipment is properly maintained, stocked, and in good working condition - Adhere to all local, state, and federal regulations regarding pest control products and safety protocols - Drive and safely operate a company provided service vehicle (we provide routine maintenance) We should keep each as

• . Third, Requirements: list as above. Fourth, Qualifications: list. Fifth, Skills: list. Sixth, Benefits: list. Seventh, Pay: maybe a

  with the sign-on bonus. Eighth, Schedule:

  or

  ? It's a single statement; we can use

  . We must not create sections with filler. All sections have content. Now ensure we don't repeat content. For example, "Available to work Monday-Friday and weekends as needed" appears both in Requirements and Schedule. That's okay but we might duplicate. However we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication if it's in the source. But we might want to avoid duplication by placing schedule info only in Schedule section and not repeat in Requirements. However the requirement list includes that as a requirement; it's also schedule info. Could keep in both but maybe better to keep in Requirements as it's a requirement, and Schedule could be derived from that but we need to include schedule section if posting actually states them. The posting states "Available to work Monday-Friday and weekends as needed" under "What do you need?" That's a requirement. It also implicitly gives schedule. The schedule section could be derived from that. But we need to include schedule section only if posting actually states them. It does state availability, which is schedule-related. So we can include schedule section with that statement. It's okay to have same content in two places? Might be considered duplication but not prohibited. However better to avoid duplication by moving that line to Schedule and not include in Requirements. But then we lose that requirement info. However the requirement list includes many items; we could keep the schedule statement in Requirements and also have Schedule section referencing same? Might be okay. Let's keep schedule section with that statement, and keep it also in Requirements? Might be redundant but okay. Alternatively we could move schedule statement to Schedule and remove from Requirements. But then we lose a requirement about availability. However availability is more schedule than qualification; but it's still a requirement. I'd keep it in Requirements and also have Schedule section maybe just restate. It's not ideal but acceptable. We'll proceed. Now Benefits list: need to capture all bullet points from Total Rewards Program. Let's extract: Professional and Personal Growth: - Multiple avenues to grow your career - Training and development programs available - Tuition Reimbursement benefits (for FT Colleagues) Health and Wellness: - Health benefits including Medical, Dental, Vision, Disability, and Life Insurance plus much more - Full-time colleagues are eligible to begin enrollment immediately upon hire with benefits starting on day 1 Savings and Retirement: - 401(k) retirement plan with company-matching contributions Work-Life Balance: - Vacation days & sick days - Company-paid holidays & floating holidays - A company mindset that prioritizes health, safety, and flexibility Also earlier: "Benefits Start Day 1 for Full-Time Colleagues - No Waiting Period!" and "$1,500 Sign-On Bonus*****". The sign-on bonus we put in Pay. We should also include "No Waiting Period!" maybe as part of Benefits. Thus Benefits list items: - Benefits start day 1 for full-time colleagues (no waiting period) - $1,500 sign-on bonus (maybe put in Pay though) But we already have Pay separate. We'll include Benefits list items as above. Now Pay: "$1,500 Sign-On Bonus". Could also mention competitive pay and performance incentives but not specific; we should not invent. So just the bonus. Now Schedule: "Available to work Monday-Friday and weekends as needed". Now ensure we don't include boilerplate like "We are proud to be a member of the Rentokil family..." that's about company; could be part of About the role? Actually that is more about company; but we could include in About the role? The About the role section should be about the role; but we could include a brief company description as part of About the role? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role likely should describe the role. The company description could be considered part of About the role or maybe we could omit as not strictly role. But we should preserve all substantive information; the company description is substantive but not about role. However we could include it in About the role as contextual info. It's not prohibited. We'll include a short paragraph about company after role description? Might be okay. But we must not invent or summarize