Travel NICU RRT - Make $1,651/week - $1,881/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 that have real, specific content. The job 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 level trauma, facility bed count) - Aya Delivers section (benefits, support, etc.) But I must follow the 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 (the page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, 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") - 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 map the content to appropriate sections. The posting has: - Pay: $1651 to $1881 weekly (specific) - Schedule: Nights, 3, 12-Hour 19:00 - 07:30 (specific) - Assignment Length: 13 weeks - Start Date: 11/02/2026 - Charting System: Epic - Requirements: Experience: 1 Year, Required Certifications & Skills (list of skills and certifications) - Facility & Unit Information: Facility Type: Acute Care Hospital, Charting Experience: Yes, Facility Level Trauma: Level 1, Facility Bed Count: 968 - Aya Delivers: benefits and support details (this is boilerplate about the agency, but it includes specific benefits like insurance, 401(k), housing, sick time, CEUs, reimbursements). However, the rule says remove boilerplate, but this is specific benefits offered by the agency. The user said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Aya Delivers section is marketing but includes specific benefits. I think we should include a Benefits section with the specific benefits listed. But note: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay, schedule, and benefits (in Aya Delivers). So we can include them. However, the Aya Delivers section is largely agency marketing. But it does list specific benefits: 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; unlimited CEUs; licensure, relocation reimbursements. That's substantive. We need to decide on sections. The user suggests headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have real content. The posting doesn't have a clear "Responsibilities" list; it has skills required. It has "Requirements" (experience, certifications, skills). It has "Facility & Unit Information". It has "Pay", "Schedule", "Benefits". It has "Assignment Length", "Start Date", "Charting System". Could group some under "Job Details" or "About the role". Let's structure: - About the role: could include profession, assignment length, shift, schedule, openings, start date, charting system, facility info. - Requirements: experience, certifications, skills. - Benefits: the benefits listed in Aya Delivers. - Pay: the pay range. - Schedule: the schedule details. But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine some. Let's create:

  About the role

  Profession: Respiratory / Neuro Diagnostics

  Assignment length: 13 weeks

  Shift: Nights

  Schedule: 3, 12-Hour shifts (19:00 - 07:30)

  Openings: 1

  Start date: 11/02/2026

  Charting system: Epic

  Facility type: Acute Care Hospital

  Facility trauma level: Level 1

  Facility bed count: 968

  Charting experience required: Yes

  But that's a lot of

  tags. Could use a list for some. But the rule says use

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

    for prose. These are details, not a list of duties. Could be a list of details. But the rule says "Use

    • for any list of duties/requirements/benefits". These are not duties/requirements/benefits; they are job details. Could use

      for each. Alternatively, create a "Job details" section with a list. But the user didn't specify "Job details" as a heading; they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for general details. Now, Requirements: Experience: 1 Year, Required Certifications & Skills (list of skills and certifications). That's a list. Skills list: Neonatal transports (inter-departmental), Assist in high risk delivery, Bubble CPAP, CPAP, CPAP/Nasal CPAP/BIPAP, High frequency oscillator, Intubation Assist, NICU, Oscillating Ventilator, Patient Transport (inter-departmental and ambulance transport), Pressure/Volume Ventilator Certifications: CRT, RRT, BLS, NRP We can put under Requirements heading with two sublists? But we only have

      for headings. Could do:

      Requirements

      Experience: 1 year

      Required skills

      but we cannot use h4? The rule says use

      for section headings. It doesn't forbid subheadings, but we should keep it simple. Could just list skills and certifications as bullet points under Requirements. Better: Under Requirements, have a paragraph for experience, then a list for skills, then a list for certifications. But the rule says "Use

      • for any list of duties/requirements/benefits". So we can make a list of requirements. Let's do:

        Requirements

        • Experience: 1 year
        • Skills: Neonatal transports (inter-departmental), Assist in high risk delivery, Bubble CPAP, CPAP, CPAP/Nasal CPAP/BIPAP, High frequency oscillator, Intubation Assist, NICU, Oscillating Ventilator, Patient Transport (inter-departmental and ambulance transport), Pressure/Volume Ventilator
        • Certifications: CRT, RRT, BLS, NRP
        But that's a list with three items, each containing a comma-separated list. Could break skills into separate list items? The posting lists them as a comma-separated string. We could split them into individual list items for clarity. But the rule says preserve ALL substantive information; do NOT invent or summarize away detail. Splitting might be okay as long as we keep all items. However, the original is a single line. I think it's fine to keep as a single list item with the full string. But the rule says "Use
        • for any list of duties/requirements/benefits". The skills are a list of skills. It might be better to split each skill into its own
        • . But the posting doesn't have them as separate lines; they are comma-separated. However, we can parse them. I'll split them for better readability. Similarly for certifications. But note: "Preserve ALL substantive information; do NOT invent or summarize away detail." Splitting doesn't lose detail. I'll split skills and certifications into separate list items under a sublist? But we only have one level of list. Could do nested lists? The rule doesn't forbid nested lists. But to keep simple, maybe just have a list of requirements with each skill as a separate bullet. Let's structure:

          Requirements

          • Minimum 1 year of experience
          • Neonatal transports (inter-departmental)
          • Assist in high risk delivery
          • Bubble CPAP
          • CPAP
          • CPAP/Nasal CPAP/BIPAP
          • High frequency oscillator
          • Intubation Assist
          • NICU
          • Oscillating Ventilator
          • Patient Transport (inter-departmental and ambulance transport)
          • Pressure/Volume Ventilator
          • Certifications: CRT, RRT, BLS, NRP
          But certifications are separate. Could make a separate list for certifications. But we can keep as one list. Alternatively, use two lists: one for skills, one for certifications. But we need headings for each? Could do:

          Requirements

          Minimum 1 year of experience

          Skills

          ...skills...

          Certifications

          ...certifications...
          But the rule says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So Skills is a valid heading. However, the posting groups them under "Required Certifications & Skills". But we can separate. But the rule: "include a section ONLY when the posting has real, specific content for it". The posting has specific skills and certifications. So we can have Skills and Certifications sections. But that might be too many thin sections. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine under Requirements. I'll combine under Requirements with a list that includes both skills and certifications. Now, Benefits: The Aya Delivers section lists benefits. We'll create a Benefits section with a list. Pay: specific pay range. Create Pay section. Schedule: specific schedule. Create Schedule section. But note: the posting also has "Assignment Length", "Start Date", "Charting System", "Facility & Unit Information". These could go under About the role. Let's decide on sections: 1. About the role (includes profession, assignment length, shift, schedule, openings, start date, charting system, facility details) 2. Requirements (experience, skills, certifications) 3. Pay 4. Schedule (though schedule is also in About the role; but we can have a separate Schedule section with details) 5. Benefits But Schedule is already in About the role. The rule says never create Schedule section unless posting actually states them. It does state schedule. But we might duplicate. Better to include schedule details in About the role and not have a separate Schedule section. However, the user example includes Schedule as