Travel Physical Therapy Assistant - $1,286 per week

We need to output HTML fragment with sections for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content for it. So we need to parse the posting. The posting: "Triage Staffing is seeking a travel Physical Therapy Assistant for a travel job in Taos, New Mexico. Job Description & Requirements Specialty: Physical Therapy Assistant Discipline: Therapy Start Date: 09/14/2026 Duration: 13 weeks 40 hours per week Shift: 8 hours, days Employment Type: Travel Travel Rehab: Physical Therapy Taos, NM Location: Taos, NM Start Date: 9/14/2026 Shift Details: 8H Days 40 hours per week Length: 13 WEEKS Apply for specific facility details. Physical Therapy Assistant Triage Staffing Job ID #PDAGGYAW. Posted job title: Rehab: Physical Therapy About Triage Staffing At Triage, we prefer to be real... (long paragraph) 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 extract sections: - About the role: maybe the description of the job: travel Physical Therapy Assistant in Taos, NM; specialty, discipline, start date, duration, hours, shift, employment type. Could be "About the role" section. - Responsibilities: Not explicitly listed. The posting does not give duties/responsibilities. So we should not create a Responsibilities section if no specific content. - Requirements: Could include specialty, discipline, maybe license? Not explicit. It mentions "Physical Therapy Assistant" as specialty. Could treat as Requirements? But we need real specific content. The posting includes "Specialty: Physical Therapy Assistant", "Discipline: Therapy". Those could be considered Requirements. But we need to decide if we should create a Requirements section. The instruction: include a section ONLY when the posting has real, specific content for it. So we can include Requirements if we have specifics like "Physical Therapy Assistant specialty", "Therapy discipline". That's specific enough. Could also include "Start Date", "Duration", "Hours", "Shift", "Employment Type". Those could be under "About the role" or "Job Details". But we have limited headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put job details under About the role. Requirements could be license/certification but not given. Might be better to not create Requirements if not specific. However we have "Specialty: Physical Therapy Assistant" and "Discipline: Therapy". Those could be considered Requirements. But we also have "Start Date", etc. Those are more about the job details. We could create About the role: includes location, start date, duration, hours, shift, employment type. Then Benefits section: list of benefits. Pay: not specified (no pay amount). So we should NOT create Pay section because no specific pay. Schedule: we have shift details (8 hours, days, 40 hours per week). That's schedule info. Could create Schedule section with that info. However schedule may be considered part of About the role. But we have a specific heading for Schedule; we can include if we have real specific content. The posting says "Shift: 8 hours, days", "40 hours per week". That's schedule. So we can create Schedule section. Qualifications: Not given. Skills: Not given. Responsibilities: Not given. Thus we will have sections: About the role, Benefits, Schedule. Possibly also Requirements if we want to include specialty/discipline. But we can incorporate those into About the role as well. Let's see: About the role could include specialty, discipline, location, start date, duration, hours, shift, employment type. That seems comprehensive. Benefits: list as

  • . Schedule: maybe we already included shift/hours in About the role; but we can still create Schedule section with shift details. However we must avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication but better to not duplicate. However we could put schedule details in Schedule section and not repeat in About the role. But About the role would then lack schedule info. We could keep About the role with location, start date, duration, employment type, and maybe specialty/discipline. Then Schedule section with shift/hours. That seems okay. Let's extract: About the role: - Travel Physical Therapy Assistant position in Taos, New Mexico. - Specialty: Physical Therapy Assistant - Discipline: Therapy - Start Date: September 14, 2026 (09/14/2026) - Duration: 13 weeks - Employment Type: Travel Schedule: - Shift: 8 hours, days - Hours per week: 40 hours Benefits: list as given. We need to format benefits as list items. The benefits paragraph: "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 split into sensible list items. Could separate by concepts: Day One comprehensive nationwide insurance plans for health, vision, dental, and life (including HSA option); Day One 401(k) program with employer-matching contributions once eligible; Facility cancelling protection; Guaranteed hours; Weekly paychecks via direct deposit; Earned vacation bonuses for time worked; Paid holidays; Employee assistance program (EAP); Continuing education, certification and licensing reimbursement; Workers compensation; Top-rated professional liability insurance; Company provided housing options; Referral bonus—$750 after completing a 13-week assignment. We'll make each as
  • . Now output HTML fragment: start with

    About the role

    then

    ... maybe combine into paragraph with semicolons or separate sentences. Could also use

    for details but instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. So About the role is prose, not a list. So we put

      containing the description. Similarly Schedule: could be prose or list? It's details; could be prose. We'll use

      . Benefits: list. Make sure no extra whitespace? It's fine. We must not include or . Just fragment. Let's craft. About the role paragraph: "Triage Staffing is seeking a travel Physical Therapy Assistant for a travel assignment in Taos, New Mexico. The position specializes in Physical Therapy Assistant within the Therapy discipline, with a start date of September 14, 2026, a duration of 13 weeks, and is structured as a travel employment type." Schedule paragraph: "The assignment involves an 8‑hour day shift, totaling 40 hours per week." Benefits list: as above. Check for any other info: "Apply for specific facility details." That's boilerplate/application instruction; remove. "Triage Staffing Job ID #PDAGGYAW. Posted job title: Rehab: Physical Therapy" - remove Job ID and posted job title as per instruction. Also remove "About Triage Staffing" paragraph? That's about the company, not the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Triage Staffing" is not boilerplate but is company description. Should we keep? It's not about the role; it's about the company. The instruction says preserve ALL substantive information; but we are to reformat a job posting into clean, well-structured semantic HTML. The "About Triage Staffing" is substantive info about the company. However the allowed headings are limited to About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no heading for "About the company". So we cannot create a heading for it. Should we drop it? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid including content outside those headings? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. If we have content that doesn't fit under those headings, we could still put it in a

      without a heading? The instruction says use

      for section headings (list). It doesn't say we cannot have other headings, but it says use

      for section headings (e.g. About the role...). It implies we should use those headings for sections. It doesn't forbid other headings, but to be safe we should stick to those. The company description could be placed under About the role? Not really. Could be placed as a

      without a heading? The instruction says use

      for section headings (e.g. About the role...). It doesn't say we must have a heading for every block, but we should use those headings for sections. Could we have a

      without preceding

      ? Possibly yes, but then it's not a section. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So if we want to make a section, we use h3. If we have a paragraph that's not a section, we could just use

      . The company description could be a

      without heading. However the instruction also says "Prefer a few substantive sections over many thin ones." So maybe we incorporate company description into About the role? Might be okay to add a sentence about the company. But About the role is about the role, not company. However we could expand About the role to include a brief note about the staffing agency. That might be acceptable. Alternatively we could create a section "About the role" and include both role details and company description. That would be a bit mixing but still substantive. Given the instruction to preserve ALL substantive information, we should not drop the company description. So we need to include it somewhere. The best place is maybe a

      after the About the role heading, but still under that heading. That would be okay: the About the role section includes both role details and company info. It's still a section. Thus About the role paragraph will include: travel PT Assistant in Taos, NM; specialty, discipline, start date,