Part Time Private Duty Nurse for Kiddo in Colleyville

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - About the role (introductory text) - Position Details (location, schedule, shifts, patient population) - Responsibilities (What You'll Do) - Why Nurses Choose PHS (could be Qualifications or Benefits, but it's more about why choose them) - Benefits (explicitly listed) - About Us (company info) Rules: - Use

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 (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, 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 - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Now, let's parse the content: The posting starts with marketing text: "Small Patients. Big Impact. One-on-One Pediatric Care | Flexible Scheduling | Full-Time, Part-Time & PRN Opportunities" - this is like a tagline. Then "Join a team where your clinical expertise becomes someone's childhood. At Pediatric Home Service (PHS), we exist so kids can be kids. For more than 35 years, we've helped children with medical complexities receive the care they need where they thrive most: at home. As a PHS nurse, you're more than a caregiver. You're a trusted part of a child's world. You'll be there for the everyday moments, milestones, victories, and challenges that matter most, helping children stay where they belong: surrounded by family, comfort, and the life they deserve. One nurse. One patient. A relationship that lasts years, not days." This is "About the role" or "About the company". Could be an introductory section. Then "Position Details" with Location, Schedule, Shifts, Patient Population. This could be a "Schedule" or "Position Details" section. Since Schedule is a heading we can use, but the rule says use

  for section headings like Schedule. However, the posting has "Schedule: Part-Time, and PRN opportunities available" and "Shifts: Thurs & Frid 10a-7p". So we can create a Schedule section. Then "What You'll Do" - list of duties. This is Responsibilities. Then "Why Nurses Choose PHS" - list of reasons. This could be Qualifications or Benefits, but it's more about why choose the company. Might be "Qualifications" or "Why Choose Us". The rule says headings like Qualifications, Skills, Benefits. This is not exactly qualifications (requirements), but more like perks. Could be "Benefits" but there is a separate Benefits section. Actually, "Why Nurses Choose PHS" includes items like "No Pediatric Home Care Experience Required", "100% Pediatric Focus", "Grow Your Clinical Expertise", "Build Lasting Connections", "Meaningful Work Without the Rush", "Flexibility That Fits Your Life". These are selling points, not benefits per se. Could be a "Qualifications" section? But qualifications usually are requirements. The rule says "Qualifications" as a heading. However, the content is not requirements but reasons to join. Might be better as "About the Role" or "Why Join Us". But the allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Nurses Choose PHS" could be "Qualifications" but that's misleading. Could be "Benefits" but there is a separate Benefits section. The Benefits section later lists "Generous PTO...", etc. So "Why Nurses Choose PHS" is more like a "Qualifications" or "Skills" but not exactly. I think we can create a section "Qualifications" for the requirements? But the posting doesn't have explicit requirements list. It says "No Pediatric Home Care Experience Required" which is a qualification note. But there is no list of required qualifications. The "Why Nurses Choose PHS" is more like a "Benefits" but not monetary. The rule says "include a section ONLY when the posting has real, specific content for it". We have a Benefits section later with specific benefits. The "Why Nurses Choose PHS" is also specific content. Could be a "Qualifications" section? But qualifications usually are requirements. The rule says "Qualifications" as a heading. I think we can use "Qualifications" for the "Why Nurses Choose PHS" because it describes what the company offers to nurses (like training, focus, growth). However, the heading "Qualifications" might be misinterpreted. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can choose among those. "Why Nurses Choose PHS" could be "About the role" but we already have an intro. Maybe we can combine the intro and "Why Nurses Choose PHS" into "About the role". But the intro is about the company and role, and "Why Nurses Choose PHS" is a list of reasons. Could be separate sections: "About the Role" for the prose, and "Qualifications" for the list? But "Qualifications" typically means required qualifications. The posting doesn't have a "Requirements" section. It has "What You'll Do" (responsibilities) and "Why Nurses Choose PHS" (perks). There's also "Your Work Changes Lives" which is more marketing. Then "Benefits We want you to feel supported both at work and outside of it. Benefits may include: ..." list. This is clearly Benefits. Then "Your Work Changes Lives" - more marketing prose. Then "Apply today..." - application instruction, should be removed. Then "Follow Us" social media - remove. Then "About Us" - company description. Could be "About the Role" or separate "About Us". But the rule says headings like "About the role". Could include company info there. Also "Pediatric Home Service is an equal opportunity employer..." - EEO boilerplate, remove. Now, let's decide sections: 1. About the Role (introductory prose about company and role) 2. Position Details (location, schedule, shifts, patient population) - but Schedule is a heading, we could make a Schedule section. However, the rule says "Schedule" as a heading. The posting has "Schedule: Part-Time, and PRN opportunities available" and "Shifts: Thurs & Frid 10a-7p". So we can create a Schedule section with those details. Also location could be part of Schedule or separate. The rule doesn't have a "Location" heading. Could include in Schedule or in About the Role. I'll include in Schedule section as a list. 3. Responsibilities (What You'll Do) 4. Qualifications? The posting doesn't have explicit requirements. "Why Nurses Choose PHS" is not qualifications. But we could create a "Qualifications" section with the note "No Pediatric Home Care Experience Required" and maybe the other points? However, the other points are not qualifications. The rule says "never emit a heading followed by filler/placeholder text". If we create a Qualifications section with only "No Pediatric Home Care Experience Required", that might be thin. But we have a list of six items under "Why Nurses Choose PHS". Those are reasons to join, not qualifications. Could be "Benefits" but we have a separate Benefits section. The Benefits section includes "Flexible Scheduling" which is also in Why Nurses Choose PHS. There's overlap. Maybe we can combine "Why Nurses Choose PHS" into the Benefits section? But the Benefits section is explicitly "Benefits may include: ..." with a list of tangible benefits. The "Why Nurses Choose PHS" is more about the work environment and culture. Could be a separate section "Why Choose PHS" but not in allowed headings. The allowed headings are limited. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so maybe we can use other headings? But the instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings. But we can use other headings if needed? The rule says "use

  for section headings (e.g. ...)". It doesn't forbid other headings, but the examples are given. However, the instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create a heading that matches the content. But the system prompt says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It might be expecting those specific headings. But we can use "Why Choose PHS" as a heading? The rule says "use

  for section headings (e.g. ...)". It's ambiguous. To be safe, I'll map to the given headings. Let's map: - About the role: introductory prose - Schedule: position details (location, schedule, shifts, patient population) - Responsibilities: What You'll Do - Qualifications: Why Nurses Choose PHS? But that's not qualifications. However, "No Pediatric Home Care Experience Required" is a qualification note. The other points are benefits. Could be "Benefits" but we have a Benefits section. The Benefits section is separate. The "Why Nurses Choose PHS" includes "Flexibility That Fits Your Life" which is also a benefit. The Benefits section includes "Flexible Scheduling". So there is duplication. Maybe we can treat "Why Nurses Choose PHS" as "Qualifications" because it describes what the company offers to qualify the nurse's experience? Not ideal. Alternatively, we can omit "Why Nurses Choose PHS" as a separate section and incorporate its points into "About the Role" or "Benefits". But the rule says "Preserve ALL substantive information". So we must include it. We can create a section "Qualifications" with the list, but rename the heading to "Why Choose PHS"? The rule says "use

  for section headings (e.g. ...)". It doesn't say we cannot use other headings. But the examples are given. I think we can use a heading that fits, like "Why Choose PHS". However, the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This might be a directive to use those specific headings. But the posting may not have all those. The rule says "include a section ONLY when the posting has real, specific content for it". So we should only include sections that have content. The posting has content for About the role, Schedule, Responsibilities, Benefits. It also has "Why Nurses Choose PHS" which is substantial. Could be "Qualifications" but that's misleading. Could be "Skills" but not skills. Could be "Requirements" but not requirements. Maybe we can create a "Qualifications" section with the note