Private Duty Nurse LVN - Full Time Days
`, `- `, `
`), avoid certain things (no job title heading, no Job ID/req numbers as headings, no boilerplate, no filler/placeholder text).
- I must preserve ALL substantive information, not invent or summarize away detail.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- Include a section ONLY when the posting has real, specific content for it.
- Never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD".
- 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 text:
"Join a company dedicated to putting people first as a Licensed Practical/Vocational Nurse (LPN/LVN). Responsibilities Include Providing compassionate homecare to children and adults, ensuring outstanding clinical outcomes. Utilizing electronic documentation via tablets in patient homes. Collaborating with a multidisciplinary team to deliver quality patient care. Qualifications Active, unencumbered LPN/LVN license in the practicing state; compact licenses transferred within 90 days if applicable. Current CPR certification with hands-on component; assistance available post-hire if needed. TB skin test completed within the last 12 months. Minimum of 6 months hands-on nursing experience; new graduates are not accepted. Reliable transportation required. Key Skills & Benefits Strong clinical skills and empathy. Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts. Access to local support, electronic documentation tools, and career advancement opportunities. Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts. We promote a diverse, inclusive work environment and comply with health-related requirements per jurisdiction. Join us to make a meaningful difference in patient care."
Now, I need to map this to the requested structure:
- Section headings: `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for any list of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat the job title as a heading (the page already shows it)
- 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
- Include a section ONLY when the posting has real, specific content for it
- Never emit a heading followed by filler/placeholder text
- Prefer a few substantive sections over many thin ones
Let's identify natural sections:
- The opening sentence "Join a company dedicated to putting people first as a Licensed Practical/Vocational Nurse (LPN/LVN)." - This is introductory prose. Since we can't have a job title heading, I'll put this as a `
` maybe, or fold it into an "About the role" section? But the rules say: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). And "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't create an "About the role" heading just to repeat the title. I could either start with Responsibilities, or have a brief `
` intro without a heading. The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." and "Include a section ONLY when the posting has real, specific content for it". The opening sentence is substantive, but it's not really a section with a heading. I think I'll start with a `
` containing the intro, then sections.
Let's list out the content by category:
**Responsibilities (from "Responsibilities Include"):**
- Providing compassionate homecare to children and adults, ensuring outstanding clinical outcomes.
- Utilizing electronic documentation via tablets in patient homes.
- Collaborating with a multidisciplinary team to deliver quality patient care.
**Qualifications:**
- Active, unencumbered LPN/LVN license in the practicing state; compact licenses transferred within 90 days if applicable.
- Current CPR certification with hands-on component; assistance available post-hire if needed.
- TB skin test completed within the last 12 months.
- Minimum of 6 months hands-on nursing experience; new graduates are not accepted.
- Reliable transportation required.
**Key Skills & Benefits (this seems to combine skills and benefits, but the rules have separate sections for Skills and Benefits. I need to check if the posting has distinct content for each. It says "Key Skills & Benefits Strong clinical skills and empathy." then lists benefits-like things under "Flexible scheduling options... Access to local support... Competitive benefits...". I need to be careful not to create thin sections. The rules: "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". I should probably combine Skills and Benefits if the posting doesn't clearly separate them, or create separate sections with actual content. Let's see: "Strong clinical skills and empathy." is a skill/attribute. "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." is a benefit/schedule. "Access to local support, electronic documentation tools, and career advancement opportunities." is a benefit. "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." is clearly benefits. "We promote a diverse, inclusive work environment and comply with health-related requirements per jurisdiction." is culture/compliance.
The requested headings include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to only include those that have real content. Let's map:
- Responsibilities: yes, has 3 items.
- Qualifications: yes, has 5 items (license, CPR, TB test, experience, transportation).
- Requirements: sometimes overlaps with Qualifications. The posting has "Qualifications" section with requirements. I could either use Qualifications or Requirements, but not both if they're redundant. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists both Requirements and Qualifications as examples. I should probably pick one or structure them logically. Looking at the posting, it has a "Qualifications" block. I don't see a separate "Requirements" block beyond qualifications. I'll use Qualifications for the license/cert/test/experience/transport stuff, and maybe skip Requirements or fold it in. But the rule says "Include a section ONLY when the posting has real, specific content for it". The posting explicitly has a "Qualifications" section, so I'll use that heading. I won't create a separate Requirements section unless there's distinct content. I'll check: the responsibilities are separate from qualifications. I'll stick with Qualifications.
- Skills: The posting has "Key Skills & Benefits Strong clinical skills and empathy." That's a skill attribute. I could put that under Skills, but it's very brief. If I create a Skills section, I need substantive content. "Strong clinical skills and empathy." is one sentence. The rule says "never emit a heading followed by filler/placeholder text". A single sentence might be okay if it's substantive, but the rule also says "Prefer a few substantive sections over many thin ones." I think I'll include a Skills section with that content, as it's actual text from the posting, not filler. But let's see: "Strong clinical skills and empathy." is indeed in the posting. I'll include it.
- Benefits: The posting has "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." and "Access to local support, electronic documentation tools, and career advancement opportunities." and "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." These are benefits. I could create a Benefits section with these. But there's also "Pay" mentioned: "weekly/daily pay". The rules have Pay and Schedule as separate headings. I need to check if the posting has specific Pay and Schedule info beyond just mentioning "weekly/daily pay" and shift times. It says "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." That's Schedule. It says "weekly/daily pay" under Benefits. I should probably create a Schedule section and a Benefits section, but be careful not to have thin content. Let's see: "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." That's a benefits list. "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." That's a schedule description. I'll create both if they have real content.
- Pay: The only pay mention is "weekly/daily pay" inside the benefits list. It's not a detailed pay section. The rule: "never emit a heading followed by filler/placeholder text". If I create a Pay section, I need specific content. "weekly/daily pay" is specific but very brief. I could fold it into Benefits, or create a Pay section with that text. The rule says "Prefer a few substantive sections over many thin ones." I think I'll fold pay-related text into Benefits, or maybe create a brief Pay section if it's substantive enough. But "weekly/daily pay" is more a benefit than pay range. I'll probably not create a separate Pay section, or include it as a short paragraph in Benefits. Let's re-read the rule: "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." So I must not create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits-related things, schedule things. It says "weekly/daily pay" which is pay-related, but it's within the benefits description. I think I can create a Benefits section that includes the pay mention, and a Schedule section for the shift info. But I need to be careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits, schedule, and a pay frequency. So I can create those sections.
Let's plan the structure:
- Start with a `
` for the introductory sentence: "Join a company dedicated to putting people first as a Licensed Practical/Vocational Nurse (LPN/LVN)." (Since we can't have a job title heading, this sets context.)
- `
Responsibilities
` with `- ` list.
- `
Qualifications
` with `- ` list. (The posting has a qualifications block.)
- `
Skills
`
`), avoid certain things (no job title heading, no Job ID/req numbers as headings, no boilerplate, no filler/placeholder text). - I must preserve ALL substantive information, not invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - Include a section ONLY when the posting has real, specific content for it. - Never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". - 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 text: "Join a company dedicated to putting people first as a Licensed Practical/Vocational Nurse (LPN/LVN). Responsibilities Include Providing compassionate homecare to children and adults, ensuring outstanding clinical outcomes. Utilizing electronic documentation via tablets in patient homes. Collaborating with a multidisciplinary team to deliver quality patient care. Qualifications Active, unencumbered LPN/LVN license in the practicing state; compact licenses transferred within 90 days if applicable. Current CPR certification with hands-on component; assistance available post-hire if needed. TB skin test completed within the last 12 months. Minimum of 6 months hands-on nursing experience; new graduates are not accepted. Reliable transportation required. Key Skills & Benefits Strong clinical skills and empathy. Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts. Access to local support, electronic documentation tools, and career advancement opportunities. Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts. We promote a diverse, inclusive work environment and comply with health-related requirements per jurisdiction. Join us to make a meaningful difference in patient care." Now, I need to map this to the requested structure: - Section headings: `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for any list of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat the job title as a heading (the page already shows it)
- 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
- Include a section ONLY when the posting has real, specific content for it
- Never emit a heading followed by filler/placeholder text
- Prefer a few substantive sections over many thin ones
Let's identify natural sections:
- The opening sentence "Join a company dedicated to putting people first as a Licensed Practical/Vocational Nurse (LPN/LVN)." - This is introductory prose. Since we can't have a job title heading, I'll put this as a `
` maybe, or fold it into an "About the role" section? But the rules say: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). And "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't create an "About the role" heading just to repeat the title. I could either start with Responsibilities, or have a brief `
` intro without a heading. The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." and "Include a section ONLY when the posting has real, specific content for it". The opening sentence is substantive, but it's not really a section with a heading. I think I'll start with a `
` containing the intro, then sections.
Let's list out the content by category:
**Responsibilities (from "Responsibilities Include"):**
- Providing compassionate homecare to children and adults, ensuring outstanding clinical outcomes.
- Utilizing electronic documentation via tablets in patient homes.
- Collaborating with a multidisciplinary team to deliver quality patient care.
**Qualifications:**
- Active, unencumbered LPN/LVN license in the practicing state; compact licenses transferred within 90 days if applicable.
- Current CPR certification with hands-on component; assistance available post-hire if needed.
- TB skin test completed within the last 12 months.
- Minimum of 6 months hands-on nursing experience; new graduates are not accepted.
- Reliable transportation required.
**Key Skills & Benefits (this seems to combine skills and benefits, but the rules have separate sections for Skills and Benefits. I need to check if the posting has distinct content for each. It says "Key Skills & Benefits Strong clinical skills and empathy." then lists benefits-like things under "Flexible scheduling options... Access to local support... Competitive benefits...". I need to be careful not to create thin sections. The rules: "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". I should probably combine Skills and Benefits if the posting doesn't clearly separate them, or create separate sections with actual content. Let's see: "Strong clinical skills and empathy." is a skill/attribute. "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." is a benefit/schedule. "Access to local support, electronic documentation tools, and career advancement opportunities." is a benefit. "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." is clearly benefits. "We promote a diverse, inclusive work environment and comply with health-related requirements per jurisdiction." is culture/compliance.
The requested headings include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to only include those that have real content. Let's map:
- Responsibilities: yes, has 3 items.
- Qualifications: yes, has 5 items (license, CPR, TB test, experience, transportation).
- Requirements: sometimes overlaps with Qualifications. The posting has "Qualifications" section with requirements. I could either use Qualifications or Requirements, but not both if they're redundant. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists both Requirements and Qualifications as examples. I should probably pick one or structure them logically. Looking at the posting, it has a "Qualifications" block. I don't see a separate "Requirements" block beyond qualifications. I'll use Qualifications for the license/cert/test/experience/transport stuff, and maybe skip Requirements or fold it in. But the rule says "Include a section ONLY when the posting has real, specific content for it". The posting explicitly has a "Qualifications" section, so I'll use that heading. I won't create a separate Requirements section unless there's distinct content. I'll check: the responsibilities are separate from qualifications. I'll stick with Qualifications.
- Skills: The posting has "Key Skills & Benefits Strong clinical skills and empathy." That's a skill attribute. I could put that under Skills, but it's very brief. If I create a Skills section, I need substantive content. "Strong clinical skills and empathy." is one sentence. The rule says "never emit a heading followed by filler/placeholder text". A single sentence might be okay if it's substantive, but the rule also says "Prefer a few substantive sections over many thin ones." I think I'll include a Skills section with that content, as it's actual text from the posting, not filler. But let's see: "Strong clinical skills and empathy." is indeed in the posting. I'll include it.
- Benefits: The posting has "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." and "Access to local support, electronic documentation tools, and career advancement opportunities." and "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." These are benefits. I could create a Benefits section with these. But there's also "Pay" mentioned: "weekly/daily pay". The rules have Pay and Schedule as separate headings. I need to check if the posting has specific Pay and Schedule info beyond just mentioning "weekly/daily pay" and shift times. It says "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." That's Schedule. It says "weekly/daily pay" under Benefits. I should probably create a Schedule section and a Benefits section, but be careful not to have thin content. Let's see: "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." That's a benefits list. "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." That's a schedule description. I'll create both if they have real content.
- Pay: The only pay mention is "weekly/daily pay" inside the benefits list. It's not a detailed pay section. The rule: "never emit a heading followed by filler/placeholder text". If I create a Pay section, I need specific content. "weekly/daily pay" is specific but very brief. I could fold it into Benefits, or create a Pay section with that text. The rule says "Prefer a few substantive sections over many thin ones." I think I'll fold pay-related text into Benefits, or maybe create a brief Pay section if it's substantive enough. But "weekly/daily pay" is more a benefit than pay range. I'll probably not create a separate Pay section, or include it as a short paragraph in Benefits. Let's re-read the rule: "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." So I must not create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits-related things, schedule things. It says "weekly/daily pay" which is pay-related, but it's within the benefits description. I think I can create a Benefits section that includes the pay mention, and a Schedule section for the shift info. But I need to be careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits, schedule, and a pay frequency. So I can create those sections.
Let's plan the structure:
- Start with a `
` for the introductory sentence: "Join a company dedicated to putting people first as a Licensed Practical/Vocational Nurse (LPN/LVN)." (Since we can't have a job title heading, this sets context.)
- `
Responsibilities
` with `- ` list.
- `
Qualifications
` with `- ` list. (The posting has a qualifications block.)
- `
Skills
`
` for prose - Do NOT repeat the job title as a heading (the page already shows it) - 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 - Include a section ONLY when the posting has real, specific content for it - Never emit a heading followed by filler/placeholder text - Prefer a few substantive sections over many thin ones Let's identify natural sections: - The opening sentence "Join a company dedicated to putting people first as a Licensed Practical/Vocational Nurse (LPN/LVN)." - This is introductory prose. Since we can't have a job title heading, I'll put this as a `
` maybe, or fold it into an "About the role" section? But the rules say: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). And "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't create an "About the role" heading just to repeat the title. I could either start with Responsibilities, or have a brief `
` intro without a heading. The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." and "Include a section ONLY when the posting has real, specific content for it". The opening sentence is substantive, but it's not really a section with a heading. I think I'll start with a `
` containing the intro, then sections. Let's list out the content by category: **Responsibilities (from "Responsibilities Include"):** - Providing compassionate homecare to children and adults, ensuring outstanding clinical outcomes. - Utilizing electronic documentation via tablets in patient homes. - Collaborating with a multidisciplinary team to deliver quality patient care. **Qualifications:** - Active, unencumbered LPN/LVN license in the practicing state; compact licenses transferred within 90 days if applicable. - Current CPR certification with hands-on component; assistance available post-hire if needed. - TB skin test completed within the last 12 months. - Minimum of 6 months hands-on nursing experience; new graduates are not accepted. - Reliable transportation required. **Key Skills & Benefits (this seems to combine skills and benefits, but the rules have separate sections for Skills and Benefits. I need to check if the posting has distinct content for each. It says "Key Skills & Benefits Strong clinical skills and empathy." then lists benefits-like things under "Flexible scheduling options... Access to local support... Competitive benefits...". I need to be careful not to create thin sections. The rules: "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". I should probably combine Skills and Benefits if the posting doesn't clearly separate them, or create separate sections with actual content. Let's see: "Strong clinical skills and empathy." is a skill/attribute. "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." is a benefit/schedule. "Access to local support, electronic documentation tools, and career advancement opportunities." is a benefit. "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." is clearly benefits. "We promote a diverse, inclusive work environment and comply with health-related requirements per jurisdiction." is culture/compliance. The requested headings include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to only include those that have real content. Let's map: - Responsibilities: yes, has 3 items. - Qualifications: yes, has 5 items (license, CPR, TB test, experience, transportation). - Requirements: sometimes overlaps with Qualifications. The posting has "Qualifications" section with requirements. I could either use Qualifications or Requirements, but not both if they're redundant. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists both Requirements and Qualifications as examples. I should probably pick one or structure them logically. Looking at the posting, it has a "Qualifications" block. I don't see a separate "Requirements" block beyond qualifications. I'll use Qualifications for the license/cert/test/experience/transport stuff, and maybe skip Requirements or fold it in. But the rule says "Include a section ONLY when the posting has real, specific content for it". The posting explicitly has a "Qualifications" section, so I'll use that heading. I won't create a separate Requirements section unless there's distinct content. I'll check: the responsibilities are separate from qualifications. I'll stick with Qualifications. - Skills: The posting has "Key Skills & Benefits Strong clinical skills and empathy." That's a skill attribute. I could put that under Skills, but it's very brief. If I create a Skills section, I need substantive content. "Strong clinical skills and empathy." is one sentence. The rule says "never emit a heading followed by filler/placeholder text". A single sentence might be okay if it's substantive, but the rule also says "Prefer a few substantive sections over many thin ones." I think I'll include a Skills section with that content, as it's actual text from the posting, not filler. But let's see: "Strong clinical skills and empathy." is indeed in the posting. I'll include it. - Benefits: The posting has "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." and "Access to local support, electronic documentation tools, and career advancement opportunities." and "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." These are benefits. I could create a Benefits section with these. But there's also "Pay" mentioned: "weekly/daily pay". The rules have Pay and Schedule as separate headings. I need to check if the posting has specific Pay and Schedule info beyond just mentioning "weekly/daily pay" and shift times. It says "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." That's Schedule. It says "weekly/daily pay" under Benefits. I should probably create a Schedule section and a Benefits section, but be careful not to have thin content. Let's see: "Competitive benefits including health, dental, vision, life insurance, paid time off, weekly/daily pay, and employee discounts." That's a benefits list. "Flexible scheduling options including full-time, part-time, or PRN, with day, night, and weekend shifts." That's a schedule description. I'll create both if they have real content. - Pay: The only pay mention is "weekly/daily pay" inside the benefits list. It's not a detailed pay section. The rule: "never emit a heading followed by filler/placeholder text". If I create a Pay section, I need specific content. "weekly/daily pay" is specific but very brief. I could fold it into Benefits, or create a Pay section with that text. The rule says "Prefer a few substantive sections over many thin ones." I think I'll fold pay-related text into Benefits, or maybe create a brief Pay section if it's substantive enough. But "weekly/daily pay" is more a benefit than pay range. I'll probably not create a separate Pay section, or include it as a short paragraph in Benefits. Let's re-read the rule: "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." So I must not create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits-related things, schedule things. It says "weekly/daily pay" which is pay-related, but it's within the benefits description. I think I can create a Benefits section that includes the pay mention, and a Schedule section for the shift info. But I need to be careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits, schedule, and a pay frequency. So I can create those sections. Let's plan the structure: - Start with a `
` for the introductory sentence: "Join a company dedicated to putting people first as a Licensed Practical/Vocational Nurse (LPN/LVN)." (Since we can't have a job title heading, this sets context.) - `
Responsibilities
` with `- ` list.
- `
Qualifications
` with `- ` list. (The posting has a qualifications block.)
- `
Skills
`
- ` list. (The posting has a qualifications block.)
- `