Travel Occupational Therapist - $2,156 per week

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 posting. Content: - Job title: Occupational Therapist (but we shouldn't repeat as heading) - Location: Farmington, New Mexico - Specialty: Occupational Therapist - Discipline: Therapy - Start Date: 10/05/2026 - Duration: 13 weeks - 40 hours per week - Shift: 8 hours, days - Employment Type: Travel - Pay package: based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - About Anders Group: description. - Benefits: list: Day One Health Insurance (with buy-up options), Dental & Vision Insurance, Life Insurance, 401(k) Retirement Plan, Competitive, Premium Pay Packages, Licensure & CEU Reimbursement, Daily Per Diems & Travel Reimbursements, Rental Car Allowances, Continuing Education Resources, Referral Bonuses, And more. Then later: Benefits: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit application instructions. We need to decide sections. We have info about role: maybe "About the role" could contain description of job: specialty, discipline, start date, duration, hours, shift, employment type. We have "Responsibilities": not given explicitly. The posting does not list responsibilities. So we should not create a Responsibilities section if no specific content. "Requirements": not given explicitly. Could infer from specialty but not explicit. Better not to create. "Qualifications": not given. "Skills": not given. "Benefits": we have specific list. So include Benefits section. "Pay": we have mention: Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's vague but it's specific content: says based on 8 hour shifts and 40 hrs/week, tax-free stipend amount TBD. It includes "subject to confirmation" and "tax-free stipend amount to be determined". This is somewhat vague but it's still content. The rule: do NOT include a section if the posting only has filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Here we have "tax-free stipend amount to be determined" which is TBD-like. Also "subject to confirmation". Might be considered placeholder. 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 Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's somewhat stating something but includes TBD. Might be considered placeholder. Safer to omit Pay section if it's mostly TBD. However we could include a short paragraph with that sentence, but it includes TBD. The rule says never create Pay section unless posting actually states them. It does state something, albeit vague. I'd lean to include Pay section with that sentence. Schedule: we have shift: 8 hours, days; 40 hours per week. That's specific. So we can include Schedule section. Also we have "About Anders Group" which is like company description. Could be under "About the role"? Or we could have a section "About Anders Group". But the allowed headings list does not include that; only the listed headings. We could put company info under "About the role" maybe? But "About the role" is for role description. Could also put under a generic heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should likely stick to those headings. However we could also add other headings if needed? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. Probably we should only use those headings. So we need to map content to those sections. We have role details: could go under About the role. We have schedule details: under Schedule. We have pay details: under Pay. We have benefits: under Benefits. We have no responsibilities, requirements, qualifications, skills. Thus output:

About the role

Occupational Therapist position in Farmington, New Mexico. Specialty: Occupational Therapist. Discipline: Therapy. Start Date: October 5, 2026. Duration: 13 weeks. 40 hours per week. Shift: 8 hours, days. Employment Type: Travel.

Pay

Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

Schedule

40 hours per week, 8‑hour day shifts.

Benefits

• Day One Health Insurance (with buy‑up options)
• Dental & Vision Insurance
• Life Insurance
• 401(k) Retirement Plan
• Competitive, Premium Pay Packages
• Licensure & CEU Reimbursement
• Daily Per Diems & Travel Reimbursements
• Rental Car Allowances
• Continuing Education Resources
• Referral Bonuses
• Medical benefits
• Dental benefits
• Vision benefits
• Life insurance
• 401k retirement plan
• License and certification reimbursement
• Continuing Education
• Referral bonus

We need to avoid duplication: some items duplicate (Medical benefits etc). The posting had both lists; we should preserve all substantive information, not remove duplicates unless they are duplicated lines. The instruction: Remove duplicated lines. So we should deduplicate. The list includes overlapping items: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. The earlier list had Day One Health Insurance (with buy-up options) (similar to medical), Dental & Vision Insurance, Life Insurance, 401(k) Retirement Plan, Licensure & CEU Reimbursement, Daily Per Diems & Travel Reimbursements, Rental Car Allowances, Continuing Education Resources, Referral Bonuses. Also Competitive, Premium Pay Packages. We need to deduplicate: For example, Dental & Vision Insurance vs Dental benefits and Vision benefits are similar but not exact duplicates. Might keep both? The instruction: Remove duplicated lines. If they are not exactly same line, maybe keep both. But we could combine to avoid redundancy. However we must preserve ALL substantive information; not invent or summarize away detail. If we combine Dental & Vision Insurance into separate Dental and Vision benefits, we are summarizing? Might be okay but risk losing nuance. Safer to keep both as separate items, even if similar. However we should avoid exact duplicate lines. The earlier list had "Dental & Vision Insurance". Later list had "Dental benefits" and "Vision benefits". Those are not exact duplicates, so we can keep both. Similarly "Life Insurance" vs "Life insurance" (case). Might be considered duplicate but case difference; still same meaning. Might be considered duplicate line? Probably we should keep one. To be safe, we can keep one. "401(k) Retirement Plan" vs "401k retirement plan". Slight difference. Keep one. "Licensure & CEU Reimbursement" vs "License and certification reimbursement". Similar but not exact. Keep both? Might be overlapping. Could keep both. "Continuing Education Resources" vs "Continuing Education". Keep both? Might be duplicate. "Referral Bonuses" vs "Referral bonus". Keep one. Given the instruction to remove duplicated lines, we should aim to eliminate exact duplicates after normalizing case and punctuation? Hard. Simplify: Keep the first list (more detailed) and omit the second list items that are essentially same meaning but not exact. But we risk losing info like "Medical benefits" (the first list had Day One Health Insurance with buy-up options, which is medical). So we keep Day One Health Insurance (with buy-up options). That covers medical. Thus we can output benefits as the first list plus Competitive, Premium Pay Packages. Let's produce:

• Day One Health Insurance (with buy‑up options)
• Dental & Vision Insurance
• Life Insurance
• 401(k) Retirement Plan
• Competitive, Premium Pay Packages
• Licensure & CEU Reimbursement
• Daily Per Diems & Travel Reimbursements
• Rental Car Allowances
• Continuing Education Resources
• Referral Bonuses

That seems comprehensive. Now schedule: we have 40 hours per week, shift: 8 hours, days. Could phrase: "40 hours per week, 8‑hour day shifts." Pay: we have the sentence. Now About the role: include location, specialty, discipline, start date, duration, hours, shift, employment type. Let's craft:

Occupational Therapist position in Farmington, New Mexico. Specialty: Occupational Therapist. Discipline: Therapy. Start Date: October 5, 2026. Duration: 13 weeks. 40 hours per week. Shift: 8 hours, days. Employment Type: Travel.

Check for any other substantive info: The posting also mentions "Anders Group Job ID #1396183." We should drop Job ID per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could drop it entirely or include in a short p. Probably drop it. Also "Posted job title: Occupational Therapist" - we already have title; we can drop. Now ensure no boilerplate: we removed Anders Group description? Actually we omitted the Anders Group description. That is substantive info about the company. Should we include it? The allowed sections do not include "About the company". But we could include under About the role? Might be okay to add a paragraph about Anders Group under About the role? But that is not about the role. However the instruction says use those headings for sections; but we could still include a paragraph about Anders Group under About the role? Might be misrepresenting. However the instruction says "Prefer a few substantive sections over many thin ones." It didn't forbid adding other headings, but gave examples. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings for sections; but we could also use other headings if needed? Safer to stick to those. Thus we may omit Anders