Travel Speech Language Pathologist - $2,374 per week

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. We need to parse the posting. Content: - Host Healthcare is seeking a travel Speech Language Pathologist for a travel job in Broken Arrow, Oklahoma. - Job Description & Requirements - Specialty: Speech Language Pathologist - Discipline: Therapy - Start Date: 10/05/2026 - Duration: 13 weeks - 40 hours per week - Shift: 8 hours, days - Employment Type: Travel - Host Healthcare Job ID #a1fVX0000043ARxYAM. - Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: Speech Therapist About Host Healthcare paragraph. 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 like EEO etc. Not present. We need to produce sections: - About the role: maybe description of role: travel Speech Language Pathologist in Broken Arrow, Oklahoma. Could include specialty, discipline, start date, duration, hours, shift, employment type. - Responsibilities: Not explicitly given. The posting does not list responsibilities. So we should not create a Responsibilities section if no specific content. - Requirements: Not explicitly given. Could infer from specialty? But we should not invent. The posting does not list specific requirements like licensure, experience. So we should not create Requirements. - Qualifications: Not given. - Skills: Not given. - Benefits: we have list. - Pay: we have mention: Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's vague but it's specific content about pay. It says based on 8 hour shifts and 40 hours per week, tax-free stipend amount to be determined. That's not a specific number but it's still content. According to instruction: do NOT 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." That's placeholder. Also "subject to confirmation". This may be considered filler. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's still stating something, albeit vague. But the instruction says avoid filler like "not specified", "varies", "TBD". "tax-free stipend amount to be determined" is similar to TBD. Might be considered filler. Safer to omit Pay section if it's just placeholder. However we could include Pay section with the statement as is? The instruction 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 essentially TBD. So we should not create Pay section. - Schedule: we have Shift: 8 hours, days; 40 hours per week. That's specific. So we can create Schedule section with that info. - Benefits: we have list, so include Benefits section. - About the role: we have description: travel Speech Language Pathologist in Broken Arrow, Oklahoma. Also specialty, discipline, start date, duration, employment type. That's substantive. Thus sections: About the role, Benefits, Schedule. We need to 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. We need to remove cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. Not put Job ID as heading. We need to fold minor metadata into a short

  or drop it. Job ID maybe minor metadata; we can drop it or include in a paragraph. We need to output only HTML fragment. Let's craft:

  About the role

  Host Healthcare is seeking a travel Speech Language Pathologist for a travel assignment in Broken Arrow, Oklahoma. Specialty: Speech Language Pathologist. Discipline: Therapy. Start date: October 5, 2026. Duration: 13 weeks. Employment type: Travel.

  We could also include 40 hours per week, shift 8 hours, days but that goes to Schedule. Benefits: list.

  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
  Schedule:

  Schedule

  40 hours per week, 8‑hour day shifts.

  We might also include shift details: "Shift: 8 hours, days". Already captured. We should not include Pay section. Check for any other specifics: Posted job title: Speech Therapist (maybe redundant). Not needed. We should not include the start date as "10/05/2026" but we wrote "October 5, 2026". That's fine. We need to preserve all substantive information: we have start date, duration, specialty, discipline, employment type, location, hours per week, shift, benefits list. We omitted the Job ID. That's minor metadata; we can drop. We omitted "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Since it's placeholder, we omitted. Check if any other specifics: "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." This is part of About Host Healthcare paragraph. We might incorporate that into About the role or a separate section? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have About the role covering the role description, and we could also have a section about Host Healthcare? Not listed as allowed headings. The allowed headings are those specific ones. So we should not create a heading like "About Host Healthcare". We should incorporate that descriptive text into About the role maybe as prose. The About the role section can include details about the employer and benefits? But we already have Benefits separate. The description about Host Healthcare's mission etc is not strictly about the role but could be considered part of About the role. However we must not invent sections. We can include that prose inside About the role

  . That would preserve all substantive information. Thus About the role paragraph could be longer: include the mission, benefits overview, etc. But we already have Benefits section listing specific benefits. The paragraph about Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on-staff clinicians is also benefits but more descriptive. We could keep them in About the role or we could add them to Benefits as list items? They are not in the bullet list. The bullet list includes many benefits but not those specifics. To preserve all substantive info, we should include them somewhere. Could add them as additional list items under Benefits. Or we could include a paragraph in About the role describing the support. Since Benefits section already exists, we could add those as list items as well. Let's extract: "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." We can turn these into list items: Day 1 medical (continues up to 30 days between assignments), 401K matching, travel reimbursements, dedicated housing support, 24/7 support, access to on-staff clinicians. Add them to Benefits list. Thus Benefits list will be longer. Now ensure we don't duplicate items already listed: we have "401k retirement plan" (lowercase). The text says "401K matching". That's similar but not exactly same; we can keep both or merge. To avoid duplication, we could keep "401k retirement plan" and also note matching? But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we have both "401k retirement plan" and "401K matching", they are slightly different but both are substantive. We could keep both as separate list items. However that may be redundant but it's preserving detail. It's okay. Similarly "dedicated housing support" vs "Company provided housing options". Those are similar but not identical; we can keep both. "travel reimbursements" vs "Mileage reimbursement". Keep both. "Day 1 medical that continues up to 30 days between assignments" vs "Medical benefits". Keep both. "24/7 support from our team" vs maybe not in list; add. "access to our on-staff clinicians" add. Thus Benefits list will be comprehensive. Now About the role paragraph: we can include location, specialty, discipline, start date, duration, employment type, and maybe a brief description of Host Healthcare's mission? But we already captured mission details in Benefits. The About the role could focus on the role itself: travel Speech Language Pathologist in Broken Arrow, Oklahoma. Provide specialty, discipline, start date, duration, employment type. That's enough. We should not repeat the job title as heading. Now Schedule: we have "40 hours per week, 8‑hour day shifts." Also maybe mention shift: days. Now check for any other specifics: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." We omitted as placeholder. Good. Now ensure we didn't include any boilerplate like EEO etc. Not present. Now output HTML fragment. Let's craft:

  About the role

  Host Healthcare is seeking a travel Speech Language Pathologist for a travel assignment in Broken Arrow, Oklahoma. Specialty: Speech Language Pathologist. Discipline: Therapy. Start date: October 5, 2026. Duration: 13 weeks. Employment type: Travel.

  Benefits

  • Referral bonus
  • School loan reimburs