Travel Med Surg Tele RN - $2,016 per week

We need to output HTML fragment with sections only where content exists. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID as heading. We must remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. We need to preserve all substantive info. Let's parse the posting: - Title: Reliant Staffing Partners is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Greensboro, North Carolina. - Job Description & Requirements - Specialty: Med Surg / Telemetry - Discipline: RN - Start Date: ASAP - Duration: 9 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Shift: 3x12s, Days, 7a-730p - Requirements: Minimum 2 years experience required, FIRST TIME TRAVELERS - OK! *BLS required *Traveler will be required to pass an EKG exam during onboarding. EPIC *Previous Charge RN exp preferred. - Reliant Staffing Partners Job ID #29910. - Pay package is 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 (company description) - Then list of 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. - Contact us: info@reliantstaffingsolutions.com (should we include? It's contact info, maybe not boilerplate but it's contact. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Contact info is not explicitly prohibited. However, it's not a section heading; we could include as a

maybe. But they said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include Job ID in a short

. Contact info maybe also as

. But we need to decide if we include contact. It's not prohibited. It's not boilerplate. It's contact. Could be included as a

. However, they said "Output ONLY the HTML fragment — no /, no markdown code fences." So we can include

for contact. Now we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real specific content. - About the role: Could include description of role: travel nurse RN Med Surg / Telemetry in Greensboro, NC. Start date ASAP, duration 9 weeks, 36 hrs/week, shift 12h days, employment type travel, shift 3x12s days 7a-7:30p. That seems like role details. So we can put that under About the role. - Responsibilities: Not explicitly listed. The posting doesn't list duties. So we should not create Responsibilities section if no specific content. So skip. - Requirements: We have: Minimum 2 years experience required, FIRST TIME TRAVELERS - OK! BLS required, Traveler will be required to pass an EKG exam during onboarding. EPIC, Previous Charge RN exp preferred. That's requirements. So we can have Requirements section. - Qualifications: Could overlap with requirements; but we might not have separate qualifications beyond requirements. Could combine? The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they are separate headings allowed. However, we should not create a heading if content is thin or placeholder. We have specific requirements; we could put them under Requirements. Qualifications could be omitted if no distinct content. So we skip Qualifications. - Skills: Not explicitly listed; maybe EPIC is a skill, but it's already in requirements. Could include under Requirements. So skip Skills. - Benefits: We have a list of benefits. So we can have Benefits section. - Pay: We have "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat vague but it's actual statement about pay. It's not placeholder like "commensurate with experience". It says based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. That's substantive enough? It mentions basis and stipend. It's not "TBD" exactly but says amount to be determined. Might be considered placeholder? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . Here it says "tax-free stipend amount to be determined." That's similar to TBD. Might be considered placeholder. However, they also say "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation)". That's some detail. I'd argue it's still substantive enough to include Pay section. But we need to be careful: they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on shifts and stipend. So we can include. - Schedule: We have shift details: 12 hours, days; 3x12s, Days, 7a-730p. That's schedule. So we can include Schedule section. Now we need to format. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive info. Let's craft:

  About the role

  Reliant Staffing Partners is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Greensboro, North Carolina. Start date: ASAP. Duration: 9 weeks. Hours: 36 per week. Shift: 12‑hour days (3×12s, 7 a.m.–7:30 p.m.). Employment type: Travel.

  That includes location, start date, duration, hours, shift, employment type. Now Requirements:

  Requirements

  • Minimum 2 years of RN experience required (first‑time travelers accepted)
  • BLS certification required
  • Must pass an EKG exam during onboarding
  • EPIC experience required
  • Previous Charge RN experience preferred
  Now Benefits:

  Benefits

  • 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
  Now Pay:

  Pay

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

  Now Schedule:

  Schedule

  Shift: 12‑hour days, 3×12s, 7 a.m.–7:30 p.m.

  We might also include contact info as a

  at the end, but not required. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include Job ID in a short

  . Also contact info. But we need to decide if we include them. They are minor metadata. Could fold into a short

  . Let's add a

  for Job ID and contact. But we must not create extra sections for them. Just a

  . Add after schedule maybe:

  Job ID #29910. Contact: info@reliantstaffingsolutions.com

  Now ensure we didn't include any boilerplate like "About Reliant Staffing Partners" description. That is company description; is that substantive? It's about the company, not the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Should we include that? It's about the company, not the role. It's not boilerplate? It's a description of the staffing firm. It's not navigation/legal/EEO. It's substantive info about the employer. Should we include? Possibly yes, as it's part of the posting. However, we have no specific heading for "About the company". The allowed headings list does not include "About the company". But we could put it under "About the role"? That would be mixing. Better to add a

  after the sections describing the company. Since we are not required to have a heading for it, we can just include a

  with that info. But we need to check if that is considered boilerplate? It's a generic description of the company, but it's specific to Reliant Staffing Partners. It's not navigation or legal. It's okay to keep. Thus we add a

  with that description. Let's copy the company description: "Reliant Staffing Solutions – Connecting Healthcare Professionals NationwideSince 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.In addition, your compensation package includes the following options:" Wait that last sentence repeats benefits list; we already have benefits. The company description includes a sentence about compensation package includes the following options: then list. That duplicates benefits. We already have benefits list. To avoid duplication, we should not repeat the list. The instruction: "Remove duplicated lines". So we should not include that sentence that leads to benefits list again. We can include the company description up to before that sentence. Let's extract: "Reliant Staffing Solutions – Connecting Healthcare Professionals NationwideSince 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