We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting.
Job description: "Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Morgantown, West Virginia."
Then "Job Description & Requirements Specialty: Registered Respiratory Therapist Discipline: Allied Health Professional Start Date: 10/09/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel Host Healthcare Job ID #a1fVX0000043avtYAA. 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. Posted job title: Respiratory Therapist"
Then "About Host Healthcare" paragraph.
Then "Benefits" list: 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.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to not repeat job title as heading. So no heading for "Respiratory Therapist". We need to include sections with content.
We have details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Pay package info (based on 12 hour shifts and 36.0 hours per week, tax-free stipend amount to be determined). That's Pay and Schedule info.
We have About Host Healthcare paragraph (could be About the role? Actually "About Host Healthcare" is about company, not role. But we can treat as "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if appropriate.
We have job description: "Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Morgantown, West Virginia." That's about the role. Could be About the role.
Responsibilities: Not listed explicitly. No duties listed. So we should not create Responsibilities section if no specific content.
Requirements: Not listed explicitly besides specialty, discipline, maybe license? Not explicit. Could infer but we shouldn't invent. So skip.
Qualifications: Not listed.
Skills: Not listed.
Benefits: we have list.
Pay: we have "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 somewhat vague but it's specific about basis. It says tax-free stipend amount to be determined (unspecified). The instruction: 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. Should we include Pay section? The posting does state pay package based on 12 hour shifts and 36.0 hours per week, but stipend amount TBD. Might be considered placeholder. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 12 hour shifts and 36.0 hours per week. That's something. However the stipend amount TBD is placeholder. But we could still include Pay section with the known info: based on 12 hour shifts and 36.0 hours per week. That's substantive. The stipend amount TBD could be omitted? We must preserve ALL substantive information; do not invent or summarize away detail. We could include the sentence as is, even if contains TBD. But the instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That suggests we should not create a section if the only content is placeholder. But we have some substantive content: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's substantive. The stipend amount TBD is extra. Might be okay to include the whole sentence; it's not purely placeholder. I'd include Pay section.
Schedule: we have Shift: 12 hours, nights; 36 hours per week; Start Date: 10/09/2026; Duration: 13 weeks. That's schedule info. So Schedule section.
Benefits: we have list.
About the role: we have first sentence.
We could also include "About Host Healthcare" as maybe "About the company"? Not in allowed headings. Could we put under "About the role"? Might be stretching. But we could include a paragraph about Host Healthcare under "About the role" or maybe we could create a section "About Host Healthcare" but not allowed headings. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings. Likely we should only use those headings. So we should map content to those headings. The "About Host Healthcare" paragraph is about the company, not the role. Could fit under "About the role"? Not really. But we could treat it as "About the role" describing the employer? Might be acceptable. However we could also omit it if not fitting. But we must preserve ALL substantive information. So we need to include that info somewhere. If we don't have a proper heading, we could put it in a
without a heading? The instruction: Output ONLY the HTML fragment. It didn't say every piece must be under a heading. It says use headings for sections. We could have a
for prose not under a heading? Probably okay to have a leading
before sections. But they said use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having prose outside headings. So we can include a
for the Host Healthcare description, then sections.
Thus structure:
Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Morgantown, West Virginia.
About Host Healthcare: ... (the paragraph).
Then sections:
Benefits
Pay
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.
Schedule
Start Date: 10/09/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights.
We could also include Specialty, Discipline, Employment Type maybe under a section like "About the role"? But we already have that sentence. Could add more details in a
under About the role? Might be better to create a section "About the role" with those details. Let's think: The posting includes Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. Those are role specifics. So we could put them under About the role.
Thus:
About the role
Specialty: Registered Respiratory Therapist; Discipline: Allied Health Professional; Start Date: 10/09/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel.
Then we keep the initial sentence maybe redundant. Could combine. But we must preserve all info; we can include both but avoid duplication. The initial sentence is basically same as About the role. We could keep it as a
before heading, but that duplicates. Better to just have About the role section with that info, and not have a separate leading sentence. The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop the initial sentence if we include its content elsewhere. Let's include the details in About the role.
Thus final HTML:
About the role
Specialty: Registered Respiratory Therapist; Discipline: Allied Health Professional; Start Date: 10/09/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel.
Benefits
- 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
Pay
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.
Schedule
Start Date: 10/09/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel.
But note we duplicated Start Date etc in Schedule and About the role. That's duplication. We should avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but could be considered redundant. Better to not duplicate. We can put Start Date, Duration, Hours per week, Shift, Employment Type under Schedule, and About the role just specialty and discipline. Let's split.
About the role: Specialty and Discipline.
Schedule: Start Date, Duration, Hours per week, Shift, Employment Type.
Pay: as given.
Benefits: list.
Thus:
About the role
Specialty: Registered Respiratory Therapist; Discipline: Allied Health Professional.
Schedule
Start Date: 10/09/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel.
Pay
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.
Benefits
We should not include Responsibilities, Requirements, Qualifications, Skills as no content.
Check for any other info: "Posted job title: Respiratory Therapist" - we should not repeat job title as heading, but we could include it as minor metadata in a short
or drop it. Since we already have specialty, we could drop.
Now ensure no boilerplate. The benefits list includes items exactly as given