Travel Post Partum/Mom Baby RN - $1,730 per week

We need to output HTML fragment with sections: About the role? Actually we need to follow rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key details: - ARMStaffing is seeking a travel nurse RN Post Partum for a travel nursing job in Asheville, North Carolina. - Specialty: Post Partum - Discipline: RN - Start Date: 10/05/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Registered Nurse - Mother Baby Unit Location Asheville, NC Assignment Duration This is a 13-week contract position. - Schedule Shift: 6:45 PM - 7:15 AM - Job Description: We are seeking a dedicated and skilled Registered Nurse to join our Mother Baby Unit. The unit features 34 private couplet rooms with a patient ratio of 1:3-4 couplets. Our facility is recognized for its commitment to patient safety and clinical quality. - Responsibilities: Provide comprehensive nursing care to mothers and newborns, ensuring safety and well-being. Monitor and document patient progress and interactions in the electronic medical record (EMR) system (Cerner). Perform routine procedures, including circumcisions. Assist in the care of patients on Magnesium Sulfate post-delivery. Collaborate with a healthcare team to deliver high-quality patient care and education. - Required Experience / Certifications / Licensure: Must have current BLS and NR certifications. Experience in Mother Baby care is required. Preferred: Travel experience in similar settings. STABLE certification is a plus. - Why ARMStaffing? At ARMStaffing, we take care of our employees! We offer: - Health Benefits: Medical, Dental, Vision, Life, and more - Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care - Clinical Support: In-house clinical team available to assist and advocate - 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution - Recruiter Matching: Get paired with a recruiter based on your location and specialty - Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more - Additional statements: SIA’s Top-50 Fastest Growing Healthcare Staffing Firms – 2019, SIA’s Largest Healthcare Staffing Agencies in the U.S. – 2023, Top Workplace in the Lehigh Valley – 2022, 2023, Perfect scores for 'Name, Not a Number' and 'Recruiters' Personalities' on Highway Hypodermics, We've earned The Joint Commission’s Gold Seal of Approval for healthcare staffing 15 years strong and counting! Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details! - ARMStaffing Job ID #38155833. Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: RN:Mother-Baby / Post Partum,19:00:00-07:00:00 (looks like weird formatting) - About ARMStaffing: description of company. We need to remove boilerplate: navigation, legal, EEO, etc. There's no explicit EEO but there is a lot of company description that might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About ARMStaffing" paragraph is likely considered company description, not necessarily boilerplate, but could be considered part of the posting. However, we need to preserve all substantive information. The "About ARMStaffing" includes details about the company, services, etc. Might be considered substantive? It's generic but maybe we keep it as a section like "About the company"? However the allowed headings list includes "About the role". Not "About the company". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings if we have content. The "About ARMStaffing" could be considered "About the role"? Not exactly. Might be better to omit that section because it's not required headings and may be considered boilerplate. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine company info into a brief paragraph under maybe "About the role"? But "About the role" is supposed to describe the role, not the company. However we could incorporate some company details into a short paragraph under "About the role" if needed. But we have a specific job description already. We need to include sections only when posting has real, specific content for it. Let's identify content for each possible heading: - About the role: Could be a brief summary of the role (maybe the first paragraph). The posting includes "Job Description We are seeking a dedicated and skilled Registered Nurse to join our Mother Baby Unit..." That's essentially about the role. So we can put that under About the role. - Responsibilities: We have a list of duties. Use

  • . - Requirements: We have required experience/certifications/licensure. Could be under Requirements or Qualifications. The heading list includes Requirements and Qualifications. We need to decide which to use. The posting includes "Required Experience / Certifications / Licensure". That's requirements. Also "Preferred: Travel experience in similar settings. STABLE certification is a plus." That could be under Qualifications or Skills. We could combine required and preferred under Requirements, or separate into Requirements and Qualifications. Since we prefer few substantive sections, maybe combine into Requirements (including required and preferred). Or we could have Requirements and Qualifications separate if we have distinct content. Let's see: Required: BLS, NR certifications, Mother Baby experience. Preferred: Travel experience, STABLE certification. That's two categories. Could put under Requirements (required) and Qualifications (preferred). That would be two sections. But we could also combine into Requirements with sub-bullets marking required vs preferred. However the instruction says use
    • for any list of duties/requirements/benefits. So we can have a list under Requirements with items, maybe marking (Preferred) etc. - Skills: Not explicitly listed; we could omit. - Benefits: The posting lists benefits under "Why ARMStaffing? At ARMStaffing, we take care of our employees! We offer:" then a list: Health Benefits, Onboarding Made Easy, Clinical Support, 401k Retirement Plan, Recruiter Matching, Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more. Also later mentions SIA rankings etc. Those are more about company accolades, not benefits. So we have benefits content. So we should include a Benefits section with a list. - Pay: The posting mentions "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific number, it's vague. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package but not a specific amount. It says "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's still vague but it's stating that pay package exists. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package, albeit not a specific number. Should we include a Pay section? The instruction also says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is like TBD. So that is placeholder/filler. So we should not create a Pay section because it would be filler. So omit Pay. - Schedule: The posting includes shift details: Start Date, Duration, 36 hours per week, Shift: 12 hours, nights, Schedule Shift: 6:45 PM - 7:15 AM. That's specific schedule info. So we can include a Schedule section. The instruction says never create Schedule section unless posting actually states them. It does state shift times. So we can include Schedule. We also have Start Date and Duration. Could be part of About the role or Schedule? Probably better to include in About the role or maybe a separate "Assignment Details" but not in allowed headings. Since we prefer few sections, we could include start date and duration in About the role paragraph. We also have location: Asheville, NC. Could be in About the role. We need to remove duplicated lines and boilerplate like "ARMStaffing Job ID #38155833." That's minor metadata; we can fold into a short

      or drop it. Probably drop it. Also remove the weird "Posted job title: RN:Mother-Baby / Post Partum,19:00:00-07:00:00" - that's duplicate and weird; drop. Also remove the long About ARMStaffing paragraph (the company description) as it's likely boilerplate. However some of it may be considered substantive? But it's generic description of the company; we can drop it as per instruction to remove boilerplate. The "Why ARMStaffing?" section is more about benefits and company culture; we already captured benefits. The accolades (SIA rankings, Top Workplace, Joint Commission) could be considered company info but not benefits; could be dropped as boilerplate. Thus final sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We need to use

      for each section heading. Use

      • for lists. Use

        for prose. Let's craft content. About the role: Paragraph summarizing: ARMStaffing seeks a travel nurse RN Post Partum for a 13-week contract in Asheville, NC. Start date 10/05/2026, 36 hours per week, 12-hour night shifts (6:45 PM - 7:15 AM). Role is in Mother Baby Unit with 34 private couplet rooms, patient ratio 1:3-4 couplets. Facility recognized for patient safety and clinical quality. We need to preserve all substantive information: include