Travel Speech Language Pathologist - $2,660 per week

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 Newberg, Oregon." That's an intro paragraph. Then "Job Description & Requirements" with bullet-like lines: Specialty: Speech Language Pathologist Discipline: Therapy Start Date: 11/02/2026 Duration: 13 weeks 40 hours per week Shift: 8 hours Employment Type: Travel Healthcare Support Job ID #529614. Pay package is based on 8 hour shifts and 40.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 explicit responsibilities or requirements listed, maybe just a "Job details" section? But the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the role" could encompass this metadata. However, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use "About the role" for the job description metadata. Then "About Healthcare Support" is a company description. That could be a section "About the company" but not in the example list. The example list includes "About the role". Could we use "About the company"? The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so maybe we can use other headings? But the instruction: "include a section ONLY when the posting has real, specific content for it". The company description is substantive. However, the allowed headings are suggested; we can use other headings if needed? The rule says "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 stick to those if possible. "About the role" is for the role, not company. Maybe we can put company description under "About the role"? That seems odd. Could create a section "About Healthcare Support" but not in the list. The instruction says "use

  for section headings (e.g. ...)" meaning those are examples, but we should use appropriate headings. However, the user might expect only those headings. But the company description is a significant part. I think we should include it as a section, maybe "About the company" or "About Healthcare Support". But the rule says "never emit a heading followed by filler/placeholder text". The company description is real content. But the instruction also says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can fold Job ID into a paragraph. Now, Benefits are listed at the end: License and certification reimbursement, Medical benefits, Dental benefits, Mileage reimbursement, Employee assistance programs, Referral bonus, 401k retirement plan, Holiday Pay, Weekly pay. That's a clear Benefits section. Pay: The posting says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's pay information. Should we include a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay package details, albeit vague. It says "tax-free stipend amount to be determined." That's not a specific pay rate. But it does mention pay package basis. Could include a Pay section with that info. However, the rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The pay info says "tax-free stipend amount to be determined." That's essentially TBD. So maybe we should not create a Pay section because it's not specific. But the posting does have a sentence about pay package. Could fold into "About the role" or "Job details". The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay, but it's vague. I'd lean to not create a separate Pay section, but include the pay info in the job details. Schedule: The posting includes "40 hours per week", "Shift: 8 hours", "Duration: 13 weeks", "Start Date: 11/02/2026". That's schedule info. Could create a Schedule section? The rule says never create Schedule section unless posting actually states them. It does state schedule details. But again, the example headings include Schedule. Could include a Schedule section with those details. However, the rule says "Prefer a few substantive sections over many thin ones." So maybe combine schedule details into "About the role" or "Job details". But the user might expect a Schedule section if there is schedule info. Let's see: The posting has "40 hours per week", "Shift: 8 hours", "Duration: 13 weeks", "Start Date: 11/02/2026". That's substantive schedule info. I think we can create a Schedule section with a list. But the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Schedule is an allowed heading. Since there is schedule info, we can include a Schedule section. Similarly, Pay info is vague, but we could include a Pay section with the given sentence. However, the rule says never create Pay section unless posting actually states them. It does state a pay package description. But it's not a specific pay rate. The example of filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". The posting says "tax-free stipend amount to be determined." That's essentially TBD. So I'd avoid a Pay section. Now, Responsibilities, Requirements, Qualifications, Skills: The posting does not list any specific responsibilities, requirements, qualifications, or skills beyond the specialty and discipline. So we should not create those sections. Thus, sections: 1. About the role (or Job details) - includes the intro paragraph and the metadata list. 2. Schedule - includes start date, duration, hours per week, shift. 3. About Healthcare Support - company description. 4. Benefits - list of benefits. But "About Healthcare Support" is not in the example headings. Could we use "About the company"? The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it's implied we should use those. However, the company description is a significant part of the posting. The user might want it included. The instruction: "Preserve ALL substantive information". So we must include it. We can create a section with heading "About Healthcare Support". That seems appropriate. Alternatively, we could fold the company description into "About the role"? That would be weird. I'll create sections: - About the role - Schedule - About Healthcare Support - Benefits Now, format each. About the role: Include the opening paragraph: "Healthcare Support is seeking a travel Speech Language Pathologist for a travel job in Newberg, Oregon." Then the metadata as a list? The metadata lines are key-value pairs. Could present as a list of items. Use

  • for each line. But some are not duties/requirements/benefits, but metadata. The rule says "Use
    • for any list of duties/requirements/benefits, and

      for prose." Metadata could be considered a list of details. I'll use a list. But the rule says "Use

      • for any list of duties/requirements/benefits". It doesn't forbid using for other lists. But we can also use

        for each line. However, a list is cleaner. I'll do:

        About the role

        Healthcare Support is seeking a travel Speech Language Pathologist for a travel job in Newberg, Oregon.

        • Specialty: Speech Language Pathologist
        • Discipline: Therapy
        • Employment Type: Travel
        • Job ID: 529614
        • Pay package based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
        But note: Start Date, Duration, hours per week, shift are schedule-related. Should they go in Schedule section? Yes, move them to Schedule. So About the role includes only the intro and maybe specialty, discipline, employment type, job ID, pay package note. Schedule section:

        Schedule

        • Start Date: 11/02/2026
        • Duration: 13 weeks
        • Hours per week: 40
        • Shift: 8 hours
        About Healthcare Support: The company description is a few paragraphs. Use

        for each paragraph. Benefits: List of benefits. Now, check for any boilerplate to remove: The posting includes "Pst! Ask us about our Direct Hire Opportunities!" That's promotional, maybe keep? It's part of company description. Could include in About Healthcare Support. 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 part of company description. Now, ensure no duplicate lines. The posting has "Healthcare Support Job ID #529614." and "Posted job title: speech language pathologist (slp)". The job title is already known, we can drop the posted job title line