In Home Healthcare LVN - Weekend Night Shift (High Acuity)

Here's a thinking process: 1. **Analyze User Input:** - The user wants me to reformat a job posting into clean, well-structured semantic HTML. - Rules are provided: use `

` for section headings (specific list), `

• ` for lists, `

  ` for prose. - Do NOT repeat job title as heading. - Do NOT put Job ID / requisition numbers as headings. - 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. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Extract Content from the Posting:** Let's parse the input text: - "Join a company committed to putting people first!" -> This is intro/boilerplate, but might be considered substantive culture statement. I'll consider if it goes somewhere or gets dropped. Rules say remove boilerplate, but this is part of the posting. I'll be careful. - "Role: Licensed Practical / Vocational Nurse – LPN/LVN" -> The rule says: "Do NOT repeat the job title as a heading (the page already shows it)". So I should NOT use "Licensed Practical / Vocational Nurse – LPN/LVN" as a heading. I'll just not include it as a heading. Maybe I can mention it in a

  or drop it entirely since the page already shows it. The rule says "Do NOT repeat the job title as a heading". I can include it in prose or just omit it. I'll omit it as a heading, maybe keep it in a

  if needed, but the rule says "Do NOT repeat the job title as a heading (the page already shows it)". I'll just not output it as a heading. I might include it in a

  at the start, but the rule says remove application instructions, boilerplate, etc. I'll see. - "Responsibilities:" -> This maps to "Responsibilities" section heading `

  `. Content: "Provide compassionate homecare to pediatric patients with complex needs such as feeding tubes, trachs, vents, and medication administration (training available). Ensure clinical outcomes through skilled nursing care, documentation via electronic tablets, and collaboration with the healthcare team." - "Qualifications And Skills" -> This maps to headings? The rules list specific headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". The input has "Qualifications And Skills". I need to map this. The rule says use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Qualifications" and "Skills" might be two separate headings, or combined. The input has them together as "Qualifications And Skills". I'll probably split them or keep as one section if it has content. But I need to check rules: "include a section ONLY when the posting has real, specific content for it". The posting has content under "Qualifications And Skills": "Active, unencumbered LPN/LVN license in the practice state", "Current CPR certification (training available)", "TB skin test within last 12 months", "Reliable transportation", "Preferred: Six months of hands-on nursing experience". These are specific qualifications/skills. I'll structure them under appropriate headings. The rule lists "Qualifications" and "Skills" as examples of headings. I'll probably make two sections: "Qualifications" and "Skills", or combine as "Qualifications and Skills" but as an `

  `. Let's see the exact list: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "Requirements" is separate from "Qualifications". The input has "Qualifications And Skills". I'll likely create "Qualifications" and "Skills" as separate `

  `s, or maybe "Requirements" if applicable. Let's map the content: * "Active, unencumbered LPN/LVN license in the practice state" -> Qualification/Requirement * "Current CPR certification (training available)" -> Qualification/Requirement * "TB skin test within last 12 months" -> Qualification/Requirement * "Reliable transportation" -> Requirement/Preference * "Preferred: Six months of hands-on nursing experience" -> Preferred qualification I'll create "Qualifications" and "Skills" sections, or maybe "Requirements". To be safe, I'll use "Qualifications" for the license/certification/test, and "Skills" for the experience/transportation, or just combine what makes sense. Actually, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I must use all of them, only include when there's real content. I'll use the ones that have specific content: "Responsibilities", "Qualifications", "Skills". Maybe "Requirements" too. Let's see. - "Key Duties:" -> This maps to "Responsibilities" already, or maybe "Key Duties" is part of Responsibilities. The input has "Responsibilities:" and then "Key Duties:". Actually the structure is: "Responsibilities:" then paragraphs, then "Qualifications And Skills:" then list, then "Key Duties:" then paragraph. Wait, let re-read the input: "Responsibilities: Provide compassionate homecare to pediatric patients with complex needs such as feeding tubes, trachs, vents, and medication administration (training available). Ensure clinical outcomes through skilled nursing care, documentation via electronic tablets, and collaboration with the healthcare team. Qualifications And Skills Active, unencumbered LPN/LVN license in the practice stateCurrent CPR certification (training available)TB skin test within last 12 monthsReliable transportationPreferred: Six months of hands-on nursing experience Key Duties: Deliver patient-centered care, maintain compliance with health requirements, and support patients and families with empathy and professionalism." So the order is: Responsibilities (prose), then Qualifications And Skills (list-like), then Key Duties (prose). This is a bit mixed. I'll structure it properly: "Responsibilities" section with the prose, then "Qualifications" and "Skills" split or combined, then maybe "Key Duties" but that overlaps with Responsibilities. Actually, "Key Duties" might be part of Responsibilities or a separate section. The rule says use `

  ` for section headings like "Responsibilities", "Requirements", "Qualifications", "Skills". I'll treat "Responsibilities" and "Key Duties" as part of the Responsibilities section, or maybe "Key Duties" as a sub-heading but rules say use `

  ` for sections. I'll likely put the first prose under "Responsibilities", and the "Key Duties" prose might be redundant or part of it. I'll check: "Responsibilities:" has two sentences. "Key Duties:" has one sentence. They overlap. I'll probably just put all duty-related content under "Responsibilities" or use "Responsibilities" and drop "Key Duties" as it's repetitive. But the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include both if they have different content, but they seem similar. I'll read carefully: Responsibilities: Provide compassionate homecare... Ensure clinical outcomes... Key Duties: Deliver patient-centered care, maintain compliance with health requirements, and support patients and families with empathy and professionalism. These are slightly different but overlapping. I'll include both but structure them maybe under one `

  Responsibilities

  ` with all bullet points/paragraphs, or use two sections. To be safe, I'll use "Responsibilities" for the first part, and maybe "Key Duties" isn't in the allowed heading list. The allowed list: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "Key Duties" is not listed, so I should fold it into "Responsibilities" or "Requirements". I'll fold it into "Responsibilities". - "Additional Information: Opportunity for flexible scheduling, career advancement, paid training, and benefits such as health insurance, paid time off, weekly/daily pay, and employee stock purchase plans. Local support and electronic documentation tools enhance the work experience." This maps to "Benefits", "Schedule", etc. But rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." And "include a section ONLY when the posting has real, specific content for it". The posting states: "Opportunity for flexible scheduling, career advancement, paid training, and benefits such as health insurance, paid time off, weekly/daily pay, and employee stock purchase plans." So there is content about scheduling, benefits, pay (weekly/daily pay). But rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It also says: "Prefer a few substantive sections over many thin ones." And "never emit a heading followed by filler/placeholder text". The posting actually states specific benefits: health insurance, paid time off, employee stock purchase plans, weekly/daily pay. Flexible scheduling is mentioned. I could create "Benefits" and "Schedule" sections. But I need to be careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. However, it also says "Implicitly, I should not create a section just because something is mentioned in passing; it needs to be substantive content for that section." The posting has a whole paragraph under "Additional Information" that covers flexible scheduling, benefits, pay, etc. I think it's valid to have "Benefits" and "Schedule" sections, but I need to check if I should combine them or keep separate. The rule lists "Benefits, Pay, Schedule" as possible headings. I'll likely create a "Benefits" section with the specific benefits listed, and maybe a "Schedule" section for flexible scheduling. But the rule also says "Prefer a few substantive sections over many thin ones." If I create both "Benefits" and "Schedule", that's two sections. I'll see if the content warrants both. "Opportunity for flexible scheduling" -> Schedule. "benefits such as health insurance, paid time off, weekly/daily pay, and employee stock purchase plans" -> Benefits. I'll create "Benefits" and "Schedule" sections, but only if I can fill them with specific content without placeholders. The rule says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So as long as I have specific text, it's fine. Let's re-evaluate the heading list from the rules: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So allowed h3 headings are those examples. I should use them appropriately. Now, let's plan the HTML structure based on the content, following all rules: - No `` or `<