Travel Outpatient Physical Therapist - $2,028 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, identify the sections: - About the role / Job Description - Requirements / Minimum Requirements - Benefits - Pay / Schedule details (but need to check if substantive) 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 into short

  or drop - Preserve ALL substantive information; no invention or summarization - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning), duplicated lines, application instructions - Include section ONLY when real, specific content — no 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 parse the posting: Content: - "Centra Healthcare Allied is seeking a travel Physical Therapist for a travel job in Fife, Washington." -> intro prose - "Job Description & Requirements" heading in source but we don't repeat job title. - Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type -> these are metadata. Could be folded into a short

  or list. Since they are specific, maybe include in "About the role" or "Job Details". But rules: use h3 for section headings like About the role, Responsibilities, Requirements, etc. Could create "Job Details" but not in the listed headings. The listed headings are examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those. Probably "About the role" for description, "Requirements" for minimum requirements, "Benefits" for benefits. Pay and Schedule: there is pay package info and schedule info. The posting says "Pay package is based on 8.0 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat specific but includes "to be determined". Might be considered placeholder? It says "tax-free stipend amount to be determined." That's not a specific number. Could be considered not substantive enough? But it does state pay package based on shifts and hours. Might include in a "Pay" section? However rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package details, albeit with TBD stipend. Could include but avoid filler. Might include a short

  in "About the role" or separate "Pay" section. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package info. However, the stipend amount is TBD. Could still include as a section with the known info. But the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So if we include Pay section, we must not include the TBD line? But that's part of the posting. We could include the known parts and omit the TBD? But we must preserve ALL substantive information. The TBD is substantive? It's a placeholder. Might be better to fold into a short

  in "About the role" or "Job Details". But we don't have a "Job Details" heading. Could use "Schedule" for shift info. The posting includes shift: 8 hours, days, 5x8 Days schedule. That's schedule info. Could create a "Schedule" section. But again, if we create Schedule section, we need substantive content. The schedule is specific: 5x8 Days schedule, 40 hours per week, shift 8 hours days. That's substantive. So we can have a Schedule section. Similarly, Benefits are listed in detail. So Benefits section. Requirements: list of minimum requirements. About the role: description of role, responsibilities? The posting says "This role assumes responsibility and accountability for incorporating the vision, values, mission and critical goals of the organization into their job performance." That's a responsibility. Could be in "Responsibilities" or "About the role". The posting doesn't have a detailed list of duties. It's a travel PT outpatient. Might have a short description. Let's structure: -

  About the role

  Centra Healthcare Allied is seeking a travel Physical Therapist for a travel job in Fife, Washington. This is a contract position with a 5x8 Days schedule. The role assumes responsibility and accountability for incorporating the vision, values, mission and critical goals of the organization into their job performance.

  Maybe include metadata like start date, duration, hours per week, shift, employment type in a list? Could be a
  under About the role or separate. But the rules say use
  • for any list of duties/requirements/benefits. Metadata could be a list. But not duties/requirements/benefits. Could be a

    with details. I'll include as a

    for clarity. -

    Requirements

    • 1 year of recent experience as a Physical Therapist (PT)
    • Outpatient experience required
    • Current Physical Therapist (PT) license within the state of practice (WA)
    -

    Benefits

    • Mileage reimbursement to assignment (if applicable)
    • Highly competitive pay package
    • 401(k) plan with matching
    • Direct deposit and weekly pay
    • CEU reimbursement
    • Medical credentials reimbursement
    • A chance to explore new places and new opportunities throughout the United States
    • High coverage of the premiums of a comprehensive health insurance plan
    • Licensure reimbursement
    • Housing accommodations or Lodging per diems (if you qualify for reimbursements)
    • Flexibility of work schedule, including guaranteed hours (if applicable)
    • Assignment completion bonuses (if applicable)
    -

    Schedule

    5x8 Days schedule, 40 hours per week, 8-hour day shifts.

    Or include start date and duration? Those are more job details. Could include in About the role. -

    Pay

    Pay package based on 8.0 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

    But the rule says never emit a heading followed by filler/placeholder text like "to be determined". That is placeholder. So maybe omit Pay section and fold into Benefits? But Benefits already has "Highly competitive pay package". The pay detail is separate. Could include in About the role as a note. But the rule says never create Pay section unless posting actually states them. It does state pay package details, but with TBD. Might be better to not create a Pay section and just mention in About the role or Benefits. However, the user might expect Pay section if there is pay info. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package. But the placeholder text "to be determined" is filler. Could we include the known part and omit the TBD? But we must preserve ALL substantive information. The TBD is part of the posting. Might be considered substantive? It's a disclosure. I think we can include a Pay section with the exact text, but the rule says never emit a heading followed by filler/placeholder text. That suggests if the only content is placeholder, don't create the section. Here there is some content: "Pay package is based on 8.0 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's a mix of specific and placeholder. Could still include. But to be safe, maybe fold into a short

    in About the role or Schedule. However, the rule says "Prefer a few substantive sections over many thin ones." So maybe we don't need a separate Pay section. We'll include pay info in Benefits? But Benefits already has "Highly competitive pay package". The pay detail is more specific. Could add as a separate bullet in Benefits? But Benefits list is for benefits. Pay package is not a benefit per se. Could create a "Compensation" section? Not in the example headings. The example headings include Pay. So we can use Pay. I'll include a Pay section with the exact sentence. But the rule says never emit a heading followed by filler/placeholder text. The text includes "to be determined". That is placeholder. Might be considered filler. However, the posting includes it. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So if we include a Pay section, we must not include that placeholder. But we must preserve ALL substantive information. This is a conflict. The resolution: if the only pay info is placeholder, don't create the section. But there is some substantive info: based on 8 hour shifts and 40 hours per week. That's substantive. The stipend amount TBD is placeholder. Could we include the substantive part and omit the placeholder? But we must preserve all substantive information. The placeholder is not substantive. So we can include the substantive part and drop the placeholder? The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." The placeholder is not substantive detail. So we can omit it. But the posting says "tax-free stipend amount to be determined." That is a detail about the pay package. It's informative that the stipend amount is not yet determined. That could be considered substantive. However, the rule explicitly says never emit a heading followed by filler/placeholder text like TBD. So if we create a Pay section, we would be emitting a heading followed by text that includes TBD. That violates the rule. Therefore, we should not create a Pay section. Instead, we can fold the pay info into another section, maybe Benefits or About the role, but without a heading. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay, but with placeholder. The rule about placeholder overrides. So we will not create a Pay section. Similarly, Schedule: the posting states schedule details (5x8 Days, 40 hours, 8-hour days). That's substantive, no placeholder. So we can create a Schedule section. Job ID: "Centra Healthcare Allied Job ID #918127." Should be folded into a short

    or dropped. We'll drop it as it's minor metadata. Application instructions: "Please apply online for this fantastic opportunity. We look forward to assisting you in finding an optimal position." Remove. Boilerplate: "About Centra: Centra Healthcare's mission is to provide unparalleled service enabling professionals to concentrate on caring for America. We have many dynamic positions with cutting edge programs throughout the entire United States and various settings to meet each professional's criteria." This is company boilerplate. Could be considered "About the company" but not required. The rules say remove boilerplate. But it's not legal/