Travel OR RN - $2,632 per week

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 with real content. We have job description: "Reliant Staffing Partners is seeking a travel nurse RN OR - Operating Room for a travel nursing job in Abilene, Texas." Then "Job Description & Requirements" then details: Specialty, Discipline, Start Date, Duration, 40 hours per week, Shift: 10 hours, days, Employment Type: Travel, Shift: Day 4x10-Hour (06:30 - 17:00). Requirements: Previous Charge Experience: Preferred, Years of Experience: 2 year(s), Charting System: Preferred, Allscripts, Trauma Level I Experience: Preferred, Trauma Level II Experience: Preferred, Travel Experience Required: No, Certifications: (Certs marked with * are preferred) ACLS*, BLS, CNOR*, NIHSS*, PALS*, TNCC*. Job ID #32011. Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Then "About Reliant Staffing Partners" paragraph. Then "In addition, your compensation package includes the following options:" list of benefits. We need to extract sections: About the role? Could be the description about the job: maybe "About the role" includes the job description (specialty, discipline, start date, duration, shift, etc). Responsibilities? Not given explicitly; maybe we can infer from OR nurse duties but we shouldn't invent. So we should not create Responsibilities if no content. Requirements: we have requirements list. Qualifications? Could be same as requirements? Might combine. Skills? Could be certifications? But we have certifications list. Benefits: we have list of compensation package options. Pay: we have mention of pay package based on 10 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's vague but it's actual content: "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific number but it's still content. According to rules: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it's "tax-free stipend amount to be determined." That's somewhat TBD. Might be considered placeholder. Safer to omit Pay section if it's just TBD. However we have "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation)". That's still somewhat vague but it's actual statement. Might be okay. But we need to avoid filler. The phrase "tax-free stipend amount to be determined" is TBD. I'd consider that placeholder and maybe omit Pay section. However we could include Pay with that sentence? The rule 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 essentially TBD. So better to omit Pay. Schedule: we have shift details: 10 hour shifts, days, Day 4x10-Hour (06:30 - 17:00). That's specific. So we can include Schedule section. Benefits: we have list of options. So include Benefits. About the role: we have description about the job: specialty, discipline, start date, duration, shift, employment type, location. That's substantive. Requirements: we have list. Qualifications: maybe we can treat certifications as qualifications? But we already have requirements includes certifications. Could combine Requirements and Qualifications? Better to have Requirements section covering years of experience, charge experience, charting system, trauma experience, travel experience, certifications. Qualifications could be empty; we should not create empty. Skills: maybe not needed. Thus 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 need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. Let's extract content. About the role: Should include location Abilene, Texas, specialty OR - Operating Room, discipline RN, start date ASAP, duration 9 weeks, 40 hours per week, shift 10 hours days, employment type Travel, shift Day 4x10-Hour (06:30 - 17:00). Also maybe mention Reliant Staffing Partners seeking a travel nurse RN OR - Operating Room for a travel nursing job in Abilene, Texas. That's the core. We should not repeat job title as heading; we already have About the role heading. We need to include the info about Reliant Staffing Partners? That's about the company, not the role. Could be part of About the role? Might be considered "About Reliant Staffing Partners" separate but we could include as part of About the role? The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we should put the role description there, not the company description. The company description could be omitted as boilerplate? It's not exactly boilerplate but it's about the staffing firm. Might be considered not required. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not those; it's about the staffing partner. Might be considered relevant? However the sections we can use are limited; we could include a section "About Reliant Staffing Partners" but that's not in the allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create other headings. So we should incorporate relevant info about the company maybe into About the role? But that might be odd. However the instruction says "Prefer a few substantive sections over many thin ones." So we can just have About the role, Requirements, Benefits, Schedule. The company description could be omitted as not required for the job posting? It's not essential to the role. It's okay to drop. Thus About the role paragraph: combine the details. Let's craft:

  Reliant Staffing Partners is seeking a travel nurse RN for an Operating Room (OR) position in Abilene, Texas. The role starts ASAP, lasts 9 weeks, requires 40 hours per week on day shifts (four 10‑hour shifts, 06:30–17:00). Specialty: OR - Operating Room; Discipline: RN; Employment Type: Travel.

  That's substantive. Requirements: list items: - Previous Charge Experience: Preferred - Years of Experience: 2 year(s) - Charting System: Preferred, Allscripts - Trauma Level I Experience: Preferred - Trauma Level II Experience: Preferred - Travel Experience Required: No - Certifications: ACLS* (preferred), BLS, CNOR* (preferred), NIHSS* (preferred), PALS* (preferred), TNCC* (preferred) We need to preserve all detail. Use
  • for each. Benefits: list from "In addition, your compensation package includes the following options:" then 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 We should keep as list. Schedule: details: Shift: 10 hours per day, days; Shift: Day 4x10-Hour (06:30 - 17:00). Also 40 hours per week. Could combine.

    Shift: 10‑hour days, four shifts per week (06:30–17:00), totaling 40 hours per week.

    Now ensure we don't include any boilerplate like "Job ID #32011." That's minor metadata; we can drop or fold into short p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we could include a short p with Job ID maybe. But we already have sections; we could add a

    after About the role? But that would be extra section not heading. It's okay to have a paragraph without heading? The instruction says use

    for section headings,

    • for any list,

      for prose. It doesn't forbid stray paragraphs without heading, but likely they expect sections only. However we can include Job ID in a short p within About the role or as a separate p before sections. Safer to drop it as minor metadata. Pay: we decided to omit because it's TBD. Now produce HTML fragment. Let's craft:

      About the role

      Reliant Staffing Partners is seeking a travel nurse RN for an Operating Room (OR) position in Abilene, Texas. The role starts ASAP, lasts 9 weeks, requires 40 hours per week on day shifts (four 10‑hour shifts, 06:30–17:00). Specialty: OR - Operating Room; Discipline: RN; Employment Type: Travel.

      Requirements

      • Previous Charge Experience: Preferred
      • Years of Experience: 2 year(s)
      • Charting System: Preferred, Allscripts
      • Trauma Level I Experience: Preferred
      • Trauma Level II Experience: Preferred
      • Travel Experience Required: No
      • Certifications: ACLS* (preferred), BLS, CNOR* (preferred), NIHSS* (preferred), PALS* (preferred), TNCC* (preferred)

      Benefits

      • 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

      Schedule

      Shift: 10‑hour days, four shifts per week (06:30–17:00), totaling 40 hours per week.

      Check for any missing info: Start date ASAP, duration 9 weeks included. Good. We didn't include "Shift: 10 hours, days" duplicate but covered. We didn't include "Employment Type: Travel" included. We didn't include "Specialty: OR - Operating Room" included. We didn't include "Discipline: RN" included. We didn't include "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." We omitted as placeholder. Check for any other substantive info: "Reliant Staffing Solutions – Connecting Healthcare Professionals Nationwide" etc. We omitted