Travel Pediatric Inpatient/Outpatient Physical Therapist - $2,195 per week

We need to output HTML fragment with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include only sections with real specific content. Let's parse the posting. Content: - TalentBurst, Inc is seeking a travel Pediatric Physical Therapist for a travel job in Anchorage, Alaska. - Job Description & Requirements Specialty: Pediatric Physical Therapist Discipline: Therapy Start Date: 10/19/2026 Duration: 13 weeks 40 hours per week Shift: 8 hours, days Employment Type: Travel Pediatric Inpatient/Outpatient Physical Therapist Assignment Length - 13 Weeks Start Date:ASAP Shift: 5x8 Days Years of Experience: 1 First Timers Accepted: Yes - with 2 Years of Experience Certs REQ: BLS, AK PT License Skills REQ: Per UD, Peds Experience Is on-call REQ: No Weekend REQ:Yes - Some weekends required - approx 1-2 weekend shifts per month Will clinician float within scope to meet facility needs?: N/a Open to accommodating block schedule?: No Locals Accepted: No - Candidates perm address must be at least 50 miles from facility Pending License Accepted: Yes, but must have license in hand for Auto Offer RTO Restrictions: Time off approved on an individual basis upon offer. All RTO must be included in submittal FACILITY INFORMATION Type of Facility: Acute Hospital Magnet/Teaching/Level Trauma: Magnet Facility, Level II Trauma, USNWR Best Hospital in Alaska Total Staffed Beds: 407 Scrub Color: Provided Charting: Epic Parking Cost: Parking is free #PHYTH1TalentBurst, Inc Job ID #26-30966. Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: Pediatric Physical Therapist - About TalentBurst, Inc: description. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive information. We need sections: About the role (maybe description of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content fits each. We have details: Specialty, Discipline, Start Date, Duration, hours per week, shift, employment type, assignment length, years of experience, first timers accepted, certs required, skills required, on-call, weekend required, floating, block schedule, locals accepted, pending license accepted, RTO restrictions, facility info (type, magnet, trauma level, beds, scrub color, charting, parking). Also pay package info: based on 8 hour shifts and 40 hours per week, tax-free stipend amount to be determined. We also have About TalentBurst. We need to avoid sections with placeholder like "commensurate with experience", "not specified", etc. We have pay: "tax-free stipend amount to be determined" - that is somewhat unspecified but still we have some info: pay package based on 8 hour shifts and 40 hours per week. Should we include Pay section? The posting says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's some info but stipend amount TBD. According to rule: 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, though stipend amount TBD. That's still stating something about pay. So we can include Pay section with that info. Schedule: we have shift details: 8 hours, days; also Shift: 5x8 Days; 40 hours per week; weekend required approx 1-2 weekend shifts per month. So we have schedule info. So we can include Schedule section. Benefits: we have scrub color provided, parking free, maybe other benefits? Not explicit benefits like health insurance, etc. The posting does not list benefits besides scrub color and parking. Are those considered benefits? Possibly yes. The rule: include a section ONLY when posting has real, specific content for it. Scrub color provided and parking free are specific. So we can include Benefits section with those. Responsibilities: Not explicitly listed. The posting does not give a list of duties. Might be implied but not explicit. We should not invent. So we should omit Responsibilities if no specific content. Requirements: we have certs required (BLS, AK PT License), years of experience (1 year? Actually says Years of Experience: 1 First Timers Accepted: Yes - with 2 Years of Experience). That's confusing. But we have requirement: BLS, AK PT License, maybe Peds Experience. Also "Skills REQ: Per UD, Peds Experience". So we can list requirements. Qualifications: maybe similar to requirements; but we can combine? The rule: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But headings are predefined; we can choose to include only those with content. Could include Requirements and Qualifications separate if we have distinct content. However we might not have clear distinction. Could put certs and license under Requirements, and years of experience under Qualifications. Or we could put all under Requirements and skip Qualifications. Since we want few sections, maybe we include Requirements and Qualifications combined? But we must use headings exactly as given if we include them. Could include Requirements and not Qualifications. Let's see if we have qualifications content: "First Timers Accepted: Yes - with 2 Years of Experience" maybe qualification. But we can treat as requirement. Skills: we have "Skills REQ: Per UD, Peds Experience". So we can include Skills section. About the role: we have a brief description: seeking travel Pediatric Physical Therapist for travel job in Anchorage, Alaska. Also facility info. Could be About the role. We also have About TalentBurst, Inc which is about the company, not the role. Could be a separate section like "About the Company" but not in allowed headings. So we might omit that or incorporate into About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those headings allowed. So we should not add a heading for About TalentBurst. We could include that info under About the role? Might be okay to include company description there? But it's not about the role. However we could still include it as part of About the role? Might be stretching. Better to omit company description as it's not requested heading. But we must preserve ALL substantive information. If we omit it, we lose info. However we could embed it in a paragraph without heading? The instruction says output ONLY the HTML fragment, no extra text. We can include paragraphs without heading? It didn't forbid paragraphs outside headings. It says use

for section headings,

• for any list,

  for prose. So we can have prose paragraphs not under a heading? Probably okay, but better to structure under headings. However we have no heading for company info. Could we treat it as "About the role" and include both role and company? Might be acceptable. Let's decide to include sections: About the role, Requirements, Skills, Benefits, Pay, Schedule. Possibly Qualifications if we have distinct content. Let's extract content for each. About the role: - TalentBurst, Inc is seeking a travel Pediatric Physical Therapist for a travel job in Anchorage, Alaska. - Pediatric Inpatient/Outpatient Physical Therapist. - Assignment Length - 13 Weeks. - Start Date: ASAP (also 10/19/2026? contradictory). We'll include both? The posting says Start Date: 10/19/2026 earlier, then Assignment Length - 13 Weeks Start Date:ASAP. We'll keep both as given. - Shift: 8 hours, days; also Shift: 5x8 Days. - Employment Type: Travel. - Facility: Acute Hospital, Magnet Facility, Level II Trauma, USNWR Best Hospital in Alaska, 407 beds, Scrub color provided, Charting: Epic, Parking free. - etc. We can put facility info maybe under Benefits? But we already have Benefits for scrub color and parking. Facility type maybe part of About the role. Requirements: - Certs REQ: BLS, AK PT License. - Years of Experience: 1 (maybe also First Timers Accepted: Yes - with 2 Years of Experience). We'll note: Minimum 1 year experience; first timers accepted with 2 years experience. - Skills REQ: Per UD, Peds Experience. - On-call REQ: No. - Weekend REQ: Yes - Some weekends required - approx 1-2 weekend shifts per month. - Will clinician float within scope to meet facility needs?: N/a (so not required). - Open to accommodating block schedule?: No. - Locals Accepted: No - Candidates perm address must be at least 50 miles from facility. - Pending License Accepted: Yes, but must have license in hand for Auto Offer. - RTO Restrictions: Time off approved on an individual basis upon offer. All RTO must be included in submittal. Qualifications: maybe we could list "First Timers Accepted: Yes - with 2 Years of Experience" as qualification. But we already covered. Skills: - Peds Experience. - Per UD (maybe meaning per unit? unclear). We'll just list "Peds Experience" and "Per UD". Benefits: - Scrub color provided. - Parking free. - (Maybe also charting Epic? Not a benefit.) We could also include "Charting: Epic" as a facility detail but not benefit. Pay: - Pay package based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Schedule: - 40 hours per week. - Shift: 8 hours, days. - Shift pattern: 5x8 Days. - Weekend required: approx 1-2 weekend shifts per month. - (Maybe also note: No on-call.) We need to output HTML fragment with

  headings and

  or

  • . For lists, we should use
    • . For prose,

      . We need to decide which info is best as list vs prose. For About the role: could be a paragraph. For Requirements: could be a list. For Skills: list. For Benefits: list. For Pay: paragraph. For Schedule: list or paragraph. Let's craft. We must not include boilerplate like Job ID etc. We should drop Job ID line. We must not repeat job title as heading. We must not include metadata like Job ID. Let's produce. Check for any duplicated lines: we will avoid. Now produce HTML. We'll start with

      About the role

      then

      ...

      . Then

      Requirements

      • ...
      . Then

      Skills

      • ...
      . Then

      Benefits

      • ...
      . Then

      Pay

      ...

      . Then

      Schedule

      • ...
      . We need to ensure we don't create empty sections. Let's write content. About the