Travel ICU RN - $2,041 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 as heading. Must remove boilerplate. We need to parse the posting. Key details: - Travel nurse RN ICU - Intensive Care Unit in San Angelo, Texas. - Specialty: ICU - Intensive Care Unit - Discipline: RN - Start Date: ASAP - Duration: 9 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Shift: Night 4x12-Hour (19:00 - 07:00) - Requirements: Years of Experience: 2 year(s) - Previous Charge Experience: Preferred - Charting System: Required, Epic - Travel Experience Required: Yes - Certifications: (Certs marked with * are preferred) ACLS, BLS, NIHSS, PALS or ENPC within 1 year of SD, PALS*, TNCC* - Pay package: based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - About Reliant Staffing Partners: description of company, services, mission, etc. - Benefits list: eligibility for health, vision and dental coverage; telemedicine; discounts on prescriptions; Simple IRA retirement plan; Life Insurance; Hospital Indemnity Insurance; Accident Insurance; Cancer Insurance; Working Advantage Program; LifeLock Identity Theft Protection; Sick Pay; Stipend Pay; Referral Pay. - Contact info: email. We need to produce sections: About the role (maybe description of role), Responsibilities (maybe not present), Requirements, Qualifications (maybe overlapping), Skills, Benefits, Pay, Schedule. We must only include sections with real specific content. The posting does not have explicit responsibilities list; but we could infer duties? However we must not invent. So we should not include Responsibilities if no specific content. Similarly Qualifications may be similar to Requirements; but we can combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have: - About the role: Could be the description of the job: travel nurse RN ICU in San Angelo, Texas, start date ASAP, duration 9 weeks, 36 hrs/week, night shift 4x12-hour, etc. That seems like role details. So we can put About the role section with that info. - Responsibilities: Not given explicitly. So skip. - Requirements: We have years of experience, previous charge experience preferred, charting system required Epic, travel experience required yes, certifications list. That's specific. So include Requirements. - Qualifications: Might be similar to Requirements; but we could treat certifications as qualifications? However we already have Requirements covering experience and certifications. Could we also include Qualifications for things like "RN license"? Not mentioned. Safer to skip Qualifications if no distinct content. - Skills: Not listed explicitly. Could infer ICU skills but not given. So skip. - Benefits: List of benefits given. So include Benefits. - Pay: Pay package description: based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's specific enough? It mentions pay package based on shifts, tax-free stipend to be determined. It's not a specific number but it's still content. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined." That's somewhat TBD but it's still stating that stipend amount to be determined. Is that considered placeholder? It says "to be determined". That is similar to TBD. Might be considered placeholder. However the pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation). That's also somewhat vague. The instruction says do not create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package info, albeit vague. Should we include? It says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "tax-free stipend amount to be determined" is akin to TBD. So maybe we should omit Pay section because it's mostly placeholder. However we could still include the part about based on 12 hour shifts and 36 hours per week (subject to confirmation). That's still somewhat vague but not exactly placeholder. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, albeit vague. I'd lean to include Pay section with the given sentence. - Schedule: We have shift details: 12 hours, nights; Night 4x12-Hour (19:00 - 07:00); 36 hours per week. That's specific. So include Schedule. Now we need to format. We must not include Job ID. Also remove boilerplate like About Reliant Staffing Partners description? That's company info, not about the role. Should we include that? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Reliant Staffing Partners is company description; not boilerplate but maybe considered generic. However it's substantive info about the employer. Could be included under About the role? Or maybe we could create a separate section like "About the company" but not in allowed headings. The allowed headings list does not include "About the company". So we should not create a new heading. We could incorporate relevant info into About the role? But About the role is supposed to be about the role, not company. However we could include company info in About the role if we want, but it's not ideal. The instruction says "Prefer a few substantive sections over many thin ones." So we could combine company info into About the role or maybe Benefits? Probably better to put company info in About the role? But the heading "About the role" suggests role description. The company description is not about the role. However we could omit it entirely, as it's not required for the job posting core. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must preserve company description. If we omit it, we lose substantive info. So we need to include it somewhere. Since we cannot create a new heading not in list, we could put it under About the role? But that would be mixing role and company. Could we put it under Benefits? No. Could we put it under Requirements? No. Could we put it under Qualifications? No. Could we put it under Skills? No. Could we put it under Pay? No. Could we put it under Schedule? No. Thus we might need to include a section not in the list? The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests these are examples, not exclusive? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might imply we should use those headings when appropriate, but we could also use other headings? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings. It doesn't explicitly forbid other headings, but the examples are given. To be safe, we should stick to those headings. However we need to preserve company info. Perhaps we can include it under About the role as a brief note about the employer. That would still be substantive. Let's do that. Thus About the role will contain: travel nurse RN ICU in San Angelo, Texas; start date ASAP; duration 9 weeks; 36 hours per week; shift nights 4x12-hour (19:00-07:00); employment type travel; plus company description about Reliant Staffing Partners. Now Requirements: years of experience 2 years; previous charge experience preferred; charting system required Epic; travel experience required yes; certifications: ACLS, BLS, NIHSS, PALS or ENPC within 1 year of SD, PALS*, TNCC*. Benefits: list as given. Pay: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Schedule: maybe we already included shift details in About the role; but we can also have Schedule section with shift details: 12-hour night shifts, 4x12-hour per week (19:00-07:00), 36 hours per week. We must avoid duplication. If we put shift details in About the role, we could still include Schedule but maybe it's okay to have some overlap? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but we should avoid duplicated lines? It says remove duplicated lines. So we should not repeat the same exact sentence. We can shift details in About the role and Schedule but rephrase? Might be considered duplication. Better to put shift details in Schedule and keep About the role focused on role basics (specialty, location, start date, duration, employment type). Then Schedule has shift specifics. Thus: About the role: Travel nurse RN ICU - Intensive Care Unit position in San Angelo, Texas. Start date ASAP. Duration 9 weeks. Employment type Travel. (maybe also mention Reliant Staffing Partners description). We'll add company description after. Requirements: as list. Benefits: as list. Pay: as given. Schedule: shift details. Now format. We need

for each section heading. Then content: use

for prose,

• for lists. We must not include markdown code fences. Let's craft. About the role:

  Travel nurse RN ICU - Intensive Care Unit position in San Angelo, Texas. Start date ASAP. Duration 9 weeks. Employment type Travel.

  Then maybe a second paragraph for company description:

  Reliant Staffing Solutions – Connecting Healthcare Professionals Nationwide. Since 2016, Reliant Staffing Solutions has been proudly serving clients and candidates across the healthcare ecosystem. Our services are designed to meet the unique needs of both employers and job seekers, creating balanced, successful, and fulfilling workplaces for everyone. We are a full-cycle staffing firm dedicated to aligning talent with organizational needs through proven strategies and the latest recruitment practices. At Reliant, we focus on building lasting relationships, knowing that exceptional service drives success for all. Our mission is simple: deliver the support you deserve while helping you achieve your goals. From temporary (PRN, local, and travel contracts) and temp-to-hire to direct hire placements, we are committed to creating positive outcomes and fostering workplaces where both employers and candidates thrive.

  That's a lot but it's substantive. Requirements:
  • 2 years of experience
  • Previous charge experience preferred
  • Charting system required: Epic
  • Travel experience required: Yes
  • Certifications: ACLS, BLS, NIHSS, PALS or ENPC within 1 year of start date; PALS* (preferred); TNCC* (preferred)
  We need to preserve the exact phrasing: "Certfications: (Certs marked with * are preferred) ACLS, B