Travel Physical Therapy Assistant - $1,147 per week

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse the job posting. Content: - Title: Physical Therapy Assistant (travel) - Location: Albuquerque, New Mexico - Specialty: Physical Therapy Assistant - Discipline: Therapy - Start Date: ASAP - Duration: 12 weeks - 40 hours per week - Shift: 8 hours, days - Employment Type: Travel Then description: "Ardor Health Solutions is seeking dedicated and compassionate nurses and therapy professionals for travel assignments across the United States..." This is generic company description. Then "Ardor Health Solutions Job ID #JPC -1493404. Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Then "Posted job title: Physical Therapist Assistant" Then "About Ardor Health Solutions" paragraph. Then benefits list: Weekly pay, Holiday Pay, Pet insurance, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1, License and certification reimbursement, Life insurance, Discount program. Also mention free medical insurance plan. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So no

Physical Therapy Assistant. We need to include sections only if real specific content. Potential sections: - About the role: could include description of role? The posting includes "Specialty: Physical Therapy Assistant Discipline: Therapy Start Date: ASAP Duration: 12 weeks 40 hours per week Shift: 8 hours, days Employment Type: Travel". That's role specifics. Could be under "About the role". Also location. - Responsibilities: Not explicitly listed. The generic description about Ardor Health is not responsibilities. No specific duties listed. So we should not create Responsibilities section if no specific content. - Requirements: Not listed explicitly (no licensure, experience). So skip. - Qualifications: Not listed. - Skills: Not listed. - Benefits: We have a list. So include Benefits section with

• items. - Pay: There is mention: "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague but mentions pay package based on shifts, tax-free stipend amount to be determined. It's not a specific number, but it's still some info about pay. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 8 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's stating something about pay, albeit not specific. Should we include? The rule says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here we have "tax-free stipend amount to be determined" which is TBD. Also "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation)". That's somewhat vague but not exactly placeholder like TBD? It says based on 8 hour shifts and 40 hours per week (subject to confirmation). That's still somewhat generic but it's stating the basis. Might be considered placeholder? The rule says avoid filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "tax-free stipend amount to be determined" is TBD essentially. So we should avoid creating a Pay section if it's just TBD. However we could still include Pay section with the info we have? The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That is stating something, albeit not specific numbers. I'd lean to include Pay section but ensure we don't include placeholder text like "tax-free stipend amount to be determined"? That is part of the content; we must preserve ALL substantive information; do NOT invent or summarize away detail. So we must include that statement. It's not invented. So we can include Pay section with that sentence. - Schedule: We have shift: 8 hours, days; 40 hours per week. That's schedule info. So we can include Schedule section. - Benefits: we have list. - About the role: we can include location, specialty, start date, duration, etc. We need to not include duplicated lines. Ensure we don't repeat. We need to wrap content in appropriate tags:

  for section headings,

  • for lists,

    for prose. We should not include or . We need to output only HTML fragment. Let's craft: maybe not needed; just headings and content. We'll have:

    About the role

    Location: Albuquerque, New Mexico. Specialty: Physical Therapy Assistant. Discipline: Therapy. Start Date: ASAP. Duration: 12 weeks. Schedule: 40 hours per week, 8‑hour day shifts. Employment Type: Travel.

    That's prose. Then maybe

    Benefits

    • Weekly pay
    • Holiday Pay
    • Pet insurance
    • Referral bonus
    • Employee assistance programs
    • Medical benefits
    • Dental benefits
    • Vision benefits
    • Benefits start day 1
    • License and certification reimbursement
    • Life insurance
    • Discount program
    Note: Also free medical insurance plan mentioned earlier. Should we include? It's part of benefits: "Ardor Health is pleased to offer a free medical insurance plan in addition to major medical plans." So add that as a bullet. Add
  • Free medical insurance plan (in addition to major medical plans)
  Now Pay section:

  Pay

  Pay package is based on 8‑hour shifts and 40 hours per week (subject to confirmation) with tax‑free stipend amount to be determined.

  Schedule section:

  Schedule

  8‑hour day shifts, 40 hours per week.

  We should avoid duplication: we already mentioned schedule in About the role; but it's okay to have separate Schedule section with specifics. Check for any other sections: Responsibilities? Not present. Requirements? Not present. Qualifications? Not present. Skills? Not present. We must not include Job ID / requisition numbers as headings; we can fold minor metadata into a short

  or drop it. The Job ID appears: "Ardor Health Solutions Job ID #JPC -1493404." We could drop it or include in a short p under About the role maybe. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include it in a short p maybe under About the role or separate small p. Since it's minor metadata, we can include a short p after the heading maybe. But we should not create a heading for it. We'll just include it in a

  after About the role maybe. But we already have About the role p; we could add the Job ID there. However that might clutter. Better to add a separate

  for minor metadata after About the role but before Benefits. Let's do:

  About the role

  Location: Albuquerque, New Mexico. Specialty: Physical Therapy Assistant. Discipline: Therapy. Start Date: ASAP. Duration: 12 weeks. Schedule: 40 hours per week, 8‑hour day shifts. Employment Type: Travel.

  Job ID: JPC‑1493404.

  That's fine. Now ensure we didn't repeat any content. Check Benefits list: includes "Weekly pay" (already mentioned in pay? but it's a benefit). It's okay. Now ensure we didn't include any boilerplate like "Ardor Health Solutions formed in 2001..." That's company description; not a specific section heading. Should we include that? It's not under any of the allowed headings (About the role, Responsibilities, etc). Could be considered "About the company" but not a permitted heading. The instructions: 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 those, we should either incorporate into existing sections or drop if not relevant. The company description is not required to be preserved? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive information. But we cannot create a heading outside the allowed list. However we could incorporate that info into an existing section like "About the role" maybe? But it's about the company, not the role. Could we add a

  without a heading? The instruction says use

  for section headings,

  • for any list,

    for prose. It doesn't forbid having

    without a heading; just says use those tags appropriately. So we can have a

    with company description without a heading. That's allowed. The instruction about headings is only for those specific headings; we can have other

    content. Thus we can add a

    after About the role (or before Benefits) containing the company description paragraphs. We need to ensure we don't include duplicated lines. The company description appears twice? There's a paragraph about Ardor Health Solutions seeking dedicated and compassionate nurses... and then later "About Ardor Health Solutions" paragraph. They are similar but not identical. We should preserve both? They are somewhat repetitive but both are substantive. We could combine? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we combine, we might lose some nuance. Better to keep both as separate paragraphs. Thus we will have:

    Ardor Health Solutions is seeking dedicated and compassionate nurses and therapy professionals for travel assignments across the United States. Our opportunities span a wide range of specialties and settings — including home health, acute care, skilled nursing facilities, outpatient clinics, and more — giving you the flexibility to grow your career while exploring new locations. Whether you're a registered nurse providing skilled care in a patient's home, a physical therapist working in an outpatient clinic, or a speech-language pathologist in an acute care setting, Ardor Health is committed to matching you with assignments that align with your clinical expertise and personal goals. As an Ardor Health traveler, you'll benefit from competitive pay packages, comprehensive benefits, and a recruiter who specializes in your field and genuinely understands it. We pride ourselves on building real relationships with our clinicians — not just filling shifts. We're here to make the logistics simple so you can focus on what you do best — delivering exceptional patient care. If you're a nurse or therapy professional ready for your next adventure, let's find your perfect fit.

    Then later:

    About Ardor Health Solutions

    but that's not an allowed heading. So we cannot use that heading. We could just treat it as a

    without heading. So we will add another

    with that content. Thus we will have two paragraphs: first generic description, second about Ardor Health Solutions history. Let's capture the second paragraph: "Ardor Health Solutions formed in 2001 and remains a privately held medical staffing business owned