Travel Physical Therapist - Outpatient - $2,500 per week

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not put Job ID as heading. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, cookie/navigation/legal/EEO etc. We need to parse the posting. Key info: - Solomon Page seeking a travel Physical Therapist for a travel job in Plymouth, New Hampshire. - Specialty: Physical Therapist - Discipline: Therapy - Start Date: 10/12/2026 - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, days - Employment Type: Travel - Job Details: Location: Plymouth, New Hampshire; Duration: 13 Weeks; Start Date: 10/12/2026; Shift: 4x10 Days; Estimated Gross Weekly Pay: 2500 - Qualifications: Certification from an accredited program; Excellent teamwork and collaboration skills; Ability to walk or stand for long periods of time; Excellent interpersonal skills including patience, empathy, and compassion; Effective communication skills, including active listening, writing, speaking and reading comprehension; Fast and adaptive problem-solving abilities - Why Work with Us: benefits: comprehensive benefits program including robust medical benefits package; dental and vision coverage; commuter benefits; 401(k) plan; flexible spending; referral bonuses; ongoing training; ESOP employee stock ownership plan; nurturing culture. - About Solomon Page: details about company, accreditation, etc. Might be considered boilerplate? It's about the company, but maybe we can include as "About the role"? Actually "About Solomon Page" is company description; could be considered "About the role"? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have: - About the role: maybe a brief description of role: "Our client is seeking a Physical Therapist to join their growing team. As a Physical Therapist, you will work closely with patients to learn more about their conditions and create a personalized care plan. You will consistently document a patient’s medical history and progress and communicate problems to supervisor and other team members." - Responsibilities: maybe the duties: work closely with patients, learn conditions, create care plan, document medical history and progress, communicate problems to supervisor and team. - Requirements: maybe the qualifications list? But we also have Qualifications heading separate. The instruction says we can have Qualifications and Skills separate. Typically Requirements could be mandatory qualifications; Skills could be abilities. But we need to decide. We have Qualifications list: Certification from an accredited program; Excellent teamwork and collaboration skills; Ability to walk or stand for long periods of time; Excellent interpersonal skills including patience, empathy, and compassion; Effective communication skills, including active listening, writing, speaking and reading comprehension; Fast and adaptive problem-solving abilities. We could treat those as Qualifications. Skills maybe overlapping; but we could put those under Skills? However we have both Qualifications and Skills headings allowed. We need to avoid filler. If we put both, we need actual content. Could split: Qualifications: certification from accredited program; maybe also requirement of being a licensed PT? Not mentioned. Skills: teamwork, interpersonal, communication, problem-solving, ability to walk/stand. But the posting lumps them together as "Qualifications:" then list includes both certification and soft skills. We could keep them under Qualifications and not create Skills unless we have distinct skills. But we could still create Skills heading with the soft skills. However that would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we split, we still preserve all info, just categorize differently. That's okay as long as we don't lose info. But we must not create headings with filler. If we put Skills heading and list the same items as under Qualifications, we would be duplicating info but not losing. Is duplication allowed? It says preserve ALL substantive information; does not forbid duplication. However better to avoid redundancy but not required. The instruction: Prefer a few substantive sections over many thin ones. So we should avoid creating many thin sections. So better to have one Qualifications section that includes both certification and skills. Then we can omit Skills heading. Similarly, Benefits: we have details: comprehensive benefits program including robust medical benefits package; dental and vision coverage; commuter benefits; 401(k) plan; flexible spending; referral bonuses; ongoing training; ESOP employee stock ownership plan; nurturing culture. Also later specifics: Medical Coverage: Available immediately; Dental Coverage: Available the 1st of the month after your hire date; Vision Coverage: Available the 1st of the month after your hire date; Commuter Benefits: Available the 1st of the month after your hire date; 401K Plan: Associates can enroll after 1000 hours; ESOP Benefits: ESOP company offers ESOP; Referral Bonus: cash bonus for referring a candidate; Training & Support: training programs and ongoing career coaching and support; ReviveHealth Virtual Care: free 100% company paid virtual care access; etc. We need to include Benefits section with those details. Pay: we have Estimated Gross Weekly Pay: 2500. Also note: Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. So we have some pay info: weekly gross $2500, plus tax-free stipend TBD. Since stipend TBD, we should not include placeholder like "tax-free stipend amount to be determined" as it's not specific? It says "tax-free stipend amount to be determined." That's not a specific number, but it's still info that stipend exists but amount TBD. The instruction: 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. For Pay section, we have actual weekly pay $2500, which is specific. The stipend TBD is placeholder; we could either omit that detail or include it but note TBD? The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include a sentence that contains TBD if we also have other substantive info. But safer to include the concrete pay and maybe mention that stipend amount is TBD as additional note? Might be considered filler. I'd include the weekly pay and maybe note that stipend amount is to be determined (that's still info). But to be safe, include the weekly pay and mention that stipend amount is TBD as a detail (though it's TBD). The instruction says never create Pay section unless posting actually states them. It does state pay package based on 10 hour shifts and 40 hours per week with tax-free stipend amount to be determined. So we can include that. Schedule: we have Shift: 10 hours, days; also Shift: 4x10 Days; 40 hours per week. So schedule: 4 days of 10-hour shifts (days). So we can include Schedule section with that. Now we need to output HTML with headings

for each section we include. We must not include / or markdown. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which info goes into which section. Let's outline: Section: About the role (maybe a brief description). Content: "Our client is seeking a Physical Therapist to join their growing team. As a Physical Therapist, you will work closely with patients to learn more about their conditions and create a personalized care plan. You will consistently document a patient’s medical history and progress and communicate problems to supervisor and other team members." That's prose ->

  . Section: Responsibilities: Could be same as above? Actually the description already covers responsibilities. To avoid duplication, we could put responsibilities in a list: - Work closely with patients to learn about their conditions and create personalized care plans. - Document patient medical history and progress. - Communicate problems to supervisor and other team members. That's a list. We'll use

  • . Section: Qualifications: list of certification and skills. We'll use
    • . Section: Benefits: list of benefits. We'll use
      • . Section: Pay: prose with weekly pay and stipend note. Section: Schedule: prose with shift details. We need to ensure we don't create sections with filler. All have concrete info. Now we need to remove boilerplate: duplicated lines, cookie/navigation/legal/EEO etc. The posting includes a lot of boilerplate about Solomon Page company details, accreditation, etc. That might be considered boilerplate but also could be relevant as "About Solomon Page". However we are not required to include a section about the company; we have About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. The company description may be considered extra but not required. The instruction: Prefer a few substantive sections over many thin ones. So we can omit the extensive company description to keep sections few. However we must preserve ALL substantive information. Is the company description substantive? It describes the company, accreditation, etc. It might be considered substantive but not directly about the job. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the company description, are we losing substantive information? It's about the company, not the job. The job posting includes it but maybe it's considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company description. However the company description might be considered part of the posting but not essential to the job. The instruction: Prefer a few substantive sections over many thin ones. So we could include a short "About the company" paragraph if we want, but we don't have a heading for that (not in allowed list). The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading like "About Solomon Page". So we must either incorporate that info into one of the allowed headings or drop it. Since we cannot add a custom heading, we likely should drop the company description to avoid creating a heading not allowed. The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should only use those headings. So we should not add other headings. Therefore we should omit the company description unless we can fold it into one of those headings (maybe About the role could include some company context). But About the role is supposed to be about the role, not company. However we could include a brief sentence about the company within About the role if it's relevant. But the instruction says 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 fold minor metadata into a short

        . The company description might be considered minor metadata? Not sure. It's fairly long. Might be better to drop it to keep sections few. Thus we will output sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't include Requirements heading (since we have Qualifications). Could also include Requirements but we don't have separate distinct requirements beyond qualifications. We'll skip Requirements to avoid thin section. Now let's craft content. About the role: prose: "Our client is seeking a