Travel Nurse RN - NICU - Neonatal Intensive Care - $2,575 per week

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Key info: - Specialty: NICU - Neonatal Intensive Care - Discipline: RN - Start Date: 10/12/2026 - Duration: 12 weeks - 36 hours per week - Shift: 12 hours - Employment Type: Travel - Job Summary: Neonatal Intensive Care Unit (NICU) Nurse Location: Not Specified. This position involves delivering specialized nursing care to neonates in a Level IV NICU environment. The role requires assessment, diagnosis, planning, intervention, and evaluation of neonatal patients, with opportunities to perform procedures such as intubation, PICC line placement, and neonatal assessments, within a dynamic and fast-paced setting. - Job Details Qualifications: Active and Compact Registered Nurse (RN) license (willing to obtain), BLS certification from the American Heart Association, Neonatal Resuscitation Program (NRP), and a minimum of 2 years of neonatal care experience. - Responsibilities: Deliver nursing assessments and care for neonates, including administering medications through PICC lines, managing ventilators such as high-frequency and conventional models, and performing procedures like spinal taps and G-tube placements. - Schedule: Rotating shifts, 12 hours per shift, including day/night rotations, working every other weekend with minimum 36 hours per week. - Additional Requirements: Willingness to float to Pediatric Intensive Care Unit (PICU) and Pediatrics (PEDS), proficiency with EPIC charting system, and scrub attire compliance. - Certifications: BLS and NRP required prior to start. - Licensing: Must have or be willing to obtain active Basic Life Support (BLS) and Neonatal Resuscitation Program (NRP) Licenses. - Additional Information: Training includes a two-day orientation on the EPIC charting system and unit norms, with badge-in/out procedures and unit-specific skills assessment. Candidates must have experience with neonatal assessments, IV care, and administering medications through PICC lines. - Benefits: Private housing or generous housing allowance; Comprehensive health insurance with prescription coverage; Dependent health insurance with prescription coverage; Competitive salaries; Referral bonuses; Travel reimbursement; 401(k) retirement plan; Direct deposit/free checking; Unlimited free CE credits. - 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: Registered Nurse / Neonatal Intensive Care Unit (we ignore) - About Cross Country Nurses: paragraph about company (maybe we can include as About the role? Actually "About the role" is generic; but we have company description; we could put under "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include About the role (maybe summarizing the role). We have job summary; we can put that under About the role. - Benefits: we have list; we can include Benefits section. - Pay: we have mention of pay package based on 12 hour shifts and 36.0 hours per week with tax-free stipend amount to be determined. That's vague; but it's still some info. However instruction: 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. Pay: they say "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 somewhat vague but still states something about pay package based on shifts and hours, but stipend amount TBD. Is that considered filler? It says "tax-free stipend amount to be determined" which is TBD. Might be considered placeholder. Safer to omit Pay section because not specific amount. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They did state something about pay package but it's not a specific number; still it's stating something. However they also say "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 TBD. So that is placeholder. So better to omit Pay section. - Schedule: we have schedule details: Rotating shifts, 12 hours per shift, including day/night rotations, working every other weekend with minimum 36 hours per week. That's specific. So we can include Schedule section. - Requirements/Qualifications: we have qualifications, certifications, licensing, additional requirements, experience. We can combine into Requirements or Qualifications. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have responsibilities list. We have qualifications list (license, BLS, NRP, 2 years experience). We have additional requirements (float to PICU/PEDS, EPIC proficiency, scrub attire). We have certifications (BLS, NRP). We have licensing (same). We have additional info (training, experience). We could put all under Requirements or Qualifications. Probably better to have Qualifications section for license, certifications, experience; and Requirements for duties? Actually Responsibilities separate. We'll do: - About the role (job summary) - Responsibilities (list) - Qualifications (license, certifications, experience) - Requirements (additional requirements like floating, EPIC, scrub attire, training) - Benefits (list) - Schedule (details) We should not include Skills unless we have specific skills list; we have some like proficiency with EPIC charting system, neonatal assessments, IV care, administering medications through PICC lines, managing ventilators, performing procedures. Those could be considered skills. But we already have responsibilities covering many. Could create Skills section for proficiencies: EPIC, neonatal assessments, IV care, PICC meds, ventilator management, intubation, spinal taps, G-tube placement. However we might avoid duplication. The instruction: prefer a few substantive sections over many thin ones. So maybe combine skills into Responsibilities or Qualifications. Let's keep Responsibilities as list of duties; Qualifications as license/certifications/experience; Requirements as additional requirements (float, EPIC, scrub, training). Benefits as list. Schedule as details. Now we need to output HTML fragment only, no /. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like "About Cross Country Nurses" maybe we can incorporate into About the role? Actually About the role should be about the role, not company. But we have company description separate; we could ignore it as boilerplate? It's somewhat promotional but still substantive about the company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Cross Country Nurses" is not exactly boilerplate but could be considered company overview; maybe we can keep as part of About the role? But the heading "About the role" expects role description; we already have job summary. We could add a short paragraph about the company under About the role? Might be okay. However we might just omit the company description to avoid fluff. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's about the company, not the role. Might be considered not essential to the job posting but still part of posting. However they said remove boilerplate; company description might be considered boilerplate? Not sure. Safer to include it as a paragraph under About the role? But the heading is About the role, not About the company. Could rename heading to About the role and include both role summary and company info? Might be okay. Alternatively we could create a section "About the company" but not in allowed headings list. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but says use those for section headings. It implies we should use those headings when appropriate. So we should stick to those. Thus we will put the job summary under About the role. The company description maybe we can omit as not required? But we risk losing substantive info. However the instruction says preserve ALL substantive information. The company description is substantive about the employer. I'd include it as a paragraph under About the role after the job summary. Now let's extract details: About the role (job summary): "Neonatal Intensive Care Unit (NICU) Nurse Location: Not Specified. This position involves delivering specialized nursing care to neonates in a Level IV NICU environment. The role requires assessment, diagnosis, planning, intervention, and evaluation of neonatal patients, with opportunities to perform procedures such as intubation, PICC line placement, and neonatal assessments, within a dynamic and fast-paced setting." We could also include the start date, duration, etc. Those are job details but not necessarily role summary. Could include them in About the role as prose. Better to include start date, duration, hours per week, shift, employment type in About the role? Might be better to put them in Schedule or maybe a separate "Job Details" but we don't have heading for that. Could incorporate into About the role as additional details. But we have Schedule section for shift details. So we can put start date, duration, employment type in About the role. Let's craft About the role paragraph:

  Start Date: 10/12/2026. Duration: 12 weeks. Employment Type: Travel. Neonatal Intensive Care Unit (NICU) Nurse. This position involves delivering specialized nursing care to neonates in a Level IV NICU environment. The role requires assessment, diagnosis, planning, intervention, and evaluation of neonatal patients, with opportunities to perform procedures such as intubation, PICC line placement, and neonatal assessments, within a dynamic and fast-paced setting.

  Note: Location: Not Specified - we could mention but it's not specified; maybe omit as it's not substantive. Now Responsibilities list: - Deliver nursing assessments and care for neonates, including administering medications through PICC lines - Managing ventilators such as high-frequency and conventional models - Performing procedures like spinal taps and G-tube placements We could also include "assessment, diagnosis, planning, intervention, evaluation" but that's in summary. Keep as given. Now Qualifications list: - Active and Compact Registered Nurse (RN) license (willing to obtain) - BLS certification from the American Heart Association - Neonatal Resuscitation Program (NRP) - Minimum of 2 years of neonatal care experience We could also include "Must have or be willing to obtain active Basic Life Support (BLS) and Neonatal Resuscitation Program (NRP) Licenses." That's duplicate; we can keep one. Now Requirements list (additional requirements): - Willingness to float to Pediatric Intensive Care Unit (PICU) and Pediatrics (PEDS) - Proficiency with EPIC charting system - Scrub attire compliance - Two-day orientation on the EPIC charting system and unit norms, with badge-in/out procedures and unit-specific skills assessment (training) - Experience with neonatal assessments, IV care, and administering medications through PICC lines (maybe this is more qualification but we