HVAC Service Technician

We need to output HTML fragment only HTML fragment, no /. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse the job posting: - Job Type Full-time (metadata, we can drop or put in short p) - Description: Southern Home Services ... (intro paragraph) - About This Role: description paragraph. - In This Role, You Will Be Responsible For: list of duties. - Required Qualifications: list of qualifications. - The Physical Requirements Of This Job Include: list of physical requirements. - Benefits: list of benefits. - Then EEO boilerplate to remove. We also have "Pay" and "Schedule" sections: Not explicitly mentioned. There's "Weekly Paychecks" under benefits, but not explicit pay amount. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have explicit list, so we can include Benefits section. Pay: we have "Weekly Paychecks" and "Generous pay incentives for your quality work". That's some pay info, but not specific numbers. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Weekly Paychecks" is specific enough? It states they pay weekly. That's a concrete detail about pay schedule. Could be considered Pay section content. However they also have "Schedule" maybe not explicit. There's "flexible schedules" mentioned under benefits. That's schedule info. So we could have a Schedule section with "flexible schedules". But we need to see if we should create separate Pay and Schedule sections or combine into Benefits? The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Pay and Schedule into Benefits? But they said use headings for those categories if content exists. Since we have some info about pay (weekly paychecks, generous pay incentives) and schedule (flexible schedules), we could create Pay and Schedule sections each with that info. However they are thin. Better to maybe include them under Benefits as they are part of benefits. But the instruction says use headings for those categories if content exists. It doesn't forbid combining, but says "Prefer a few substantive sections over many thin ones." So if Pay and Schedule are thin, maybe we omit them and include that info within Benefits. However Benefits already has list; we could add "Weekly paychecks" and "Generous pay incentives" and "Flexible schedules" as items in Benefits list. That would make Benefits more substantive. That seems aligned with preference. Thus we will have sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Physical Requirements?), Qualifications, Skills, Benefits. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with substantive content. We have: - About the role: paragraph about role. - Responsibilities: list of duties. - Requirements: maybe combine Required Qualifications and Physical Requirements? Could be separate: Requirements (maybe includes qualifications) and Qualifications (maybe skills). But we have both "Required Qualifications" and a list of skills/attributes. Could treat Required Qualifications as Requirements, and the bullet list of skills as Qualifications or Skills. However the instruction says use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. Let's extract: About the role: paragraph after "About This Role". Responsibilities: list after "In This Role, You Will Be Responsible For". Requirements: maybe the "Required Qualifications" list (2-5+ years experience, EPA cert, driver's license, etc.) That seems like requirements. Qualifications: maybe the list of skills/attributes: "Possesses strong troubleshooting...", "Demonstrates a positive attitude...", etc. Those are qualifications/skills. Skills: maybe we could split further but we have overlapping. Could treat the list after Required Qualifications as Qualifications, and the later bullet list as Skills. But the later list includes many skill-like items. Actually the Required Qualifications list includes: "2-5+ years of residential HVAC Service experience", "EPA Certification is required.", "Valid driver’s license and clean driving record", "Possesses strong troubleshooting and critical thinking skills for resolving complex HVAC issues.", "Demonstrates a positive attitude and a strong commitment to high-quality workmanship.", "Prioritizes exceptional customer service and effectively addresses diverse client needs.", "Skilled in interacting professionally with individuals at all organizational levels.", "Flexible and innovative team player, thriving in dynamic environments and adapting to new challenges." That's a mix of experience, certifications, and soft skills. Then after that, there is "The Physical Requirements Of This Job Include". That's physical requirements, could go under Requirements as well (maybe as a sublist). But we have a separate heading for Requirements; we could include both the qualification list and physical requirements under Requirements. However we also have a Qualifications heading; maybe we put the skill/attribute list there. But the Required Qualifications list already includes skill attributes. Hmm. We could decide: - Requirements: include the "Required Qualifications" list (experience, cert, driver's license) and maybe also physical requirements? But physical requirements are separate; we could put them under Requirements as well, but then Qualifications heading might be empty. Better to split: Requirements = the mandatory qualifications (experience, cert, license). Qualifications = the skill/attribute list (troubleshooting, attitude, customer service, interaction, team player). Skills = maybe we could leave empty or combine with Qualifications. But we need to avoid empty headings. We could make Skills section include the physical requirements? No, physical requirements are not skills. Could we put physical requirements under Requirements? Then Qualifications could be the skill list, and Skills could be empty -> not allowed. So we need to give Skills some content. Perhaps we can treat the skill list as Skills, and Qualifications as the experience/cert/license list. Then Requirements could be the physical requirements. That seems plausible: Requirements = physical demands. Qualifications = experience/cert/license. Skills = soft skills/attributes. Let's map: - Requirements: The Physical Requirements Of This Job Include list. - Qualifications: Required Qualifications list (experience, EPA cert, driver's license). - Skills: list of soft skills: strong troubleshooting, positive attitude, customer service, interacting professionally, flexible team player. Check if any content missing: The list after Required Qualifications includes those soft skills; we will move them to Skills. Now Benefits: we have list: Reliable, Year-Round Work; Generous pay incentives for your quality work; Weekly Paychecks; Paid Time Off and Paid Holidays; Comprehensive Medical, Dental and Vision Benefits; Company Matched 401k; Company provided vehicle; Employee discounts. Also "flexible schedules" mentioned earlier under benefits paragraph. We'll include that as an item. Now About the role: paragraph. Responsibilities: list of duties. Now we need to ensure we don't repeat job title as heading. Not needed. We must not include boilerplate: EEO etc. We must not include navigation, cookie, legal, etc. We must not include application instructions. We must preserve all substantive information. Now produce HTML fragment: We'll wrap sections in appropriate tags: each section heading

then content: either

for prose or

• for lists. We need to decide for each section what type. About the role: prose ->

  . Responsibilities: list ->

  • . Requirements (physical): list ->
    • . Qualifications (experience/cert/license): list ->
      • . Skills (soft skills): list ->
        • . Benefits: list ->
          • . We must not include Pay or Schedule sections as we merged into Benefits. Now check that we haven't omitted any substantive info: - Intro paragraph: "Southern Home Services is a residential HVAC, Plumbing and Electrical company that acquires, owns, and operates businesses around the United States. We are seeking business leaders to join our growing team and become an integral part of our company's future. Are you ready to be Part of Something BIGGER! AirNow, a Southern Home Services Company, is looking for a dynamic HVAC Service Technician to join a thriving business that believes in work life balance and cares about YOU!" This is substantive; we should include it maybe as a

            before About the role? The instruction says do not repeat job title as heading; we can include this as a

            before sections. It's part of description. We'll include it as a

            at start. - About This Role paragraph: we will put as

            under About the role. - Responsibilities list: we have items: "Clean, adjust, and repair HVAC systems, including air handling units, ductwork, vents, and condensation drainage." "Diagnose and perform service work on HVAC systems in residential settings to ensure optimal performance." "Provide expert HVAC solutions to customers, addressing their needs and offering professional recommendations." "Additional duties as assigned." We'll make

          • for each. - Requirements (physical): list items: "Lifting 50 pounds regularly and up to 100 pounds occasionally", "Climbing ladders, accessing attics, navigating tight spaces, driving, entering crawlspaces, pushing, carrying, pulling, using hand tools, and performing fine detail work.", "Ability to drive.", "Working in various environments, including indoor and outdoor settings, attics, crawlspaces.", "Ability to stand, walk and sit; talk or hear, both in person and by telephone.", "Use hands to handle or feel objects or controls; reach with hands and arms.", "Regularly stoop, kneel, bend, and crouch.", "The work requires regular exposure to extreme temperatures both indoors and outdoors, such as heat or cold, and adverse weather conditions such as wind, rain, ice or snow.", "Southern Home Services will make reasonable accommodations to allow an employee to perform the essential functions of the job." We'll include each as
          • . - Qualifications (experience/cert/license): list items: "2-5+ years of residential HVAC Service experience", "EPA Certification is required.", "Valid driver’s license and clean driving record". We'll include. - Skills (soft skills): list items: "Possesses strong troubleshooting and critical thinking skills for resolving complex HVAC issues.", "Demonstrates a positive attitude and a strong commitment to high-quality workmanship.", "Prioritizes exceptional customer service and effectively addresses diverse client needs.", "Skilled in interacting professionally with individuals at all organizational levels.", "Flexible and innovative team player, thriving in dynamic environments and adapting to new challenges." - Benefits: list items: "Reliable, Year-Round Work", "Generous pay incentives for your quality work", "Weekly Paychecks", "Paid Time Off and Paid Holidays", "Comprehensive Medical, Dental and Vision Benefits", "Company Matched 401k", "Company provided vehicle", "Employee discounts", "Flexible schedules". Also maybe "professional and on-the-job training, and growth plans." from benefits paragraph: "We offer a rewarding career path with great benefits, flexible schedules, professional and on-the-job training, and growth plans." So we should include "professional and on-the-job training", "growth plans". Also "Be a part of the team our customers call the finest in the industry." That's more fluff but could be included as a

            maybe. But we can incorporate as part of benefits description? The instruction: preserve all substantive information. So we should include that sentence somewhere. Could be a

            under Benefits before list or after. But we said we prefer few sections; we could add a

            before the list describing benefits. That's okay