Travel Registered Respiratory Therapist - $2,110 per week

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. Rules: - Use

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

• for lists of duties/requirements/benefits, and

  for prose - Do NOT repeat the job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, let's parse the job posting: Job Title: Travel Respiratory Therapist - Registered RT/RRT (but we don't repeat as heading) Content sections: 1. Assignment Overview / Job Description & Requirements: includes specialty, discipline, start date, duration, hours per week, shift, employment type, shift details, hours, start date, length, openings. 2. Description: "American Traveler is seeking a Registered Respiratory Therapist (RRT) for a night shift position requiring 2+ years of experience and an active Ohio RRT license." 3. Details: Respiratory/Neuro Diagnostics unit at a hospital Main Campus, night shift schedule 3x12 hour shifts 19:00-7:30, weekend coverage as needed, may float to other facilities within health system as needed. 4. Requirements: list of requirements (minimum 2 years experience, active Ohio RRT license, NBRC certification, BLS certification, 1 year combined permanent experience in specialty for Ohio locations, two professional references from manager/ANM/supervisor/director within past 12 months, co-worker references not accepted) 5. Additional Information: Travelers expected to work every other holiday, RTO requests discussed during interview, facility smoke-free and nicotine-free, negative 10-panel drug screen including nicotine required within 12 months of start updated annually, COVID-19 vaccine required with medical/religious exemptions only, flu vaccine required with medical/religious exemptions only, background check findings reviewed, license hits not accepted, permanent and per diem candidates cannot return for 1 year from previous end date, local candidates accepted at same bill rate, first-time travelers not required. 6. Pay package info: "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 pay info but vague. The rule says never create Pay section unless posting actually states them. It states a pay package but with "tax-free stipend amount to be determined". That's not specific. Might be considered filler. But it does mention pay package based on shifts and hours. Could include a Pay section with that info? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package info, but it's not specific. However, it's substantive info about pay structure. I'll include a Pay section with that detail. 7. About American Traveler: company description, benefits offered (premium medical, dental, vision, life insurance day one, 401(k) match, housing stipends, 24/7 support, in-house clinicians). This is benefits info. Should include Benefits section. Also, there is Job ID #P-767620. That's minor metadata, fold into a short

  or drop. I'll include a brief meta paragraph at the end maybe. Now, decide on sections: - About the role (or Assignment Overview) - could combine description and details. - Responsibilities? The posting doesn't have explicit responsibilities list. It has details about unit and schedule. Might not have a Responsibilities section. - Requirements: definitely. - Qualifications? Could be same as requirements. But we have Requirements section. - Skills? Not explicitly listed. - Benefits: yes, from About American Traveler. - Pay: yes, from pay package info. - Schedule: shift details are in details. Could have a Schedule section. But rule: prefer a few substantive sections over many thin ones. Let's see. We have: - Assignment Overview (could be "About the Role") - Details (could be part of About the Role) - Requirements - Additional Information (could be "Additional Requirements" or "Other Information") - Pay - Benefits But we must not create sections with filler. Let's map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use: - About the role (for description and details) - Requirements (for requirements list) - Additional Information (maybe not a standard heading; but we can use "Qualifications" or "Other Requirements"? The rule says use h3 for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. "Additional Information" is not in the list. Could fold into Requirements or Qualifications. But Qualifications is similar to Requirements. Might combine. Better to have: - About the role - Requirements - Schedule (since shift details are specific) - Pay - Benefits But Schedule is not explicitly a heading in the list? It is: "Schedule" is in the example list. Yes, "Schedule" is allowed. Let's structure:

  About the role

  Description...

  • Details...

  Requirements

  • ...

  Schedule

  • Night shift, 3x12 hour shifts (19:00–7:30)
  • Weekend coverage as needed
  • May float to other facilities within the health system as needed

  Pay

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

  Benefits

  • Premium medical, dental, vision, and life insurance starting day one
  • Generous 401(k) match
  • Substantial housing stipends
  • 24/7 support and access to in-house clinicians
  Also include Additional Information items? They are important: holiday work, RTO, smoke-free, drug screen, vaccines, background check, return policy, local candidates, first-time travelers. These are not exactly requirements, but conditions. Could be under "Additional Information" but not a standard heading. Could fold into "Requirements" or "Qualifications". But Qualifications is allowed. Could make a "Qualifications" section for these? However, the rule says use h3 for section headings e.g. ... Qualifications. So we can use Qualifications for these additional conditions. But they are not qualifications per se. Might be better to include them in a "Additional Details" but not allowed. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so maybe we can use other headings? But it says "use

  for section headings (e.g. ...)" implying those are the typical ones. But we can use other headings if needed? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid others, but suggests those. However, we should prefer those. For additional info, maybe we can put under "Requirements" as additional requirements? Or create a "Qualifications" section. I think "Qualifications" could encompass the additional conditions. But the additional info includes things like "Travelers are expected to work every other holiday" which is a condition, not a qualification. Could be "Schedule" but not exactly. Might create a "Conditions" heading? Not in list. Better to include in "About the role" as prose? Or create a separate "Additional Information" heading? The rule says "include a section ONLY when the posting has real, specific content for it". It doesn't restrict heading names to only those examples. But the examples are given. I think it's safe to use "Additional Information" as a heading if needed. However, the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But to be safe, I'll use the provided ones where possible. Let's see: The additional info includes many specific details. Could be split: some are schedule-related (holiday work), some are compliance (drug screen, vaccines, background check), some are policy (return policy, local candidates). Could be under "Requirements" as additional requirements? But they are not requirements for the candidate's qualifications, but conditions of employment. Might be "Qualifications" but not exactly. Maybe we can have a "Compliance & Policies" but not in list. I think it's okay to have an "Additional Information" heading. The rule doesn't forbid it. But the instruction says "use

  for section headings (e.g. ...)". It doesn't say "only these". I'll include an "Additional Information" section. But the rule also says "Prefer a few substantive sections over many thin ones." So maybe combine additional info into "Requirements" or "About the role". However, they are distinct. Let's decide: I'll create sections: About the role, Requirements, Schedule, Pay, Benefits, Additional Information. But Additional Information is not in the example list. Might be okay. Alternatively, fold into "Requirements" as a subsection? But we can't have subsections with h3? We could use h3 for each. I'll include it. Now, also need to include the Job ID as a short p. Maybe at the end. Now, write HTML. First, About the role: combine description and details. Description: "American Traveler is seeking a Registered Respiratory Therapist (RRT) for a night shift position requiring 2+ years of experience and an active Ohio RRT license." Details: - Respiratory/Neuro Diagnostics unit at a hospital Main Campus - Night shift schedule with 3x12 hour shifts from 19:00 to 7:30 - Weekend coverage as needed - May float to other facilities within the health system as needed I'll put description as p, details as ul. Requirements: list from Requirements section. Additional Information: list from Additional Information. Schedule: could be separate, but details already include schedule. Might duplicate. Better to have Schedule section with shift details, and About the role with unit description. Let's separate: About the role: description and unit. Schedule: shift details, weekend, float. Requirements: requirements list. Additional Information: other conditions. Pay: pay package. Benefits: benefits list. That seems good. Now, write HTML. Note: The posting says "Start Date: 01/11/2027" and "Duration: 24 weeks" etc. That's metadata. Could include in About the role as a list. Let