DirectJobHub
Jobs · Healthcare · Oregon

School Speech Language Pathologist - $2,594 per week

Triage Staffing | Healthcare Staffing · Roseburg, OR · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Job description: "Triage Staffing is seeking a travel School Speech Language Pathologist for a travel job in Roseburg, Oregon." Then "Job Description & Requirements" heading. Details: Specialty: Speech Language Pathologist, Discipline: Therapy, Start Date: ASAP, Duration: 40 weeks, 40 hours per week, Shift: 8 hours, days, Employment Type: Travel, Travel Rehab: Speech Language Pathology Roseburg Location: Roseburg Start Date: 9/8/2026 Shift Details: 8H Days 40 hours per week Length: 40 WEEKS Apply for specific facility details. Then "Speech Therapist/SLTriage Staffing Job ID #GMEKCYUR. Posted job title: Rehab: Speech Language Pathology" Then "About Triage Staffing" paragraph. Then "Benefits:" list. No explicit responsibilities, requirements, qualifications, skills, pay, schedule beyond shift details. We have schedule: 8 hours days, 40 hours per week, length 40 weeks. That's schedule info. Pay: Not mentioned. So we should not create Pay section. Benefits: we have list. About the role: maybe we can include description of role: travel School Speech Language Pathologist in Roseburg, Oregon. Could be a short paragraph. Responsibilities: Not given explicitly. Could we infer? Probably not; we should not invent. So skip Responsibilities. Requirements: Not given explicitly; maybe specialty, discipline, etc. Could treat those as requirements? The posting includes Specialty, Discipline, Start Date, Duration, etc. Those could be considered requirements. But we need to see if they are substantive. They are specifics: Speech Language Pathologist, Therapy, ASAP start, 40 weeks, 40 hrs/week, 8 hour days, travel. Those could be considered job requirements. However the instruction: "Use
  • for any list of duties/requirements/benefits". So we could create a Requirements section with list items: Specialty: Speech Language Pathologist; Discipline: Therapy; Start Date: ASAP; Duration: 40 weeks; Hours: 40 per week; Shift: 8 hours, days; Employment Type: Travel; Location: Roseburg, Oregon. But we need to avoid repeating job title as heading. That's fine. Qualifications: Not given; maybe none. Skills: Not given. Pay: none. Schedule: we have schedule details; could be separate Schedule section. But we already have schedule info in requirements; maybe better to have Schedule section with details: 8 hour days, 40 hours per week, length 40 weeks, start date ASAP (or 9/8/2026). However start date appears twice: ASAP and 9/8/2026. We need to preserve all substantive info; we can include both. We must not create sections with filler like "not specified". So we include only those with content. Thus sections: About the role (paragraph), Requirements (list), Benefits (list), Schedule (list). Possibly also "Qualifications" if we have any like "Speech Language Pathologist license"? Not given. So skip. We need to ensure we don't include boilerplate like EEO etc. The About Triage Staffing paragraph is not boilerplate? It's promotional but it's part of posting; we can include as About the role? Actually About Triage Staffing is about the company, not the role. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role section; we could put the description of the role there. The About Triage Staffing paragraph is more about the company; maybe we could incorporate into About the role? But it's not about the role. However we could still include as part of About the role? Might be considered filler? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep the About Triage Staffing paragraph somewhere. Where? Could be a separate section like "About the company" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. The About Triage Staffing paragraph is about the company, not the role. But maybe we can treat it as "About the role" because it's describing the employer? Might be acceptable. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not strict limitation? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we need to map all content to those sections. Thus we can put the About Triage Staffing paragraph under About the role (maybe as a brief description of the employer). That's okay. Now we need to ensure we don't repeat job title as heading. We'll not. We'll output HTML fragment:

    About the role

    Triage Staffing is seeking a travel School Speech Language Pathologist for a travel job in Roseburg, Oregon.

    At Triage, we prefer to be real. Real about expectations—both ours and yours. Real about how a decision you make today could affect your tomorrows. Real about how compensation actually works. Real about how great—or grating—your next supervisor may be. Being real allows everyone at Triage to be ready. Ready to serve you with real honesty. So if that gig near the ocean is really no day at the beach, or that third shift comes with a second-class rate, we tell you. So you can be ready, too. We staff all five major divisions of acute care—nursing, lab, radiology, cardiopulmonary and rehab therapy, offering: - Competitive, custom pay packages - One point of contact for both travelers and facilities (per division) - A reliable recruiter who's got your back throughout your entire assignment - In-house compliance and accounting specialists - A clinical liaison team available 24/7 to offer medical and professional support and career development - A mentoring program that is run and managed by actual clinicians—yeah, you read that right - And more (because of course there’s more) Are we the biggest? No. Are we the best? That’s rather subjective, but we’re trying to be. Will we work like hell to get you as close to your idea of heaven as possible? Yes. Yes, we will.

    But note that the bullet list in that paragraph includes dash lines; we should convert to
    • for list. The instruction: Use
      • for any list of duties/requirements/benefits. The list under About Triage Staffing is a list of offerings; could be considered benefits? But it's more about company offerings. Might be better to keep as
        • . However the paragraph includes the dash list inline; we should extract them as list. Let's parse the About Triage Staffing paragraph: After "offering:" there is a list: - Competitive, custom pay packages - One point of contact for both travelers and facilities (per division) - A reliable recruiter who's got your back throughout your entire assignment - In-house compliance and accounting specialists - A clinical liaison team available 24/7 to offer medical and professional support and career development - A mentoring program that is run and managed by actual clinicians—yeah, you read that right - And more (because of course there’s more) Then after that there are sentences: "Are we the biggest? No. Are we the best? That’s rather subjective, but we’re trying to be. Will we work like hell to get you as close to your idea of heaven as possible? Yes. Yes, we will." We should keep those sentences as

          . Thus About the role section: first paragraph describing the role, then

          • list of offerings, then

            for the remaining sentences. Now Requirements section: list items: Specialty: Speech Language Pathologist; Discipline: Therapy; Start Date: ASAP (also 9/8/2026); Duration: 40 weeks; Hours: 40 per week; Shift: 8 hours, days; Employment Type: Travel; Location: Roseburg, Oregon. We could combine start date both ASAP and 9/8/2026 as separate items. Schedule section: maybe we can include shift details: 8 hour days, 40 hours per week, length 40 weeks, start date ASAP/9/8/2026. But we already have start date in requirements; maybe schedule just includes shift pattern and length. We need to avoid duplication? The instruction says preserve ALL substantive information; duplication is okay if it's in original? But we should not invent. Duplication is okay if it's present in original; but we could avoid repeating same info in two sections if it's redundant. However we have start date appearing in both "Job Description & Requirements" and later "Shift Details". It's same info; we could include once. Better to put start date in Requirements, and schedule includes shift pattern and length. Thus Schedule section:

            • Shift: 8 hours, days
            • Hours per week: 40
            • Assignment length: 40 weeks
            Benefits section: list from Benefits: Day One comprehensive, nationwide insurance plans for health, vision and dental and life—including a HSA option; Day One 401(k) program with employer-matching contributions once eligible; Facility cancelling protection—your time is money on and off-the-clock; Guaranteed hours; Weekly paychecks via direct deposit; Earned vacation bonuses for time worked; Paid holidays; Employee assistance program (EAP)—your mental health is important, too; Continuing education, certification and licensing reimbursement; Workers comp—because accidents happen; Top-rated professional liability insurance; Company provided housing options; Referral bonus—$750 in your pocket after they’ve completed a 13-week assignment. We need to convert each bullet to
          • . Now ensure we don't include any boilerplate like EEO etc. Not present. Now output HTML fragment. We must not include or . Just the fragment. Let's craft. We need to be careful with HTML escaping: apostrophes fine. Let's produce:

            About the role

            Triage Staffing is seeking a travel School Speech Language Pathologist for a travel job in Roseburg, Oregon.

            • Competitive, custom pay packages
            • One point of contact for both travelers and facilities (per division)
            • A reliable recruiter who's got your back throughout your entire assignment
            • In-house compliance and accounting specialists
            • A clinical liaison team available 24/7 to offer medical and professional support and career development
            • A mentoring program that is run and managed by actual clinicians—yeah, you read that right
            • And more (because of course there’s more)

            Are we the biggest? No. Are we the best? That’s rather subjective, but we’re trying to be. Will we work like hell to get you as close to your idea of heaven as possible? Yes. Yes, we will.

            Requirements

            • Specialty: Speech Language Pathologist
            • Discipline: Therapy
            • Start Date: ASAP (9/8/2026)

Similar jobs