Jobs · Healthcare · Oregon

Travel Physical Therapist job in Medford, OR - Make $2,261 to $2,455/week

Aya Healthcare · Medford, OR · 5 days ago
On-siteHealthcareInternship
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 (profession, pay, assignment length, shift, schedule, openings, start date, charting system) - Requirements (experience, required certifications & skills) - Facility & Unit Information (facility type, charting experience, facility bed count) - Aya Delivers (benefits, support, etc.) 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 short

    or drop - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to sections. The job title is "PT Inpatient Rehab in Medford, OR" — but we shouldn't repeat as heading. We have: - Pay: $2261 to $2455 weekly (specific) - Schedule: 5, 8-Hour 07:00 - 15:00 (specific) - Assignment Length: 13 weeks - Shift: Days - Openings: 1 - Start Date: 11/23/2026 - Charting System: Epic These are details about the role. Could be under "About the role" or "Job Details". The rules mention headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We should use those when appropriate. We have a "Requirements" section with Experience and Required Certifications & Skills. That's a clear Requirements section. We have "Facility & Unit Information" — could be part of "About the role" or separate. We have "Aya Delivers" which lists benefits and support. That's a Benefits section. We also have Pay and Schedule explicitly stated, so we can have Pay and Schedule sections. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, so we can include. However, we should avoid thin sections. For example, Pay is just a range, Schedule is just a line. Could combine into "Job Details" but the rules suggest using specific headings like Pay, Schedule. The example headings include Pay, Schedule. So we can create them. But also "About the role" could encompass the job details. Let's see. The user says: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can choose which to use. We have no explicit "Responsibilities" list. The skills list is more like required skills. There's no duties list. So maybe no Responsibilities section. We have "Requirements" with experience and certifications/skills. That's a Requirements section. We have "Skills" listed as a list of skills. Could be a Skills section, but it's under Requirements. Might be part of Requirements. We have "Benefits" from Aya Delivers. We have "Pay" and "Schedule" explicitly. We have "Facility & Unit Information" — could be part of About the role. Let's structure: - About the role: includes profession, assignment length, shift, openings, start date, charting system, facility info. - Pay: the weekly pay range. - Schedule: the schedule details. - Requirements: experience and required certifications & skills. - Benefits: the Aya Delivers benefits. But note: "Aya Delivers" includes more than benefits: it includes competitive advantage, expedited licensing, career guidance, support system, benefits. That's a mix. Could be "Benefits" or "Why Aya". But the rule says use Benefits for benefits. The benefits listed: premium medical, dental, vision, life insurance day one, keep insurance up to 24 days between assignments, 401(k) match, paid company housing or housing stipend, paid sick time, continuing education, licensure/relocation reimbursements. That's substantive. Also note: "Pay listed above includes taxable wages and tax-free expense reimbursements." That's a note about pay. We should include that in Pay section. Now, we must remove boilerplate: "Aya is an Equal Employment Opportunity..." — that's EEO boilerplate, remove. Also "We’ll work with you to build the healthcare career of your dreams..." — that's marketing fluff, but maybe keep as part of About the role? The rule says remove duplicated lines and application instructions. The marketing fluff might be considered boilerplate. But it's part of the posting. However, the rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The marketing fluff is not exactly boilerplate, but it's generic. The rule says "Preserve ALL substantive information". The marketing fluff is not substantive. I'd drop it. Also "Aya Delivers: The most jobs in the industry..." — that's marketing. But the benefits are substantive. We'll extract the benefits. Let's parse the content: Job Details: - Profession: Therapy/Rehabilitation - Pay: $2261 to $2455 weekly - Assignment Length: 13 weeks - Shift: Days - Schedule: 5, 8-Hour 07:00 - 15:00 - Openings: 1 - Start Date: 11/23/2026 - Charting System: Epic Requirements: - Experience: New grads welcome to apply - Required Certifications & Skills: - Skills: Acute Care, Assessment, Discharge, Evaluation, AROM/AAROM/PROM, Crutches, Gait belt, Gait training, Hip fractures/injuries, Long Term Goals, Low back pain, Plan of Care, Reassessments, Post op cervical surgery, Post op spinal surgery, Standard Walker, Strength testing, Total hip replacement, Total knee replacement - Certifications: BLS Facility & Unit Information: - Facility Type: Acute Care Hospital - Charting Experience: Yes - Facility Bed Count: 99 Aya Delivers: (marketing) then benefits: - Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment. - Want to take time off? Keep insurance coverage for up to 24 Days between assignments. - A generous 401(k) match. - Paid company housing (we’ll help you bring your pets along, too!) or a generous housing stipend, if eligible. - Paid sick time in accordance with all applicable state, federal, and local laws. Aya’s general sick leave policy is that employees accrue one hour of paid sick leave for every 30 hours worked. However, to the extent any provisions of the statement above conflict with any applicable paid sick leave laws, the applicable paid sick leave laws are controlling. - Access to unlimited continuing education units online. - Licensure, relocation and other reimbursements, when applicable. - Pay listed above includes taxable wages and tax-free expense reimbursements. Also note: "Aya is an Equal Employment Opportunity..." — remove. Now, create HTML. We'll have sections:

    About the role

    Profession: Therapy/Rehabilitation

    Assignment length: 13 weeks

    Shift: Days

    Openings: 1

    Start date: 11/23/2026

    Charting system: Epic

    Facility type: Acute Care Hospital

    Charting experience required: Yes

    Facility bed count: 99

    But maybe combine into a list? The rule: use
    • for any list of duties/requirements/benefits, and

      for prose. These are key-value pairs, not a list of items. Could be a definition list, but not required. Use

      for each line. Alternatively, we could make a list of details. But the rule says use

      • for any list of duties/requirements/benefits. These are not duties/requirements/benefits, they are metadata. So

        is fine.

        Pay

        $2,261 to $2,455 weekly (includes taxable wages and tax-free expense reimbursements)

        Schedule

        5, 8-hour shifts, 07:00–15:00

        Requirements

        Experience: New grads welcome to apply

        Required certifications

        • BLS

        Required skills

        • Acute Care
        • Assessment
        • Discharge
        • Evaluation
        • AROM/AAROM/PROM
        • Crutches
        • Gait belt
        • Gait training
        • Hip fractures/injuries
        • Long Term Goals
        • Low back pain
        • Plan of Care
        • Reassessments
        • Post op cervical surgery
        • Post op spinal surgery
        • Standard Walker
        • Strength testing
        • Total hip replacement
        • Total knee replacement
        But the rule says use

        for section headings. Subheadings like "Required certifications" could be

        but not specified. The rule only mentions

        for section headings. It doesn't forbid

        . But to keep simple, maybe just include as part of Requirements section with lists. We could do:

        Requirements

        Experience: New grads welcome to apply

        Certifications:

        • BLS

        Skills:

          ...skills list...
        That's fine.

        Benefits

        • Premium medical, dental, vision, and life insurance beginning day one of assignment
        • Option to keep insurance coverage for up to 24 days between assignments
        • Generous 401(k) match
        • Paid company housing (pets welcome) or generous housing stipend, if eligible
        • Paid sick time in accordance with applicable laws (accrual: 1 hour per 30 hours worked)
        • Unlimited continuing education units online
        • Licensure, relocation, and other reimbursements when applicable
        Note: The sick time detail is specific, include. Now, check for any other sections: "Qualifications" maybe same as Requirements. "Skills" is part of Requirements.

Similar jobs