Travel Peds Polysomnography Respiratory Therapist - $2,359 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, I need to identify the sections: - The job title is "travel Pediatric Polysomnography Technologist" but the rule says do NOT repeat the job title as a heading (the page already shows it). - There's a "Job Description & Requirements" section with metadata: Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type, Job ID. - There's an "About Access Healthcare" section with company description. - There's mention of pay package: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." - Benefits are mentioned: "competitive pay packages and an unmatched benefits package!" but no specific benefits listed. - No explicit Responsibilities, Requirements, Qualifications, Skills sections. Rules: - Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). - Use

• for any list of duties/requirements/benefits, and

  for prose. - Do NOT repeat the job title as a heading. - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, let's structure: The posting has: 1. Job metadata (specialty, discipline, start date, duration, hours, shift, employment type, job ID). This could be folded into a short

  or maybe a "Job Details" section? The rules say use headings like "About the role", "Responsibilities", etc. But there's no explicit "About the role" section. However, the metadata describes the role. Could create a "Job Details" heading? But the allowed headings are listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Job Details" not listed. Could use "About the role" for the metadata? The metadata is not really "about the role" but more like assignment details. Might be better to put metadata in a

  under a "Job Details" heading? But the rule says use

  for section headings (e.g. About the role, Responsibilities, ...). It says "e.g." meaning those are examples, not exhaustive. But we should prefer those. However, we must not create a heading if no real content. The metadata is real content. Could create a "Job Details" heading? But the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should stick to those if possible. "About the role" could encompass the metadata. But the metadata includes start date, duration, shift, etc. That's more like "Schedule" and "Duration". There's a "Schedule" heading example. The posting says "36 hours per week Shift: 12 hours, nights". That's schedule info. Also "Duration: 13 weeks". That could be under "Schedule" or "About the role". The pay package is mentioned: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's pay info, but it's vague (amount to be determined). The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule (36 hours per week, 12 hours, nights) and pay (pay package based on...). But pay amount is not determined. Should we include a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule and pay (though pay amount TBD). 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 create a Pay section, we would have to say "tax-free stipend amount to be determined" which is placeholder. So maybe we should not create a Pay section. Similarly, Benefits: "unmatched benefits package!" but no specifics. So no Benefits section. The "About Access Healthcare" section is company description. That could be "About the Company" or "About Access Healthcare". The allowed headings don't include "About the Company", but "About the role" is there. Could use "About the Company" as a heading? The rule says "use

  for section headings (e.g. About the role, Responsibilities, ...)". It doesn't say we cannot use other headings. But we should prefer those. However, "About the role" is for the role, not the company. The company description is substantive. I think we can create a heading "About Access Healthcare" as it's a specific section in the posting. The rule says "include a section ONLY when the posting has real, specific content for it". The posting has a paragraph about Access Healthcare. So we can include it. Now, the metadata: Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type, Job ID. We can fold minor metadata into a short

  . The Job ID is minor metadata. The rest are important details about the assignment. Could create a "Job Details" heading? But not in the example list. Could use "Schedule" for shift and hours, and "Duration" for duration? But the example headings include "Schedule". The posting has shift and hours per week. That's schedule. Duration is 13 weeks. Could be under "Schedule" or separate. Start Date: ASAP. Employment Type: Travel. Specialty and Discipline are about the role. Could be under "About the role". Let's create an "About the role" section with a paragraph summarizing the role details, and maybe a list for the metadata? The rule says use

  • for any list of duties/requirements/benefits. Metadata could be a list. But it's not duties/requirements/benefits. It's assignment details. Could be a list. But the rule says "use
    • for any list of duties/requirements/benefits". It doesn't say we cannot use lists for other things. But we should use

      for prose. The metadata is more like key-value pairs. Could present as a list. Let's decide on sections: 1. About the role: Could include a paragraph describing the role (travel Pediatric Polysomnography Technologist in Morgantown, WV). Then a list of assignment details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. Job ID can be omitted or included in a short p. 2. Schedule: The shift details are already in the list. But maybe a separate Schedule section? The posting says "36 hours per week Shift: 12 hours, nights". That's schedule. Could be under "About the role". The rule says "Prefer a few substantive sections over many thin ones." So combine. 3. Pay: The posting mentions pay package but amount TBD. Since it's placeholder, we should not create a Pay section. 4. Benefits: Mentioned but no specifics. No section. 5. About Access Healthcare: Company description. Keep as a section. 6. Responsibilities, Requirements, Qualifications, Skills: Not provided in the posting. So no sections. Thus, we'll have two sections: "About the role" and "About Access Healthcare". Maybe also "Job Details" but we'll use "About the role". Let's craft HTML. First, "About the role" heading. Then a paragraph: "Access Healthcare is seeking a travel Pediatric Polysomnography Technologist for a travel job in Morgantown, West Virginia." Then a list of details. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "travel Pediatric Polysomnography Technologist". We are not using it as a heading; we are using "About the role". That's fine. We'll include the metadata as a list. Then "About Access Healthcare" heading with the paragraph. We must remove the "Access Healthcare Job ID #80769738" as minor metadata, fold into a short p or drop. We'll drop it. Also remove "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Since it's placeholder, we should not include a Pay section. But it's substantive info about pay structure? It says "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific pay amount, but it describes the pay structure. However, the rule says never create Pay section unless posting actually states them. It does state pay package basis. But the amount is TBD. The rule says never emit a heading followed by filler/placeholder text. If we create a Pay section, we would have to include that sentence, which includes "amount to be determined". That's placeholder. So we should not create a Pay section. We could include that sentence in the "About the role" paragraph? But it's about pay. Might be better to omit entirely? The rule says "Preserve ALL substantive information". The pay structure is substantive. But the rule also says never create Pay section with placeholder. Could we include it in "About the role" as a note? That might be okay. But the rule says "never emit a heading followed by filler/placeholder text". It doesn't say we can't include placeholder text in a paragraph under another heading. However, we should preserve substantive info. I think we can include a sentence about pay package in the "About the role" section. Similarly, benefits: "competitive pay packages and an unmatched benefits package!" is vague. We could mention in "About Access Healthcare" paragraph. Let's structure:

      About the role

      Access Healthcare is seeking a travel Pediatric Polysomnography Technologist for a travel job in Morgantown, West Virginia.

      • Specialty: Pediatric Polysomnography Technologist
      • Discipline: Allied Health Professional
      • Start Date: ASAP
      • Duration: 13 weeks
      • Hours per week: 36
      • Shift: 12 hours, nights
      • Employment Type: Travel

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

      About Access Healthcare

      Access Healthcare aims to provide superior service to our nursing family by providing around the clock support, competitive pay packages and an unmatched benefits package! Unlike other agencies, we offer a true family feel and work with you to find the placement that is right for you. We offer one of the top leading pay packages in the