Travel Physical Therapist - Acute Care - $2,142 per week

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

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. Given posting: - Job title: travel Physical Therapist (but we don't repeat as heading) - Location: Bridgeport, West Virginia - Specialty: Physical Therapist - Discipline: Therapy - Start Date: ASAP (also later: 09/26/2026) - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days (also later: 3x12 Days) - Employment Type: Travel - Job Details: location, duration, start date, shift, estimated gross weekly pay: 2142 - Qualifications: list bullet points - Why Work with Us: benefits description - About Solomon Page: description - Additional benefits list: Medical benefits, Dental benefits, Vision benefits, 401k retirement plan, Referral bonus, etc. - Also mention ReviveHealth Virtual Care, etc. We need to produce sections: About the role (maybe description of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not invent or summarize away detail. Must preserve all substantive info. We need to decide what goes where. "About the role": could be the introductory paragraph: "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 seems role description. "Responsibilities": maybe the duties listed: 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 they also have Qualifications section separate. Could treat Requirements as mandatory items like certification, ability to walk/stand, etc. Qualifications maybe same? But we need to follow instruction: use headings only if posting has real specific content for it. The posting includes a "Qualifications:" list. It also includes "Why Work with Us" which is benefits. It also includes "About Solomon Page". It also includes "Benefits" list at end. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (intro). Responsibilities (duties). Requirements (maybe certification etc). Qualifications (maybe same as requirements? but we could split: Requirements could be mandatory like certification, ability to walk/stand, etc. Qualifications could be interpersonal skills, problem-solving, etc. But we need to preserve all info; we can split arbitrarily as long as we keep all info. Skills: maybe interpersonal skills, communication, problem-solving. Benefits: we have benefits description. Pay: we have estimated gross weekly pay: 2142 (maybe also note based on 12 hour shifts and 36 hours per week, tax-free stipend TBD). Since stipend TBD we should not include placeholder. We can include the pay amount as concrete. Also mention "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That includes TBD stipend; we should not create a Pay section with filler? 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. The posting does state estimated gross weekly pay: 2142. That's concrete. The stipend TBD is extra but we can mention that as part of pay description but we must avoid placeholder text. We could include the concrete pay and note that stipend TBD is not included? Might be considered placeholder. Safer to include only the concrete pay: "Estimated Gross Weekly Pay: $2142". We can omit mention of stipend TBD. Schedule: we have shift: 12 hours, days; 36 hours per week; 3x12 Days. So we can give schedule details. Now we need to output HTML fragment only, no markdown. We'll produce something like:

About the 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

• Work closely with patients to learn about their conditions
• Create personalized care plans
• Document patient medical history and progress
• Communicate problems to supervisor and other team members

Requirements

• Certification from an accredited program
• Ability to walk or stand for long periods of time

Qualifications

• Excellent teamwork and collaboration skills
• 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

Skills

(Could combine interpersonal and communication? But we already have qualifications. Maybe we can omit Skills if no distinct content. But we need to include only if real content. We could put Skills as the same as qualifications? Might be duplication. Better to omit Skills heading if no distinct content beyond what's already covered. However we have interpersonal skills etc. Those could be considered skills. But we already used them in Qualifications. To avoid duplication, we could place them under Skills and move other items to Qualifications. Let's think: The posting has "Qualifications:" list includes certification, teamwork, ability to walk, interpersonal skills, communication, problem-solving. So we could treat Requirements as certification and ability to walk; Qualifications as teamwork, interpersonal, communication, problem-solving. Then Skills could be maybe none left. But we could still include Skills heading with same list? That would be duplicate. Better to omit Skills if no distinct content. Thus we will not include Skills heading.

Benefits

• Comprehensive medical benefits package
• Dental coverage (available the 1st of the month after hire date)
• Vision coverage (available the 1st of the month after hire date)
• Commuter benefits (available the 1st of the month after hire date)
• 401(k) plan (eligible after 1000 hours)
• Employee stock ownership plan (ESOP)
• Referral bonus
• Training programs and ongoing career coaching and support
• ReviveHealth Virtual Care (free, 100% company paid virtual primary care, urgent care, mental health therapy, vision program, prescription medications)

But we need to ensure we don't include placeholder. All specifics are present. We also have "Medical Coverage: Available immediately." etc. We'll incorporate. We need to avoid repeating lines like "Medical benefitsDental benefitsVision benefits401k retirement planReferral bonus" at end; we already covered. Now Pay:

Pay

Estimated gross weekly pay: $2,142 (based on 12‑hour shifts and 36 hours per week)

We could also note that pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation). We'll include that. Schedule:

Schedule

36 hours per week, consisting of three 12‑hour day shifts (3×12)

We should also include location? Not under any heading; maybe we can include in About the role or a separate paragraph? The instruction: do not repeat job title as heading; we can include location in a paragraph maybe under About the role or as a separate

before headings? The instruction says output only HTML fragment; we can include a

for location and other metadata like start date, duration. Where to put? Could be a short

after the initial paragraph? The instruction: "Prefer a few substantive sections over many thin ones." So we could incorporate location, start date, duration into About the role paragraph. Let's craft About the role to include location, start date, duration, shift, etc. But we already have Responsibilities separate. We could keep About the role as general description plus logistics. Let's draft:

About the role

Solomon Page is seeking a travel Physical Therapist for a 13‑week assignment in Bridgeport, West Virginia, starting ASAP (listed start date 09/26/2026). The position entails 36 hours per week on three 12‑hour day shifts (3×12). As a Physical Therapist, you will work closely with patients to learn about their conditions, create personalized care plans, document medical history and progress, and communicate issues to supervisors and team members.

That covers location, start date, duration, shift. Now Responsibilities as above. Requirements: certification, ability to walk/stand. Qualifications: teamwork, interpersonal, communication, problem-solving. Benefits as above. Pay as above. Schedule as above. We should not include Skills heading. Check for any leftover substantive info not covered: "Discipline: Therapy" maybe not needed. "Specialty: Physical Therapist" covered. "Employment Type: Travel" maybe mention in About the role: travel Physical Therapist. Good. "Job Details: Location: Bridgeport, West Virginia Duration: 13 Weeks Start Date: 09/26/2026 Shift: 3x12 Days Estimated Gross Weekly Pay: 2142" covered. "Why Work with Us" we turned into benefits. "About Solomon Page" we could incorporate into benefits? Actually it's about the company; we could add a separate section maybe "About the company" but not in allowed headings. Allowed headings are limited; we could put that info under Benefits? Not appropriate. Could we add a

after benefits? The instruction: Only use those headings for sections; we can still have

paragraphs outside headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other paragraphs, but we should prefer few sections. However we could include a brief

about Solomon Page after benefits maybe as a general description. But it's not under a heading; is that allowed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading ... Prefer a few substantive sections over many thin ones." It doesn't forbid extra paragraphs outside headings, but we should avoid thin sections. Adding a paragraph about the company might be okay. But we could incorporate Solomon Page description into Benefits section? Not ideal. Maybe we can add a heading "About the company" but not allowed. So better to add a

  after benefits without heading. We need to ensure we don't create a heading with filler. So we can add a

  describing Solomon Page. Let's craft: