Local Contract CCU RN - $62 per hour

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if there is real specific content. We need to parse the posting. Content: - Job title: local contract nurse RN CCU - Coronary Care (but we don't repeat as heading) - Location: Urbana, Illinois - Specialty: CCU - Coronary Care - Discipline: RN - Start Date: 10/12/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Local Contract - Description: ICU RN contract position in Urbana, IL. 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. - Benefits list: *$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 - Job ID #L-881969 (metadata) - 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 (maybe duplicate) - About Stability Healthcare: description of company. - Benefits: Guaranteed Hours, Benefits start day 1 (maybe duplicate) - Also earlier: BenefitsGuaranteedHoursBenefits start day 1 (looks like formatting glitch) We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to include sections only if real specific content. Potential sections: - About the role: could contain description of role (ICU RN responsibilities). We have description: "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." That's substantive. - Responsibilities: maybe not explicitly listed; we could infer but better not to invent. The posting does not list specific responsibilities beyond that description. Could treat that as About the role. - Requirements: maybe includes specialty, discipline, start date, duration, hours, shift, employment type. Those are job details, could be considered Requirements. But we need to decide. - Qualifications: maybe RN license, CCU experience? Not explicitly stated. Could be implied but not explicit. Safer not to create Qualifications if not explicit. - Skills: not listed. - Benefits: we have list of benefits: $600 travel bonus, Day 1 health insurance with United Healthcare, PTO plan, Guaranteed stipend if facility calls you off, Extra hour bonus. Also Guaranteed Hours, Benefits start day 1 (maybe duplicate). So we have specific benefits. - Pay: we have "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; stipend amount TBD, not specific. According to rule: do NOT create Pay section unless posting actually states them. It states pay package based on shifts/hours but stipend amount TBD. Is that enough? 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 not a specific amount; it's vague. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Since stipend amount TBD, that's placeholder. So we should not create Pay section. - Schedule: we have shift: 12 hours, nights; 36 hours per week; start date, duration. That's schedule info. Could create Schedule section with those details. - About the company: Could be "About Stability Healthcare". That's not a standard heading but could be "About the company" but not in list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a custom heading like About Stability Healthcare. Instead we could incorporate that info into About the role? Probably not. 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; we could also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. Thus we need to decide which sections have real specific content. - About the role: we have description of role (ICU RN duties). That's appropriate. - Responsibilities: maybe we could extract from description: treat acutely ill patients, continuous vigilance, high-intensity therapies, can specialize in disciplines. That's more responsibilities. Could split but we might combine. - Requirements: includes specialty (CCU), discipline (RN), start date, duration, hours per week, shift, employment type. Those are requirements for the contract. - Benefits: list as above. - Schedule: shift details, hours per week, maybe start date and duration? Could be schedule. We must not repeat job title as heading. Not include Job ID. We must not include boilerplate like "About Stability Healthcare" unless we fit into allowed headings. Could we put that under "About the role"? Not really. Could we omit it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep that info somewhere. If we cannot use a heading not in list, maybe we can incorporate it into a

without a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

for section headings (e.g. those). Likely they expect we use those headings for sections; we could also have other headings but they'd be non-standard. Safer to stick to those. We could put the company description under "About the role" as a paragraph? But that would be mixing. Better to create a section "About the role" that includes both role description and company info? Might be okay. Alternatively, we could create a section "About the role" for role description, and then another section "About the company" not in list but maybe they'd accept? The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we could use other headings like "About the company". However, they also say "Prefer a few substantive sections over many thin ones." So we could combine. I'll produce sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We need to ensure we don't create empty sections. Let's extract content: About the role: "ICU RN contract position in Urbana, IL. 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." Responsibilities: Could be same as above? Might be redundant. Maybe we can treat the description as responsibilities. But we need to avoid duplication. Perhaps we can split: About the role: brief overview; Responsibilities: list of duties (treat acutely ill patients, provide continuous vigilance, administer high-intensity therapies, monitor patients, collaborate with team, etc.) But we don't have explicit list. Safer to not create Responsibilities if it's just same as About the role. However we need to preserve all substantive info; we can put it under About the role only. Requirements: list items: Specialty: CCU - Coronary Care; Discipline: RN; Start Date: 10/12/2026; Duration: 13 weeks; Hours per week: 36 hours; Shift: 12 hours, nights; Employment Type: Local Contract. We could format as

• each. Benefits: list: $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. Note: "Guaranteed Hours" and "Benefits start day 1" maybe duplicates but we keep. Schedule: Shift: 12 hours, nights; Hours per week: 36 hours; Start Date: 10/12/2026; Duration: 13 weeks. Could also include that it's nights. We need to avoid duplication: start date and duration appear both in Requirements and Schedule. Might be okay but could be considered duplication. The instruction: "Remove duplicated lines". So we should not repeat same info in multiple places. We need to decide where to put each piece. We could put start date, duration, hours, shift in Schedule, and requirements could be specialty, discipline, employment type. Or vice versa. Let's think: Requirements likely refer to qualifications needed: specialty, discipline, maybe license. Schedule refers to shift pattern, hours, start date, duration. Thus: Requirements: - Specialty: CCU - Coronary Care - Discipline: RN - Employment Type: Local Contract Schedule: - Start Date: 10/12/2026 - Duration: 13 weeks - Hours per week: 36 hours - Shift: 12 hours, nights That avoids duplication. About the role: description of role. Benefits: list. Now we need to output HTML fragment with

  headings and

  • for lists,

    for prose. We must not include any extra text outside HTML. Let's craft:

    About the role

    ICU RN contract position in Urbana, IL. 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: CCU - Coronary Care
    • Discipline: RN
    • Employment Type: Local Contract

    Schedule

    • Start Date: 10/12/2026
    • Duration: 13 weeks
    • Hours per week: 36 hours
    • Shift: 12 hours, nights

    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