Life Enrichment Aide
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (not provided anyway)
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no html/body, no markdown
Let me map the content to appropriate sections:
1. The first paragraph is about the company/team - could be "About the role" or "About the company". Since it's about the workplace culture, maybe "About the role" or just a general intro. The rules mention "About the role" as a possible heading.
2. "Advantages" - this seems like benefits/perks. Could be "Benefits" section.
3. "Benefits and Perks" - definitely "Benefits" section.
4. "Position Summary" - this is "About the role" or "Responsibilities". The summary describes the primary purpose, which is about the role.
5. "Education/Qualifications" - this is "Qualifications" or "Requirements".
6. "Shift & Wage" - this is "Schedule" and "Pay" information.
7. The note about program details varying and HR contact - could be folded into a short
or dropped.
8. EEO statement - boilerplate, remove.
I need to combine "Advantages" and "Benefits and Perks" into one Benefits section since they're both benefits.
"Position Summary" can be "About the role" or "Responsibilities". The summary says "The primary purpose of your job is to assist in the planning, implementation, and evaluation of recreational, social, educational/intellectual, cultural, physical, emotional and spiritual programs..." This sounds like responsibilities.
"Education/Qualifications" is clearly qualifications.
"Shift & Wage" has schedule info (Full-Time, Monday-Friday, some weekends) and pay info (Flexible Pay Options: On-Demand Pay or Weekly Pay). So both Schedule and Pay sections are warranted.
The note "Program details can vary amongst buildings. Please see HR for the facility-specific benefit plans." - this is minor metadata, fold into a short
or drop. I'll include it as a note in Benefits or at the end.
Now, let's structure:
-
About the role
with the first paragraph and position summary? Or separate? The first paragraph is about the company culture, not the role specifically. The position summary is about the role. I'll put the company intro as a before sections, or under "About the role". The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the role" is appropriate for the position summary.
But the first paragraph: "Join a team where compassion meets excellence..." is more about the company. Could be "About the company" but not in the example list. I'll include it as a
before the first heading, or under "About the role". Since the rule says "Do NOT repeat the job title as a heading (the page already shows it)", but there's no job title given. The user didn't provide a job title. The posting seems to be for an activities/recreational role based on the summary. But I shouldn't invent a title.
I'll start with a
for the company intro, then sections.
Sections:
1. About the role (position summary)
2. Responsibilities? The position summary is essentially responsibilities. Could be "Responsibilities". But the example includes both "About the role" and "Responsibilities". The position summary is a summary of the role, so "About the role" fits.
3. Qualifications (education/qualifications)
4. Benefits (combining Advantages and Benefits and Perks)
5. Pay (from Shift & Wage: Flexible Pay Options)
6. Schedule (from Shift & Wage: Full-Time, Monday-Friday, some weekends)
7. Maybe a note about program details varying.
But the rules: "Prefer a few substantive sections over many thin ones." So combine where appropriate.
Benefits section will have two lists: Advantages and Benefits and Perks. I'll make one list or two sublists? Use
- for any list. I can have two separate lists under Benefits heading.
Pay section: "Flexible Pay Options – Choose On-Demand Pay and get paid as soon as tomorrow for work done today or opt for our Weekly Pay schedule!" That's substantive.
Schedule section: "Full-Time Opportunity Available Shifts Needed: Monday - Friday Some Weekends" That's substantive.
The note "Program details can vary amongst buildings. Please see HR for the facility-specific benefit plans." I'll add as a
at the end of Benefits or as a separate note.
EEO statement: remove.
Now, write HTML.
No markdown, just HTML fragment.
Let's draft:
Join a team where compassion meets excellence in a skilled nursing facility - we're dedicated to delivering heartfelt care and making a meaningful difference in every patient's life. We’ve been recognized by Newsweek and Plant-A Insights Group as one of America’s Most Admired Workplaces for 2026! As an employee recently said, “I feel I have a lot of support. I feel like part of the team.”
About the role
The primary purpose of your job is to assist in the planning, implementation, and evaluation of recreational, social, educational/intellectual, cultural, physical, emotional and spiritual programs, in accordance with the resident’s assessment and care plan, and as directed by your supervisor.
Qualifications
- Must be currently enrolled in a high school program or have a high school diploma or equivalent.
- Previous long-term care experience preferred.
Benefits
Advantages:
- Flexible Pay Options – Choose On-Demand Pay and get paid as soon as tomorrow for work done today or opt for our Weekly Pay schedule!
- Positive, Family-Like Atmosphere – Work in a fun, supportive environment where you’re valued.
- Generous PTO & Benefits – Enjoy a comprehensive benefits package designed to support your well-being.
- Tuition Assistance – Advance your career with educational opportunities and support.
Benefits and Perks:
- DAILY Pay!
- Benefit eligibility the first of the month following 30 days
- Comprehensive benefit packages including medical, dental, and vision, and more.
- Health Savings Account available with employer contribution.
- 401K through Fidelity
- Employer-paid life insurance (FT employees)
- Robust Employee Assistance Program
- Generous Paid Time Off (PTO)
- Educational, leadership, and tuition opportunities
- Various discount programs offered, including discounted childcare programs through Kindercare
- Wellness programs offered through WebMD
- Employee recognition programs
- Culture of employees creating an IMPACT!
Program details can vary amongst buildings. Please see HR for the facility-specific benefit plans.
Pay
Flexible Pay Options – Choose On-Demand Pay and get paid as soon as tomorrow for work done today or opt for our Weekly Pay schedule.
Schedule
Full-Time Opportunity Available. Shifts Needed: Monday - Friday, Some Weekends.
But note: The "Flexible Pay Options" appears in both Advantages and Pay. That's duplication. In the original, "Advantages" includes "Flexible Pay Options" and "Benefits and Perks" includes "DAILY Pay!". Actually "DAILY Pay!" might be the same as On-Demand Pay. But I should preserve all substantive information. The Advantages list includes Flexible Pay Options as a bullet, and Benefits and Perks includes DAILY Pay! as a bullet. They might be redundant but I'll keep both as they appear.
However, the Pay section I created duplicates the Flexible Pay Options. Better to not duplicate. Since the Advantages list is under Benefits, and Pay section is separate, I could omit the Pay section and just have the info in Benefits? But the rules say include Pay section if posting actually states them. The posting states "Shift & Wage: Full-Time Opportunity Available Shifts Needed: Monday - Friday Some Weekends Program details can vary amongst buildings. Please see HR for the facility-specific benefit plans." And earlier "Advantages: Flexible Pay Options – Choose On-Demand Pay and get paid as soon as tomorrow for work done today or opt for our Weekly Pay schedule!" So pay info is in Advantages. But the "Shift & Wage" heading suggests pay and schedule. I'll keep Pay and Schedule sections, but for Pay, I'll reference the flexible pay options. However, to avoid duplication, I could move the pay info to Pay section and keep Advantages as other advantages. But the original has "Advantages" as a list that includes pay, atmosphere, PTO, tuition. Then "Benefits and Perks" as another list. I think it's okay to have Pay section with the pay details, and Benefits section with the other advantages and benefits perks. But the Advantages list includes pay as first bullet. I could split: keep the non-pay advantages in Benefits, and pay in Pay. But the rule: preserve ALL substantive information. Duplication is okay if it's in the source? The source has it in two places? Actually, "Flexible Pay Options" appears only in Advantages. "DAILY Pay!" appears in Benefits and Perks. They are similar but not identical. I'll keep both lists as they are under Benefits, and also have a Pay section summarizing? That would duplicate. Better to not have a separate Pay section if the pay info is already in Benefits. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay info (Flexible Pay Options, DAILY Pay) and schedule info (Full-Time, Monday-Friday, Some Weekends). So I should include Pay and Schedule sections. But to avoid duplication, I can have the Pay section contain the pay details, and in Benefits, I can omit the pay bullets? But the Advantages list is a cohesive list. The user said "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the Advantages list as is. Then Pay section would duplicate. Hmm.
Maybe I can structure: Benefits section includes both Advantages and Benefits and Perks lists. Then Pay section can be a short paragraph referencing the flexible pay options, but that duplicates. Alternatively, I can not have a separate Pay section, because the pay info is already in Benefits. But the rules say "include a section ONLY when the posting has real,
for prose - Do NOT repeat job title as heading (not provided anyway) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown Let me map the content to appropriate sections: 1. The first paragraph is about the company/team - could be "About the role" or "About the company". Since it's about the workplace culture, maybe "About the role" or just a general intro. The rules mention "About the role" as a possible heading. 2. "Advantages" - this seems like benefits/perks. Could be "Benefits" section. 3. "Benefits and Perks" - definitely "Benefits" section. 4. "Position Summary" - this is "About the role" or "Responsibilities". The summary describes the primary purpose, which is about the role. 5. "Education/Qualifications" - this is "Qualifications" or "Requirements". 6. "Shift & Wage" - this is "Schedule" and "Pay" information. 7. The note about program details varying and HR contact - could be folded into a short
or dropped. 8. EEO statement - boilerplate, remove. I need to combine "Advantages" and "Benefits and Perks" into one Benefits section since they're both benefits. "Position Summary" can be "About the role" or "Responsibilities". The summary says "The primary purpose of your job is to assist in the planning, implementation, and evaluation of recreational, social, educational/intellectual, cultural, physical, emotional and spiritual programs..." This sounds like responsibilities. "Education/Qualifications" is clearly qualifications. "Shift & Wage" has schedule info (Full-Time, Monday-Friday, some weekends) and pay info (Flexible Pay Options: On-Demand Pay or Weekly Pay). So both Schedule and Pay sections are warranted. The note "Program details can vary amongst buildings. Please see HR for the facility-specific benefit plans." - this is minor metadata, fold into a short
or drop. I'll include it as a note in Benefits or at the end. Now, let's structure: -
About the role
with the first paragraph and position summary? Or separate? The first paragraph is about the company culture, not the role specifically. The position summary is about the role. I'll put the company intro as abefore sections, or under "About the role". The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the role" is appropriate for the position summary. But the first paragraph: "Join a team where compassion meets excellence..." is more about the company. Could be "About the company" but not in the example list. I'll include it as a
before the first heading, or under "About the role". Since the rule says "Do NOT repeat the job title as a heading (the page already shows it)", but there's no job title given. The user didn't provide a job title. The posting seems to be for an activities/recreational role based on the summary. But I shouldn't invent a title. I'll start with a
for the company intro, then sections. Sections: 1. About the role (position summary) 2. Responsibilities? The position summary is essentially responsibilities. Could be "Responsibilities". But the example includes both "About the role" and "Responsibilities". The position summary is a summary of the role, so "About the role" fits. 3. Qualifications (education/qualifications) 4. Benefits (combining Advantages and Benefits and Perks) 5. Pay (from Shift & Wage: Flexible Pay Options) 6. Schedule (from Shift & Wage: Full-Time, Monday-Friday, some weekends) 7. Maybe a note about program details varying. But the rules: "Prefer a few substantive sections over many thin ones." So combine where appropriate. Benefits section will have two lists: Advantages and Benefits and Perks. I'll make one list or two sublists? Use
- for any list. I can have two separate lists under Benefits heading.
Pay section: "Flexible Pay Options – Choose On-Demand Pay and get paid as soon as tomorrow for work done today or opt for our Weekly Pay schedule!" That's substantive.
Schedule section: "Full-Time Opportunity Available Shifts Needed: Monday - Friday Some Weekends" That's substantive.
The note "Program details can vary amongst buildings. Please see HR for the facility-specific benefit plans." I'll add as a
at the end of Benefits or as a separate note. EEO statement: remove. Now, write HTML. No markdown, just HTML fragment. Let's draft:
Join a team where compassion meets excellence in a skilled nursing facility - we're dedicated to delivering heartfelt care and making a meaningful difference in every patient's life. We’ve been recognized by Newsweek and Plant-A Insights Group as one of America’s Most Admired Workplaces for 2026! As an employee recently said, “I feel I have a lot of support. I feel like part of the team.”
About the role
The primary purpose of your job is to assist in the planning, implementation, and evaluation of recreational, social, educational/intellectual, cultural, physical, emotional and spiritual programs, in accordance with the resident’s assessment and care plan, and as directed by your supervisor.
Qualifications
- Must be currently enrolled in a high school program or have a high school diploma or equivalent.
- Previous long-term care experience preferred.
Benefits
Advantages:
- Flexible Pay Options – Choose On-Demand Pay and get paid as soon as tomorrow for work done today or opt for our Weekly Pay schedule!
- Positive, Family-Like Atmosphere – Work in a fun, supportive environment where you’re valued.
- Generous PTO & Benefits – Enjoy a comprehensive benefits package designed to support your well-being.
- Tuition Assistance – Advance your career with educational opportunities and support.
Benefits and Perks:
- DAILY Pay!
- Benefit eligibility the first of the month following 30 days
- Comprehensive benefit packages including medical, dental, and vision, and more.
- Health Savings Account available with employer contribution.
- 401K through Fidelity
- Employer-paid life insurance (FT employees)
- Robust Employee Assistance Program
- Generous Paid Time Off (PTO)
- Educational, leadership, and tuition opportunities
- Various discount programs offered, including discounted childcare programs through Kindercare
- Wellness programs offered through WebMD
- Employee recognition programs
- Culture of employees creating an IMPACT!
Program details can vary amongst buildings. Please see HR for the facility-specific benefit plans.
Pay
Flexible Pay Options – Choose On-Demand Pay and get paid as soon as tomorrow for work done today or opt for our Weekly Pay schedule.
Schedule
Full-Time Opportunity Available. Shifts Needed: Monday - Friday, Some Weekends.
But note: The "Flexible Pay Options" appears in both Advantages and Pay. That's duplication. In the original, "Advantages" includes "Flexible Pay Options" and "Benefits and Perks" includes "DAILY Pay!". Actually "DAILY Pay!" might be the same as On-Demand Pay. But I should preserve all substantive information. The Advantages list includes Flexible Pay Options as a bullet, and Benefits and Perks includes DAILY Pay! as a bullet. They might be redundant but I'll keep both as they appear. However, the Pay section I created duplicates the Flexible Pay Options. Better to not duplicate. Since the Advantages list is under Benefits, and Pay section is separate, I could omit the Pay section and just have the info in Benefits? But the rules say include Pay section if posting actually states them. The posting states "Shift & Wage: Full-Time Opportunity Available Shifts Needed: Monday - Friday Some Weekends Program details can vary amongst buildings. Please see HR for the facility-specific benefit plans." And earlier "Advantages: Flexible Pay Options – Choose On-Demand Pay and get paid as soon as tomorrow for work done today or opt for our Weekly Pay schedule!" So pay info is in Advantages. But the "Shift & Wage" heading suggests pay and schedule. I'll keep Pay and Schedule sections, but for Pay, I'll reference the flexible pay options. However, to avoid duplication, I could move the pay info to Pay section and keep Advantages as other advantages. But the original has "Advantages" as a list that includes pay, atmosphere, PTO, tuition. Then "Benefits and Perks" as another list. I think it's okay to have Pay section with the pay details, and Benefits section with the other advantages and benefits perks. But the Advantages list includes pay as first bullet. I could split: keep the non-pay advantages in Benefits, and pay in Pay. But the rule: preserve ALL substantive information. Duplication is okay if it's in the source? The source has it in two places? Actually, "Flexible Pay Options" appears only in Advantages. "DAILY Pay!" appears in Benefits and Perks. They are similar but not identical. I'll keep both lists as they are under Benefits, and also have a Pay section summarizing? That would duplicate. Better to not have a separate Pay section if the pay info is already in Benefits. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay info (Flexible Pay Options, DAILY Pay) and schedule info (Full-Time, Monday-Friday, Some Weekends). So I should include Pay and Schedule sections. But to avoid duplication, I can have the Pay section contain the pay details, and in Benefits, I can omit the pay bullets? But the Advantages list is a cohesive list. The user said "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the Advantages list as is. Then Pay section would duplicate. Hmm. Maybe I can structure: Benefits section includes both Advantages and Benefits and Perks lists. Then Pay section can be a short paragraph referencing the flexible pay options, but that duplicates. Alternatively, I can not have a separate Pay section, because the pay info is already in Benefits. But the rules say "include a section ONLY when the posting has real,