Travel Nurse RN - Med Surg / Telemetry - $2,812 per week

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to parse the job posting. Given text: "Reliant Staffing Partners is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Columbia, South Carolina. Job Description & Requirements Specialty: Med Surg / Telemetry Discipline: RN Start Date: 10/12/2026 Duration: 13 weeks 48 hours per week Shift: 12 hours, days Employment Type: Travel Day 4x12-Hour (07:00 - 19:30) 2 year MS/TELE EXP needed LTAC MS/TELE - NIGHT BLS / ACLS / NIH Required LTAC experience preferred ** NEURO EXP NEEDED *** Reliant Staffing Partners Job ID #29284. 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 [description...] In addition, your compensation package includes the following options: o Eligibility for health, vision and dental coverage o Telemedicine o Discounts on prescriptions o Simple IRA retirement plan o Life Insurance o Hospital Indemnity Insurance o Accident Insurance o Cancer Insurance o Working Advantage Program o LifeLock Identity Theft Protection o Sick Pay o Stipend Pay o Referral Pay Contact us: info@reliantstaffingsolutions.com" We need to remove boilerplate: contact us maybe considered minor metadata; we can drop or fold into short p. Also remove Job ID line? It says 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 p maybe. We need sections: About the role? The posting includes "Job Description & Requirements" but not separate sections. We can create sections: About the role (maybe from first paragraph?), Responsibilities (maybe not explicit), Requirements (list of qualifications), Qualifications (maybe same), Skills (maybe not), Benefits (list of compensation options), Pay (mention of pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined - but that is vague; we should not create Pay section unless posting actually states them. It says "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 specific but includes "subject to confirmation" and "amount to be determined". Might be considered not specific enough? 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. Here they state pay package based on 12 hour shifts and 36 hours per week, with tax-free stipend amount to be determined. The stipend amount is TBD, but they do give basis. Might be okay to include Pay section with that sentence. However they also say "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation)". That's somewhat vague but still states basis. I'd include Pay section with that sentence. Schedule: they give Shift: 12 hours, days; Day 4x12-Hour (07:00 - 19:30); also 48 hours per week earlier but then pay package based on 36 hours per week. There's some inconsistency. We have schedule info: Shift: 12 hours, days; Day 4x12-Hour (07:00 - 19:30). That's specific. So we can include Schedule section. Benefits: they list many options; we can include Benefits section with ul. Now we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: we could use the first paragraph describing the job: "Reliant Staffing Partners is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Columbia, South Carolina." plus maybe the Job Description & Requirements heading? But we should not repeat job title as heading. We can put a short paragraph about the role. - Responsibilities: The posting does not list specific duties/responsibilities beyond specialty etc. No explicit responsibilities. So we should not create Responsibilities section if no specific content. - Requirements: we have list: 2 year MS/TELE EXP needed, LTAC MS/TELE - NIGHT, BLS / ACLS / NIH Required, LTAC experience preferred, ** NEURO EXP NEEDED ***. Also Specialty, Discipline, Start Date, Duration, hours per week, shift, employment type. Those could be considered requirements. We'll put them in Requirements section as ul. - Qualifications: maybe similar to Requirements; but we could combine. However we should avoid thin sections. Perhaps we just have Requirements and Qualifications combined? But we need to follow instruction: prefer a few substantive sections over many thin ones. So we could have Requirements (includes qualifications) and Benefits, Pay, Schedule, About the role. That's four sections. - Skills: not explicitly listed; we could skip. - Benefits: we have list. - Pay: we have statement. - Schedule: we have shift details. Thus sections: About the role, Requirements, Benefits, Pay, Schedule. We need to use

for each section heading. Inside each section, use

for prose,

• for lists. We must not include markdown code fences. We must output only HTML fragment. Let's craft:

  About the role

  Reliant Staffing Partners is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Columbia, South Carolina.

  Requirements

  • Specialty: Med Surg / Telemetry
  • Discipline: RN
  • Start Date: 10/12/2026
  • Duration: 13 weeks
  • 48 hours per week
  • Shift: 12 hours, days
  • Employment Type: Travel
  • Day 4x12-Hour (07:00 - 19:30)
  • 2 year MS/TELE experience needed
  • LTAC MS/TELE - NIGHT
  • BLS / ACLS / NIH required
  • LTAC experience preferred
  • Neuro experience needed
  Note: The original had "** NEURO EXP NEEDED ***" we can phrase as "Neuro experience needed".

  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

  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

  Shift: 12 hours, days; Day 4x12-Hour (07:00 - 19:30).

  We should also maybe include Job ID? It's minor metadata; we could fold into a short p after About the role or at end. But we can drop it. The instruction: fold minor metadata into a short

  or drop it. We can drop it. Check for any boilerplate: "About Reliant Staffing Partners" section we omitted because it's generic company description; we could consider it as "About the role"? Actually "About Reliant Staffing Partners" is about the company, not the role. The instruction says use headings like About the role, Responsibilities, etc. So we should not include a section about the company unless it's about the role. The posting includes a paragraph about Reliant Staffing Solutions; that's boilerplate-ish but could be considered "About the role"? Not exactly. The instruction says "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." It didn't forbid including company description; but we should prefer substantive sections. The company description is generic; maybe we can include it as part of About the role? But the About the role heading is for role description, not company. However we could incorporate a short sentence about the company within About the role paragraph. But we already have a short paragraph about the role. We could add a sentence: "Reliant Staffing Partners connects healthcare professionals nationwide..." but that's from the company description. Might be okay. But we must preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's generic but still info. Should we preserve it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the company description info. However we also need to avoid thin sections. We could include a short paragraph under About the role that includes both role and company info. That would preserve it. Let's extract 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 about compensation package is actually part of the benefits list; we already captured benefits. The company description ends before "In addition, your compensation package includes the following options:" which is benefits. Thus we can incorporate the company description into About the role paragraph. Let's craft About the role paragraph:

  Reliant Staffing Partners is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Columbia, South Carolina. Reliant Staffing Solutions connects healthcare professionals nationwide, serving clients and candidates since 2016 with a full-cycle staffing approach focused on building lasting relationships and delivering support to help professionals achieve their goals.

  That preserves substance. Now ensure we didn't miss any other substantive info: The posting also had "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Already in Pay. We also had "48 hours per week