Travel ICU RN - $2,345 per week

We need to produce HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not put Job ID as heading. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. We need to parse the posting for content. Let's extract: - Specialty: ICU - Intensive Care Unit - Discipline: RN - Start Date: 10/05/2026 - Duration: 13 weeks (also says 13.14 weeks) - 36 hours per week - Shift: 12 hours, rotating - Employment Type: Travel - Certifications: ACLS (AHA or ARC), BLS (AHA or ARC) - Trauma Level: Facility Specific - 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: Benefits list: Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. - 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 some pay info but not exact amount. The rule: do NOT include Pay section unless posting actually states them. It does state some info about pay package, but not a specific number. 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 some info. Should we include Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay package, albeit vague. We can include Pay section with that info. However we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "tax-free stipend amount to be determined" is TBD-like. Might be considered placeholder. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we must ensure we have substantive content, not just placeholder. The posting 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 partially placeholder. Might be better to omit Pay section because it's not a concrete amount. The rule says "Prefer a few substantive sections over many thin ones." So we could omit Pay. Schedule: we have shift details: 12 hours, rotating; 36 hours per week; start date; duration. That's schedule info. So we can include Schedule section. Benefits: we have substantive list: Insurance Plans starting under $175/month, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement, Weekly pay (though that's pay). So we can include Benefits. About the role: we have summary: "Junxion Med Staffing is looking for a ICU RN to take an assignment in Woodruff, Wisconsin. This assignment lasts 13.14 WEEKS and is scheduled to start on October 5, 2026. If the start date, shift, or pay doesn’t line up with what you're looking for, let’s talk. We often have multiple openings in the same market. Give us a call opt 1". Also "Job Details: Shift: 12 H Rotating Total Weekly Hours: 36 Certifications: ACLS (AHA or ARC), BLS (AHA or ARC) Trauma Level: Facility Specific". Also "Job Notes: Thank you for providing the details. If you have any questions or need further clarification regarding the job description, feel free to ask! When you apply with Junxion, you speak with a live U.S.-based recruiter who understands the travel market. No call centers. No automated responses. Our team works directly with you throughout your assignment." Also "About the Company:" and "About Junxion Med Staffing". Those are about company, not role. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We need to decide which sections to include based on actual content. - About the role: we have summary description of the role, location, start date, duration, etc. That fits. - Responsibilities: not explicitly listed. The posting does not list duties/responsibilities. So we should not include Responsibilities heading. - Requirements: we have Certifications: ACLS, BLS. Also maybe RN license implied. Also Trauma Level: Facility Specific (maybe not a requirement). Could include Requirements section with certifications. - Qualifications: maybe similar to Requirements. Could combine? But we need to avoid thin sections. Could put Requirements and Qualifications together? But headings are separate. We could include Requirements with certifications, and Qualifications maybe empty -> not allowed. So we should only include Requirements if we have substantive content. We have certifications. That's enough. - Skills: not listed explicitly. Could infer ICU RN skills but not stated. So omit. - Benefits: we have substantive list. - Pay: we have vague info; maybe omit. - Schedule: we have shift, hours, start date, duration. Thus we will output sections: About the role, Requirements, Benefits, Schedule. We need to use

for each heading. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Let's extract precise text. About the role: Could combine summary and job details. We can write:

  Junxion Med Staffing is looking for an ICU RN to take an assignment in Woodruff, Wisconsin. The assignment lasts 13.14 weeks and is scheduled to start on October 5, 2026.

  Maybe also include note about start date, shift, pay not lining up etc. That's more like a call to action; but it's substantive? It says "If the start date, shift, or pay doesn’t line up with what you're looking for, let’s talk. We often have multiple openings in the same market. Give us a call opt 1". That's not essential job description but still part of posting. Might keep. But we should avoid fluff? It's still part of posting. We'll include. Job Details: Shift: 12 H Rotating, Total Weekly Hours: 36, Certifications: ACLS (AHA or ARC), BLS (AHA or ARC), Trauma Level: Facility Specific. We can incorporate that into Requirements or About the role. Since Requirements is for certifications, we can put that there. Let's craft: About the role:

  Junxion Med Staffing is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Woodruff, Wisconsin. The assignment lasts 13.14 weeks and is scheduled to start on October 5, 2026. If the start date, shift, or pay doesn’t line up with what you're looking for, let’s talk. We often have multiple openings in the same market. Give us a call opt 1.

  Requirements:
  • Current RN license (implied)
  • ACLS certification (AHA or ARC)
  • BLS certification (AHA or ARC)
  But we must not invent info not present. The posting does not explicitly say "Current RN license". It says Discipline: RN, which implies RN license. Is that considered substantive? It's given. We could include "RN license" as requirement based on Discipline: RN. That's not inventing; it's directly from posting. So we can include. Also Trauma Level: Facility Specific is not a requirement but a detail. Could include in Requirements? Might be better to put under About the role or separate. But we have no separate heading for "Details". Could add to About the role. Better: Keep Requirements to certifications only. Add note about RN license as part of Discipline. Thus Requirements:
  • RN license
  • ACLS certification (AHA or ARC)
  • BLS certification (AHA or ARC)
  Benefits: we need to list all benefits mentioned. From posting: - 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 - Medical benefits - Dental benefits - Vision benefits - Mileage reimbursement - Weekly pay (though that's pay, but listed under Benefits later). We'll include as benefit? It's under Benefits list later: "Weekly pay". Might be considered part of compensation but we already omitted Pay section. Could include as benefit. We should not duplicate. We'll list all. Thus Benefits:
  • Insurance plans starting under $175/month for employees
  • Referral bonus
  • Additional contract bonus opportunities
  • Vacation incentives
  • Employee Assistance Program (EAP)
  • 401k plan with access to financial advisors
  • Medical benefits
  • Dental benefits
  • Vision benefits
  • Mileage reimbursement
  • Weekly pay
  Schedule: we have start date, duration, shift, hours. We can write:

  Start date: October 5, 2026

  Duration: 13.14 weeks (approximately 13 weeks)

  Shift: 12 hours, rotating

  Total weekly hours: 36

  Or combine into a
  . Since schedule details are a list, we can use
  • . Thus Schedule:
    • Start date: October 5, 2026
    • Duration: 13.14 weeks
    • Shift: 12 hours, rotating
    • Total weekly hours: 36
    We must not include Pay section. Now ensure we do not include any boilerplate like EEO, navigation, etc. We removed. Check for any other substantive content: "About the Company:" and "About Junxion Med Staffing" includes description of company. That's not role-specific; but could be considered "About the role"? Not exactly. The instruction says use headings like About the role, Responsibilities, etc. So we should not include company description unless it fits under About the role? It's about the company, not the role. Probably we should omit as it's not role-specific. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit company description. Also "Click here for licensing requirements" is a link; we should not include as it's navigation? It's a link but maybe substantive? It's a directive to