Travel Registered Respiratory Therapist - $1,739 per week

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. From posting: - Job description: "Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Jackson, Mississippi." That's about the role. - Job Description & Requirements: includes Specialty, Discipline, Start Date, Duration, 40 hours per week, Shift: 8 hours, nights, Employment Type: Travel, Host Healthcare Job ID #... (metadata). Pay package based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Benefits: list of benefits. - No explicit responsibilities list; maybe we can infer from description? Not given. So we should not create Responsibilities if no specific content. - Requirements: maybe specialty, discipline, start date, duration, shift, hours, employment type. Those are specifics. - Qualifications: maybe none explicit. - Skills: none explicit. - Benefits: we have list. - Pay: mention pay package based on 8 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's vague but still some content. However rule: do NOT include Pay section unless posting actually states them. It does state "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's still some content, albeit not specific numbers. It's not "not specified" but it's vague. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it's "tax-free stipend amount to be determined" which is TBD. So that is placeholder. So we should not include Pay section. - Schedule: we have shift: 8 hours, nights; 40 hours per week. That's specific. So we can include Schedule section. - Benefits: we have list. - About the role: we have description. - Requirements: we have specialty, discipline, start date, duration, hours, shift, employment type. We should not repeat job title as heading. So we will not have a heading for the job title. We need to output only HTML fragment, no /. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details: About the role: "Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Jackson, Mississippi." Also maybe include "Posted job title: RRT (Registered Respiratory Therapist) -Respiratory Therapist Respiratory Therapist Reg" but that's duplicate and maybe boilerplate. We can ignore as it's not substantive. Requirements: list: - Specialty: Registered Respiratory Therapist - Discipline: Allied Health Professional - Start Date: 10/12/2026 - Duration: 13 weeks - Hours: 40 hours per week - Shift: 8 hours, nights - Employment Type: Travel We could also include "Host Healthcare Job ID #a1fVX0000042p7NYAQ" but that's metadata; rule says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. We could include it in a short p under About the role or Requirements? Probably drop it as minor metadata. Benefits list: many items: - Referral bonus - School loan reimbursement - Vision benefits - Wellness and fitness programs - Company provided housing options - License and certification reimbursement - Life insurance - Medical benefits - Mileage reimbursement - Pet insurance - Discount program - Employee assistance programs - Guaranteed Hours - Health savings account - Holiday Pay - 401k retirement plan - Continuing Education - Dental benefits Also "Day 1 medical that continues up to 30 days between assignments" mentioned earlier in description of benefits. Also "401K matching", "travel reimbursements", "dedicated housing support", "24/7 support", "access to on-staff clinicians". Those are also benefits. We need to preserve all substantive information. So we should include those as well. Let's capture benefits from the paragraph: "During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment." Then the bullet list after "Benefits". So combine. Thus benefits list: - Day 1 medical that continues up to 30 days between assignments - 401K matching - Travel reimbursements - Dedicated housing support - 24/7 support from team - Access to on-staff clinicians - Referral bonus - School loan reimbursement - Vision benefits - Wellness and fitness programs - Company provided housing options - License and certification reimbursement - Life insurance - Medical benefits - Mileage reimbursement - Pet insurance - Discount program - Employee assistance programs - Guaranteed Hours - Health savings account - Holiday Pay - 401k retirement plan - Continuing Education - Dental benefits Note there may be duplication: "401K matching" and "401k retirement plan" both present; we keep both as they are distinct. Schedule: "40 hours per week", "Shift: 8 hours, nights". So we can put in a

  or

  . Since it's not a list of multiple items, we can use

  . Pay: we decided not to include because it's placeholder. Now we need to output HTML fragment with sections: About the role (

  About the role

  ), Requirements (

  Requirements

  ), Benefits (

  Benefits

  ), Schedule (

  Schedule

  ). Possibly also Qualifications? No specific content. Skills? No. We must not repeat job title as heading. Good. We need to preserve all substantive information: include start date, duration, etc. Let's craft:

  About the role

  Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Jackson, Mississippi.

  Requirements

  • Specialty: Registered Respiratory Therapist
  • Discipline: Allied Health Professional
  • Start Date: 10/12/2026
  • Duration: 13 weeks
  • 40 hours per week
  • Shift: 8 hours, nights
  • Employment Type: Travel

  Benefits

  • Day 1 medical that continues up to 30 days between assignments
  • 401K matching
  • Travel reimbursements
  • Dedicated housing support
  • 24/7 support from our team
  • Access to on-staff clinicians
  • Referral bonus
  • School loan reimbursement
  • Vision benefits
  • Wellness and fitness programs
  • Company provided housing options
  • License and certification reimbursement
  • Life insurance
  • Medical benefits
  • Mileage reimbursement
  • Pet insurance
  • Discount program
  • Employee assistance programs
  • Guaranteed Hours
  • Health savings account
  • Holiday Pay
  • 401k retirement plan
  • Continuing Education
  • Dental benefits

  Schedule

  40 hours per week, 8‑hour night shifts.

  Check for any missing info: The posting also mentions "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." We decided not to include Pay section because it's placeholder. However we could include a short p under About the role or Requirements? The rule says: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. For pay, it's not minor metadata; it's about compensation. But the rule also says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay, albeit vague. However the rule also says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is TBD. So that is placeholder. So we should not include Pay section. Could we include a short p about pay under About the role? That would be mixing pay info with about role; but the rule about sections is about headings. It didn't forbid including pay info in a paragraph elsewhere. However the instruction: "Prefer a few substantive sections over many thin ones." It didn't forbid including pay info in a paragraph. But we must preserve ALL substantive information. If we omit pay info entirely, we lose substantive info (though it's vague). The rule says preserve ALL substantive information; do NOT invent or summarize away detail. The pay info is substantive albeit vague. Should we include it? The rule about sections: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, albeit vague. So we could create a Pay section but we must avoid filler/placeholder text. The content includes "tax-free stipend amount to be determined" which is placeholder. If we include that as is, it's still placeholder text. The rule says never emit a heading followed by filler/placeholder text. So if we create a Pay section with that text, it's violating. Could we rephrase? Not allowed to invent or summarize away detail. We could include the exact sentence: "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That includes the placeholder phrase. That would be filler/placeholder text. The rule says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include that sentence in a paragraph; it's about headings followed by filler/placeholder text. If we put that sentence in a

  under a Pay heading, the heading is followed by that sentence which contains filler/placeholder text. That likely violates. Better to avoid Pay section altogether and maybe incorporate the non-placeholder part: "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation)" into a paragraph elsewhere, dropping the TBD part? But that would be summarizing away detail (removing the TBD part). That's not allowed because we must preserve ALL substantive information. The TBD part is substantive? It's stating that amount is to be determined; that's info. If we drop it, we lose that info. So we need to keep it somewhere. Maybe we can include a

  without a heading that contains the pay info. The rule about headings only applies to sections we create. We are not required to have a Pay heading. We can just include a paragraph about pay without a heading. The instruction: "Use

  for section headings (