Jobs · Healthcare · Ohio

Travel Registered Respiratory Therapist - Critical Care - $1,986 per week

Slate Healthcare · Columbus, OH · 1 wk ago
On-siteHealthcareInternship
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, identify the sections: - About the role / Description - Requirements - Highlights (could be Benefits or part of description) - About Slate Healthcare (company info) Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use
  • for lists - Use

    for prose - Do NOT repeat job title as heading - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when real, specific content — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, parse the posting: Job title: "Slate Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Columbus, Ohio." - This is the title, but page already shows it, so don't repeat as heading. Job Description & Requirements section includes: - Specialty: Registered Respiratory Therapist - Discipline: Allied Health Professional - Start Date: 11/30/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel Description: "This Registered Respiratory Therapist position involves working night shifts with a focus on critical care. The role includes managing respiratory therapy for adult and geriatric patients in a large academic medical center. You will be responsible for providing care, conducting assessments, and collaborating with the healthcare team to ensure optimal patient outcomes. The position requires a commitment to quality care and the ability to adapt in a dynamic environment." Highlights: - Night Shift: 3x12 hours - Competitive pay and supportive workplace - Collaborative environment in a large academic center - Vibrant city life in Columbus, OH - Focus on critical care for adults and geriatrics Requirements: - Minimum experience required: 0 years - EMR System: not specified - Slate Healthcare Job ID #de4086eb-5c34-4303-a294-21633cdb8ee9. - Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. About Slate Healthcare: company description. Now, decide sections: 1. About the role (or Description) - include the description prose and maybe the highlights? Highlights could be a list under Benefits or separate. But the rule: include section only when real specific content. Highlights are specific: night shift schedule, competitive pay, collaborative environment, vibrant city, focus on critical care. Could be a "Highlights" section or "Benefits". The posting calls it "Highlights". I'll use "Highlights" as a heading? The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Highlights" not in list, but we can use "Benefits" if they are benefits. However, "Night Shift: 3x12 hours" is schedule info. "Competitive pay" is pay. "Collaborative environment" is culture. "Vibrant city life" is location perk. "Focus on critical care" is role focus. Might be better to fold into "About the role" or create a "Benefits" section. But the rule: never create Benefits section unless posting actually states them. The posting has a "Highlights" section with bullet points. That's substantive. I'll create a "Highlights" heading? The allowed headings list is not exhaustive; it says "e.g." So we can use other headings if appropriate. But the instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. However, to be safe, I'll map Highlights to "Benefits" or "Schedule"? Actually, "Night Shift: 3x12 hours" is schedule. "Competitive pay" is pay. But they are mixed. I think a "Highlights" section is fine as it's in the posting. But the instruction says "use

    for section headings (e.g. ...)" meaning those are examples. I'll use "Highlights" as a heading. But the rule: "include a section ONLY when the posting has real, specific content for it". The posting has a Highlights section with specific bullets. So include. 2. Requirements: includes minimum experience, EMR system (not specified), Job ID, pay package details. The Job ID is minor metadata, fold into a short

    or drop. The pay package details: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's pay info. Could create a Pay section? The posting doesn't have a separate Pay section, but it's in Requirements. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay package details in Requirements. But it's not a separate Pay section. However, we could extract pay info into a Pay section if it's substantive. But the pay info is vague: "tax-free stipend amount to be determined." That's placeholder. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT create a Pay section because the pay is not specified (amount to be determined). Similarly, Schedule: we have shift details (12 hours, nights, 36 hours per week). That's specific. Could create a Schedule section. But the posting includes shift info in the initial metadata. The rule: include section only when real specific content. Schedule info is specific: 12-hour nights, 36 hours/week, 3x12. That's substantive. But the posting also has "Highlights" with "Night Shift: 3x12 hours". Might be duplication. Better to structure: - About the role: description prose. - Schedule: shift details (12-hour nights, 36 hours/week, 13 weeks duration, start date). But start date and duration are also metadata. Could include in About the role or Schedule. - Requirements: minimum experience, EMR system (not specified - but "not specified" is placeholder, so maybe omit EMR line or include as "EMR System: Not specified"? The rule: never emit filler/placeholder text. So if EMR System is not specified, we should not include it. But the posting says "EMR System: not specified". That's placeholder. So we should drop that line. Minimum experience required: 0 years - that's specific (0 years). Keep. - Highlights: list of highlights. - About Slate Healthcare: company description. Also, the initial metadata: Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type. These are details about the role. Could be in About the role or a separate "Position Details" section. But the allowed headings don't include "Position Details". Could fold into About the role as a list. Let's decide on sections: 1. About the role: include description prose and maybe a list of key details (specialty, discipline, start date, duration, hours, shift, employment type). But the rule: use

    • for any list of duties/requirements/benefits. The metadata is not duties/requirements/benefits. Could be a list of position details. I'll include as a list under About the role. 2. Schedule: maybe separate? But the shift details are already in metadata. The Highlights also mention night shift. To avoid duplication, I'll put schedule details in About the role. 3. Requirements: minimum experience (0 years). That's it. EMR not specified - drop. Job ID - drop or fold into a short p. Pay package details - placeholder, drop. 4. Highlights: list of highlights. 5. About Slate Healthcare: company description. Now, ensure no boilerplate: The posting includes "Slate Healthcare Job ID #de4086eb-5c34-4303-a294-21633cdb8ee9." That's minor metadata, fold into a short

      or drop. I'll drop it. Pay package line: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is placeholder (amount to be determined). So drop. Now, write HTML. Structure:

      About the role

      This Registered Respiratory Therapist position involves working night shifts with a focus on critical care. The role includes managing respiratory therapy for adult and geriatric patients in a large academic medical center. You will be responsible for providing care, conducting assessments, and collaborating with the healthcare team to ensure optimal patient outcomes. The position requires a commitment to quality care and the ability to adapt in a dynamic environment.

      • Specialty: Registered Respiratory Therapist
      • Discipline: Allied Health Professional
      • Start Date: 11/30/2026
      • Duration: 13 weeks
      • Hours per week: 36
      • Shift: 12 hours, nights
      • Employment Type: Travel

      Requirements

      • Minimum experience required: 0 years

      Highlights

      • Night Shift: 3x12 hours
      • Competitive pay and supportive workplace
      • Collaborative environment in a large academic center
      • Vibrant city life in Columbus, OH
      • Focus on critical care for adults and geriatrics

      About Slate Healthcare

      Slate Healthcare is a premier travel healthcare staffing agency, connecting healthcare professionals with thousands of opportunities at top-tier hospitals and facilities across the country.

      We’re committed to supporting nurses and allied health professionals in building stable, fulfilling careers—while embracing the freedom and excitement that comes with travel. Our goal is simple: to offer flexibility, competitive pay, and personalized placements that align with each clinician’s lifestyle and career goals.

      At Slate, we empower our professionals to choose when and where they work, while ensuring they receive the highest compensation possible—because we believe that exceptional care starts with empowered caregivers.

      Check rules: - No job title heading. - No Job ID heading. - No Pay/Schedule/Benefits sections unless stated. We have Highlights (not in list but okay). We have Requirements, About the role, About Slate Healthcare. - No filler text: we omitted EMR not specified, pay package TBD. - All substantive info preserved. - Used
      • for lists,

        for prose. - No markdown fences. Output only HTML fragment. Let's

Similar jobs