Travel Outpatient Orthopedic Physical Therapist - $1,801 per week
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to parse the job posting.
Content:
- Uniti Med is seeking a travel Physical Therapist for a travel job in Kenosha, Wisconsin.
- Job Description & Requirements
Specialty: Physical Therapist
Discipline: Therapy
Start Date: 11/30/2026
Duration: 13 weeks
36 hours per week
Shift: 12 hours, days
Employment Type: Travel
Benefits: Day 1 Insurance Cigna medical, MetLife dental and vision insurance License reimbursement for new licenses needed for each assignment Discounts with hotels and rental cars A dedicated recruiter and support team that will help you every step of the way to sure you start on time and have an exceptional experience Referral bonus up to $700
- About the Company: ... (some prose)
- Uniti Med Job ID #859437. 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
- About Uniti Med (some prose)
- Benefits (list again): Referral bonus, Benefits start day 1, Employee assistance programs
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit application instructions.
We need to preserve all substantive information.
We need to decide which sections to include.
We have:
- About the role: maybe the description of the job (Specialty, Discipline, Start Date, Duration, hours, shift, employment type). Could be "About the role" heading.
- Responsibilities: Not explicitly listed. The posting doesn't list duties/responsibilities. So we should not create a Responsibilities section if no specific content.
- Requirements: Could include specialty, discipline, maybe license? Not explicit. There's "License reimbursement for new licenses needed for each assignment" but that's a benefit. Not a requirement. There's no explicit requirements like "must have PT license". Not given. So we should not create Requirements unless we have real content.
- Qualifications: Not given.
- Skills: Not given.
- Benefits: We have benefits listed: Day 1 Insurance Cigna medical, MetLife dental and vision insurance; License reimbursement for new licenses needed for each assignment; Discounts with hotels and rental cars; A dedicated recruiter and support team; Referral bonus up to $700; Benefits start day 1; Employee assistance programs. Also maybe "Referral bonus" appears twice. We'll combine.
- Pay: There's mention: "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." This is vague but it's some pay info. It says "tax-free stipend amount to be determined." That's not a specific number, but it's still some content about pay. The instruction says: "never 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 similar to TBD. It's not a specific amount. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package based on shifts and hours, with tax-free stipend amount to be determined. That's still stating something about pay, albeit vague. However the rule says avoid filler/placeholder text like "TBD". "tax-free stipend amount to be determined" is essentially TBD. So maybe we should not include Pay section because it's not substantive. But we could include it if we consider the statement about pay package based on 12 hour shifts and 36 hours per week as substantive (it tells you the shift and hours). But the Pay section is supposed to contain pay details, not just shift/hours. The shift/hours already covered elsewhere. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So if the only pay info is "tax-free stipend amount to be determined", that's placeholder. So better to omit Pay section.
- Schedule: We have shift: 12 hours, days; 36 hours per week. That's schedule info. So we can include Schedule section with those details.
- About the role: Could include specialty, discipline, start date, duration, employment type.
- About the Company: Could be a section maybe "About the Company" but not in the allowed headings list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create a custom heading like "About the Company". We could fold that prose into About the role? Or maybe we can omit it if not matching allowed headings. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but likely the only allowed headings. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. So we need to map content to those headings.
Thus we need to decide which sections have real content.
- About the role: we can put description of the role: specialty, discipline, start date, duration, hours, shift, employment type, location (Kenosha, Wisconsin). That's substantive.
- Responsibilities: none.
- Requirements: none.
- Qualifications: none.
- Skills: none.
- Benefits: we have benefits list.
- Pay: maybe omit because vague.
- Schedule: we have shift and hours.
We should avoid duplicate info: schedule info may overlap with About the role (hours/shift). But we can keep both if needed. However instruction: "Prefer a few substantive sections over many thin ones." So maybe combine schedule info into About the role and omit Schedule section. But we need to see if schedule is separate substantive content. The posting includes shift and hours explicitly; we could include them in About the role. Then we could omit Schedule section.
But we need to check if we have enough content for Benefits: yes.
Thus final HTML could have:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. So we need to map content to those headings.
Thus we need to decide which sections have real content.
- About the role: we can put description of the role: specialty, discipline, start date, duration, hours, shift, employment type, location (Kenosha, Wisconsin). That's substantive.
- Responsibilities: none.
- Requirements: none.
- Qualifications: none.
- Skills: none.
- Benefits: we have benefits list.
- Pay: maybe omit because vague.
- Schedule: we have shift and hours.
We should avoid duplicate info: schedule info may overlap with About the role (hours/shift). But we can keep both if needed. However instruction: "Prefer a few substantive sections over many thin ones." So maybe combine schedule info into About the role and omit Schedule section. But we need to see if schedule is separate substantive content. The posting includes shift and hours explicitly; we could include them in About the role. Then we could omit Schedule section.
But we need to check if we have enough content for Benefits: yes.
Thus final HTML could have:
About the role
...
Benefits
- ... ...
for location etc. We need to preserve all substantive information: location (Kenosha, Wisconsin), specialty, discipline, start date, duration, hours per week, shift, employment type, benefits list, about the company prose, Uniti Med description, referral bonus, employee assistance programs, etc. We need to include the "About the Company" prose and "About Uniti Med" prose. Where to put them? Could be part of About the role? Or maybe we can create a separate section but not allowed heading. Could we put them as
under About the role? The instruction says use
for section headings (e.g. About the role, ...). It doesn't forbid other headings, but says use for section headings (e.g ...). It might be okay to use other headings but they gave examples. Safer to stick to those headings. So we can incorporate the company prose into About the role as a paragraph.
Thus About the role paragraph will include: Uniti Med is seeking a travel Physical Therapist for a travel job in Kenosha, Wisconsin. Specialty: Physical Therapist; Discipline: Therapy; Start Date: 11/30/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, days; Employment Type: Travel. Also include the company description: "About the Company: Finding the right role is about more than just matching skills to a job—it’s about aligning with your goals, values, and the way you want to work. As an award-winning talent partner, we support healthcare professionals through every step of that process, offering meaningful opportunities, clear guidance, and long-term partnership. From our first conversation to your first day on the job (and beyond!), we’re here to help you move forward with confidence." Also include "About Uniti Med: Uniti Med meticulously matches your talents to our open needs to ensure the ultimate travel experience. Tell us where you want to go and let our experienced staff lead the way!" Also maybe include the Job ID? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include Job ID in a short paragraph maybe under About the role or separate
but not as heading. We'll include it as a short
maybe after the list. We need to avoid duplication: Benefits list appears twice; we will combine. Benefits list items: - Day 1 Insurance Cigna medical - MetLife dental and vision insurance - License reimbursement for new licenses needed for each assignment - Discounts with hotels and rental cars - A dedicated recruiter and support team that will help you every step of the way to ensure you start on time and have an exceptional experience - Referral bonus up to $700 - Benefits start day 1 (maybe redundant with Day 1 Insurance) - Employee assistance programs We should deduplicate: Day 1 Insurance Cigna medical, MetLife dental and vision insurance, License reimbursement, Discounts with hotels and rental cars, Dedicated recruiter and support team, Referral bonus up to $700, Employee assistance programs. Benefits start day 1 is already covered by Day 1 Insurance; we can omit duplicate. Now schedule: we might not include separate Schedule section; we already included shift and hours in About the role. Pay: we might omit. Now ensure we don't include any boilerplate like "Posted job title: Physical Therapist" (duplicate of role). We can ignore. Now produce HTML fragment:
About the role
Uniti Med is seeking a travel Physical Therapist for a travel job in Kenosha, Wisconsin. Specialty: Physical Therapist; Discipline: Therapy; Start Date: 11/30/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, days; Employment Type: Travel.
About the Company: Finding the right role is about more than just matching skills to a job—it’s about aligning with your goals, values, and the way you want to work. As an award-winning talent partner, we support healthcare professionals through every step of that process, offering meaningful opportunities, clear guidance, and long-term partnership. From our first conversation to your first day on the job (and beyond!), we’re here to help you move forward with confidence.
About Uniti Med: Uniti Med meticulously matches your talents to our open needs to ensure the ultimate travel experience. Tell us where you want to go and let our experienced staff lead the way!
Job ID: #859437.
Benefits
- Day 1 Insurance: Cigna medical
- MetLife dental and vision insurance
- License reimbursement for new licenses needed for each assignment
- Discounts with hotels and rental cars
- A dedicated recruiter and support team that will help you every step of the way to ensure you start on time and have an exceptional experience