Travel ER RN - $3,500 per week

We need to output HTML fragment with sections: About the role? Actually we have "About Curam Staffing". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have job description: "Curam Staffing is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Rochester, New York." Then "Job Description & RequirementsSpecialty: ED - Emergency DepartmentDiscipline: RNStart Date: 09/28/2026Duration: 13 weeks48 hours per weekShift: 12 hours, rotatingEmployment Type: TravelCuram Staffing Job ID #V. Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Then "About Curam StaffingCuram Staffing was started to help candidates find good, viable jobs. Our goal is to partner with hospitals and streamline the interviewing process to reduce the amount of times you need to be submitted to a position." Then "BenefitsLicense and certification reimbursementWeekly payContinuing Education" We need to remove boilerplate: cookie/navigation/legal/EEO etc none present. Remove duplicated lines, application instructions none. We need to preserve all substantive info. We need sections: maybe "About the role" could be the description? But we have "About Curam Staffing" which is about the company. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We have details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Pay package based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's Pay info but says "subject to confirmation" and stipend amount TBD. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have "Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That includes TBD for stipend amount, but we still have some concrete: based on 12 hour shifts and 48.0 hours per week. However "subject to confirmation" maybe considered placeholder? It says "subject to confirmation" which is not a concrete number. The instruction says never create Pay section unless posting actually states them. It does state pay package based on 12 hour shifts and 48.0 hours per week (subject to confirmation). That's somewhat vague but still states basis. Might be okay to include Pay section with that sentence? But we must avoid filler like "TBD". The stipend amount to be determined is TBD. That's filler. Could we omit the stipend part? We must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the stipend amount to be determined, we are removing info. But we could include it as is, even though it's TBD. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says never create Pay section unless posting actually states them. It does state Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's stating something, albeit with TBD. The instruction about filler text: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That seems to refer to the content under the heading being just filler. If we include the Pay section, we would have some substantive info (based on 12 hour shifts and 48.0 hours per week) plus filler (stipend amount TBD). Might be okay? But maybe better to avoid Pay section because the stipend amount is TBD and the base is subject to confirmation, making it vague. However we still have concrete: 12 hour shifts and 48.0 hours per week. That's schedule info actually. Schedule: 12 hours, rotating. So we could put Schedule section with that. Pay could be omitted because stipend TBD and base subject to confirmation. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, we have "Shift: 12 hours, rotating" and "48 hours per week". That's schedule info. So we can include Schedule section. Benefits: we have "License and certification reimbursementWeekly payContinuing Education". That's substantive. So Benefits section. About the role: we have description of job: seeking travel nurse RN ED - Emergency Department in Rochester, New York. Also maybe "About Curam Staffing" is about company, not role. Could treat as "About the role" or "About Curam Staffing". The instruction list includes "About the role". We could use that heading for the job description summary. Then we could have a separate section for "About Curam Staffing"? Not in list. Could fold into About the role or maybe omit. But we need preserve all substantive info. The About Curam Staffing paragraph is substantive. Could we put it under a heading like "About the company"? Not allowed headings list. Could we put it as a

without heading? Yes, we can have prose

without heading. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. So we can have headings only for those specific sections; other prose can be just

  . So we can have a

  for the About Curam Staffing paragraph. Thus structure:

  About the role

  Curam Staffing is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Rochester, New York.

  Then maybe we need Responsibilities? Not given. Requirements? We have Specialty: ED - Emergency Department, Discipline: RN, Start Date: 09/28/2026, Duration: 13 weeks, 48 hours per week, Shift: 12 hours, rotating, Employment Type: Travel. Those could be considered Requirements or Qualifications. We could put them under

  Requirements

  as a list. But we must not repeat job title as heading. That's fine. We need to decide which sections to include: About the role, Requirements, Benefits, Schedule maybe. Pay maybe omitted. We have Schedule: 12 hours, rotating and 48 hours per week. That's schedule. Could be under Schedule. We have Benefits list. We have Pay info: maybe we could include under Pay but it's vague. I'd omit Pay to avoid filler. We need to preserve all substantive info: Start Date, Duration, 48 hours per week, Shift, Employment Type, Specialty, Discipline, Benefits items. Let's craft:

  About the role

  Curam Staffing is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Rochester, New York.

  Requirements

  • Specialty: ED - Emergency Department
  • Discipline: RN
  • Start Date: 09/28/2026
  • Duration: 13 weeks
  • 48 hours per week
  • Shift: 12 hours, rotating
  • Employment Type: Travel

  Benefits

  • License and certification reimbursement
  • Weekly pay
  • Continuing Education

  Schedule

  12 hour shifts, rotating; 48 hours per week.

  We also have "Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is partially covered by Schedule and maybe Pay. Since we omitted Pay, we might lose the mention of "tax-free stipend amount to be determined" and "subject to confirmation". That's substantive? It's about pay. The instruction says never create Pay section unless posting actually states them. It does state Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's a statement about pay, albeit vague. Should we include it? Perhaps we can include a Pay section with that sentence, but we must avoid filler like TBD. The stipend amount to be determined is TBD, which is filler. However we could still include the sentence as is; it's not purely filler, it includes concrete basis. The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". If we put that sentence under Pay heading, the content includes TBD, which is filler. Might violate. Could we rephrase to keep only substantive part? But we must not invent or summarize away detail. Summarizing away the stipend TBD would be removing detail. So we need to keep it. Maybe we can include Pay section but note that the stipend amount is TBD; that's still info. The instruction says never emit a heading followed by filler/placeholder text. It might be interpreted as: don't create a section whose only content is filler. If we have some substantive plus filler, it's okay? Not sure. Safer to include Pay section with the exact sentence. Thus add:

  Pay

  Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

  Now we have duplicated info about 12 hour shifts and 48 hours per week in both Schedule and Pay. That's okay; we preserve all. We also have About Curam Staffing paragraph. We'll add as a

  after About the role maybe. Thus final HTML:

  About the role

  Curam Staffing is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Rochester, New York.

  Curam Staffing was started to help candidates find good, viable jobs. Our goal is to partner with hospitals and streamline the interviewing process to reduce the amount of times you need to be submitted to a position.

  Requirements

  • Specialty: ED - Emergency Department
  • Discipline: RN
  • Start Date: 09/28/2026
  • Duration: 13 weeks
  • 48 hours per week
  • Shift: 12 hours, rotating
  • Employment Type: Travel

  Benefits

  • License and certification reimbursement
  • Weekly pay
  • Continuing Education

  Schedule

  12 hour shifts, rotating; 48 hours per week.