Travel Nurse RN - ICU - Intensive Care Unit - $2,055 per week
About the role
As an ICU RN, you'll provide hands-on care for critically ill patients. Intensive Care nurses must be able to assess, plan, and implement care strategies for patients who may suffer from a variety of complex health conditions, but all of whom need round-the-clock attention.
Responsibilities
- Provide hands-on care for critically ill ICU patients.
- Assess patient conditions and develop care plans.
- Implement care strategies for patients with complex health conditions.
- Ensure round-the-clock monitoring and attention.
under Responsibilities, not a list. But we need to use
- for any list of duties/requirements/benefits. If we have a list, we need to use ul/li. If we have prose, use
. The responsibilities are not explicitly a list; we could keep as
. However the rule: "Use
- for any list of duties/requirements/benefits, and
for prose." So if we have a list, we must use ul/li. If we have prose, use p. The responsibilities could be expressed as prose. Let's keep as
. Similarly for Requirements: we have start date, duration, hours per week, shift, employment type, specialty, discipline. Could be a list. Use ul/li. Qualifications: maybe none; skip. Skills: none. Benefits: list. Pay: prose. Schedule: could be list or prose. We have shift, hours per week, start date, duration. Could be list. Let's extract exact text: - Specialty: ICU - Intensive Care Unit - Discipline: RN - Start Date: 10/25/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel We'll put those as list items. Benefits list from posting: "Weekly pay", "Guaranteed Hours", "Wellness and fitness programs", "Referral bonus", "Medical benefits", "Dental benefits", "Vision benefits", "401k with employer match", "Assistance with travel, compliance, and housing", "Great bonuses for completions, referring friends, and more". Also earlier they mention "industry-leading pay, benefits, and bonuses" but that's generic. We'll keep the explicit list. 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." Schedule: Could include start date, duration, shift, hours per week. But we already have those in Requirements; maybe we should not duplicate. However the instruction: preserve ALL substantive information; do not invent or summarize away detail. If we put start date etc in Requirements, we still need to include them somewhere; we could put them in Schedule instead. But we need to avoid duplication. Let's decide: Put start date, duration, shift, hours per week in Schedule section. Requirements could focus on specialty, discipline, employment type. But the posting lumps them together. To avoid duplication, we can put all job specifics under Requirements and not have Schedule. However the rule says we should include a section only when posting has real specific content for it. It does have schedule info (shift, hours, start date, duration). So we could have Schedule section with those details. Then Requirements could be about specialty, discipline, employment type. But we need to avoid duplication; we can split. Let's define: - Requirements: Specialty: ICU - Intensive Care Unit; Discipline: RN; Employment Type: Travel. - Schedule: Start Date: 10/25/2026; Duration: 13 weeks; Hours per week: 36 hours; Shift: 12 hours, nights. That seems reasonable and avoids duplication. Now About the role: we have the description paragraph. Responsibilities: maybe we can extract from description: "provide hands-on care for critically ill patients", "assess, plan, and implement care strategies". We'll put as a list? Could be prose. Let's keep as
with two sentences. Now Benefits: list. Pay: paragraph. Schedule: list. Now ensure we don't include any boilerplate like "About Trustaff" etc. That's not a section heading we need; but we might incorporate some of that into Benefits? The "About Trustaff" paragraph includes generic agency description; not specific to the job. It's not required to preserve? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The About Trustaff paragraph is substantive about the company, but it's not specific to the job posting? It's still part of the posting. Should we preserve it? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Trustaff is not boilerplate; it's marketing copy about the agency. It's substantive. Should we include it? Possibly under a section like "About the company" but we only have predefined headings. We could put it under "About the role"? No, that's about role. Could we create a custom heading? Not allowed; only use those headings. So we might need to drop it because it doesn't fit any allowed heading. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are the allowed headings. It also says "include a section ONLY when the posting has real, specific content for it". So we cannot create other headings. Therefore we must either incorporate that content into one of those sections or drop it. The About Trustaff content is about the agency, not the role. Could fit under "About the role"? Not really. Could be considered part of "Benefits"? Not exactly. Could be part of "Requirements"? No. So maybe we should drop it as it's not directly about the job. The instruction says preserve ALL substantive information; but if we cannot fit it into allowed headings, maybe we drop it because it's not required to be in those sections? However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't say we must include all text; it says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep all substantive info, but we can only use those headings. If some info doesn't fit, we might need to incorporate it into the closest section, maybe as a paragraph under "About the role" or "Benefits". The About Trustaff is about the company, but we could treat it as additional info about the role's employer, maybe under "About the role". That seems plausible: "About the role" could include info about the employer. We'll add a paragraph after the role description. Thus About the role will have two paragraphs: first the role description, second the Trustaff description. Now let's craft HTML. We must not include or . Just fragment. Let's write:
About the role
As an ICU RN, you'll provide hands-on care for critically ill patients. Intensive Care nurses must
- for any list of duties/requirements/benefits, and