Caregivers
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to decide which sections to include based on actual content.
We have content for:
- About the role? The intro paragraph could be considered "About the role". It's prose describing the job and company. We could put that under
About the role
with a .
- Responsibilities: we have bullet list of duties. So
Responsibilities
with - ... .
- Qualifications: we have bullet list of qualifications. So
Qualifications
with - ... .
- Benefits: we have medical, hospitalization, vision, dental benefits, retirement plan after 6 months, accrued PTO up to 80 hours, 1.5x pay for holidays, employee wellbeing recognition, exceptional support team, manager 24/7, excellent training program day one and ongoing, career opportunities. Also flexible schedule and starting wage maybe separate sections Pay and Schedule.
But we need to avoid many thin sections; prefer a few substantive sections. Could combine Pay and Schedule into Benefits? But instruction says use headings for Pay, Schedule, Benefits etc if they exist. However we can decide to make a Benefits section that includes pay, schedule, and other benefits. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Starting Wage, flexible schedule, etc. So we could create separate Pay and Schedule sections if we want, but they said prefer a few substantive sections over many thin ones. So maybe we combine Pay and Schedule into a Benefits section, but we need to follow heading examples: they gave examples but not mandatory to use exactly those headings; they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if we have content. But we can also choose to not create Pay and Schedule separate if we think it's too thin; but we have concrete info: Starting Wage $16.50 per hour (plus Holiday premium pay). That's specific pay info. Flexible schedule – Full Time and Part Time hours available! Work when and where YOU want (hourly shifts or live-in). That's schedule info. So we have substantive content for both Pay and Schedule. Could we combine them into a "Compensation and Schedule" section? Not in examples. But we could still create Pay and Schedule sections each with a - containing the info. That would be two sections; still few.
But we also have Benefits: medical etc, retirement, PTO, holiday pay, support team, training, career opportunities, wellbeing recognition. That's also substantive.
Thus we could have sections: About the role, Responsibilities, Qualifications, Pay, Schedule, Benefits.
That's six sections; maybe okay. But they said prefer a few substantive sections over many thin ones. Six might be okay if each has substantive content.
Alternatively, we could merge Pay and Schedule into Benefits, making Benefits section longer. But then we would lose explicit Pay and Schedule headings; but we could still include that info inside Benefits as prose or list. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't mandate we must use those exact headings; they are examples. So we could choose to use Benefits heading and include pay and schedule info there. That would reduce number of sections.
Given the instruction to prefer few substantive sections, I'd lean to combine Pay and Schedule into Benefits. However we must ensure we don't create a heading with filler text. Benefits will have real content: medical, dental, vision, retirement, PTO, holiday pay, support, training, career opportunities, wellbeing recognition, flexible schedule, starting wage. That's substantive.
Thus sections: About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we don't miss any substantive info: The intro also mentions "We service clients in YOUR area!" and "We are proud of our 95% employee satisfaction rating." and "With over 35 years in the home care industry, we are constantly in need of GREAT workers for our clients." That's all about the role/company.
Responsibilities list: Companionship and engaging activities; Assist with personal care and medication reminders; Provide basic house cleaning, laundry, and assist with meal preparation.; Escort client to appointments and errands as needed.
Qualifications list: Able to pass a criminal background check.; A warm heart and gentle touch!; Reliable, energetic, self-motivated and well-organized.; 2 references (1 professional, 1 personal). #indcaregiver1 #DJPCS
Benefits: Starting Wage is $16.50 per hour (plus Holiday premium pay). Flexible schedule – Full Time and Part Time hours available! Work when and where YOU want (hourly shifts or live-in). Exceptional support team. Manager is available 24 hours a day, 7 days a week! Excellent training program on day one… and ongoing! Career opportunities. Medical, hospitalization, vision, dental benefits through employer sponsored minimum essential plan. Eligible to enroll in employer sponsored retirement plan after 6 months of service (21 years of age). Accrued paid time off (up to 80 hours per year based on tenure). 1.5x pay for scheduled/worked covered holidays. Employee wellbeing is top priority at Addus Homecare, and we're thrilled to announce our recognition as the top healthcare company on Indeed's 2024 Top 100 Work Wellbeing Index. View the full rankings here: https://www.indeed.com/employers/work-wellbeing/work-wellbeing-100-ranking.
We need to decide how to format Benefits: could be a - for each benefit item. But some items are sentences; we can still put each as
- . That's fine.
We must not include application instructions: "Apply to join our team, and START WITHIN DAYS!" and "Call or apply today and learn more about our current opportunities. 1(888)342-4636, extension 3." Remove those.
Also remove hashtags? The qualifications include "#indcaregiver1 #DJPCS". Those are likely tags; they are part of qualifications line. Should we keep them? They are part of the line "2 references (1 professional, 1 personal). #indcaregiver1 #DJPCS". The hashtags might be
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include based on actual content. We have content for: - About the role? The intro paragraph could be considered "About the role". It's prose describing the job and company. We could put that under
About the role
with a. - Responsibilities: we have bullet list of duties. So
Responsibilities
with- ... .
- Qualifications: we have bullet list of qualifications. So
Qualifications
with- ... .
- Benefits: we have medical, hospitalization, vision, dental benefits, retirement plan after 6 months, accrued PTO up to 80 hours, 1.5x pay for holidays, employee wellbeing recognition, exceptional support team, manager 24/7, excellent training program day one and ongoing, career opportunities. Also flexible schedule and starting wage maybe separate sections Pay and Schedule.
But we need to avoid many thin sections; prefer a few substantive sections. Could combine Pay and Schedule into Benefits? But instruction says use headings for Pay, Schedule, Benefits etc if they exist. However we can decide to make a Benefits section that includes pay, schedule, and other benefits. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Starting Wage, flexible schedule, etc. So we could create separate Pay and Schedule sections if we want, but they said prefer a few substantive sections over many thin ones. So maybe we combine Pay and Schedule into a Benefits section, but we need to follow heading examples: they gave examples but not mandatory to use exactly those headings; they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if we have content. But we can also choose to not create Pay and Schedule separate if we think it's too thin; but we have concrete info: Starting Wage $16.50 per hour (plus Holiday premium pay). That's specific pay info. Flexible schedule – Full Time and Part Time hours available! Work when and where YOU want (hourly shifts or live-in). That's schedule info. So we have substantive content for both Pay and Schedule. Could we combine them into a "Compensation and Schedule" section? Not in examples. But we could still create Pay and Schedule sections each with a
- containing the info. That would be two sections; still few.
But we also have Benefits: medical etc, retirement, PTO, holiday pay, support team, training, career opportunities, wellbeing recognition. That's also substantive.
Thus we could have sections: About the role, Responsibilities, Qualifications, Pay, Schedule, Benefits.
That's six sections; maybe okay. But they said prefer a few substantive sections over many thin ones. Six might be okay if each has substantive content.
Alternatively, we could merge Pay and Schedule into Benefits, making Benefits section longer. But then we would lose explicit Pay and Schedule headings; but we could still include that info inside Benefits as prose or list. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't mandate we must use those exact headings; they are examples. So we could choose to use Benefits heading and include pay and schedule info there. That would reduce number of sections. Given the instruction to prefer few substantive sections, I'd lean to combine Pay and Schedule into Benefits. However we must ensure we don't create a heading with filler text. Benefits will have real content: medical, dental, vision, retirement, PTO, holiday pay, support, training, career opportunities, wellbeing recognition, flexible schedule, starting wage. That's substantive. Thus sections: About the role, Responsibilities, Qualifications, Benefits. We need to ensure we don't miss any substantive info: The intro also mentions "We service clients in YOUR area!" and "We are proud of our 95% employee satisfaction rating." and "With over 35 years in the home care industry, we are constantly in need of GREAT workers for our clients." That's all about the role/company. Responsibilities list: Companionship and engaging activities; Assist with personal care and medication reminders; Provide basic house cleaning, laundry, and assist with meal preparation.; Escort client to appointments and errands as needed. Qualifications list: Able to pass a criminal background check.; A warm heart and gentle touch!; Reliable, energetic, self-motivated and well-organized.; 2 references (1 professional, 1 personal). #indcaregiver1 #DJPCS Benefits: Starting Wage is $16.50 per hour (plus Holiday premium pay). Flexible schedule – Full Time and Part Time hours available! Work when and where YOU want (hourly shifts or live-in). Exceptional support team. Manager is available 24 hours a day, 7 days a week! Excellent training program on day one… and ongoing! Career opportunities. Medical, hospitalization, vision, dental benefits through employer sponsored minimum essential plan. Eligible to enroll in employer sponsored retirement plan after 6 months of service (21 years of age). Accrued paid time off (up to 80 hours per year based on tenure). 1.5x pay for scheduled/worked covered holidays. Employee wellbeing is top priority at Addus Homecare, and we're thrilled to announce our recognition as the top healthcare company on Indeed's 2024 Top 100 Work Wellbeing Index. View the full rankings here: https://www.indeed.com/employers/work-wellbeing/work-wellbeing-100-ranking. We need to decide how to format Benefits: could be a
- for each benefit item. But some items are sentences; we can still put each as
- . That's fine. We must not include application instructions: "Apply to join our team, and START WITHIN DAYS!" and "Call or apply today and learn more about our current opportunities. 1(888)342-4636, extension 3." Remove those. Also remove hashtags? The qualifications include "#indcaregiver1 #DJPCS". Those are likely tags; they are part of qualifications line. Should we keep them? They are part of the line "2 references (1 professional, 1 personal). #indcaregiver1 #DJPCS". The hashtags might be
- containing the info. That would be two sections; still few.
But we also have Benefits: medical etc, retirement, PTO, holiday pay, support team, training, career opportunities, wellbeing recognition. That's also substantive.
Thus we could have sections: About the role, Responsibilities, Qualifications, Pay, Schedule, Benefits.
That's six sections; maybe okay. But they said prefer a few substantive sections over many thin ones. Six might be okay if each has substantive content.
Alternatively, we could merge Pay and Schedule into Benefits, making Benefits section longer. But then we would lose explicit Pay and Schedule headings; but we could still include that info inside Benefits as prose or list. The instruction says "Use
- ... .
- Benefits: we have medical, hospitalization, vision, dental benefits, retirement plan after 6 months, accrued PTO up to 80 hours, 1.5x pay for holidays, employee wellbeing recognition, exceptional support team, manager 24/7, excellent training program day one and ongoing, career opportunities. Also flexible schedule and starting wage maybe separate sections Pay and Schedule.
But we need to avoid many thin sections; prefer a few substantive sections. Could combine Pay and Schedule into Benefits? But instruction says use headings for Pay, Schedule, Benefits etc if they exist. However we can decide to make a Benefits section that includes pay, schedule, and other benefits. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Starting Wage, flexible schedule, etc. So we could create separate Pay and Schedule sections if we want, but they said prefer a few substantive sections over many thin ones. So maybe we combine Pay and Schedule into a Benefits section, but we need to follow heading examples: they gave examples but not mandatory to use exactly those headings; they said use