Travel Physical Therapist - $1,663 per week

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections. The posting has: - Job details (specialty, discipline, start date, duration, hours, shift, employment type, location) - About Triage Staffing (company description) - Benefits list Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  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 structure: The job details are metadata: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Location, Shift Details, Length. These are not really "About the role" but more like job metadata. The rules say fold minor metadata into a short

  or drop it. But they are substantive details about the assignment. I think we can create a "Job Details" section or "Assignment Details" but the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The rules say 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: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the typical ones. However, we should include a section ONLY when the posting has real, specific content for it. The posting doesn't have explicit Responsibilities, Requirements, Qualifications, Skills sections. It has "About Triage Staffing" and "Benefits". Also there is a list of what they offer (competitive pay packages, one point of contact, etc.) which could be "Benefits" or "What We Offer". But the Benefits section is explicitly listed later with bullet points. The posting has: - A paragraph about Triage Staffing philosophy. - A bullet list of what they offer (competitive pay packages, one point of contact, etc.) - A "Benefits:" heading with a list of benefits. We need to preserve all substantive information. The job metadata (start date, duration, shift, etc.) should be included. Since there's no "About the role" section, maybe we can create a "Job Details" heading? But the allowed headings are examples. 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 prefer those. However, the job details are not responsibilities or requirements. They are assignment details. Could be "Schedule" but schedule is only shift. There's no Pay section (though they mention competitive pay packages but not specifics). The Benefits section is explicit. I think we can create: -

  Assignment Details

  with a
  of the metadata? But the rule says use
  • for any list of duties/requirements/benefits. Metadata is not duties/requirements/benefits. Could be a

    with the details. But there are many lines. Could be a

    of details. The rule says "use
    • for any list of duties/requirements/benefits". It doesn't say we cannot use for other lists. But we should follow semantic HTML. A definition list might be better but not required. The instruction says use
      • for any list of duties/requirements/benefits, and

        for prose. So for metadata, maybe a

        with line breaks? But we can't use
        ? Not specified. Could use a

        for the details as a list of facts. I think it's acceptable. But the rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So we should fold metadata into a short

        . However, there is a lot of metadata: Start Date, Duration, Hours per week, Shift, Employment Type, Location, Shift Details, Length. That's not minor. But the rule says "fold minor metadata into a short

        or drop it." The Job ID is minor. The other details are important for the job. The posting includes them prominently. We should include them. Perhaps we can create a "Job Details" section with a

        of these details. The rule doesn't explicitly forbid other headings. It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples. I think we can use a heading like "Assignment Details" or "Job Details". But to be safe, maybe we can use "Schedule" for shift details? But there's more than schedule. Alternatively, we can include the metadata in a

        at the beginning. But the rule says "Preserve ALL substantive information". So we must include them. Let's look at the posting again: It starts with "Triage Staffing is seeking a travel Physical Therapist for a travel job in Aberdeen, Washington." Then "Job Description & Requirements" but then lists Specialty, Discipline, Start Date, Duration, etc. Then "Apply for specific facility details." Then "Physical Therapist Triage Staffing Job ID #LJKA6RN6. Posted job title: Rehab: Physical Therapy". Then "About Triage Staffing" with prose and a bullet list. Then "Benefits:" with a bullet list. We need to output HTML fragment. We'll omit the job title heading. We'll include a section for "About the Company" or "About Triage Staffing"? The allowed headings include "About the role". Not "About the company". But we can use "About the role" for the company description? That seems off. The company description is not about the role. However, the rule says "include a section ONLY when the posting has real, specific content for it". The posting has "About Triage Staffing" which is about the company. We could create a heading "About Triage Staffing" but the rule says use

        for section headings (e.g. About the role, ...). It doesn't say we cannot use other headings. But the instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This might be a whitelist. However, the example includes "Benefits" which is present. "Pay" and "Schedule" are not explicitly present (though shift details could be schedule). The posting does not have a Pay section. It mentions "Competitive, custom pay packages" but no details. So we should not create a Pay section. Schedule: we have shift details (8 hours, days, 40 hours per week). Could be a Schedule section. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states shift details, so Schedule could be included. But the shift details are part of the metadata. We could create a Schedule section with the shift info. But the posting also has "Benefits:" explicitly. So we must include Benefits section. Now, the "About Triage Staffing" section: we could map to "About the role"? Not appropriate. Maybe we can create a "Company Overview" heading? But the rule says use

        for section headings (e.g. ...). It might be okay to use a custom heading. However, the instruction says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as "use these headings". But the posting doesn't have Responsibilities, Requirements, etc. So we only include sections that have content. The posting has company description and benefits. Also the job metadata. I think the best is to create: - A

        for the introductory sentence (Triage Staffing is seeking...) - A

        Job Details

        with a
        of the metadata (Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Location, Length). But the rule says "use
        • for any list of duties/requirements/benefits". This is not duties/requirements/benefits. But it's a list. Could be a but not required. I'll use
          for simplicity. - A

          About Triage Staffing

          with the prose and the bullet list of what they offer (competitive pay packages, etc.) That bullet list is not benefits per se, but what they offer. Could be part of the company description. - A

          Benefits

          with the benefits list. But the rule says "never emit a heading followed by filler/placeholder text". So we must ensure each section has real content. Also, we must remove duplicated lines. The posting has "Physical Therapist Triage Staffing Job ID #LJKA6RN6. Posted job title: Rehab: Physical Therapy" which is duplicate of title and job ID. We should fold Job ID into a short

          or drop it. We'll drop Job ID. Also "Apply for specific facility details." is application instruction, remove. Now, let's write the HTML. We'll start with a

          for the opening statement: "Triage Staffing is seeking a travel Physical Therapist for a travel job in Aberdeen, Washington." Then Job Details: maybe a

          Assignment Details

          with a
          of the details. But the allowed headings are examples. I'll use "Assignment Details" as a heading. However, 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 others. But to be safe, maybe we can use "Schedule" for shift details? But there's more than schedule. Could use "About the role" for the job details? The job details are about the role. The opening statement is about the role. The "Job Description & Requirements" heading in the posting is generic. The details are specialty, discipline, start date, duration, hours, shift, employment type, location. That's about the role. So we could have

          About the role

          and include those details. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". That's about the job title. "About the role" is a generic heading. It's allowed. The posting doesn't have an explicit "About the role" section, but we can create one with the details. However, the rule says "include a section ONLY when the posting has real, specific content for it". The posting has those details, so yes. But