Travel Occupational Therapist - $1,964 per week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no /, no markdown code fences
Now, let's map the content to appropriate sections.
The job details: specialty, discipline, start date, duration, hours per week, shift, employment type, job ID. This could be "About the role" or "Job Details". The rules mention "About the role" as a possible heading. I'll use "About the role" for the job details.
The "About Anders Group" section: this is company description. Could be "About the Company" but the rules don't list that. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Anders Group" might not fit exactly. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. But we should prefer those. However, the posting has "About Anders Group" and "The Anders Difference". That's company info. Could be under "About the role"? Not really. Maybe we can create a section "About the Company" but the rules didn't list it. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." meaning for example. So we can use other headings if needed, but we should prefer those. However, the posting doesn't have responsibilities, requirements, qualifications, skills explicitly. It has benefits listed twice: "What You Can Expect" and "Benefits". The benefits list is substantive.
We need to include sections only when there is real content. The posting has:
- Job details (metadata)
- Company description (About Anders Group, The Anders Difference)
- Benefits (two lists, but they are similar)
We should not create a Pay section because the pay is described as "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 not specific pay numbers, but it's some info. However, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay package details, but it's vague. It says "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 a statement about pay. But the rule says "unless the posting actually states them." It does state something about pay. However, the example says "commensurate with experience", "not specified", "N/A", "varies", "TBD" are filler. Here it's "tax-free stipend amount to be determined." That's TBD. So maybe we should not create a Pay section. Similarly, Schedule: shift is given (8 hours, days). That's schedule info. But the rule says never create Schedule section unless posting actually states them. It does state shift. But we can fold schedule into "About the role". The job details include shift and hours.
Benefits: the posting has a list of benefits under "What You Can Expect" and again under "Benefits". That's substantive. So we should have a Benefits section.
Now, responsibilities, requirements, qualifications, skills: not explicitly listed. The posting is for a travel Occupational Therapist, but no specific duties or requirements listed. So we should not create those sections.
Thus, we can have:
- About the role (job details)
- About the Company (or maybe "About Anders Group") but the rules didn't list that heading. However, we can use a heading that fits. The rules say "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 prefer those. Could we put company info under "About the role"? Not appropriate. Maybe we can omit company info? But the rule says "Preserve ALL substantive information". The company description is substantive. So we need to include it. We can create a heading "About the Company" or "Company Overview". Since the rules say "e.g.", we can use a different heading. I'll use "About the Company".
But the user might expect only the example headings. However, the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This is a guideline. I think it's okay to use "About the Company" as a heading.
Alternatively, we could fold company info into a paragraph under "About the role"? That would be messy.
Let's see the example: they gave a list of possible headings. The posting has "About Anders Group" and "The Anders Difference". That's about the company. I'll create a section "About the Company".
Now, benefits: we have two lists. We should combine them into one Benefits section, removing duplicates.
Job ID: fold into a short
or drop it. The rule: "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 paragraph in "About the role".
Now, let's structure.
First, "About the role" section: include job details as a list or paragraphs. The details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Job ID. We can present as a list.
Second, "About the Company" section: include the description from "About Anders Group" and "The Anders Difference". That's prose.
Third, "Benefits" section: combine the two lists.
We should not include "Posted job title: |OT|Rehab|Reliant - The Boulevard Post Acute|Open" as it's maybe internal. But it's part of the job description. Could be included in "About the role".
Now, write HTML.
We'll output only the HTML fragment.
Let's draft:
About the role
Anders Group is seeking a travel Occupational Therapist for a travel job in Fairfax, Virginia.
- Specialty: Occupational Therapist
- Discipline: Therapy
- Start Date: ASAP
- Duration: 13 weeks
- Hours per week: 40
- Shift: 8 hours, days
- Employment Type: Travel
- Job ID: #1407705
- Posted job title: OT | Rehab | Reliant - The Boulevard Post Acute | Open
Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
About the Company
At Anders Group, we do things differently. As a Joint Commission–accredited healthcare staffing agency, we’re committed to one thing above all else—you. Our travelers aren’t just placements, they’re partners. That’s why we focus on delivering exceptional customer service, personalized support, and access to some of the best-paying travel opportunities nationwide.
Founded in 2010 by experienced healthcare recruiters, Anders Group was built on a simple idea: people come before numbers. While many staffing firms focus on volume, we focus on relationships, quality placements, and your long-term success. By aligning your goals with the needs of top healthcare facilities across the country, we create assignments that truly fit, professionally and personally.
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
But note: the benefits list has duplicates (e.g., Dental & Vision Insurance vs Dental benefits, Vision benefits; Life Insurance vs Life insurance; 401(k) Retirement Plan vs 401k retirement plan; Licensure & CEU Reimbursement vs License and certification reimbursement; Continuing Education Resources vs Continuing Education; Referral Bonuses vs Referral bonus). We should deduplicate. The rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." But duplicates are not substantive. We can combine and keep unique items. However, the two lists are slightly different: first list includes "Competitive, Premium Pay Packages", "Daily Per Diems & Travel Reimbursements", "Rental Car Allowances", "Continuing Education Resources", "Referral Bonuses". Second list is more generic. We should include all unique benefits. But we must not summarize away detail. So we can list each unique benefit. However, "Medical benefits" is generic, but first list has "Day One Health Insurance (with buy-up options)". That's more specific. We'll keep both? Might be redundant. But we can keep both as separate items? The rule says preserve all substantive information. If they are different, keep both. But "Medical benefits" is vague. I'll keep the more specific ones and omit the generic duplicates. But to be safe, I'll include all unique strings.
Let's list unique benefits from both sections:
From "What You Can Expect":
- 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
From "Benefits":
- Medical benefits
- Dental benefits
- Vision benefits
- Life insurance
- 401k retirement plan
- License and certification
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, let's map the content to appropriate sections. The job details: specialty, discipline, start date, duration, hours per week, shift, employment type, job ID. This could be "About the role" or "Job Details". The rules mention "About the role" as a possible heading. I'll use "About the role" for the job details. The "About Anders Group" section: this is company description. Could be "About the Company" but the rules don't list that. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Anders Group" might not fit exactly. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. But we should prefer those. However, the posting has "About Anders Group" and "The Anders Difference". That's company info. Could be under "About the role"? Not really. Maybe we can create a section "About the Company" but the rules didn't list it. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." meaning for example. So we can use other headings if needed, but we should prefer those. However, the posting doesn't have responsibilities, requirements, qualifications, skills explicitly. It has benefits listed twice: "What You Can Expect" and "Benefits". The benefits list is substantive.
We need to include sections only when there is real content. The posting has:
- Job details (metadata)
- Company description (About Anders Group, The Anders Difference)
- Benefits (two lists, but they are similar)
We should not create a Pay section because the pay is described as "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 not specific pay numbers, but it's some info. However, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay package details, but it's vague. It says "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 a statement about pay. But the rule says "unless the posting actually states them." It does state something about pay. However, the example says "commensurate with experience", "not specified", "N/A", "varies", "TBD" are filler. Here it's "tax-free stipend amount to be determined." That's TBD. So maybe we should not create a Pay section. Similarly, Schedule: shift is given (8 hours, days). That's schedule info. But the rule says never create Schedule section unless posting actually states them. It does state shift. But we can fold schedule into "About the role". The job details include shift and hours.
Benefits: the posting has a list of benefits under "What You Can Expect" and again under "Benefits". That's substantive. So we should have a Benefits section.
Now, responsibilities, requirements, qualifications, skills: not explicitly listed. The posting is for a travel Occupational Therapist, but no specific duties or requirements listed. So we should not create those sections.
Thus, we can have:
- About the role (job details)
- About the Company (or maybe "About Anders Group") but the rules didn't list that heading. However, we can use a heading that fits. The rules say "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 prefer those. Could we put company info under "About the role"? Not appropriate. Maybe we can omit company info? But the rule says "Preserve ALL substantive information". The company description is substantive. So we need to include it. We can create a heading "About the Company" or "Company Overview". Since the rules say "e.g.", we can use a different heading. I'll use "About the Company".
But the user might expect only the example headings. However, the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This is a guideline. I think it's okay to use "About the Company" as a heading.
Alternatively, we could fold company info into a paragraph under "About the role"? That would be messy.
Let's see the example: they gave a list of possible headings. The posting has "About Anders Group" and "The Anders Difference". That's about the company. I'll create a section "About the Company".
Now, benefits: we have two lists. We should combine them into one Benefits section, removing duplicates.
Job ID: fold into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. But we should prefer those. Could we put company info under "About the role"? Not appropriate. Maybe we can omit company info? But the rule says "Preserve ALL substantive information". The company description is substantive. So we need to include it. We can create a heading "About the Company" or "Company Overview". Since the rules say "e.g.", we can use a different heading. I'll use "About the Company".
But the user might expect only the example headings. However, the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This is a guideline. I think it's okay to use "About the Company" as a heading.
Alternatively, we could fold company info into a paragraph under "About the role"? That would be messy.
Let's see the example: they gave a list of possible headings. The posting has "About Anders Group" and "The Anders Difference". That's about the company. I'll create a section "About the Company".
Now, benefits: we have two lists. We should combine them into one Benefits section, removing duplicates.
Job ID: fold into a short
or drop it. The rule: "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 paragraph in "About the role". Now, let's structure. First, "About the role" section: include job details as a list or paragraphs. The details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Job ID. We can present as a list. Second, "About the Company" section: include the description from "About Anders Group" and "The Anders Difference". That's prose. Third, "Benefits" section: combine the two lists. We should not include "Posted job title: |OT|Rehab|Reliant - The Boulevard Post Acute|Open" as it's maybe internal. But it's part of the job description. Could be included in "About the role". Now, write HTML. We'll output only the HTML fragment. Let's draft:
About the role
Anders Group is seeking a travel Occupational Therapist for a travel job in Fairfax, Virginia.
- Specialty: Occupational Therapist
- Discipline: Therapy
- Start Date: ASAP
- Duration: 13 weeks
- Hours per week: 40
- Shift: 8 hours, days
- Employment Type: Travel
- Job ID: #1407705
- Posted job title: OT | Rehab | Reliant - The Boulevard Post Acute | Open
Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
About the Company
At Anders Group, we do things differently. As a Joint Commission–accredited healthcare staffing agency, we’re committed to one thing above all else—you. Our travelers aren’t just placements, they’re partners. That’s why we focus on delivering exceptional customer service, personalized support, and access to some of the best-paying travel opportunities nationwide.
Founded in 2010 by experienced healthcare recruiters, Anders Group was built on a simple idea: people come before numbers. While many staffing firms focus on volume, we focus on relationships, quality placements, and your long-term success. By aligning your goals with the needs of top healthcare facilities across the country, we create assignments that truly fit, professionally and personally.
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