Travel PICU RN - $2,434 per week

We need to produce HTML fragment with sections only if there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to extract content. Let's parse the posting. Key details: - Job: travel nurse RN PICU - Pediatric Intensive Care in Idaho Falls, Idaho. - Specialty: PICU - Pediatric Intensive Care - Discipline: RN - Start Date: 10/12/2026 - Duration: 26 weeks (also mentions 26.14 weeks) - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Summary: Junxion Med Staffing looking for PICU RN assignment in Idaho Falls, Idaho. Assignment lasts 26.14 weeks, start Oct 12, 2026. If start date, shift, or pay doesn’t line up, talk. Often multiple openings. Give us a call opt 1. - Job Details: Shift: 12H Nights, Total Weekly Hours: 36, Certifications: BLS, ACLS, PALS, Trauma Level: Facility Specific - Job Notes: **Required Experience and Skills:** list bullet points. - **Preferred Experience:** precepting novice and new graduate nurses. - **Certifications:** BLS, ACLS, PALS (again) - **Additional Qualifications:** Team player, enjoys kids, sense of humor. - When you apply with Junxion, you speak with a live U.S.-based recruiter... (maybe part of About the Company) - Benefits: Insurance Plans starting under $175/month for employees, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors. - Junxion was built by a traveler... dedicated recruiter and support team based in the U.S. who will guide you through credentialing, submission, and onboarding... - Click here for licensing requirements (maybe ignore as boilerplate? It's a link but maybe keep? It's not boilerplate but it's a link; but we can keep as part of About the Company? It's not essential but maybe we can keep as a link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Click here for licensing requirements" might be considered application instruction? It's a link to licensing requirements; maybe we keep as part of About the Company? Not sure. Safer to drop it as it's like a link to external info. But we can keep if it's substantive. I'd drop it. - About the Company: Junxion Med Staffing partners with hospitals... goal: provide strong support, transparent communication, assignments that make sense for your career and your life. - *Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems for eligible clinicians based on nationally published GSA rates. Actual weekly pay and per diems may differ from the amount shown and may be subject to change during an assignment. - For all employees and employee applicants, Junxion Med Staffing is an Equal Employment Opportunity ("EEO") Employer, including Disability/Vets, and welcomes all to apply. (EEO boilerplate - remove) - Junxion Med Staffing Job ID #1389415. (drop) - 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. (Pay info: we have mention of pay package based on shifts, tax-free stipend amount to be determined. Not specific numbers. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package is 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 stating something about pay. However "tax-free stipend amount to be determined" is not specific. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined" which is TBD-like. So we should not create a Pay section if it's only placeholder. However we do have estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems... That's also not specific numbers. It's still vague. So maybe we should not include Pay section because no concrete numbers. The instruction: Prefer a few substantive sections over many thin ones. So we may omit Pay. - Schedule: we have shift details: 12 hours, nights, 36 hours per week, duration 26 weeks, start date. That's specific. So we can create a Schedule section with those details. - Benefits: we have specific benefits list: Insurance Plans starting under $175/month for employees, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors. Also later Benefits section repeats: Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. There's duplication. We need to preserve all substantive information, not invent or summarize away detail. So we need to combine benefits info, avoiding duplication but preserving all. Let's list unique benefits: From first benefits list: - Insurance Plans starting under $175/month for employees - Referral Bonus - Additional contract bonus opportunities - Vacation Incentives - Employee Assistance Program (EAP) - 401k with access to financial advisors From second benefits list (under "Benefits" heading near end): - Weekly pay (but we decided not to include Pay section; but weekly pay is a benefit? It's part of compensation. Might be considered pay. Since we are not making Pay section, maybe we can include weekly pay under Benefits? But the instruction says only create Benefits section if posting actually states them. It does state benefits list includes Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. So we should include those. However we already have some overlapping: Referral Bonus, 401k (with access to financial advisors). Also we have Medical, Dental, Vision benefits not previously listed. Mileage reimbursement not previously listed. Weekly pay not previously listed (though we have estimated weekly pay mention). So we should include all. Thus final benefits list should include: - Weekly pay (estimated based on projected hourly wages and weekly meal and lodging per diems) - Insurance Plans starting under $175/month for employees - Referral Bonus - Additional contract bonus opportunities - Vacation Incentives - Employee Assistance Program (EAP) - 401k with access to financial advisors (or 401k retirement plan) - Medical benefits - Dental benefits - Vision benefits - Mileage reimbursement We need to avoid duplication: Referral Bonus appears twice; keep one. 401k appears twice; keep one (maybe combine: 401k with access to financial advisors). Weekly pay we have mention of estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems. We'll phrase as "Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems (based on GSA rates)". That's substantive. Now sections: We need headings for sections that have real specific content. Potential sections: - About the role (summary of role, location, start date, duration, shift, hours) - Responsibilities (maybe from Required Experience and Skills? Those are more qualifications. Responsibilities could be duties: managing pediatric critical care patients, ventilation, etc. But the posting lists required experience and skills, not explicit responsibilities. However we could treat "Required Experience and Skills" as Responsibilities or Requirements. The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content appropriately. We have: - Summary: description of assignment. - Job Details: shift, hours, certifications, trauma level. - Required Experience and Skills (list) - Preferred Experience (list) - Certifications (list) - Additional Qualifications (list) - About the Company (description) - Benefits (list) - Schedule (shift, hours, duration, start date) - Pay (maybe not include due to vagueness) - Qualifications? Could combine Required Experience and Skills, Certifications, Additional Qualifications as Qualifications. - Skills? Could be part of Qualifications. We need to avoid thin sections. Let's think: We could have About the role (summary + location + start date + duration + shift + hours). Responsibilities maybe not explicitly stated; we could skip Responsibilities if no specific duties beyond the required experience. But we could infer responsibilities from required experience: caring for pediatric critical care patients, managing ventilation, lines, infusions, weight-based pharmacology, assessments. That is substantive. So we can create Responsibilities section with those bullet points. Requirements could be the minimum experience: 1+ year recent direct bedside experience with pediatric critical care patients. Also maybe trauma level facility specific? Not exactly. Could include certifications as Requirements. But we already have Certifications list. Could combine. Qualifications could be preferred experience and additional qualifications. Skills could be specific skills like weight-based pharmacology, age-specific assessments, etc. But that overlaps. We need to avoid duplication. Let's decide on sections: - About the role: includes summary, location, start date, duration, shift, hours. - Responsibilities: bullet list of duties (from Required Experience and Skills). - Requirements: bullet list of mandatory items: Minimum 1+ year recent direct bedside experience with pediatric critical care patients; Certifications BLS, ACLS, PALS; maybe also trauma level facility specific? Not a requirement but note. - Qualifications: bullet list of preferred experience (precepting novice nurses) and additional qualifications (team player, enjoys kids, sense of humor). - Skills: maybe we could list specific skills like pediatric mechanical ventilation, HFNC, nasal CPAP, tracheostomy management, arterial lines, central lines, titrating vasoactive/paralytic/sedative infusions, weight-based pharmacology, age-specific assessments. But those are already in Responsibilities. To avoid duplication, maybe we skip Skills section and keep Responsibilities covering those. Or we could move those to Skills and keep Responsibilities more generic. But we need to preserve all substantive info; we can put them in either section as long as not duplicated. Let's put them in Responsibilities (makes sense). Then Skills section could be omitted or we could include something like "Competency in weight-based pharmacology (Broset-method/PALS dosing) and age-specific assessments from neonates to adolescents". But that's also in Responsibilities. To avoid duplication, we can omit Skills. - Benefits: as compiled. - Schedule: shift, hours, duration, start date. We must not include Pay section due to vagueness. Now we need to format using

for each section heading, then content:

for prose,

• for lists. We must not repeat job title as heading. We must not include Job ID. We must not include boilerplate EEO etc. We must not include navigation etc. Let's craft. First, About the role: prose summarizing: Junxion Med Staffing seeks a travel nurse RN PICU for assignment in Idaho Falls, Idaho. Start date Oct 12, 2026, duration approx 26.14 weeks (26 weeks), 36 hours per week, 12‑hour night shifts. Employment type: travel. We can include location and shift etc. Now Responsibilities: list bullet points from Required Experience and Skills: - Minimum of 1+ year of recent, direct bedside experience with pediatric