Certified Nursing Assistant (CNA) - On Call

We need to output HTML fragment only, with sections as per content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting: - Title: Certified Nursing Assistant (CNA) - Home Care, On Call (not to be repeated as heading) - Baywood Home Care hiring On-Call CNA in Twin Cities Area, MN — $75 flat rate on weekdays or $100 on weekends to be on call, plus your hourly wage for the shift if called in. Apply today and hear back within 48 hours. - Pay: $75 flat on-call rate (weekdays) or $100 flat on-call rate (weekends), plus hourly wage for shift duration if called in - Job Type: On-call - Location: Twin Cities Area, MN (In person) - About the Role: paragraph. - Why You'll Love Working Here: bullet points: Competitive pay..., flexible schedule..., personalized care..., supportive team..., quick hiring process... - What You'll Do: list of duties. - What You'll Need: list of requirements. - Ready to Apply? paragraph (application instruction) - we should remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop the "Ready to Apply?" paragraph. Also we have Pay and Schedule sections: Pay is given; Schedule: on-call shifts (flexible schedule). So we can include Pay and Schedule sections. Benefits: Not explicitly listed; maybe "Competitive pay" etc is pay, not benefits. There's no explicit benefits like health insurance, etc. So we should not create Benefits section unless posting actually states them. It does not. Qualifications: Could be same as Requirements? The posting has "What You'll Need" which includes certificate, age, vehicle, experience, attitude, diploma preferred. That's requirements/qualifications. We can put under Requirements or Qualifications. Since we have both headings possible, we need to decide which to use. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have About the role, Responsibilities (What You'll Do), Requirements (What You'll Need), Pay, Schedule. Possibly also Qualifications (maybe same as Requirements). To avoid duplication, we can combine Requirements and Qualifications into one section? But we have separate headings; we should not create thin sections. Better to use Requirements for the list of needs, and maybe not include Qualifications if it's redundant. Or we could treat "What You'll Need" as Qualifications. But we need to pick one heading. The instruction says "Prefer a few substantive sections over many thin ones." So we should not split into both Requirements and Qualifications if they'd be similar. Choose one that best fits. The list includes certificate, age, vehicle, experience, attitude, diploma preferred. That's more like Requirements/Qualifications. I'd use Requirements. Skills: Not explicitly listed; maybe "compassionate attitude" etc but not explicit skills list. Could skip. Thus sections: About the role, Responsibilities, Requirements, Pay, Schedule. Now format:

About the role

Make a difference in someone's life every day. At Baywood Home Care, we believe that people heal and thrive best where they feel most comfortable — at home. Join our trusted team of caregivers and provide one-on-one care that truly matters.

Responsibilities

• Provide personal care, including bathing, dressing, toileting, and mobility support
• Offer gentle reminders for medications and routines
• Ensure safety and peace of mind throughout each shift
• Support independence and dignity through compassionate care

Requirements

• CNA certificate (does not need to be current)
• At least 21 years old
• Personal vehicle, valid driver's license, and auto insurance required
• 1 year of caregiving experience required
• Dependable and compassionate attitude
• High school diploma or GED preferred

Pay

$75 flat on-call rate (weekdays) or $100 flat on-call rate (weekends), plus hourly wage for shift duration if called in

Schedule

On-call shifts (flexible schedule)

We should not include duplicated lines like "Apply today and hear back within 48 hours." That's application instruction; remove. Check for any other content: "Why You'll Love Working Here" includes bullet points about Competitive pay, flexible schedule, personalized care, supportive team, quick hiring process. Some of that overlaps with Pay and Schedule and About the role. We already captured pay and schedule. The other points (personalized care, supportive team, quick hiring process) could be considered benefits or about the role. But we already have About the role paragraph; we could incorporate those points into About the role or maybe a Benefits section? However, the instruction says to include a section only when posting has real specific content for it. The "Why You'll Love Working Here" is basically a list of benefits/positive aspects. Could be considered Benefits section. But we already have Pay and Schedule; we could add a Benefits section for the other points: personalized care, supportive team, quick hiring process. However, the instruction says "Prefer a few substantive sections over many thin ones." Adding Benefits might be okay if it's substantive. Let's see if we can incorporate those into About the role or Responsibilities? About the role currently is a paragraph about mission. We could expand About the role to include those points, but we must not invent or summarize away detail; we can rephrase but must preserve all substantive information. The "Why You'll Love Working Here" bullet points are substantive; we should preserve them. We could add them as a

under About the role? But About the role is supposed to be prose per rule: use

for prose. However, we could still have a

inside a section if it's a list; the rule says use
• for any list of duties/requirements/benefits, and

  for prose. So if we have a list of benefits, we should use

  . So we could create a Benefits section with those points. But we need to decide: Is "Why You'll Love Working Here" considered Benefits? It includes Competitive pay (already covered), flexible schedule (covered), personalized care, supportive team, quick hiring process. Those are benefits/positive aspects. So we could have a Benefits section with those items (excluding pay and schedule if we already have them separate). However, we must not repeat information. If we already have Pay and Schedule sections, we could omit those from Benefits to avoid duplication. So Benefits would include: personalized care — focus on one client at a time, no facility hustle; supportive team — we value our caregivers as much as our clients; quick hiring process — apply today and hear back within 48 hours. However, the last includes application instruction ("apply today and hear back within 48 hours") which we are supposed to remove per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop that line. So Benefits would be personalized care and supportive team. Thus we could have Benefits section with two items. Now we have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Check if any of these are thin: Benefits has two items, that's substantive enough. Now we need to ensure we didn't miss any other substantive info: The posting also mentions "Baywood Home Care is hiring an On-Call CNA in the Twin Cities Area, MN — $75 flat rate on weekdays or $100 on weekends to be on call, plus your hourly wage for the shift if called in. Apply today and hear back within 48 hours." The first sentence is basically covered by Pay and location. Location we haven't included as a section; we could include location under About the role or maybe a separate section? There's no heading for Location in the allowed list, but we could fold minor metadata into a short

  or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Location is minor metadata; we could include it in a short

  maybe under About the role or as a separate paragraph before sections. But we should not create a heading for it. Since we already have About the role paragraph, we could append location info there. However, we must preserve ALL substantive information; location is substantive. So we need to include it somewhere. We could add a

  before the first heading: "Location: Twin Cities Area, MN (In person)". Or we could incorporate into About the role: "At Baywood Home Care in the Twin Cities Area, MN..." but that would be altering the original wording. Better to add a short paragraph before sections:

  Location: Twin Cities Area, MN (In person)

  . That's allowed as minor metadata folded into a short

  . It's not a heading. Also we have Job Type: On-call. That's also minor metadata; we could include in same short paragraph or separate. Could combine:

  Job Type: On-call • Location: Twin Cities Area, MN (In person)

  . That's fine. Now check for any other info: "Certified Nursing Assistant (CNA) - Home Care, On CallBaywood Home Care is hiring an On-Call CNA in the Twin Cities Area, MN — $75 flat rate on weekdays or $100 on weekends to be on call, plus your hourly wage for the shift if called in. Apply today and hear back within 48 hours." The first part duplicates title; we ignore title. The rest we covered. Now ensure we removed application instructions: "Apply today and hear back within 48 hours" appears in Why You'll Love Working Here bullet (quick hiring process) and also in the Ready to Apply? paragraph. We removed the Ready to Apply? paragraph entirely. For the quick hiring process bullet, we need to decide whether to keep it. Since it's an application instruction (telling candidates they'll hear back quickly), it's arguably a benefit but also an application instruction. The rule says remove application instructions. The "quick hiring process" is a benefit about the hiring speed, not exactly an instruction to apply. It's more like a selling point. However, the phrase "apply today and hear back within 48 hours" is an instruction. The bullet says "A quick hiring process — apply today and hear back within 48 hours". That includes an instruction. We could keep the benefit of quick hiring process but strip the instruction? The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the application instruction part. We could keep "A quick hiring process" as a benefit, but we need to preserve substantive information. The substantive part is that the hiring process is quick. The instruction to apply is not substantive for the job description; it's a call to action. So we could rephrase to just "Quick hiring process" without the instruction. However, we must not invent or summarize away detail; we can drop the instruction part as it's application instruction. Keeping "Quick hiring process" preserves the substance (the process is quick). That seems acceptable. Thus Benefits bullet points: Personalized care — focus on one client at a time, no facility hustle; Supportive team — we value our caregivers as much as our clients; Quick hiring process. Now we need to ensure we didn't include any duplicated lines. The posting also had "Competitive