LPN - Overnights
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. 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. 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. We have Pay: "$35 - $40 / per hour Weekly Pay | Flexible Scheduling". So we have Pay and Schedule info. Could combine into Pay section? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have separate Pay and Schedule sections if content exists. The posting says "Pay: $35 - $40 / per hour Weekly Pay | Flexible Scheduling". So we have both pay and schedule. Could make a Pay section with the pay info and schedule info? Or separate: Pay section with "$35 - $40 per hour", Schedule section with "Weekly Pay | Flexible Scheduling". However "Weekly Pay" is about pay frequency, not schedule. "Flexible Scheduling" is schedule. Might be better to have Pay section with pay rate and weekly pay, and Schedule section with flexible scheduling. But the instruction says prefer a few substantive sections over many thin ones. Could combine into one "Pay and Schedule" but headings limited to given list. Could use Pay heading and include both pay and schedule info in that section. Or use Schedule heading and include flexible scheduling. Since we have both, maybe two sections: Pay and Schedule. That's okay.
Benefits: listed: Weekly pay with direct deposit (but weekly pay already mentioned), Health, dental, and vision insurance, 401(k) savings plan, Paid time off and sick time (where applicable), Flexible scheduling (again), Ongoing training and professional development, Employee discount programs, Local office and clinical support team available when you need it. Also later "Maxim Benefits Health and Wellness Medical/Prescription, Dental, Vision, Health Advocacy (company paid if enrolled Medical) and Health Advocate Employee Assistance Program Retirement And Financial Security Health Savings Account, 401(k), Short Term Disability, Voluntary Group Life Insurance and Supplemental Accidental Insurance, Hospital Expense Protection Plan, Critical Illness Insurance, Home and Auto Insurance discounts, Pet Insurance and Legal Benefits Lifestyle Benefits Paid Time Off, Employee Discount Program, Transportation Benefits and College Partnership Program Benefit eligibility is dependent on employment status." That's a lot of benefits details. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all benefit items. However we must avoid duplication. The posting repeats some items (weekly pay, flexible scheduling). We should include each unique benefit once.
We need to remove boilerplate: EEO, equal opportunity, application instructions like "Apply Today", "Apply today to learn more", etc. Also remove duplicated lines.
We need to keep substantive info: "Provide Care One Patient at a Time Join Maxim Healthcare and deliver personalized 1:1 nursing care in patients' homes. Enjoy consistent assignments, a manageable pace, and the opportunity to make a meaningful impact on the lives of your patients and their families." That's prose.
"Why This Homecare LPN Role Works One patient at a timeStable hours and long-term casesFull-time, part-time, and PRN opportunitiesDay, evening, and overnight shifts availableDedicated local clinical and office support" This seems like bullet points but without punctuation. We need to turn into list items under Responsibilities? Actually that's more about role attributes. Could be part of "About the role" or "Responsibilities". The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have "About the role" section with that prose. Then "Responsibilities" section with bullet list of duties: "Provide direct patient care in the homeMonitor patient condition and report changesAdminister medications and treatments as orderedSupport individualized care plansDocument care and communicate with the healthcare team". Those are duties.
"Requirements" section: "Required: Active LPN licenseCurrent BLS certification Preferred 1+ year of nursing experience". Also "Additional Details Adult and pediatric patient opportunities availableHome-based care within an assigned service areaOrientation, onboarding, and ongoing clinical support provided". That could be part of Requirements or Qualifications. Could treat as "Qualifications" maybe. But we have headings: Requirements, Qualifications, Skills. We need to decide.
We have "Required: Active LPN licenseCurrent BLS certification Preferred 1+ year of nursing experience". That's requirements. Then "Additional Details Adult and pediatric patient opportunities availableHome-based care within an assigned service areaOrientation, onboarding, and ongoing clinical support provided". That's more details about the role, could be part of "About the role" or "Qualifications". Since we already have About the role, we could add that as additional details there.
We must not repeat job title as heading. The job title is likely "LPN Homecare" but we don't output it.
We must not include application instructions like "Apply Today", "Apply today to learn more", etc. Also remove EEO boilerplate at end.
We must not include navigation, cookie, legal, etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
About the role
Provide Care One Patient at a Time Join Maxim Healthcare and deliver personalized 1:1 nursing care in patients' homes. Enjoy consistent assignments, a manageable pace, and the opportunity to make a meaningful impact on the lives of your patients and their families. Adult and pediatric patient opportunities available. Home-based care within an assigned service area. Orientation, onboarding, and ongoing clinical support provided.
Maybe also include "One patient at a timeStable hours and long-term casesFull-time, part-time, and PRN opportunitiesDay, evening, and overnight shifts availableDedicated local clinical and office support". That seems like role attributes. Could incorporate into About the role as list? But we can make a separate section "Role Highlights"? Not allowed headings except those listed. Could incorporate into About the role as prose. Better: After About the role, we could have aResponsibilities
with- list.
Responsibilities list items:
- Provide direct patient care in the home
- Monitor patient condition and report changes
- Administer medications and treatments as ordered
- Support individualized care plans
- Document care and communicate with the healthcare team
Also maybe include "One patient at a time", "Stable hours and long-term cases", "Full-time, part-time, and PRN opportunities", "Day, evening, and overnight shifts available", "Dedicated local clinical and office support". Those are more about role attributes, not duties. Could be placed under About the role as a list? But we already used prose. Could add another
- for any list of duties/requirements/benefits, and
for prose. So if we have a list of role attributes, we could still use
- . It didn't restrict to only duties/requirements/benefits, but said "for any list of duties/requirements/benefits". Might be okay to use for any list. Safer to use
for prose and
- for lists. We'll treat role attributes as a list under About the role maybe.
But we already have About the role as prose; we could add a
- after the paragraph.
Let's decide: About the role paragraph: "Provide Care One Patient at a Time Join Maxim Healthcare and deliver personalized 1:1 nursing care in patients' homes. Enjoy consistent assignments, a manageable pace, and the opportunity to make a meaningful impact on the lives of your patients and their families."
Then a
- Flexible scheduling
- Day, evening, and overnight shifts available
- Full-time, part-time, and PRN opportunities
- with list items:
- One patient at a time
- Stable hours and long-term cases
- Full-time, part-time, and PRN opportunities
- Day, evening, and overnight shifts available
- Dedicated local clinical and office support
- Adult and pediatric patient opportunities available
- Home-based care within an assigned service area
- Orientation, onboarding, and ongoing clinical support provided
That seems comprehensive.
Now Pay section:
Pay
$35 - $40 per hour
Maybe also mention weekly pay? Could add "Weekly pay with direct deposit" but that's also a benefit. Actually weekly pay is a benefit/pay frequency. Could include in Pay section: "$35 - $40 per hour, weekly pay". Or we could have Pay section with rate and mention weekly pay. Since benefits also list weekly pay with direct deposit, we might duplicate. Better to keep Pay section just the rate, and Benefits section includes weekly pay with direct deposit. But the posting says "Pay: $35 - $40 / per hour Weekly Pay | Flexible Scheduling". So they combined. We'll follow that: Pay section includes both rate and weekly pay. We'll phrase: "$35 - $40 per hour, weekly pay". Also note flexible scheduling? That's schedule. Schedule section:Schedule
Flexible scheduling
But we also have "Day, evening, and overnight shifts available" etc. That's schedule details. Could include in Schedule section as list. Better: Schedule section includes flexible scheduling and shift options. Thus Schedule section:Schedule
- for lists. We'll treat role attributes as a list under About the role maybe.
But we already have About the role as prose; we could add a
- . It didn't restrict to only duties/requirements/benefits, but said "for any list of duties/requirements/benefits". Might be okay to use for any list. Safer to use
Role Details
but not allowed. Could incorporate into About the role as a list using- . However the instruction says Use