Weekend Personal Caregiver - driving required

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. No job title heading. No Job ID. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract content: - Opening: "Help at Home is hiring TODAY in your community! We are seeking a compassionate and reliable caregiver who can provide in-home support to clients and assist with transportation needs on weekends. The ideal candidate MUST have a valid driver’s license, insurance and a safe & reliable vehicle. They will help with daily activities and safely transport clients to appointments, errands, and social outings. Start your career with the nation’s leading provider of in-home support to seniors and become a hero for someone in your community." That's about the role. - "Why should you join Help at Home?" then bullet list: Flexible scheduling and weekend shifts Pay starts from $14 per hour (can vary by location, experience, and/or care plan) Mileage reimbursement for all client-related driving No experience required Amazing benefits – health care, paid time off, and referral bonuses! Meaningful work with clients who need your help Industry leader with 40+ years of history in a high-demand field Veteran-Friendly Employer: We encourage veterans, active military, and their spouses to apply for positions. Our roles are flexible, and we value your experience and expertise. - Then "Become a Help at Home Hero TODAY! Apply online or in person!" (application instruction, remove) - Then "As a Home Care Aide, You’ll Work 1-on-1 With Your Clients Inside Their Homes, And Support Them With The Following Types Of Activities" then list: Light housekeeping, including organizing, laundry, and basic cleaning Personal activities such as dressing, grooming, and assisting with meals Provide Safe and timely transportation to run errands, grocery shopping, and/or accompanying your clients to appointments. - Then "We are hiring now in your community – join our team and build your career in a high-demand industry." (maybe part of about role) - Then "Eligibility Requirements" list: Valid driver’s license Access to insured and reliable transportation Comfortable driving clients of all mobility levels Ability to assist clients in and out of vehicles as needed Dedication to professional development, including organizational and state-required training Caregivers must comply with state background screening requirements. - Then "Compensation, benefits, time off, and bonuses vary by state and location, so please ask for complete details at your interview." (maybe part of Pay/Benefits but it's vague; we should not create sections with vague content like "varies". We can include Pay and Benefits only if specific content. The posting gave Pay starts from $14 per hour (can vary...). That's somewhat specific but includes variability. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we cannot create a Pay section if the content is just "Pay starts from $14 per hour (can vary by location, experience, and/or care plan)". That includes "can vary". Might be considered placeholder? It does give a base rate. But the rule says avoid filler like "varies". The phrase includes "can vary". Might be considered not specific enough. Safer to omit Pay section? However we have other benefits specifics: Mileage reimbursement, health care, paid time off, referral bonuses. Those are specific. Also flexible scheduling and weekend shifts (Schedule). So we can have Benefits, Schedule sections. We must not repeat job title as heading. So we will have sections: About the role (maybe we can call it About the role), Responsibilities, Requirements, Qualifications? The posting includes eligibility requirements (driver's license etc). That's more like Requirements. Also there is "No experience required" which is a qualification? Could be under Qualifications. But we need to decide. We have content for: - About the role: introductory paragraph about seeking caregiver, transportation, etc. - Responsibilities: list of duties: light housekeeping, personal activities, transportation. - Requirements: eligibility requirements: driver's license, insured vehicle, comfortable driving, assist in/out, dedication to professional development, background screening. - Qualifications: maybe "No experience required" and "Veteran-friendly" etc? But those are more like benefits/encouragement. Could be under Benefits? Actually "Veteran-Friendly Employer" is a statement about encouraging veterans; could be under Benefits or maybe under About the role? Might be better to put under Benefits as a perk? But it's not a benefit per se. Could be under Qualifications? Not exactly. Might be better to include under About the role as a note. However we need to avoid thin sections. Perhaps combine some. We have Benefits: health care, paid time off, referral bonuses, mileage reimbursement, flexible scheduling and weekend shifts (though schedule could be separate). Also "Industry leader with 40+ years of history" maybe not a benefit but could be under About the role. Schedule: flexible scheduling and weekend shifts. Pay: we might omit due to variability. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Check if any content duplicated: we must not repeat. Now craft HTML. Use

for each section heading. Inside each section, use

for prose,

• for lists. We need to preserve all substantive info. Let's draft. About the role paragraph: Combine the opening sentences and maybe the "Why should you join Help at Home?" intro? Actually that's a heading for benefits list. We'll keep About the role as: "Help at Home is hiring TODAY in your community! We are seeking a compassionate and reliable caregiver who can provide in-home support to clients and assist with transportation needs on weekends. The ideal candidate MUST have a valid driver’s license, insurance and a safe & reliable vehicle. They will help with daily activities and safely transport clients to appointments, errands, and social outings. Start your career with the nation’s leading provider of in-home support to seniors and become a hero for someone in your community." That's good. Responsibilities: list: - Light housekeeping, including organizing, laundry, and basic cleaning - Personal activities such as dressing, grooming, and assisting with meals - Provide safe and timely transportation to run errands, grocery shopping, and/or accompanying your clients to appointments. We could also include "assist with transportation needs on weekends" but that's covered. Requirements (eligibility): - Valid driver’s license - Access to insured and reliable transportation - Comfortable driving clients of all mobility levels - Ability to assist clients in and out of vehicles as needed - Dedication to professional development, including organizational and state-required training - Caregivers must comply with state background screening requirements. Benefits: - Flexible scheduling and weekend shifts (maybe schedule separate) - Pay starts from $14 per hour (can vary by location, experience, and/or care plan) - but we said maybe omit Pay due to variability. However we could still include Pay as part of Benefits? The rule says do not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay starts from $14 per hour (can vary...). That's a statement about pay, albeit with variability. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase includes "can vary". That's similar to "varies". Might be considered filler. Safer to omit Pay section entirely. However we could still include the pay info inside Benefits as a note? But that would be mixing pay into Benefits, which may be okay if we don't create a Pay heading. The rule only forbids creating Pay/Schedule/Benefits sections unless posting actually states them. It doesn't forbid including pay info inside another section. So we could include pay info in Benefits section as a bullet. But the rule also says "Prefer a few substantive sections over many thin ones." So we could have Benefits section that includes pay, mileage reimbursement, health care, PTO, referral bonuses, veteran-friendly, industry leader, etc. However some of those are not benefits per se but could be included. But we also have Schedule section for flexible scheduling and weekend shifts. If we put flexible scheduling in Benefits, we might not need Schedule section. However the rule says we should create Schedule section only if posting actually states schedule info. It does: "Flexible scheduling and weekend shifts". So we could have Schedule section. Thus we can have: - Benefits: Mileage reimbursement, health care, paid time off, referral bonuses, Veteran-Friendly Employer statement, Industry leader with 40+ years of history. - Schedule: Flexible scheduling and weekend shifts. Pay: we could either omit or include as a bullet under Benefits? The rule says do not create Pay section unless posting actually states them. It does state pay, but it's vague. Might be better to omit Pay section entirely, but we could still mention pay in Benefits as a bullet? That would be including pay info but not having a dedicated Pay heading. The rule does not forbid that. However the instruction says "Prefer a few substantive sections over many thin ones." Adding pay as a bullet under Benefits may be okay. But we need to decide if we want to include pay info. The posting says "Pay starts from $14 per hour (can vary by location, experience, and/or care plan)". That's substantive info (a starting rate). Even though it includes variability, it's still a concrete number. The rule about filler text says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That refers to headings, not content. So we could have a Pay heading with that content; the content includes "can vary". That's not purely filler; it's a statement that includes a number and a note about variability. It's not just "varies". So maybe we can include Pay section. However the rule also says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay. So we can include Pay section. Thus we will have Pay section with that sentence. Now Schedule section: "Flexible scheduling and weekend shifts". That's specific. Now Benefits section: list mileage reimbursement, health care, paid time off, referral bonuses, Veteran-Friendly Employer statement, Industry leader with 40+ years of history, Meaningful work with clients who need your help (maybe that's more about role but could be benefit). Also "No experience required" could be a qualification but we could put under Requirements? Actually it's a qualification: no experience required. That's a qualification. We could have Qualifications section: "No experience required". Also "Veteran-Friendly Employer: We encourage veterans, active military, and their spouses to apply for positions. Our roles are flexible, and we value your experience and expertise." That's more like encouragement but could be under Benefits or About the role. We need to avoid thin sections. Perhaps combine Qualifications and Requirements? But they are distinct: Requirements are mandatory (driver's license, etc). Qualifications are preferred or optional (no experience required, veteran-friendly). However we have only one qualification: no experience required. Could be included in Requirements as a note? But it's not a requirement; it's a lack of requirement. Could be under About the role? Hmm. We could create a Qualifications section with that bullet. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if any section becomes thin: Qualifications only has one bullet "No experience required". That's thin but still substantive. Could we combine Qualifications into