Travel Nurse RN - OR - Operating Room - $2,673 per week

We need to output HTML fragment with headings

for 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. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. The posting includes: Talent4Health is seeking a travel nurse RN OR - Operating Room for a travel nursing job in Summit, New Jersey. Then Job Description & Requirements: Specialty: OR - Operating Room Discipline: RN Start Date: 10/12/2026 Duration: 13 weeks 38 hours per week Shift: 12 hours, days Employment Type: Travel Schedule Notes:7a - 8p Skills:1 year experience BLS - Required RN License - Required CNOR - Preferred Education:Graduate of an accredited School of Nursing Associates or Bachelor's Degree - Preferred About Talent4Health... then Why Choose us? etc. We need to extract sections: About the role (maybe description), Responsibilities (maybe not explicit), Requirements (maybe skills, license, experience), Qualifications (education), Skills (list), Benefits (maybe not explicit), Pay (none), Schedule (shift, hours, start date, duration). We must not create sections with placeholder or vague content. So we need to see what actual content exists. Let's parse: - Job location: Summit, New Jersey (maybe part of About the role) - Specialty: OR - Operating Room - Discipline: RN - Start Date: 10/12/2026 - Duration: 13 weeks - 38 hours per week - Shift: 12 hours, days - Employment Type: Travel - Schedule Notes: 7a - 8p - Skills: 1 year experience, BLS - Required, RN License - Required, CNOR - Preferred - Education: Graduate of an accredited School of Nursing Associates or Bachelor's Degree - Preferred About Talent4Health: description of company, why choose us. We need to avoid boilerplate like "Why Choose us?" maybe considered marketing but still substantive? It's about the agency. Might be considered "About the company" but not required sections. The instruction: "Prefer a few substantive sections over many thin ones." We can include About the role (maybe combine job description and company info). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could include location, specialty, discipline, start date, duration, hours, shift, employment type, schedule notes. That's substantive. - Responsibilities: Not explicitly listed. Could infer OR nurse duties but not given. So we should not create Responsibilities section if no specific content. - Requirements: Could include license, experience, BLS, CNOR preferred. That's specific. - Qualifications: Could include education (Associates or Bachelor's preferred). That's specific. - Skills: Could list 1 year experience, BLS, RN License, CNOR preferred. But that overlaps with Requirements. Might combine. However we have separate Skills heading allowed. We could put skills list there. - Benefits: Not mentioned. So omit. - Pay: Not mentioned. Omit. - Schedule: Could include shift details, hours per week, start date, duration, schedule notes. That's specific. Thus we will output sections: About the role, Requirements, Qualifications, Skills, Schedule. We must not repeat job title. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info. Let's craft. About the role: location Summit, NJ; specialty OR - Operating Room; discipline RN; start date 10/12/2026; duration 13 weeks; 38 hours per week; shift 12 hours, days; employment type Travel; schedule notes 7a - 8p. We can put as

  with sentences or maybe list. Since it's prose, use

  . Requirements: BLS - Required; RN License - Required; CNOR - Preferred; 1 year experience. Could be list. Qualifications: Graduate of an accredited School of Nursing; Associates or Bachelor's Degree - Preferred. Skills: Could list same as requirements? But maybe we separate: Skills: 1 year experience; BLS; RN License; CNOR (preferred). However that duplicates. Might be okay but we could instead put Skills: (maybe none distinct). But we need to include Skills section only if there is real specific content. The posting has "Skills:" line with those items. So we can treat that as Skills section. Thus we have both Requirements and Skills with overlapping content. Might be thin but still specific. The instruction: "Prefer a few substantive sections over many thin ones." Having both Requirements and Skills may be thin. Perhaps we combine them into one section, but we have to follow allowed headings; we can omit Skills if we put its content under Requirements. However the instruction says use headings only when posting has real specific content for it. It does not forbid combining content under a heading that is not exactly matching the line. So we could put all under Requirements and omit Skills. But we need to decide. Better to follow the posting: they have a "Skills:" line. So we should include Skills section with that content. Requirements could be about license and experience? Actually they also have "Requirements" not explicitly labeled but we can infer. The posting has "Job Description & Requirements" heading, then list of items. So we could treat that as Requirements section. Then Skills could be separate? But the line "Skills:" appears after that. Actually the posting: after "Education:" line, then "About Talent4Health". Wait let's re-read: "Job Description & RequirementsSpecialty: OR - Operating RoomDiscipline: RNStart Date: 10/12/2026Duration: 13 weeks38 hours per weekShift: 12 hours, daysEmployment Type: TravelSchedule Notes:7a - 8pSkills:1 year experience BLS - Required RN License - Required CNOR - PreferredEducation:Graduate of an accredited School of Nursing Associates or Bachelor's Degree - PreferredAbout Talent4Health..." So they have no explicit line break but we can parse: after Schedule Notes: they list Skills: then Education: then About Talent4Health. Thus the "Skills:" line includes: 1 year experience BLS - Required RN License - Required CNOR - Preferred. Education line includes: Graduate of an accredited School of Nursing Associates or Bachelor's Degree - Preferred. Thus we could treat Skills as that line, Requirements maybe as the earlier items (Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type, Schedule Notes). But those are more job details not requirements. However the instruction says we can use Requirements for any list of duties/requirements/benefits. So we could put the earlier items under Requirements? But they are not requirements; they are job specifics. Might be better to put them under About the role. Thus we have: - About the role: location, specialty, discipline, start date, duration, hours, shift, employment type, schedule notes. - Requirements: maybe none explicit besides license and experience? But those are under Skills. Hmm. We could treat Requirements as the license and experience items (BLS, RN License, CNOR preferred, 1 year experience). But those are also under Skills. To avoid duplication, we could put those under Requirements and omit Skills. But then we lose the explicit "Skills:" heading but content is same. The instruction: "Prefer a few substantive sections over many thin ones." So better to have one section for license/experience/education maybe called Requirements or Qualifications. But we have separate Qualifications for education. Thus we could have: - About the role: job details (location, specialty, discipline, start date, duration, hours, shift, employment type, schedule notes). - Requirements: BLS - Required; RN License - Required; CNOR - Preferred; 1 year experience. - Qualifications: Graduate of an accredited School of Nursing; Associates or Bachelor's Degree - Preferred. - Skills: maybe omit as duplicate. - Schedule: maybe we already put schedule details in About the role (shift, hours, start date, duration, schedule notes). Could create Schedule section with those details instead. But then About the role would lose schedule info. Which is better? The instruction: "Prefer a few substantive sections over many thin ones." Having both About the role and Schedule may be thin if we split. Better to keep schedule info within About the role or create Schedule section and keep About the role shorter. Let's decide: We'll create sections: About the role (location, specialty, discipline, employment type). Requirements (license, experience). Qualifications (education). Schedule (shift, hours, start date, duration, schedule notes). Skills omitted. Check if any content left out: The "Skills:" line content is now under Requirements. That's okay. Now we need to ensure we don't include boilerplate like "About Talent4Health" etc. That's company description; not required sections. Could we put that under About the role? It's about the company, not the role. The instruction says we should not include boilerplate like navigation/legal/EEO/equal-opportunity/scam-warning. Company description might be considered boilerplate but it's substantive about the agency. However the sections we have are about the role, requirements, qualifications, schedule. The company description is not requested in headings list; we could omit it as it's not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description is not explicitly listed as boilerplate, but it's not part of the job posting details we need to preserve? The instruction says "Preserve ALL substantive information". The company description is substantive info about the employer. However we have no heading for "About the company". Could we include it under About the role? That might be misleading. But we could add a paragraph under About the role that includes company info? The heading "About the role" is for the role, not company. But we could still include it as prose under that heading; it's not incorrect but might be odd. However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not strict that we must only use those headings for those exact meanings. It says use those headings for section headings. So we should only use those headings. If we put company description under About the role, it's still using that heading. It's not prohibited. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role to avoid extra section. Thus About the role will include: location, specialty, discipline, employment type, plus company description (Talent4Health info). That's substantive. Now we need to ensure we don't include duplicated lines. The posting had duplicate lines? Not really. Now produce HTML:

  About the role

  Travel nurse RN position in Summit, New Jersey for the Operating Room (OR) specialty. Employed through Talent4Health, a healthcare recruitment agency based in Wilmington, DE that provides talent solutions nationwide.

  Maybe also include employment type Travel. Better to incorporate all details. Let's craft:

  Travel nurse RN position in Summit, New Jersey for the Operating Room (OR) specialty. Employment type: Travel. Talent4Health, based in Wilmington, DE, is a leader and innovator offering comprehensive talent solutions for the healthcare industry across the nation, with over 3000 clinicians placed in top facilities across 50 states.

  That's good. Now Requirements:

  Requirements

  • 1 year of experience
  • BLS certification – Required
  • RN license – Required