Travel ICU RN - $2,250 per week

We need to output HTML fragment with sections: 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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting for content. Let's extract sections: - About the role: maybe summary: "Junxion Med Staffing is looking for a ICU RN to take an assignment in Lawrence, Kansas. This assignment lasts 13.14 WEEKS and is scheduled to start on October 25, 2026." Also location: Lawrence, Kansas. Specialty: ICU - Intensive Care Unit. Discipline: RN. Start Date: 10/25/2026. Duration: 13 weeks (13.14 weeks). Shift: 12 hours, nights. Employment Type: Travel. Total Weekly Hours: 36. So we can put that in About the role. - Responsibilities: Not explicitly listed. The posting does not give duties. Might be implied but not specific. So we should not create Responsibilities section if no specific content. - Requirements: Experience Requirement: 1 year of ICU RN experience- large facility, critical care. Certifications: KS or compact license, BLS, ACLS, NIHSS. Also maybe "Experience Preferred: ICU, Med/Surg, Experience w/ ventilators and titration drips". New graduates accepted: No. So we can list requirements. - Qualifications: Might overlap with requirements. Could combine? But we need separate sections only if content. Could put qualifications as license and certification? But we already have that in requirements. Might treat qualifications as license/certification. However we need to avoid duplication. Perhaps we can put "License and Certification Requirement: KS or compact license, BLS, ACLS, NIHSS" under Qualifications. And requirements as experience. But the posting lumps them. We need to decide. Better: Use Requirements for experience and preferred experience. Use Qualifications for license and certifications. Use Skills maybe for ventilators and titration drips? But that's experience preferred. We need to avoid thin sections. Let's see what we have substantive: - About the role: location, specialty, start date, duration, shift, hours, employment type. - Requirements: 1 year ICU RN experience in large facility, critical care. - Preferred qualifications/experience: ICU, Med/Surg, experience with ventilators and titration drips. New graduates not accepted. - Qualifications: KS or compact license, BLS, ACLS, NIHSS. - 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. Also later list: Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. There's duplication. Need to preserve all substantive info but not duplicate lines. We'll combine unique benefits. - Pay: "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." Also "*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." So we have pay info but not specific amount. It says tax-free stipend amount to be determined. That's somewhat vague but still content. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on shifts and hours, tax-free stipend amount to be determined. That's stating something about pay, albeit not a number. So we can include Pay section with that info. - Schedule: Shift: 12 hours, nights; Total Weekly Hours: 36; Duration: 13 weeks; Start date: Oct 25, 2026. That's schedule info. Could be in About the role but we could also make Schedule section. However we should avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we keep schedule info in About the role and not create separate Schedule section unless we have distinct schedule details beyond what's in About. But we have shift, hours, duration, start date. That's schedule. Could be part of About the role. However About the role already includes shift, duration, start date, hours. So we can keep About the role covering that. Then we don't need separate Schedule section. - Benefits: we have multiple items. We'll create Benefits section with list. - Skills: maybe we can list "Experience with ventilators and titration drips" as a skill. But that's also experience preferred. Could be under Skills. But we already have Requirements and Qualifications. Might be thin. Could combine experience preferred into Requirements as "Preferred: ICU, Med/Surg, experience with ventilators and titration drips". That's okay. Thus sections: About the role, Requirements, Qualifications, Benefits, Pay. Check if any other: maybe "About the Company" but that's boilerplate? It's about Junxion Med Staffing. Could be considered About the Company but not required. The instruction: include a section ONLY when the posting has real, specific content for it. The About the Company section has some description: "Junxion Med Staffing partners with hospitals..." etc. That's substantive. Could be a section "About the Company". However the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the Company". So we cannot add a heading not in list. So we must fit that content into allowed headings. Perhaps we can put company description under About the role? But About the role is for the role. However we could incorporate some of that into About the role as extra context. But the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but likely we should only use those headings. It didn't forbid other headings, but says use those for section headings. Safer to stick to those. Thus we will not include company description unless we can incorporate into About the role (maybe as a brief note). But we must preserve ALL substantive information. If we omit company description, we lose info. However maybe we can treat that as part of About the role? The role description includes "Junxion Med Staffing is looking for a ICU RN...". The company description is separate but we could add a sentence about the company under About the role as extra. That would preserve it. Similarly, the "About Junxion Med Staffing" paragraph later repeats similar info. We'll incorporate unique points. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we remove lines like "Click here for licensing requirements", "Junxion Med Staffing Job ID #1388794.", "For all employees and employee applicants, Junxion Med Staffing is an Equal Employment Opportunity ("EEO") Employer..." etc. Also remove "Estimated weekly pay includes projected hourly wages..." maybe keep as part of Pay? It's about pay but it's a disclaimer. Might be considered boilerplate? It's about pay disclaimer; but it's substantive about pay. We'll keep it in Pay section. Now craft HTML. Structure:

About the role

Junxion Med Staffing is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Lawrence, Kansas. The assignment starts October 25, 2026, lasts approximately 13.14 weeks, involves 12‑hour night shifts for a total of 36 hours per week, and is a travel employment type.

Maybe also include specialty and discipline.

Requirements

• 1 year of ICU RN experience in a large facility, critical care setting.
• Preferred experience includes ICU, Med/Surg, and work with ventilators and titration drips.
• New graduates are not accepted.

Qualifications

• Valid Kansas (KS) or compact nursing license.
• Current BLS, ACLS, and NIHSS certifications.

Benefits

• Insurance plans starting under $175 per month for employees.
• Referral bonus.
• Additional contract bonus opportunities.
• Vacation incentives.
• Employee Assistance Program (EAP).
• 401(k) plan with access to financial advisors.
• Medical, dental, and vision benefits.
• Mileage reimbursement.
• Weekly pay (see Pay section for details).

Pay

Pay package is based on 12‑hour shifts and 36.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined. 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 and may change during the assignment.

We should not include Schedule section as we already covered shift/hours/duration in About the role. Check for any duplicated content: Benefits list includes Weekly pay (we also have Pay section). Might be redundant but okay. Could remove Weekly pay from benefits to avoid duplication. But we need to preserve all substantive info; the benefits section originally listed "Weekly pay" as a benefit. It's redundant with Pay section but we could keep it as a bullet referencing Pay section. Might be okay. However to avoid thin duplication, maybe we keep it but it's okay. Check for any other specifics: "Trauma Level: Facility Specific" - that's a detail. Should we include? It's under Job Details. Could be included in About the role or Requirements? It's a facility attribute. Could add to About the role: "Trauma level: facility specific." We'll add. Also "Certifications: KS or compact license, BLS, ACLS, NIHSS" we already have. Also "Job Notes: Experience Requirement: 1 year of ICU RN experience- large facility, critical care Experience Preferred: ICU, Med/Surg, Experience w/ ventilators and titration drips New graduates accepted: No License and Certification Requirement: KS or compact license, BLS, ACLS, NIHSS In Hand" we covered. Also "When you apply with Junxion, you speak with a live U.S.-based recruiter..." that's about process; could be considered boilerplate? It's about recruiter support. Might be considered part of Benefits? It's a support benefit. Could add to Benefits: "Direct access to a live U.S.-based recruiter (no call centers or automated responses)." Also "dedicated recruiter and support team based in the U.S. who will guide you through credentialing, submission, and onboarding". That's a benefit. We'll add. Also "Junxion was built by a traveler and designed to support travelers." That's company description; we could incorporate into About the role or Benefits? It's more about company. Could add to About the role as a note: "Junxion Med Staffing was built by a traveler to support travelers, offering dedicated U.S.-based recruiter support." We'll incorporate. Also "Click here for licensing requirements" - remove as navigation. Also "About Junxion Med Staffing" paragraph we already used. Also "At Junxion, we keep it simple:" bullet list: Transparent communication, Ded