Travel Cardiac Tele RN - $2,192 per week

We need to output HTML fragment with sections: About the role? The posting includes "Job Description & Requirements" and "About Reliant Staffing Partners". Also includes details: specialty, discipline, start date, duration, hours, shift, requirements, certifications, pay package info (though pay package is vague: based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined). According to rules: include a section only when posting has real, specific content for it. Pay: they mention pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined. That's not specific amount; it's vague. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. They state pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined. That's still stating something about pay (though amount TBD). It's still stating pay package exists. I'd include a Pay section with that info. Schedule: they give shift details: 36 hours per week, shift: 12 hours, nights, Night 3x12-Hour (19:00 - 07:00). That's specific schedule. So include Schedule section. Benefits: they list many benefits after "In addition, your compensation package includes the following options:" then a list. That's benefits. So include Benefits section. We need headings:

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. We should not repeat job title as heading. No Job ID as heading. We can include minor metadata in short

  or drop it. The Job ID can be dropped or placed in a short p. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need sections only when posting has real specific content. We have content for: About the role? The posting includes "Job Description & Requirements" which contains specialty, discipline, start date, duration, hours, shift. That could be considered "About the role". Could also be "Responsibilities" but not given. We'll use "About the role" heading for that descriptive info. We have Requirements: list of requirements (years of experience, EPIC experience, EKG tele competency, BLS, NIH required, ACLS preferred, ability to read strips, IV start, N95 fitting). We'll put under

  Requirements

  with
  . We have Certifications: ACLS, BLS, NIHSS. Could be part of Requirements or separate Qualifications. Since we have a Certifications line, we could include under Requirements or Qualifications. The instruction says use headings like Qualifications, Skills, etc. We could put Certifications under Qualifications. But we already have Requirements heading; we could combine. However we need to avoid thin sections. Maybe combine Certifications into Requirements list. That's fine. We have Benefits: list of options. We have Pay: mention pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined. We have Schedule: 36 hours per week, shift: 12 hours, nights, Night 3x12-Hour (19:00 - 07:00). We also have About Reliant Staffing Partners: that's company description; could be under "About the role"? Actually "About the role" is about the job, not company. Could add a section "About the company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No company about. So we might omit that or incorporate into About the role? But About the role should be about the job, not company. However we could still include a short paragraph about the company under About the role? Might be considered filler. Better to drop company description as it's not required heading; but we must preserve ALL substantive information. The company description is substantive? It's about the staffing agency, not the job. The instruction says preserve ALL substantive information; but we can drop boilerplate/navigation/legal/EEO etc. Is company description considered boilerplate? It's describing the staffing firm; might be considered relevant but not required heading. Since we cannot create a heading not in list, we could put it in a

  without heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid stray paragraphs without heading. It said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say you cannot have other headings, but likely they expect only those headings. Safer to include company description under a heading like "About the role"? Might be misrepresenting. However we could treat "About Reliant Staffing Partners" as "About the role"? Not accurate. Alternatively we could create a section "About the role" that includes both job details and a brief note about the staffing firm? Might be okay. But we need to preserve all substantive information; dropping company description might lose info. However the company description is generic fluff; maybe considered boilerplate? It's not legal/EEO but it's promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it. We could add a heading "About the role" and put the job details there, and then after that a

  about Reliant Staffing Partners. That would be okay: we keep the info. Let's structure:

  About the role

  Telemetry RN travel position in Troy, Ohio. Start date ASAP, duration 9 weeks, 36 hours per week, 12‑hour night shifts (Night 3x12‑Hour, 19:00‑07:00).

  Then Requirements:

  Requirements

  • 3 years of experience
  • EPIC experience
  • Pass an online EKG tele competency assessment before starting the assignment
  • BLS, NIH required; ACLS preferred
  • Ability to read and interpret strips
  • IV start
  • Nurses will be fitted for N95 prior to working on the HRRU unit unless PAPR is offered/needed
  • Certifications: ACLS, BLS, NIHSS
  But note we duplicated certifications; we can include as separate list item. 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.

  Schedule:

  Schedule

  36 hours per week, 12‑hour night shifts: Night 3x12‑Hour (19:00‑07:00).

  Benefits:

  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
  We should not include any fluff like "About Reliant Staffing Partners" description. We could add a short paragraph after Benefits maybe as a

  without heading. But we might drop it to avoid extra content not under a heading. However we need to preserve all substantive information; the company description is substantive but maybe considered boilerplate? It's not legal/EEO but it's promotional. The instruction didn't explicitly say to remove promotional fluff. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should keep it. We could add a heading "About the company"? Not allowed. But we could just add a

  after Benefits without heading. The instruction didn't forbid stray

  . It said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say you cannot have other elements. So we can add a

  describing the company. Thus final HTML:

  About the role

  Telemetry RN travel position in Troy, Ohio. Start date ASAP, duration 9 weeks, 36 hours per week, 12‑hour night shifts (Night 3x12‑Hour, 19:00‑07:00).

  Requirements

  • 3 years of experience
  • EPIC experience
  • Pass an online EKG tele competency assessment before starting the assignment
  • BLS, NIH required; ACLS preferred
  • Ability to read and interpret strips
  • IV start
  • Nurses will be fitted for N95 prior to working on the HRRU unit unless PAPR is offered/needed
  • Certifications: ACLS, BLS, NIHSS

  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.

  Schedule

  36 hours per week, 12‑hour night shifts: Night 3x12‑Hour (19:00‑07:00).

  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

  Reliant Staffing Solutions – Connecting Healthcare Professionals Nationwide. Since 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.

  We need to ensure no duplicated lines. Looks fine. Check that we didn't include Job ID. Good.