Travel Nurse RN - Cardiac Cath Lab - $3,450 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 as heading. Must not include Job ID as heading; can fold into short

. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. Let's parse the posting: - Reliant Staffing Partners is seeking a travel nurse RN Cardiac Cath Lab for a travel nursing job in Petoskey, Michigan. Job Description & Requirements: - Specialty: Cardiac Cath Lab - Discipline: RN - Start Date: 10/12/2026 - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, days - Employment Type: Travel - Shift: 4x10s Days - Requirement description: 2 years RN Cath Lab experience - [REQUIRED] - CERTIFICATION REQUIREMENTS: BLS (AHA), ACLS (AHA) - STATE LICENSE REQUIREMENTS: Michigan - ADDITIONAL LICENSE REQUIREMENTS: Active at time of Submission - Weekend Requirements: Weekend call is required Friday 1730-Monday 0700 - On Call Requirements: On call should be 1 night a week and typically every 4-6th weekend - Reliant Staffing Partners Job ID #29486. - Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. About Reliant Staffing Partners: description paragraph. 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 be removed? It's contact info; maybe we can keep as part of Benefits? It's not a benefit; but we can drop as boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Contact info might be considered application instructions? Not sure. Probably we can drop contact info as it's not substantive job info. But we could keep as a short p? The instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So contact info maybe minor metadata; we could drop. Safer to drop. We need to include sections only when posting has real specific content. Let's map: - About the role: Could include description of role: travel nurse RN Cardiac Cath Lab in Petoskey, Michigan; start date, duration, hours, shift, employment type. That's substantive. - Responsibilities: Not explicitly listed; we have weekend call, on call requirements. Those could be responsibilities. Also maybe "Weekend call is required Friday 1730-Monday 0700" and "On call should be 1 night a week and typically every 4-6th weekend". Those are responsibilities. So we can include Responsibilities section with those bullet points. - Requirements: includes 2 years RN Cath Lab experience, certifications BLS, ACLS, state license Michigan, additional license active at time of submission. That's requirements. - Qualifications: maybe overlapping with requirements; but we could combine? The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But we have separate headings allowed. However we should not create thin sections. Could we put all under Requirements? The posting includes "Requirement description" and "CERTIFICATION REQUIREMENTS" etc. That's all requirements. Qualifications maybe not separate. Could skip Qualifications. - Skills: Not explicitly listed; maybe we could infer but we shouldn't invent. So skip Skills. - Benefits: list of benefits given. So include Benefits section. - Pay: Pay package based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's specific enough? It mentions pay package based on shifts, tax-free stipend amount to be determined. It's not a specific number but it's still substantive. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined" which is TBD-like. Might be considered placeholder. However the pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation). That's somewhat vague but still some info. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's stating something, albeit not a specific number. I'd include Pay section with that sentence. - Schedule: The posting includes shift: 10 hours, days; 4x10s Days; 40 hours per week; weekend call; on call. So we have schedule info. So include Schedule section. Now we need to format with

headings,

• for lists,

  for prose. We must not repeat job title as heading. So we start with maybe

  About the role

  then a paragraph. Let's craft:

  About the role

  Reliant Staffing Partners is seeking a travel nurse RN for a Cardiac Cath Lab position in Petoskey, Michigan. The assignment starts October 12, 2026, lasts 13 weeks, requires 40 hours per week (10‑hour shifts, days) and is a travel employment type.

  That's good.

  Responsibilities

  • Weekend call required: Friday 1730 to Monday 0700.
  • On‑call responsibility: approximately one night per week, typically every 4‑6th weekend.

  Requirements

  • Minimum 2 years of RN experience in a Cardiac Cath Lab.
  • Current BLS (AHA) certification.
  • Current ACLS (AHA) certification.
  • Active Michigan RN license.
  • License must be active at time of submission.
  We could also include "Start Date: 10/12/2026" etc but that's in About the role. Now Benefits:

  Benefits

  • Eligibility for health, vision and dental coverage.
  • Telemedicine access.
  • 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

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

  Schedule:

  Schedule

  • 40 hours per week, consisting of four 10‑hour day shifts (4x10s).
  • Weekend call required Friday 1730–Monday 0700.
  • On‑call approximately one night per week, typically every 4‑6th weekend.
  We might have duplicated weekend call and on-call in Responsibilities and Schedule; but it's okay to have in both? Might be duplication. Could consolidate: maybe put weekend and on-call under Schedule only, and Responsibilities could be empty? But we need to avoid thin sections. Let's think: Responsibilities could include the weekend and on-call duties; Schedule could include shift pattern and hours. That's fine; not duplicate exactly same text but similar. We can keep both but maybe rephrase to avoid exact duplication. Responsibilities: "Weekend call required Friday 1730–Monday 0700." and "On‑call responsibility: approximately one night per week, typically every 4‑6th weekend." Schedule: "Standard schedule: four 10‑hour day shifts per week (4x10s), totaling 40 hours." plus maybe mention weekend/on-call again? Could keep schedule just about shift pattern; but we already have weekend/on-call in responsibilities. That's okay. Let's adjust Schedule to just the regular shift pattern. Schedule:
  • Four 10‑hour day shifts per week (4x10s), totaling 40 hours.
  Now we have no duplicate exact lines. Check for any other substantive info: Job ID we can drop or put in a short p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could add a short p at end:

  Job ID: 29486.

  but maybe better to drop as minor metadata. I'd drop. Contact info also drop. Now ensure we didn't include any boilerplate like "About Reliant Staffing Partners" description. That's actually substantive about the company; but we have no section for company description. Could we include under "About the role"? Already we have a paragraph about the role. The company description could be considered "About Reliant Staffing Partners" but not required. The instruction says use headings for sections like About the role, Responsibilities, etc. Not about the company. So we can omit the company description; it's not required to preserve all substantive information? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must preserve all substantive information. The company description is substantive info about the staffing firm. Should we preserve it? It's not about the job but about the employer. The instruction didn't say to exclude employer description. It said to use headings for sections like About the role, Responsibilities, etc. It didn't forbid adding a section like "About the company". But the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list "About the company". However we could incorporate the company description into About the role paragraph? Might be okay to add a short paragraph about the company under About the role? But About the role is supposed to be about the role, not the company. However we could add a separate

  after the role description that describes the company; but that would be without a heading, which is allowed as prose. The instruction: Use

  for prose. So we can add a paragraph describing Reliant Staffing Partners after the role paragraph, without a heading. That would preserve the info. Let's do that: After About the role paragraph, add a

  describing Reliant Staffing Partners. Now check for any other info: "Contact us: info@reliantstaffingsolutions.com" we drop. Now ensure we didn't include any filler like "subject to confirmation" is okay; it's not placeholder like TBD but indicates uncertainty. It's fine. Now output only HTML fragment. Let's craft final HTML:

  About the role

  Reliant Staffing