Travel ICU RN - $2,212 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. Let's parse the posting. Content: - Stability Healthcare is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Grand Junction, Colorado. - Job Description & Requirements - Specialty: ICU - Intensive Care Unit - Discipline: RN - Start Date: 10/19/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Stability Healthcare is looking for a ICU RN contract position in Grand Junction, CO. Intensive Care Unit (ICU) Nurses treat acutely ill patients with life-threatening conditions, in settings requiring continuous vigilance and high-intensity therapies. ICU nurses can specialize in a variety of disciplines including medical, surgical, cardiac, burn or Neuro ICU. - *$600 travel bonus - *Day 1 health insurance with United Healthcare - *PTO plan -- start accruing on day 1, use during contract or cash out at the end! - *Guaranteed stipend if facility calls you off - *Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours - Stability Healthcare Job ID #883567. 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: ICU - About Stability Healthcare: description. - Benefits: Guaranteed Hours, Benefits start day 1 (maybe repeated). Also earlier bullet points list benefits. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So no heading for ICU. We need to not put Job ID as heading; fold minor metadata into short p or drop it. We need to preserve all substantive information. We need to include sections only when posting has real specific content. Let's identify sections: About the role: Could be description of role: "Intensive Care Unit (ICU) Nurses treat acutely ill patients...". That's about role. Responsibilities: Not explicitly listed. Could infer from description but not explicit. Probably we should not create Responsibilities if not specific. Requirements: Could include specialty, discipline, start date, duration, hours, shift, employment type. Those are requirements. Qualifications: Not explicit beyond RN license? Not given. Skills: Not explicit. Benefits: bullet list includes travel bonus, health insurance, PTO, guaranteed stipend, extra hour bonus, guaranteed hours, benefits start day 1. 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." That's vague; not specific amount. It says tax-free stipend amount to be determined. That's not specific; we should not create Pay section unless posting actually states them. It does mention pay package based on shifts but no amount. It says "subject to confirmation" and "tax-free stipend amount to be determined". That's not specific. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have no specific amount; we could consider that not specific enough. So we should omit Pay section. Schedule: we have shift: 12 hours, nights; 36 hours per week; start date, duration. That's schedule info. So we can create Schedule section with those details. Benefits: we have specific benefits: $600 travel bonus, Day 1 health insurance with United Healthcare, PTO plan, Guaranteed stipend if facility calls you off, Extra hour bonus, Guaranteed Hours, Benefits start day 1. Those are specific. So Benefits section. About the role: we have description of ICU nurses role. So we can create About the role. Requirements: we have specialty, discipline, start date, duration, hours, shift, employment type. Those are requirements. So Requirements section. We should not repeat job title as heading. So no heading for ICU. We need to output HTML fragment only. Structure: Use

for section headings. Use

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

  for prose. We need to decide what goes into each section. About the role: prose describing ICU nurses role. Could be a

  . Requirements: list items: Specialty: ICU - Intensive Care Unit; Discipline: RN; Start Date: 10/19/2026; Duration: 13 weeks; Hours: 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel. Could be

  • each. Benefits: list items: $600 travel bonus; Day 1 health insurance with United Healthcare; PTO plan -- start accruing on day 1, use during contract or cash out at the end!; Guaranteed stipend if facility calls you off; Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours; Guaranteed Hours; Benefits start day 1. Schedule: Could include shift details? But we already have shift in requirements. However schedule section could contain shift, hours per week, start date, duration. But start date and duration maybe also requirements. To avoid duplication, we need to decide where to place each piece. The instruction: preserve ALL substantive information; do not invent or summarize away detail. We can place shift/hours in Schedule, and other details like start date, duration, employment type maybe in Requirements. But we must not duplicate. Let's think: The posting includes Start Date, Duration, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel. Those are all job logistics. Could be considered Schedule (hours, shift) and Requirements (start date, duration, specialty, discipline, employment type). But we can also put all under Requirements and not have Schedule. However we have schedule info (shift, hours) that is specific; we could create Schedule section for shift and hours. The rule: Prefer a few substantive sections over many thin ones. So maybe combine schedule info into Requirements to avoid many sections. But we also have Benefits section separate. About the role separate. So we could have About the role, Requirements, Benefits. That's three sections. That seems reasonable. Thus we will not create Schedule section separately; we will put shift and hours in Requirements list. Check if any other schedule specifics: start date, duration. Those also go in Requirements. Thus we will have:

    About the role

    Intensive Care Unit (ICU) Nurses treat acutely ill patients with life-threatening conditions, in settings requiring continuous vigilance and high-intensity therapies. ICU nurses can specialize in a variety of disciplines including medical, surgical, cardiac, burn or Neuro ICU.

    Requirements

    • Specialty: ICU - Intensive Care Unit
    • Discipline: RN
    • Start Date: 10/19/2026
    • Duration: 13 weeks
    • 36 hours per week
    • Shift: 12 hours, nights
    • Employment Type: Travel

    Benefits

    • $600 travel bonus
    • Day 1 health insurance with United Healthcare
    • PTO plan -- start accruing on day 1, use during contract or cash out at the end!
    • Guaranteed stipend if facility calls you off
    • Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours
    • Guaranteed Hours
    • Benefits start day 1
    We should also include maybe a brief About Stability Healthcare? That's about the company, not role. Could be considered About the role? Actually About the role is about the job. The company description could be considered "About the company" but not requested. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not add a section for company description unless it fits one of those headings. It could be considered "About the role"? Not really. The company description is not required to be included? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Where could we put it? Could be a

    under About the role? But that would mix role description with company description. Might be okay but could be considered not accurate. However we could add a separate section like "About the company" but not allowed headings. We could incorporate it into a

    after the role description, maybe as a separate paragraph but still under About the role heading? The heading is About the role, but we could put multiple paragraphs under it. That's acceptable: the heading describes the section, but we can include multiple paragraphs about role and company. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other content under those headings. So we can put company description under About the role as a paragraph. Thus About the role section will have two paragraphs: first about ICU nurses role, second about Stability Healthcare. Let's extract company description: "About Stability Healthcare Stability Healthcare was founded in 2009, with the mission of becoming the best Travel Nursing Agency in California. We have been rated one of the top travel nursing agencies and offer our nurses the highest paying travel nursing jobs available. We have access to the best travel assignments from 1000’s of facilities. You can start the year off in sunny California, spend the Spring in the Colorado Rockies, enjoy the Summer in the Mid-West, experience the change of seasons in Boston and New York, and hit the beaches of Florida in the winter. Our Nurses work in the best hospitals and health systems in the country." We need to preserve that exactly. Thus About the role:

    ICU nurses description.

    About Stability Healthcare...

    Now check for any other substantive info: The posting also mentions "Stability Healthcare Job ID #883567." That's minor metadata; we can fold into a short

    or drop it. Since we already have a paragraph for company description, we could add the Job ID there or separate short p. But rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can add a

    with Job ID maybe after the Benefits section or at end. But we need to preserve all substantive information; Job ID is minor but still substantive? It's metadata; we can include as a short p. We should not create a heading for it. So we can add a

    at the end:

    Job ID: #883567

    . But we need to ensure we don't duplicate any info already covered. Not duplicated. Now check for any other info: "Posted job title: ICU" - we should not repeat job title as heading; we can drop or include as minor metadata. Could add to same p. Thus final HTML:

    About the role

    Intensive Care Unit (ICU) Nurses treat acutely ill patients with life-threatening conditions, in settings requiring continuous vigilance and high-intensity therapies. ICU nurses can specialize in a variety of disciplines including medical, surgical, cardiac, burn or Neuro ICU.

    About Stability Healthcare Stability Healthcare was founded in 2009, with the mission of becoming the best Travel Nursing