Travel Pediatric OR RN - $2,137 per week

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Given text: "Host Healthcare is seeking a travel nurse RN Pediatrics OR - Operating Room for a travel nursing job in Tacoma, Washington. Job Description & Requirements Specialty: Pediatrics OR - Operating Room Discipline: RN Start Date: 10/19/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, days Employment Type: Travel Host Healthcare Job ID #a1fVX0000046MwPYAU. Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: RN - Peds OR About Host Healthcare At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare. Benefits Referral bonus School loan reimbursement Vision benefits Wellness and fitness programs Company provided housing options License and certification reimbursement Life insurance Medical benefits Mileage reimbursement Pet insurance Discount program Employee assistance programs Guaranteed Hours Health savings account Holiday Pay 401k retirement plan Continuing Education Dental benefits" We need to extract sections: About the role? The posting includes "About Host Healthcare" which is about the company, not role. But we can treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if present. We have: - About Host Healthcare (company description). Could be "About the role"? Not exactly. But maybe we can treat as "About the role" if we consider it's about the role? However the instruction says use those headings as examples; we can use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those exact headings when appropriate. If content doesn't match, we may not create a heading. But we need to include sections only when posting has real specific content for it. So we need to decide which sections we have content for. We have details: Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type, Pay package info (based on 12 hour shifts and 36.0 hours per week, tax-free stipend amount to be determined). That's Pay info but stipend amount TBD -> we should not create Pay section if it's not specified (they said "tax-free stipend amount to be determined" - that's not a specific amount, so we should not create Pay section). However we could include Pay section with note? The instruction: 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. So we should not create Pay section because stipend amount TBD (unspecified). Also schedule: we have shift details: 12 hours, days; 36 hours per week; that is schedule info. So we can create Schedule section with those details. Benefits: we have a list of benefits. So we can create Benefits section with that list. Responsibilities/Requirements/Qualifications/Skills: The posting does not list specific responsibilities or requirements beyond specialty and discipline. It mentions "Specialty: Pediatrics OR - Operating Room" and "Discipline: RN". That could be considered Requirements/Qualifications. But we need to see if we have enough specific content. The instruction: Prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section maybe "Requirements". But we need to decide. We have "Job Description & Requirements" heading but no actual description beyond specialty. So we could create a Requirements section with the specialty and discipline. Also we have Start Date, Duration, Employment Type - those could be considered part of "About the role" maybe. But we already have schedule and benefits. We could create sections: About the role (includes start date, duration, employment type, location). Responsibilities maybe not present. Requirements (specialty, discipline). Benefits (list). Schedule (shift, hours). Possibly Pay not included. We must not repeat the job title as a heading. The job title is "RN - Peds OR" (posted job title). We should not put that as heading. We must not put Job ID as heading. We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment. Let's craft:

About the role

Location: Tacoma, Washington. Start date: October 19, 2026. Duration: 13 weeks. Employment type: Travel.

Requirements

Specialty: Pediatrics OR - Operating Room. Discipline: Registered Nurse (RN).

Schedule

Shift: 12-hour days. Hours per week: 36.

Benefits

• Referral bonus
• School loan reimbursement
• Vision benefits
• Wellness and fitness programs
• Company provided housing options
• License and certification reimbursement
• Life insurance
• Medical benefits
• Mileage reimbursement
• Pet insurance
• Discount program
• Employee assistance programs
• Guaranteed Hours
• Health savings account
• Holiday Pay
• 401k retirement plan
• Continuing Education
• Dental benefits

We might also include "About Host Healthcare" as a section? But not in the list of allowed headings. Could we use "About the company"? Not allowed. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.). Likely they expect only those headings. So we should not add a heading for About Host Healthcare. However we could incorporate that description into About the role? But it's about the company, not role. Might be okay to include in About the role as part of description? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine company description into About the role? Might be stretching. Better to omit the company description entirely? But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop the company description. We need to include it somewhere. If we don't have a matching heading, we could just put it in a

without a heading? The instruction: 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. It doesn't say every piece must be under a heading; we can have prose paragraphs without headings. So we can include the Host Healthcare description as a

  without a heading, or we could put it under a heading like "About Host Healthcare" but that's not in the list. The examples are not exhaustive; they say e.g. So we could use "About Host Healthcare" as a heading. However they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies those are examples; we can use other headings if appropriate. But to be safe, we could use

  About Host Healthcare

  . However the instruction about not repeating job title as heading and not putting Job ID as heading doesn't forbid other headings. So we can include a heading for About Host Healthcare. But we need to consider that they might want only those headings. However the phrase "e.g." indicates examples, not exclusive list. So we can use other headings if they make sense. Thus we can have:

  About Host Healthcare

  At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare.

  But note that benefits are already listed in Benefits section; the paragraph mentions benefits again. Might be duplication. The paragraph includes benefits description; we already have a Benefits list. To avoid duplication, we could keep the paragraph but not repeat benefits list? However we must preserve ALL substantive information; the paragraph includes benefits description (Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on-staff clinicians). The Benefits list includes many items, some overlapping (medical benefits, 401k, etc). The paragraph's benefits are a subset. We could keep both; it's okay to have some overlap as long as we don't invent or summarize away detail. Duplication is allowed? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It says remove duplicated lines. So we should avoid duplicated lines. The benefits paragraph duplicates some of the benefits list items. To avoid duplication, we could either omit the benefits paragraph and keep the list, or keep the paragraph and not list those duplicated items. But the list includes many items not in paragraph (vision, wellness, etc). The paragraph mentions Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on-staff clinicians. Those are covered partially in list: Medical benefits, 401k retirement plan, Travel reimbursements? Not explicitly in list