Jobs · Healthcare · Tennessee

Travel Speech Language Pathologist - $2,327 per week

HealthCare Support · Nashville, TN · 6 days ago
On-siteHealthcareInternship
The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and apply the rules. First, identify sections: - About the role / Job Description: There's a job description with details like specialty, discipline, start date, duration, hours, shift, employment type, job ID, pay package info. - About Healthcare Support: This is a company description. - Benefits: Listed at the end. Rules: - Use

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 (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and 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, parse the content: The posting starts with: "Healthcare Support is seeking a travel Speech Language Pathologist for a travel job in Nashville, Tennessee." That's a prose intro. Then "Job Description & Requirements" with bullet-like lines: Specialty: Speech Language Pathologist Discipline: Therapy Start Date: ASAP Duration: 13 weeks 36 hours per week Shift: 12 hours Employment Type: Travel Healthcare Support Job ID #528070. 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: speech language pathologist (slp) This is metadata about the job. Could be under "About the role" or "Job details". Since there's no separate responsibilities/requirements list, maybe combine into a "Job details" section. But the rules suggest headings like "About the role", "Responsibilities", "Requirements", etc. The posting doesn't have explicit responsibilities or requirements lists. It has a description of the company and benefits. The "About Healthcare Support" section is a prose paragraph about the company. Benefits list: License and certification reimbursement, Medical benefits, Dental benefits, Mileage reimbursement, Employee assistance programs, Referral bonus, 401k retirement plan, Holiday Pay, Weekly pay. Pay information: "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." That's a pay detail, but not a specific pay range. The rule says never create Pay section unless posting actually states them. It does state pay package details, but it's vague. Could include in "Job details" or "Pay". Since it's mentioned, maybe include a Pay section with that info. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package info, so we can include a Pay section. However, the pay info is not a specific number, but it's substantive. I'll include a Pay section with that detail. Schedule: The posting mentions "36 hours per week", "Shift: 12 hours". That's schedule info. Could include a Schedule section. But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine job details, pay, schedule into one "Job details" section? However, the suggested headings include "Pay" and "Schedule" as separate. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those if content exists. Let's decide sections: 1. About the role: Could include the introductory sentence and the job description details. 2. Pay: The pay package description. 3. Schedule: The hours and shift. 4. About Healthcare Support: The company description. 5. Benefits: The list. But the job description details include start date, duration, etc. That's more like "Job details". The heading "About the role" is appropriate for a summary. The posting doesn't have responsibilities or requirements lists, so we won't create those sections. We must not repeat job title as heading. The page already shows it. Job ID: fold into a short

    or drop. I'll include it in a paragraph in "About the role" or "Job details". Now, structure:

    About the role

    Healthcare Support is seeking a travel Speech Language Pathologist for a travel job in Nashville, Tennessee.

    • Specialty: Speech Language Pathologist
    • Discipline: Therapy
    • Start Date: ASAP
    • Duration: 13 weeks
    • Hours per week: 36
    • Shift: 12 hours
    • Employment Type: Travel
    • Job ID: #528070
    • Posted job title: speech language pathologist (slp)
    But the pay package info is separate. Could be in Pay section.

    Pay

    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.

    Schedule

    36 hours per week, 12-hour shifts.

    But that duplicates info. Maybe combine schedule into About the role. However, the rule says include a section ONLY when the posting has real, specific content for it. The posting has specific schedule info (36 hours/week, 12-hour shifts). That's substantive. But we already have it in the list. Could keep it in the list and not create a separate Schedule section. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but we can choose to include them in a combined section. The instruction says "Prefer a few substantive sections over many thin ones." So maybe combine Pay and Schedule into "Job details" or keep separate? The example headings include Pay and Schedule as separate, but we can decide. I think it's better to have a "Job details" section that includes all the metadata, and then separate Pay if there's a distinct pay description. The pay description is a sentence. Could be part of Job details. But the rule says use

    for section headings like Pay, Schedule. It doesn't forbid combining. I'll create a "Job details" heading (though not in the example list, but "About the role" is). The example list includes "About the role". I'll use "About the role" for the introductory paragraph and the list of details. Then separate "Pay" and "Schedule" if they have distinct content. But the pay content is one sentence, schedule is already in the list. To avoid thin sections, I'll include pay info in the "About the role" list or as a separate paragraph. However, the pay info is about pay package, which is a specific topic. The benefits are listed separately. I'll create a "Pay" section with that sentence. For schedule, it's already in the list, so I won't create a separate Schedule section. Now, "About Healthcare Support" is a prose paragraph. That's a company description. Could be under "About the company" but the example headings don't include that. The example includes "About the role". Could use "About Healthcare Support" as heading? The rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g.", so we can use other headings if appropriate. But to stay consistent, maybe use "About the company" or "Company overview". However, the posting says "About Healthcare Support". I'll use that as heading. Benefits: list. Now, ensure no boilerplate: The posting includes "Pst! Ask us about our Direct Hire Opportunities!" That's promotional, maybe keep? It's part of the company description. I'll include it in the company paragraph. Also, "Don’t get lost in the shuffle of another overblown staffing agency. Choose HealthCare Support to be your trusted partner that you can rely on for all your travel assignments. We can’t wait to hear about the amazing adventures you’ll have!" That's marketing prose. Keep as part of company description. Now, output HTML fragment. Let's write:

    About the role

    Healthcare Support is seeking a travel Speech Language Pathologist for a travel job in Nashville, Tennessee.

    • Specialty: Speech Language Pathologist
    • Discipline: Therapy
    • Start Date: ASAP
    • Duration: 13 weeks
    • Hours per week: 36
    • Shift: 12 hours
    • Employment Type: Travel
    • Job ID: #528070
    • Posted job title: speech language pathologist (slp)

    Pay

    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.

    About Healthcare Support

    Healthcare Support excels at providing a streamlined and red-carpet experience for our travelers. Whether you are a nurse, a therapist, or an allied health professional, our goal is to connect you with top-rated facilities throughout the country and get you on the road to your next adventure. We leverage 20 years of relationships with the industry’s most respectable companies across all 50 states, both through direct client partnerships and via national MSP programs. From health systems and hospitals to specialty clinics and post-acute facilities, you can work where you want to work and go where you want to go. Not only does HealthCare Support reimburse for relocation and travel costs on your first check, but we also offer license and certification reimbursements required for your assignments so that you can focus on building your career. During your assignment, you’ll have access to medical benefits, 24/7 support from our Clinical Advocacy Team, and a travel team with stateside operations. Your travel team will include a designated credentialing expert to help you navigate every step of the on-boarding process, a payroll specialist who you can communicate with directly, and a skilled recruiter who takes the time to understand your needs and works hard to find the right position for you. Don’t get lost in the shuffle of another overblown staffing agency. Choose HealthCare Support to be your trusted partner that you can rely on for all your travel assignments. We can’t wait to hear about the amazing adventures you’ll have! Pst! Ask us about our Direct Hire Opportunities!

    Benefits

    • License and certification reimbursement
    • Medical benefits
    • Dental benefits
    • Mileage reimbursement
    • Employee assistance programs
    • Referral bonus
    • 401k retirement plan
    • Holiday Pay
    • Weekly pay
    Check for any duplicate or boilerplate: The posting includes "Healthcare Support Job ID

Similar jobs