Travel Physical Therapist - Home Health - $2,556 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. Let's parse the posting. Job description: "Healthcare Support is seeking a travel Physical Therapist for a travel job in Hawthorne, New York." Then "Job Description & Requirements Specialty: Physical Therapist Discipline: Therapy Start Date: 10/05/2026 Duration: 13 weeks 40 hours per week Shift: 8 hours Employment Type: Travel Healthcare Support Job ID #522583. 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: physical therapist (pt)" Then About Healthcare Support paragraph. Then Benefits list: License and certification reimbursement Medical benefits Dental benefits Mileage reimbursement Employee assistance programs Referral bonus 401k retirement plan Holiday Pay Weekly pay We need to avoid boilerplate: remove navigation, legal, EEO, etc. The posting includes no explicit responsibilities or requirements beyond specialty, discipline, start date, duration, hours, shift, employment type. Those could be considered "Requirements" or "Qualifications". The posting does not list duties/responsibilities explicitly. So we may have sections: About the role (maybe a short paragraph describing the role), Requirements (specialty, discipline, start date, duration, hours, shift, employment type), Benefits (list), Pay (mention of pay package based on 8 hour shifts and 40 hours per week, tax-free stipend amount TBD - but we should not include Pay section if content is vague like "tax-free stipend amount to be determined" and "based on 8 hour shifts and 40.0 hours per week (subject to confirmation)". The rule: never create Pay/Schedule/Benefits sections unless the 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 somewhat vague but still states something about pay. However "tax-free stipend amount to be determined" is vague; but we have some concrete: based on 8 hour shifts and 40 hours per week. Could include Pay section with that sentence. Schedule: they mention 40 hours per week, shift: 8 hours. That's schedule info. So we could include Schedule section with those details. But we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "tax-free stipend amount to be determined" is TBD-like. Might be considered filler. Better to omit Pay section if it's mostly TBD. However we have concrete: based on 8 hour shifts and 40 hours per week. That's not filler. Could include Pay section with that sentence, but we need to ensure we don't include the TBD part? We could include only the concrete part: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation)". That's still somewhat vague but includes concrete. I'd include Pay section. Schedule: 40 hours per week, shift: 8 hours. That's concrete. Benefits: list provided. About the role: we could summarize the role as travel Physical Therapist in Hawthorne, NY, 13-week assignment, etc. But we must not invent details; we can use the given info: seeking a travel Physical Therapist for a travel job in Hawthorne, New York. Specialty: Physical Therapist, Discipline: Therapy, Start Date: 10/05/2026, Duration: 13 weeks, 40 hours per week, Shift: 8 hours, Employment Type: Travel. That's about the role. We could put that in About the role section as a paragraph. Requirements: maybe we list Specialty, Discipline, etc. But that duplicates. Better to have About the role include those details, and maybe Requirements empty? We should not create empty sections. So we need to decide which sections to include. We have substantive content for: About the role (description), Benefits (list), Pay (some info), Schedule (hours/shift). Possibly also Requirements (maybe we could list "Specialty: Physical Therapist; Discipline: Therapy" as requirements). But that overlaps with About the role. To avoid duplication, we could put About the role as a brief narrative, and Requirements as bullet list of specialty, discipline, start date, duration, etc. But that repeats info. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay? It says remove duplicated lines. So we should avoid duplicating the same line. So we need to split info without duplication. We could have About the role: narrative about the company and role? Actually About Healthcare Support is about the company, not the role. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (description of the role), Responsibilities (duties), Requirements (needed qualifications), etc. The posting does not give responsibilities. So we skip Responsibilities. Requirements: we can list the specialty, discipline, start date, duration, hours, shift, employment type as requirements. That's specific. About the role could be a brief description: "Healthcare Support is seeking a travel Physical Therapist for a travel assignment in Hawthorne, New York." That's not duplicating the specifics if we keep them in Requirements. However the phrase "travel Physical Therapist" is part of the role; we could keep that in About the role. The specifics (start date, duration, etc.) go to Requirements. Benefits: list. Pay: we have "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." The concrete part is based on 8 hour shifts and 40 hours per week. The stipend TBD is vague; we could include the concrete part and maybe omit the TBD part? But we must preserve ALL substantive information; we cannot omit the stipend TBD because it's substantive? It's stating that amount to be determined, which is info. However it's vague/TBD. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that stipend amount to be determined, which is essentially TBD. That's placeholder. So including that might be considered filler. But we could still include the Pay section with the concrete basis and note that stipend amount TBD? That includes TBD phrase. Might be considered filler. Safer to omit Pay section entirely? But we would lose the info about pay being based on 8 hour shifts and 40 hours per week. That's substantive. Could we include that info in Schedule or Requirements? Pay is separate. The instruction: prefer a few substantive sections over many thin ones. We could combine Pay and Schedule into one? But headings are prescribed. We could include Pay section with just the concrete basis, and maybe omit the TBD phrase? But that would be omitting info. However the TBD phrase is not substantive; it's just saying amount TBD. Could we drop that phrase? It's still part of the posting. The rule: preserve ALL substantive information; do NOT invent or summarize away detail. The TBD phrase is not substantive detail; it's placeholder. So we could drop it as it's not substantive. The concrete part is substantive. So we can include Pay section with that concrete sentence, dropping the TBD clause. That seems acceptable. Schedule: we have 40 hours per week, shift: 8 hours. That's concrete. So Schedule section with that. Now Benefits: list. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include / or markdown. Let's craft:

  About the role

  Healthcare Support is seeking a travel Physical Therapist for a travel assignment in Hawthorne, New York.

  Requirements

  • Specialty: Physical Therapist
  • Discipline: Therapy
  • Start Date: October 5, 2026
  • Duration: 13 weeks
  • Hours: 40 hours per week
  • Shift: 8 hours
  • Employment Type: Travel

  Benefits

  • License and certification reimbursement
  • Medical benefits
  • Dental benefits
  • Mileage reimbursement
  • Employee assistance programs
  • Referral bonus
  • 401k retirement plan
  • Holiday Pay
  • Weekly pay

  Pay

  Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation).

  Schedule

  40 hours per week with 8‑hour shifts.

  Check for duplication: Requirements includes Hours and Shift; Schedule repeats similar info. That's duplication. We should avoid duplicating lines. The instruction: remove duplicated lines. So we need to decide where to put hours/shift. Could put them in Schedule only, and remove from Requirements. Or put them in Requirements only and remove Schedule. But we need Schedule section only if posting actually states them. It does state 40 hours per week and shift: 8 hours. So we need Schedule. Then we should not duplicate in Requirements. So Requirements should exclude hours/shift. Let's adjust Requirements to exclude Hours and Shift. Thus Requirements list: Specialty, Discipline, Start Date, Duration, Employment Type. Now we have no duplication. Check About the role: we said seeking a travel Physical Therapist for a travel assignment in Hawthorne, New York. That's fine. Now Benefits list as given. Pay section: we included based on 8 hour shifts and 40.0 hours per week (subject to confirmation). That's okay. Schedule section: 40 hours per week with 8‑hour shifts. Now ensure we didn't include any boilerplate like "Posted job title: physical therapist (pt)" - we omitted that. That's okay. Check for any other info: "Healthcare Support Job ID #522583." We omitted Job ID as per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. We dropped it entirely; that's okay. "About Healthcare Support" paragraph: we omitted that because it's boilerplate about the company, not the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Healthcare Support paragraph is promotional but not boilerplate? It's describing the company. Could be considered boilerplate? It's not legal/EEO, but it's still about the company. The instruction says we can include About the role, not About the company. So we should omit the company description. Good. Now check for any other specifics: "Pst! Ask us about our Direct Hire Opportunities!" That's promotional, we can drop. Now ensure we haven't missed any substantive info: The posting also mentions "From health systems and hospitals to specialty clinics and post-acute facilities, you can work where you want to work and go where you want to go." That's promotional fluff; could be considered boilerplate? It's not a specific requirement. Likely we can drop. Now ensure we haven't missed any