Jobs · Healthcare · Virginia

Travel Speech Language Pathologist - $1,873 per week

Anders Group, LLC · Danville, VA · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with sections only if content present. The posting includes: Job description & requirements (but we need to extract specifics). Let's parse. The posting: "Anders Group is seeking a travel Speech Language Pathologist for a travel job in Danville, Virginia. Job Description & Requirements Specialty: Speech Language Pathologist Discipline: Therapy Start Date: ASAP Duration: 13 weeks 40 hours per week Shift: 8 hours, days Employment Type: Travel Anders Group Job ID #1400111. Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: |SLP|Rehab|Odyssey - Cardinal Senior Living at Danville|Open About Anders Group About Anders Group Why Anders?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. What You Can ExpectFrom your very first assignment, you’ll have access to a comprehensive benefits package designed to support you both professionally and personally: 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 The Anders Difference You’re committed to providing exceptional patient care and we’re committed to supporting you every step of the way. 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 Medical benefits Dental benefits Vision benefits Life insurance 401k retirement plan License and certification reimbursement Continuing Education Referral bonus" We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none explicit. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real specific content. We have: About Anders Group (company description) - could be "About the role"? Actually "About the role" is typical heading for role description. But we have "Job Description & Requirements" with specifics: Specialty, Discipline, Start Date, Duration, hours, shift, employment type. That's more like responsibilities/requirements. We also have Pay info: "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; we should not create Pay section if content is not specific (no actual numbers). The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It states pay package based on 8 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's still somewhat generic but mentions shift and hours. However it's not a specific amount. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here "tax-free stipend amount to be determined" is placeholder. So we should not create Pay section. Schedule: we have shift: 8 hours, days; 40 hours per week. That's schedule info. Could create Schedule section with that detail. It's specific: 8 hour shifts, days, 40 hours per week. That's not placeholder. So we can include Schedule. Benefits: there is a list of 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, And more. Also later a Benefits list: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. Some duplication. We need to preserve all substantive information, but remove duplicated lines. So we need to combine unique benefits. Let's extract unique benefits: - Day One Health Insurance (with buy-up options) - Dental & Vision Insurance (or separate Dental benefits, Vision benefits) - Life Insurance - 401(k) Retirement Plan (or 401k retirement plan) - Competitive, Premium Pay Packages (maybe part of Pay but we aren't making Pay section) - Licensure & CEU Reimbursement (License and certification reimbursement) - Daily Per Diems & Travel Reimbursements - Rental Car Allowances - Continuing Education Resources (Continuing Education) - Referral Bonuses (Referral bonus) - Medical benefits (maybe covered by Day One Health Insurance) - Dental benefits (covered) - Vision benefits (covered) - etc. We should avoid duplication. Let's produce a Benefits section with a
  • list of unique benefits. We need to decide headings: About the role (maybe we can put company description under About Anders Group? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We have content for: - About the role: maybe we can put a brief description of the role: travel Speech Language Pathologist in Danville, Virginia. That's from first sentence. Could be considered About the role. - Responsibilities: maybe we don't have explicit responsibilities list; we have specialty, discipline, etc. Could treat those as Requirements? Actually "Specialty: Speech Language Pathologist", "Discipline: Therapy" are qualifications. "Start Date: ASAP", "Duration: 13 weeks", "40 hours per week", "Shift: 8 hours, days", "Employment Type: Travel" are more like job details (schedule, etc). Could be Requirements. - Requirements: maybe we can list those details. - Qualifications: maybe we don't have specific qualifications like licensure, etc. Not given. - Skills: not given. - Benefits: we have list. - Pay: we have vague; we should not create. - Schedule: we have shift and hours. Thus we will output sections: About the role, Responsibilities (maybe we can put the job description specifics), Requirements (maybe duplicate?), Benefits, Schedule. But we need to avoid thin sections. Let's think: Could combine Responsibilities and Requirements into one? But we must follow headings list; we can choose which to include. Better: About the role: brief role description. Responsibilities: maybe we can list duties? Not given. Could skip Responsibilities if no specific content. Requirements: we can list the specifics: Specialty, Discipline, Start Date, Duration, hours, shift, employment type. That's substantive. Qualifications: maybe we can include licensure & CEU reimbursement? That's a benefit not qualification. Not given. Skills: none. Benefits: list. Schedule: we already have shift/hours in Requirements; but schedule could be separate. However we might duplicate. The rule: Prefer a few substantive sections over many thin ones. So maybe we include Schedule separately and not include shift/hours in Requirements. But Requirements would then be missing those details. Could we put shift/hours under Schedule and keep Requirements as specialty, discipline, start date, duration, employment type? That seems reasonable. Thus: About the role: "Anders Group is seeking a travel Speech Language Pathologist for a travel job in Danville, Virginia." Requirements: list: - Specialty: Speech Language Pathologist - Discipline: Therapy - Start Date: ASAP - Duration: 13 weeks - Employment Type: Travel Schedule: - 40 hours per week - Shift: 8 hours, days Benefits: list unique benefits. We also need to include maybe "About Anders Group" content? That's not a heading we have; but we could put under About the role? Actually About the role is about the job, not company. The company description could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the Anders Group description somewhere. Where could it fit? Possibly under About the role? But that's not accurate. Could we create a section "About Anders Group"? Not in allowed headings list. The allowed headings are only those listed; we cannot create other headings. So we must fit that content into one of the allowed headings. Perhaps we can put it under "About the role" as a description of the employer? But that seems off. However the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning examples, not exclusive? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we need to map company info to one of those. Perhaps "About the role" can include both role and employer info. We'll include a brief description of Anders Group within that section. Thus About the role will contain: "Anders Group is seeking a travel Speech Language Pathologist for a travel job in Danville, Virginia. Anders Group is a Joint Commission–accredited healthcare staffing agency focused 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." We need to preserve all substantive information from Anders Group description: they talk about benefits, etc. But we already have benefits section. We should not duplicate benefits. The Anders Group description includes a list of benefits; we already have benefits section. We should not repeat them. So we can summarize the Anders Group description but not repeat benefits list. However we must preserve ALL substantive information; we cannot omit details like "Day One Health Insurance (with buy-up options)" etc. Those are benefits; we already have them in Benefits section. So it's okay to not repeat them in About the role if we have them elsewhere. But we need to ensure we didn't lose any substantive info: we have benefits list covering those. The Anders Group description also includes "The Anders Difference" paragraph about relationships, quality placements, etc. That's substantive; we should include that somewhere. Could be part of About the role. Thus About the role will include: role description, company overview, mission, difference. Now Responsibilities: we have none specific; maybe we can skip. Requirements: we have specialty, discipline, start date, duration, employment type. Schedule: shift and hours. Benefits: list. Now we need to ensure we don't create sections with placeholder text. Benefits list we have concrete items. Let's compile unique benefits list: From first 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 - Refer

Similar jobs