NURSE HOME VISITOR

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Title: Build a Career with Purpose NURSE HOME VISITOR Nurse Home Visitor Full-Time – Exempt 60,000 - 64,000 DailyPay Available But we must not repeat job title as heading. So we will not output a heading for title. We need sections: - About the role: likely the introductory paragraph after title: "Looking for More Than Just a Job? At The Children’s Home of Reading, we believe ..." plus maybe "About The Children’s Home of Reading". Actually "About The Children’s Home of Reading" is a section about organization. Could be considered "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include based on content. We have: - About The Children’s Home of Reading (organization description) - Why Join Our Team? (with subpoints: Competitive Pay & Benefits, Career Growth & Development, Meaningful Work That Matters) - What You’ll Do As a Nurse Home Visitor, you will: (list of duties) - Who We’re Looking For (list of traits) - Qualifications Required: (list) - Schedule • Full-Time w/flexible schedule - Physical Requirements (list) - About Our Organization (again) - Equal Opportunity Employer (boilerplate to remove) - etc. We need to include sections only if they have real specific content. We must not include placeholder like "commensurate with experience". We have actual pay: "60,000 - 64,000". Also DailyPay Available. So we can include Pay section with that info. Schedule: "Full-Time w/flexible schedule". That's specific enough. Benefits: we have list under Competitive Pay & Benefits: Competitive Compensation, DailyPay, Medical, Dental & Vision Insurance- AFTER 30 DAYS, 401(k) Retirement Plan, Paid Time Off, Employee Assistance Program, Wellness Programs, Employee Referral Bonuses, Company-Paid Training. Also under Career Growth & Development: Paid Training Programs, Professional Development Opportunities, Certification Opportunities, Leadership Development Programs, Career Advancement Opportunities, Opportunities Across Multiple Service Lines. Also under Meaningful Work That Matters: Make a Difference Every Day, Support Individuals and Families, Build Meaningful Relationships, Strengthen Communities, Join a Mission-Driven Organization. Those could be considered Benefits? Actually they are more like "Why Join Our Team?" categories. Could be considered Benefits (non-monetary) or separate sections like Skills? But we have limited set of headings. We could put Benefits section covering the bullet points under Competitive Pay & Benefits, Career Growth & Development, Meaningful Work That Matters. Or we could split into Benefits and Skills? The instruction says use those headings as examples; we can include only those that have real content. So we need to decide which sections to include. We have: - About the role: could be the introductory paragraph "Looking for More Than Just a Job? At The Children’s Home of Reading, we believe ..." plus maybe "About The Children’s Home of Reading". We'll combine. - Responsibilities: the "What You’ll Do As a Nurse Home Visitor, you will:" bullet list. - Requirements: maybe the "Who We’re Looking For" traits? Or Qualifications? Actually Requirements could be the traits (Compassionate, Dependable, etc.) and Qualifications could be the formal qualifications (license, degree, etc.). We'll separate. - Skills: maybe not explicitly listed; we could omit if no specific skills beyond traits. But we could put Skills as the traits? However the instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But we have headings for both; we can include both if they have content. - Benefits: we have substantive content. - Pay: we have salary range. - Schedule: we have full-time flexible. We should not include sections with placeholder or vague. So we will include:

About the role

with paragraph(s) about mission and organization.

Responsibilities

with

• for duties.

  Requirements

  with
  • for personal traits (Compassionate, Dependable, Patient, Team-Oriented, Service-Focused, Professional, Positive, Committed to Helping Others).

    Qualifications

    with
    • for formal qualifications: Valid driver's license and insured automobile, Bachelor's degree in Nursing, Current RN license (MUST BE IN GOOD STANDING), Maternal/child health and/or previous home health experience preferred, Ability to speak and understand Spanish desired but not required, Worked with diverse populations, communities, and organizations.

      Benefits

      with
      • for benefits list: Competitive Compensation, DailyPay – Access Your Earned Wages Before Payday, Medical, Dental & Vision Insurance- AFTER 30 DAYS, 401(k) Retirement Plan, Paid Time Off, Employee Assistance Program, Wellness Programs, Employee Referral Bonuses, Company-Paid Training, Paid Training Programs, Professional Development Opportunities, Certification Opportunities, Leadership Development Programs, Career Advancement Opportunities, Opportunities Across Multiple Service Lines, Make a Difference Every Day, Support Individuals and Families, Build Meaningful Relationships, Strengthen Communities, Join a Mission-Driven Organization. But that list is long; we can keep as is.

        Pay

        with

        Salary range: $60,000 - $64,000. DailyPay available.

        Schedule

        with

        Full-Time with flexible schedule.

        We should not include Physical Requirements? It's substantive but not in the list of headings. The instruction says use those headings as examples; we could add other headings if needed? It says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But we should prefer a few substantive sections over many thin ones. Physical Requirements could be a section, but we might omit to keep fewer sections. However it's substantive info; but we could incorporate into Responsibilities or Qualifications? Probably better to include as a separate section if we want to preserve all substantive info. But the instruction says "Prefer a few substantive sections over many thin ones." So we need to decide if Physical Requirements is thin enough to omit? It's a list of physical demands; it's substantive. Could be included under Requirements? But it's not a requirement per se; it's a physical demand. Could be its own section. However we already have many sections; adding another may be okay if it's substantive. But we need to balance. We could include Physical Requirements as a section

        Physical Requirements

        with list. That would be another section. But the instruction says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. It's safer to stick to those headings only. So we should not add Physical Requirements as a heading; we could incorporate that info into Responsibilities or Qualifications? Probably not appropriate. But we could drop it to keep fewer sections. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot drop Physical Requirements if it's substantive. We need to preserve it. So we need to include it somewhere, maybe as a

        under Responsibilities or Qualifications? But that would be mixing categories. Could we add a section with heading Physical Requirements? The instruction didn't forbid; it just gave examples. It says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections, but we could also use other headings if needed. However to be safe, we could include Physical Requirements as a

        Physical Requirements

        . It's still an h3. The instruction didn't say we cannot use other headings; it just gave examples. So I think it's okay. Thus we will include Physical Requirements section. Now we need to remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "Apply Today" etc. Also remove "About Our Organization" duplicate? We already have About the role covering organization description; we might keep only one. We need to ensure we don't repeat job title as heading. We'll not. Now produce HTML fragment. We'll start with

        About the role

        then

        ...

        containing the introductory paragraphs: "Looking for More Than Just a Job? At The Children’s Home of Reading, we believe every person deserves the opportunity to live a meaningful, fulfilling, and independent life. We’re seeking compassionate, dedicated professionals who are looking for more than a paycheck. We’re looking for individuals who want to make a difference, build rewarding careers, and become part of a team committed to helping others succeed. Whether you’re beginning your career, changing professions, or bringing years of experience, we provide the training, support, and opportunities needed to help you thrive. No experience required for many positions. Paid training provided." Then maybe also include "About The Children’s Home of Reading For more than 140 years, The Children’s Home of Reading has been dedicated to improving lives through high-quality services and support. Our employees play a vital role in helping individuals achieve greater independence, confidence, and success while promoting dignity, respect, inclusion, and personal choice. Every day, our team members make a meaningful impact by supporting people in reaching their goals and living their best lives." That seems appropriate. Now Responsibilities:

        Responsibilities

        • Partner with first time mothers during their pregnancy and continue to see them and their babies until the child is 2 years of age.
        • Form a relationship with a client that will challenge you to have important conversations in order to improve birth outcomes, improve child growth and development and support clients with personal goals to change her life course.
        • Manage approximately 25 cases
        • Visits twice a month
        Requirements:

        Requirements

        • Compassionate
        • Dependable
        • Patient
        • Team-Oriented
        • Service-Focused
        • Professional
        • Positive
        • Committed to Helping Others
        Qualifications:

        Qualifications

        • Valid driver's license and insured automobile
        • Bachelor's degree in Nursing
        • Current RN license (MUST BE IN GOOD STANDING)
        • Maternal/child health and/or previous home health experience preferred
        • Ability to speak and understand Spanish desired but not required
        • Worked with diverse populations, communities, and organizations
        Benefits:

        Benefits

        • Competitive Compensation
        • DailyPay – Access Your Earned W