Travel Physical Therapist - $2,302 per week
Trustaff · Lewistown, MT · 1 mo ago
On-siteInternship
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
Content:
- Job title: Physical Therapist (already shown, not repeat)
- Location: Lewistown, Montana (maybe part of metadata)
- Specialty: Physical Therapist
- Discipline: Therapy
- Start Date: 10/26/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, days
- Employment Type: Travel
- Description: As a Physical Therapist, you'll work closely with patients to improve their movement and manage pain. PTs are a critical part of rehabilitation, treatment, and prevention for patients with injuries or chronic issues. PT job duties include: assessing the patient?s health history, diagnosing their functions and movements, and developing and implementing a specialize plan of care for their benefit.
- Job ID #2196807 (metadata)
- 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: Physical Therapist (duplicate)
- About Trustaff Allied: paragraphs about company.
- Benefits list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus (maybe also industry-leading pay, bonuses, etc.)
- Also mention: Priority access to thousands of travel healthcare jobs, Industry-leading pay, Guaranteed weekly hours, Experienced recruiters, Comprehensive benefits, including medical, dental, and vision, 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to output sections only if real specific content.
Potential sections:
- About the role (maybe description of role)
- Responsibilities (list of duties)
- Requirements/Qualifications (maybe none explicit)
- Skills (maybe none)
- Benefits (list)
- Pay (mention of pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined - but that's vague; "tax-free stipend amount to be determined" is not specific; "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)" is not a specific number. According to rule: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week, but no actual amount. It says "tax-free stipend amount to be determined." That's not specific. Should we include Pay? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package, but it's not a concrete number. However it's still stating pay package exists. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (pay package based on...). So we could include a Pay section with that info. But also we should avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Here we have "tax-free stipend amount to be determined" which is TBD. That's like TBD. Might be considered filler. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we must not have placeholder text. The posting says "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 includes "tax-free stipend amount to be determined" which is TBD. That's placeholder. So we should not include Pay section because it would contain placeholder. Could we rephrase to avoid placeholder? We must preserve ALL substantive information; do NOT invent or summarize away detail. We cannot omit the stipend amount to be determined? That's part of the posting. If we include Pay section, we must include that statement, which is placeholder. That violates rule. So better to omit Pay section entirely.
Schedule: The posting includes shift: 12 hours, days; 36 hours per week; duration 13 weeks; start date. That's schedule info. We could include a Schedule section with those details. That is specific: start date, duration, hours per week, shift. No placeholder. So include Schedule.
Benefits: The posting lists specific benefits: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus, also mentions industry-leading pay, bonuses, 401k with employer match, assistance with travel, compliance, housing, great bonuses for completions, referring friends, etc. Those are substantive. So include Benefits section.
About the role: Could be a section describing the role. The description: "As a Physical Therapist, you'll work closely with patients to improve their movement and manage pain. PTs are a critical part of rehabilitation, treatment, and prevention for patients with injuries or chronic issues. PT job duties include: assessing the patient?s health history, diagnosing their functions and movements, and developing and implementing a specialize plan of care for their benefit." That's substantive. Could be About the role or Responsibilities. We need to decide which sections to include. We can have About the role (prose) and Responsibilities (list). The duties list is given as a sentence with colon; we can turn into
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
Content:
- Job title: Physical Therapist (already shown, not repeat)
- Location: Lewistown, Montana (maybe part of metadata)
- Specialty: Physical Therapist
- Discipline: Therapy
- Start Date: 10/26/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, days
- Employment Type: Travel
- Description: As a Physical Therapist, you'll work closely with patients to improve their movement and manage pain. PTs are a critical part of rehabilitation, treatment, and prevention for patients with injuries or chronic issues. PT job duties include: assessing the patient?s health history, diagnosing their functions and movements, and developing and implementing a specialize plan of care for their benefit.
- Job ID #2196807 (metadata)
- 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: Physical Therapist (duplicate)
- About Trustaff Allied: paragraphs about company.
- Benefits list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus (maybe also industry-leading pay, bonuses, etc.)
- Also mention: Priority access to thousands of travel healthcare jobs, Industry-leading pay, Guaranteed weekly hours, Experienced recruiters, Comprehensive benefits, including medical, dental, and vision, 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to output sections only if real specific content.
Potential sections:
- About the role (maybe description of role)
- Responsibilities (list of duties)
- Requirements/Qualifications (maybe none explicit)
- Skills (maybe none)
- Benefits (list)
- Pay (mention of pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined - but that's vague; "tax-free stipend amount to be determined" is not specific; "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)" is not a specific number. According to rule: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week, but no actual amount. It says "tax-free stipend amount to be determined." That's not specific. Should we include Pay? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package, but it's not a concrete number. However it's still stating pay package exists. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (pay package based on...). So we could include a Pay section with that info. But also we should avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Here we have "tax-free stipend amount to be determined" which is TBD. That's like TBD. Might be considered filler. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we must not have placeholder text. The posting says "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 includes "tax-free stipend amount to be determined" which is TBD. That's placeholder. So we should not include Pay section because it would contain placeholder. Could we rephrase to avoid placeholder? We must preserve ALL substantive information; do NOT invent or summarize away detail. We cannot omit the stipend amount to be determined? That's part of the posting. If we include Pay section, we must include that statement, which is placeholder. That violates rule. So better to omit Pay section entirely.
Schedule: The posting includes shift: 12 hours, days; 36 hours per week; duration 13 weeks; start date. That's schedule info. We could include a Schedule section with those details. That is specific: start date, duration, hours per week, shift. No placeholder. So include Schedule.
Benefits: The posting lists specific benefits: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus, also mentions industry-leading pay, bonuses, 401k with employer match, assistance with travel, compliance, housing, great bonuses for completions, referring friends, etc. Those are substantive. So include Benefits section.
About the role: Could be a section describing the role. The description: "As a Physical Therapist, you'll work closely with patients to improve their movement and manage pain. PTs are a critical part of rehabilitation, treatment, and prevention for patients with injuries or chronic issues. PT job duties include: assessing the patient?s health history, diagnosing their functions and movements, and developing and implementing a specialize plan of care for their benefit." That's substantive. Could be About the role or Responsibilities. We need to decide which sections to include. We can have About the role (prose) and Responsibilities (list). The duties list is given as a sentence with colon; we can turn into - . So we can have Responsibilities section with list.
Requirements/Qualifications: Not explicitly listed besides specialty and discipline maybe. The posting includes Specialty: Physical Therapist, Discipline: Therapy, Start Date, Duration, etc. Those are more job details not requirements. No explicit requirements like education, licensure. So we might not include Requirements.
Skills: Not listed.
Thus sections: About the role (prose), Responsibilities (list), Benefits (list), Schedule (list or prose). Also maybe About Trustaff Allied (company description) could be a section like About the company. But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't list About the company. However we could still include a section like About Trustaff Allied under maybe "About the company" but not in list. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exhaustive. Could we add a section like About Trustaff Allied? Possibly but better to stick to given examples. The company description could be considered part of About the role? Not really. Might be considered boilerplate? It's substantive about the employer. The instruction didn't forbid adding other headings, but gave examples. Safer to include only those headings that have content. We could treat the Trustaff Allied description as part of "About the role"? Not accurate. Could we omit it? It's substantive but not required. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include that info somewhere. If we don't have a heading for it, we could put it in a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. We could add a heading like About Trustaff Allied (maybe not in list but still ). The instruction didn't forbid other headings; it gave examples. So we can add a heading for Trustaff Allied description.
Thus sections: About Trustaff Allied (prose), About the role (prose), Responsibilities (list), Benefits (list), Schedule (list). Ensure no empty sections.
Now craft HTML.
We need to output only HTML fragment, no /, no markdown.
We'll produce:
About Trustaff Allied
Our traveler-first attitude has set us apart from other travel healthcare agencies. When you join the Trustaff family, you’re more than just a body filling a role—you're a vibrant individual with dreams and aspirations. As one of the nation's leading travel healthcare companies, your recruiter will work with you one-on-one to guide your career and help you achieve your goals. You decide when and where you want to work. Enjoy industry-leading pay, benefits, and bonuses. Experience new people and places. Grow your clinical skills and expand your experience. Travel healthcare lets you take your professional career to the next level while maintaining your flexibility and freedom. At Trustaff, we put you first, so you never have to compromise your work or pay. We are proud to have one of the highest nurse retention rates in the country. Some of the other reasons people choose us include: priority access to thousands of travel healthcare jobs, industry-leading pay, guaranteed weekly hours, experienced recruiters, comprehensive benefits including medical, dental, and vision, 401k with employer match, assistance with travel, compliance, and housing, great bonuses for completions, referring friends, and more.
About the role
As a Physical Therapist, you'll work closely with patients to improve their movement and manage pain. PTs are a critical part of rehabilitation, treatment, and prevention for patients with injuries or chronic issues.
Responsibilities
- Assessing the patient’s health history
- Diagnosing their functions and movements
- Developing and implementing a specialized plan of care for their benefit
Benefits
- Dental benefits
- Medical benefits
- Vision benefits
- Guaranteed hours
- Referral bonus
- Industry-leading pay
- Bonuses for completions and referrals
- 401k with employer match
- Assistance with travel, compliance, and housing
Schedule
- Start date: October 26, 2026
- Duration: 13 weeks
- Hours per week: 36 hours
- Shift: 12 hours, days
- Employment type: Travel
We need to ensure we didn't repeat job title as heading. Good.
We removed Job ID etc. Could we include Job ID in a short ? The instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." We could include a short paragraph with Job ID maybe under a heading? But we don't have a heading for metadata. Could add a
before sections: "Job ID #2196807". But that is minor metadata; we could drop it. The instruction says preserve ALL substantive information; Job ID is maybe not substantive? It's an identifier; could be considered metadata. It's ambiguous. Safer to drop it? The instruction says "fold minor metadata into a short
or drop it." So we could include a short
with Job ID. Let's include a
at top:
Job ID #2196807
. That's minor metadata.
Also include location? Could be metadata. Not required.
We'll add that.
Now ensure no empty sections.
Check for any placeholder text: Benefits list
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exhaustive. Could we add a section like About Trustaff Allied? Possibly but better to stick to given examples. The company description could be considered part of About the role? Not really. Might be considered boilerplate? It's substantive about the employer. The instruction didn't forbid adding other headings, but gave examples. Safer to include only those headings that have content. We could treat the Trustaff Allied description as part of "About the role"? Not accurate. Could we omit it? It's substantive but not required. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include that info somewhere. If we don't have a heading for it, we could put it in a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. We could add a heading like About Trustaff Allied (maybe not in list but still ). The instruction didn't forbid other headings; it gave examples. So we can add a heading for Trustaff Allied description.
Thus sections: About Trustaff Allied (prose), About the role (prose), Responsibilities (list), Benefits (list), Schedule (list). Ensure no empty sections.
Now craft HTML.
We need to output only HTML fragment, no /, no markdown.
We'll produce:
About Trustaff Allied
About Trustaff Allied
Our traveler-first attitude has set us apart from other travel healthcare agencies. When you join the Trustaff family, you’re more than just a body filling a role—you're a vibrant individual with dreams and aspirations. As one of the nation's leading travel healthcare companies, your recruiter will work with you one-on-one to guide your career and help you achieve your goals. You decide when and where you want to work. Enjoy industry-leading pay, benefits, and bonuses. Experience new people and places. Grow your clinical skills and expand your experience. Travel healthcare lets you take your professional career to the next level while maintaining your flexibility and freedom. At Trustaff, we put you first, so you never have to compromise your work or pay. We are proud to have one of the highest nurse retention rates in the country. Some of the other reasons people choose us include: priority access to thousands of travel healthcare jobs, industry-leading pay, guaranteed weekly hours, experienced recruiters, comprehensive benefits including medical, dental, and vision, 401k with employer match, assistance with travel, compliance, and housing, great bonuses for completions, referring friends, and more.
About the role
As a Physical Therapist, you'll work closely with patients to improve their movement and manage pain. PTs are a critical part of rehabilitation, treatment, and prevention for patients with injuries or chronic issues.
Responsibilities
- Assessing the patient’s health history
- Diagnosing their functions and movements
- Developing and implementing a specialized plan of care for their benefit
Benefits
- Dental benefits
- Medical benefits
- Vision benefits
- Guaranteed hours
- Referral bonus
- Industry-leading pay
- Bonuses for completions and referrals
- 401k with employer match
- Assistance with travel, compliance, and housing
Schedule
- Start date: October 26, 2026
- Duration: 13 weeks
- Hours per week: 36 hours
- Shift: 12 hours, days
- Employment type: Travel
? The instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." We could include a short paragraph with Job ID maybe under a heading? But we don't have a heading for metadata. Could add a
before sections: "Job ID #2196807". But that is minor metadata; we could drop it. The instruction says preserve ALL substantive information; Job ID is maybe not substantive? It's an identifier; could be considered metadata. It's ambiguous. Safer to drop it? The instruction says "fold minor metadata into a short
or drop it." So we could include a short
with Job ID. Let's include a
at top:
Job ID #2196807
. That's minor metadata. Also include location? Could be metadata. Not required. We'll add that. Now ensure no empty sections. Check for any placeholder text: Benefits list