Travel Respiratory Therapist - $2,259 per week

We need to output HTML fragment with sections only if content exists. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. Job posting: "Stability Healthcare is seeking a travel Respiratory Therapist for a travel job in Denver, Colorado." Then "Job Description & Requirements Specialty: Respiratory Therapist Discipline: Allied Health Professional Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel" Then "Stability Healthcare is looking for a Registered Respiratory Therapist Allied contract position in Denver, CO. Responsible for monitoring and treating patients with temporary or chronic respiratory conditions like asthma, COPD, pneumonia, bronchitis or emphysema. Patients range from premature infants with undeveloped lungs to elderly patients who have diseased lungs 2 years of experience required*$600 travel bonus *Day 1 health insurance with United Healthcare *PTO plan -- start accruing on day 1, use during contract or cash out at the end! *Guaranteed stipend if facility calls you off *Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours" Then "Stability Healthcare Job ID #879425. 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: Registered Respiratory Therapist" Then "About Stability Healthcare Stability Healthcare was founded in 2009, with the mission of becoming the best Travel Nursing Agency in California. We have been rated one of the top travel nursing agencies and offer our nurses the highest paying travel nursing jobs available. We have access to the best travel assignments from 1000’s of facilities. You can start the year off in sunny California, spend the Spring in the Colorado Rockies, enjoy the Summer in the Mid-West, experience the change of seasons in Boston and New York, and hit the beaches of Florida in the winter. Our Nurses work in the best hospitals and health systems in the country." Then "Benefits Guaranteed Hours Benefits start day 1" We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to include sections only if real specific content. Let's identify sections: - About the role: Could be description of role: "Stability Healthcare is seeking a travel Respiratory Therapist for a travel job in Denver, Colorado." plus maybe "Stability Healthcare is looking for a Registered Respiratory Therapist Allied contract position in Denver, CO. Responsible for monitoring and treating patients..." That's role description. - Responsibilities: The duties: "Responsible for monitoring and treating patients with temporary or chronic respiratory conditions like asthma, COPD, pneumonia, bronchitis or emphysema. Patients range from premature infants with undeveloped lungs to elderly patients who have diseased lungs". Could also include other duties? Not explicit. - Requirements: "2 years of experience required". Also maybe "Registered Respiratory Therapist". Also "Allied Health Professional". Also "Specialty: Respiratory Therapist". Also "Discipline: Allied Health Professional". Also "Duration: 13 weeks", "36 hours per week", "Shift: 12 hours, nights", "Employment Type: Travel". Those could be under Requirements or maybe Schedule? But schedule is shift and hours. - Qualifications: maybe "Registered Respiratory Therapist". Could be same as requirements. - Skills: Not explicit. - Benefits: list: "$600 travel bonus", "Day 1 health insurance with United Healthcare", "PTO plan -- start accruing on day 1, use during contract or cash out at the end!", "Guaranteed stipend if facility calls you off", "Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours", "Guaranteed Hours", "Benefits start day 1". Also maybe "tax-free stipend amount to be determined" but that's pay. - 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." Also maybe "$600 travel bonus" is benefit not pay. Pay specifics not given exact rate. 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 vague; we should not create Pay section if content is just placeholder like "subject to confirmation" and "tax-free stipend amount to be determined". The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "subject to confirmation" and "tax-free stipend amount to be determined". That's placeholder. So we should NOT create a Pay section. - Schedule: we have shift details: "12 hours, nights", "36 hours per week". That's specific. So we can create Schedule section with those details. - Benefits: we have concrete benefits: $600 travel bonus, Day 1 health insurance with United Healthcare, PTO plan, Guaranteed stipend if facility calls you off, Extra hour bonus, Guaranteed Hours, Benefits start day 1. Those are specific. So Benefits section. - About the role: we have description. - Responsibilities: we have duties. - Requirements: we have 2 years experience required, maybe also Registered Respiratory Therapist, Allied Health Professional, Specialty, Discipline. Those are requirements. - Qualifications: maybe same as requirements; but we could combine. The instruction: prefer few substantive sections over many thin ones. So we could merge Requirements and Qualifications into one section? But headings are predefined; we could choose to include only those with substantive content. Could combine Requirements and Qualifications into one? But we must use headings exactly as given if we include them. We could decide to include Requirements and not Qualifications if content overlaps. Or include both but risk thin. Better to include Requirements (covers experience, specialty, discipline) and maybe Qualifications not needed. - Skills: none. - Pay: skip. - Schedule: include. - Benefits: include. - About the role: include. Now we need to format: 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 precisely. About the role prose: Could combine two sentences: "Stability Healthcare is seeking a travel Respiratory Therapist for a travel job in Denver, Colorado." and "Stability Healthcare is looking for a Registered Respiratory Therapist Allied contract position in Denver, CO." Might be redundant but both are substantive. We'll keep both as prose. Responsibilities: "Responsible for monitoring and treating patients with temporary or chronic respiratory conditions like asthma, COPD, pneumonia, bronchitis or emphysema. Patients range from premature infants with undeveloped lungs to elderly patients who have diseased lungs". That's prose; could be a

  . Requirements: list items: "2 years of experience required", "Registered Respiratory Therapist", "Allied Health Professional", "Specialty: Respiratory Therapist", "Discipline: Allied Health Professional", "Duration: 13 weeks", "36 hours per week", "Shift: 12 hours, nights", "Employment Type: Travel". Some of these are more like job details; but we can list them as requirements. But note: "Duration: 13 weeks", "36 hours per week", "Shift: 12 hours, nights", "Employment Type: Travel" could also go under Schedule? However schedule is about shift pattern and hours; duration is length of contract. Could be separate but we don't have a heading for Duration. Could put under Requirements as well. We need to avoid duplication: The shift and hours also appear in Schedule section; we might list them there only. But we need to preserve all info; if we put them only under Schedule, that's fine. However the requirement list may also include them; but we can avoid duplication by not repeating. Let's decide: Schedule section will contain shift and weekly hours. Requirements will contain experience, specialty, discipline, employment type, duration. That seems reasonable. Thus Requirements list: "2 years of experience required", "Registered Respiratory Therapist", "Allied Health Professional", "Specialty: Respiratory Therapist", "Discipline: Allied Health Professional", "Employment Type: Travel", "Duration: 13 weeks". That's specific. Benefits list: "$600 travel bonus", "Day 1 health insurance with United Healthcare", "PTO plan -- start accruing on day 1, use during contract or cash out at the end!", "Guaranteed stipend if facility calls you off", "Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours", "Guaranteed Hours", "Benefits start day 1". Also maybe "tax-free stipend amount to be determined" is placeholder; we skip. Schedule: "Shift: 12 hours, nights", "36 hours per week". Could also mention "12 hour shifts". We'll list as items. Now we need to output HTML fragment only. Structure:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  • ...
  ...

  Benefits

  ...

  Schedule

  ...
  We must not include empty sections. Check for any other sections: Qualifications maybe not needed. Skills none. Pay omitted. Now ensure we preserve all substantive info: Did we miss any? The posting also mentions "Stability Healthcare Job ID #879425." That's minor metadata; we can drop per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. We can drop it. Also "Posted job title: Registered Respiratory Therapist" - that's basically same as role; we can drop. Also "About Stability Healthcare" paragraph about company history; that's not about the role but about the company. Could be considered "About the company" but we have no heading for that. The instruction: we should not repeat job title as heading; but we can include company info maybe under About the role? Not exactly. The instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid adding other headings not listed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The examples are given but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add a heading for company description. Should we include that prose somewhere? It's substantive but not about the role. Could we fold it into About the role? Might be okay to include as extra paragraph under About the role? But it's about the company, not the role. However the instruction says "Preserve ALL substantive information". If we omit company info, we lose substantive info. But maybe it's considered boilerplate? It's not cookie/navigation/legal/EEO; it's about the company. Might be considered relevant. However there is no appropriate heading; we could put it under About the role as extra paragraph, but that might misrepresent. However the instruction says "Prefer a few substantive sections over many thin ones." Could we add a section "About the company"? Not in list. Might be disallowed. Perhaps we can drop it