Travel Inpatient Occupational Therapist - $2,237 per week
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not put Job ID as heading; fold minor metadata into short
or drop it. We need to preserve all substantive information; remove boilerplate like cookie/navigation/legal/EEO etc. There's none. We need to include sections only when posting has real specific content. So we need to decide which sections apply. We have: - About the role: could include description of OT role (evaluate and treat...). That's substantive. - Responsibilities: maybe the description includes responsibilities (evaluate and treat...). Could be placed under Responsibilities. - Requirements: maybe specialty, discipline, start date, duration, hours, shift, employment type. Those are requirements. - Qualifications: maybe not explicitly listed; but could infer from specialty etc. However we should not invent. If not explicit, we should not create Qualifications section. - Skills: not listed explicitly. - Benefits: there is a list: Industry-leading pay, Generous cost of living and housing stipends, Opportunities for referral, sign-on, and extension bonuses, Weekly health insurance or health insurance Marketplace weekly bonus, Continuing education credits. Also mention "We offer:" bullet list. So we can create Benefits section. - Pay: posting says "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." That's vague; not a specific amount. The rule: do NOT include Pay section unless posting actually states them. It states pay package based on... but not actual numbers. It says "tax-free stipend amount to be determined." That's not specific. Likely we should not create Pay section because it's not a concrete figure. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on... but it's not a specific amount; still it's stating something about pay. However they said "unless the posting actually states them." It does state something about pay (based on 8 hour shifts and 40 hours per week). Might be considered stating pay? But they also say "Prefer a few substantive sections over many thin ones." Might be better to include Pay only if there is actual pay rate or stipend amount. Since it's "to be determined", it's not substantive. I'd skip Pay. - Schedule: posting says "40 hours per week Shift: 8 hours, days". That's schedule info. So we can create Schedule section. We also have "Start Date: 10/05/2026 Duration: 13 weeks". Could be part of Requirements or maybe a separate section like Assignment Details, but not in allowed headings. We can fold into Requirements or About the role. We need to avoid repeating job title as heading. So no
Occupational Therapist
. We need to output only HTML fragment. Let's structure:About the role
Occupational therapists evaluate and treat people who have injuries, illnesses, or disabilities. They help clients meet goals to develop, recover, improve, and maintain skills needed for daily living and working.
Responsibilities
Evaluate and treat patients with injuries, illnesses, or disabilities; assist clients in developing, recovering, improving, and maintaining daily living and work skills.
But that duplicates the description. Might be okay but we risk duplication. Better to keep description under About the role and not repeat. Responsibilities could be derived from same sentence but we could keep it brief. Alternatively we could combine About the role and Responsibilities into one section? But we need to follow headings only when content exists. We could have About the role with description, and Responsibilities maybe not needed if same. But we need to preserve all substantive information; we already have description in About the role. That's fine. Requirements: include specialty, discipline, start date, duration, hours, shift, employment type. We can make a- list.
Benefits: list as given.
Schedule: 40 hours per week, 8 hour shifts, days.
We could also include Pay? I'd skip.
Let's craft.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We'll output:
About the role
Occupational therapists evaluate and treat people who have injuries, illnesses, or disabilities. They help clients meet goals to develop, recover, improve, and maintain skills needed for daily living and working.
Requirements
- Specialty: Occupational Therapist
- Discipline: Therapy
- Start Date: October 5, 2026
- Duration: 13 weeks
- Hours: 40 hours per week
- Shift: 8‑hour day shifts
- Employment Type: Travel
Benefits
- Industry‑leading pay
- Generous cost of living and housing stipends
- Opportunities for referral, sign‑on, and extension bonuses
- Weekly health insurance or health insurance Marketplace weekly bonus
- Continuing education credits
Schedule
40 hours per week, 8‑hour day shifts.
We might also include a short paragraph for metadata like Job ID? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." We could add a
at top: Job ID #19227818. But it's minor metadata; we could drop it. Safer to drop? The instruction says fold minor metadata into a short
or drop it. So we could include a
with Job ID. But it's not required. I'd include a short p at beginning:
Job ID #19227818
. That's minor metadata. But we must not repeat job title as heading; we aren't. Check for any duplicated lines: we have not. Check for boilerplate: none. Check for any invented content: we didn't invent. Check for preserving all substantive information: we captured description, requirements, benefits, schedule. Did we capture "Why ALOIS Healthcare? ALOIS means “brave warrior” and that’s what you are- Warrior in Scrubs! ..."? That's promotional content about the company. Could be considered part of Benefits or About the role? It's not a benefit per se but more about company culture. The allowed headings do not include "Company Overview". But we could incorporate into About the role? Might be considered "About ALOIS Healthcare". Not in allowed headings. The instruction: Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings. It didn't say we cannot use other headings, but likely we should stick to those. The company description may be considered part of Benefits? Not really. Could be omitted? The instruction: "Preserve ALL substantive information". So we need to include that info somewhere. We could put it under About the role as a paragraph describing the employer. That seems acceptable: About the role can include info about the employer and role. So we can add a paragraph after the OT description about ALOIS Healthcare's mission and values. Let's incorporate: After the OT description, add a paragraph: "ALOIS Healthcare means “brave warrior” and that’s what you are- Warrior in Scrubs! Just as you advocate for your patients, we will advocate for you. The pay you deserve. The support you need. We’re in your corner for every battle – because you shouldn’t settle for anything less when it comes to your career. We offer: ..." But we already have Benefits list separate. Might duplicate. Better to keep the motivational sentences separate from benefits list. We could put them under About the role as a paragraph describing the company culture, and keep Benefits list as separate section with the bullet list of benefits. Thus About the role will have two paragraphs: first OT description, second about ALOIS Healthcare's mission/values. Let's craft:
About the role
Occupational therapists evaluate and treat people who have injuries, illnesses, or disabilities. They help clients meet goals to develop, recover, improve, and maintain skills needed for daily living and working.
ALOIS Healthcare means “brave warrior” and that’s what you are- Warrior in Scrubs! Just as you advocate for your patients, we will advocate for you. The pay you deserve. The support you need. We’re in your corner for every battle – because you shouldn’t settle for anything less when it comes to your career.
Then Benefits section as bullet list. We need to ensure we don't repeat the "We offer:" line that introduces the bullet list; we can just have the bullet list. Now check for any other substantive info: "We’re proud to be recognized globally as a certified minority-owned staffing supplier." That's also substantive about company. Could be added to About the role as another sentence. Add after the mission paragraph: "We’re proud to be recognized globally as a certified minority-owned staffing supplier." Then bullet list of At ALOIS Healthcare: values: Everyone Matters, We are Performance Driven, We are Open, Honest and Direct, We are Transparent, We are Inclusive, We Do the Right Thing. That's also substantive; could be included in About the role as a list or paragraph. But we have no specific heading for values; we could incorporate into About the role as a paragraph list. We could add an- inside About the role? But the instruction: Use
- for any list of duties/requirements/benefits. Values list is not duties/requirements/benefits; it's more about company culture. Could still be a list but not specified. Safer to put as a paragraph separated by commas.
We'll add a paragraph: "At ALOIS Healthcare: Everyone Matters; We are Performance Driven; We are Open, Honest and Direct; We are Transparent; We are Inclusive; We Do the Right Thing."
Now we have preserved all substantive info.
Check for any other info: "Posted job title: Occupational Therapist (OT) Inpatient" - we should not repeat job title as heading, but we could include as minor metadata maybe in a short p. But we already have Job ID maybe. We could include posted job title as a short p. However the instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It mentions Job ID/requisition numbers specifically, not posted job title. But posted job title is similar to job title; we already have the job title displayed elsewhere (page already shows it). So we can drop it. Thus final HTML:
Job ID #19227818
maybe optional. I'd include it as minor metadata. But we already have a lot of content; adding Job ID line is fine. Let's output:Job ID #19227818
About the