Travel Pediatric RN - $2,137 per week
for headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Host Healthcare is seeking a travel nurse RN Pediatrics for a travel nursing job in Hyannis, Massachusetts.
- Job Description & Requirements
- Specialty: Pediatrics
- Discipline: RN
- Start Date: 10/13/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Travel
- Host Healthcare Job ID #a1fVX000003w8OTYAY.
- 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
- About Host Healthcare: paragraph describing company.
- Benefits list: 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 decide which sections to include.
We have:
- About the role: Could include description of role: travel nurse RN Pediatrics, location Hyannis, MA, start date, duration, hours, shift, employment type. That's substantive.
- Responsibilities: Not given explicitly. The posting does not list duties/responsibilities. So we should not create a Responsibilities section if no specific content.
- Requirements: Not given explicitly beyond specialty and discipline. Could treat "Specialty: Pediatrics, Discipline: RN" as requirements. But we need to see if we have enough to make a Requirements section. The posting includes "Job Description & Requirements" heading but no bullet list of requirements. It includes Specialty and Discipline. Could treat that as requirements. However we need to avoid filler. If we only have two items, we could still make a Requirements section with a
- list. That's okay.
- Qualifications: Not given separately; could be same as requirements? Might be redundant. Better to not create Qualifications if no distinct content.
- Skills: Not given.
- Benefits: We have a list of benefits. So we should create a Benefits section with
- list.
- Pay: The posting says "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." This is vague; it's not a specific number, it's "subject to confirmation" and "tax-free stipend amount to be determined." According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "subject to confirmation" and "amount to be determined." That's placeholder-ish. So we should NOT create a Pay section because it's not specific. We could maybe include it as a short
within About the role? But instruction: Prefer a few substantive sections over many thin ones. Since Pay is not specific, we should omit Pay section.
- Schedule: We have shift details: 12 hours, nights, 36 hours per week. That's specific. So we can create a Schedule section with that info. Could be a
or
- . Since it's not a list, we can use
.
- Also we have Start Date and Duration. Those could be part of About the role or Schedule? Probably About the role.
- Job ID: minor metadata; we can fold into a short
or drop it. Probably drop it.
- About Host Healthcare: That's company description; could be part of About the role? But we already have About the role section for the job. Could we have an "About Host Healthcare" section? Not in the allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate Host Healthcare description into About the role or maybe as a separate paragraph within About the role. Since we cannot create a heading not in list, we should embed that info in About the role as prose.
Thus final HTML:
About the role
Host Healthcare is seeking a travel nurse RN Pediatrics for a travel nursing job in Hyannis, Massachusetts. Specialty: Pediatrics. Discipline: RN. Start date: October 13, 2026. Duration: 13 weeks. Hours: 36 hours per week. Shift: 12-hour nights. Employment type: Travel.
Requirements
- Specialty: Pediatrics
- Discipline: RN
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
Schedule
12-hour night shifts, 36 hours per week.
We should not include Pay section. Also we should not repeat job title. No Job ID.
Check for any duplicated lines: we have not included any.
Check for any boilerplate: we omitted the Host Healthcare description paragraphs beyond the first sentence? Actually we included only the first sentence about seeking a travel nurse. The rest of the Host Healthcare paragraph about mission etc is boilerplate? It's generic company description; could be considered boilerplate but it's still substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Host Healthcare mission paragraph is not exactly boilerplate but it's generic marketing. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. It doesn't explicitly say remove generic marketing fluff. However we should preserve ALL substantive information; do NOT invent or summarize away detail. The Host Healthcare mission paragraph is substantive? It describes the company's mission and benefits. But we already captured benefits in a list. The mission paragraph may be considered fluff but not explicitly prohibited. However to keep sections few and substantive, we could omit that paragraph as it's not directly about the role. The instruction: "Prefer a few substantive sections over many thin ones." Including that paragraph would add prose to About the role making it longer but still substantive. It's not disallowed. However we might consider it as boilerplate? It's not legal/EEO etc. It's marketing. I'd keep it minimal: we already have a short About the role. Could add a sentence about Host Healthcare's mission? But we already have benefits list; the mission may be redundant.
Given the instruction to preserve ALL substantive information, we should include the Host Healthcare description if it's substantive. But we already have benefits list; the mission paragraph is about helping healers, providing comfortable experience, etc. That's substantive about the company. I'd include it as a paragraph in About the role after the role details.
Thus About the role could be:
Host Healthcare is seeking a travel nurse RN Pediatrics for a travel nursing job in Hyannis, Massachusetts. Specialty: Pediatrics. Discipline: RN. Start date: October 13, 2026. Duration: 13 weeks. Hours: 36 hours per week. Shift: 12-hour nights. Employment type: Travel. Host Healthcare provides a comfortable travel nursing experience, handling details so you can focus on your assignment, with access to thousands of jobs, responsive recruiters, Day 1 medical benefits, 401K matching, travel reimbursements, housing support, 24/7 support, and on‑staff clinicians.
That captures the mission and benefits briefly, but we already have a Benefits section listing specifics. To avoid duplication, we could keep the About the role short and let Benefits section cover details. The Host Healthcare paragraph includes many of those benefits; but we already list them. Duplication is to be avoided per instruction: "Remove ... duplicated lines". So we should not duplicate benefit details. So we should keep About the role focused on role specifics, not repeat benefits. So we keep About the role as earlier short paragraph without repeating benefits.
Thus final HTML as earlier.
Check for any missing specifics: The posting also mentions "Posted job title: RN - Peds". That's just the title; we should not repeat job title as heading. We can ignore.
Check for any other specifics: "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." We omitted Pay section because it's not specific. Good.
Check for any other specifics: "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." This is part of Host Healthcare description; we omitted to avoid duplication. But we could incorporate a sentence about Day 1 medical etc in About the role if not duplicated in Benefits list. However Benefits list includes Medical benefits, 401k retirement plan, etc. Day 1 medical that continues up to 30 days between assignments is a specific detail about medical benefits not captured in the generic "Medical benefits". Should we include that as a separate benefit? The Benefits list we have includes "Medical benefits". That is generic; the posting also mentions Day 1 medical continues up to 30 days between assignments. That's more specific. Should we add that as a separate bullet? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should capture that detail. However we must not create filler/placeholder text. This detail is substantive. So we need to include it in Benefits section. We could either add a bullet: "Day 1 medical coverage (continues up to 30 days between assignments)". Or we could modify the Medical benefits bullet to include that detail. Since we already have a generic "Medical benefits" bullet, we could replace it with the more specific description. But we also have other benefits like "401K matching", "travel reimbursements", "dedicated housing support". Those are also mentioned in the Host Healthcare paragraph but not in our Benefits list. We should include them as separate bullets if they are substantive.
Let's extract all benefits mentioned:
From
for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - Host Healthcare is seeking a travel nurse RN Pediatrics for a travel nursing job in Hyannis, Massachusetts. - Job Description & Requirements - Specialty: Pediatrics - Discipline: RN - Start Date: 10/13/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Host Healthcare Job ID #a1fVX000003w8OTYAY. - 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 - About Host Healthcare: paragraph describing company. - Benefits list: 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 decide which sections to include. We have: - About the role: Could include description of role: travel nurse RN Pediatrics, location Hyannis, MA, start date, duration, hours, shift, employment type. That's substantive. - Responsibilities: Not given explicitly. The posting does not list duties/responsibilities. So we should not create a Responsibilities section if no specific content. - Requirements: Not given explicitly beyond specialty and discipline. Could treat "Specialty: Pediatrics, Discipline: RN" as requirements. But we need to see if we have enough to make a Requirements section. The posting includes "Job Description & Requirements" heading but no bullet list of requirements. It includes Specialty and Discipline. Could treat that as requirements. However we need to avoid filler. If we only have two items, we could still make a Requirements section with a
- list. That's okay.
- Qualifications: Not given separately; could be same as requirements? Might be redundant. Better to not create Qualifications if no distinct content.
- Skills: Not given.
- Benefits: We have a list of benefits. So we should create a Benefits section with
- list.
- Pay: The posting says "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." This is vague; it's not a specific number, it's "subject to confirmation" and "tax-free stipend amount to be determined." According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "subject to confirmation" and "amount to be determined." That's placeholder-ish. So we should NOT create a Pay section because it's not specific. We could maybe include it as a short
within About the role? But instruction: Prefer a few substantive sections over many thin ones. Since Pay is not specific, we should omit Pay section. - Schedule: We have shift details: 12 hours, nights, 36 hours per week. That's specific. So we can create a Schedule section with that info. Could be a
or
- . Since it's not a list, we can use
. - Also we have Start Date and Duration. Those could be part of About the role or Schedule? Probably About the role. - Job ID: minor metadata; we can fold into a short
or drop it. Probably drop it. - About Host Healthcare: That's company description; could be part of About the role? But we already have About the role section for the job. Could we have an "About Host Healthcare" section? Not in the allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate Host Healthcare description into About the role or maybe as a separate paragraph within About the role. Since we cannot create a heading not in list, we should embed that info in About the role as prose. Thus final HTML:
About the role
Host Healthcare is seeking a travel nurse RN Pediatrics for a travel nursing job in Hyannis, Massachusetts. Specialty: Pediatrics. Discipline: RN. Start date: October 13, 2026. Duration: 13 weeks. Hours: 36 hours per week. Shift: 12-hour nights. Employment type: Travel.
Requirements
- Specialty: Pediatrics
- Discipline: RN
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
Schedule
12-hour night shifts, 36 hours per week.
We should not include Pay section. Also we should not repeat job title. No Job ID. Check for any duplicated lines: we have not included any. Check for any boilerplate: we omitted the Host Healthcare description paragraphs beyond the first sentence? Actually we included only the first sentence about seeking a travel nurse. The rest of the Host Healthcare paragraph about mission etc is boilerplate? It's generic company description; could be considered boilerplate but it's still substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Host Healthcare mission paragraph is not exactly boilerplate but it's generic marketing. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. It doesn't explicitly say remove generic marketing fluff. However we should preserve ALL substantive information; do NOT invent or summarize away detail. The Host Healthcare mission paragraph is substantive? It describes the company's mission and benefits. But we already captured benefits in a list. The mission paragraph may be considered fluff but not explicitly prohibited. However to keep sections few and substantive, we could omit that paragraph as it's not directly about the role. The instruction: "Prefer a few substantive sections over many thin ones." Including that paragraph would add prose to About the role making it longer but still substantive. It's not disallowed. However we might consider it as boilerplate? It's not legal/EEO etc. It's marketing. I'd keep it minimal: we already have a short About the role. Could add a sentence about Host Healthcare's mission? But we already have benefits list; the mission may be redundant. Given the instruction to preserve ALL substantive information, we should include the Host Healthcare description if it's substantive. But we already have benefits list; the mission paragraph is about helping healers, providing comfortable experience, etc. That's substantive about the company. I'd include it as a paragraph in About the role after the role details. Thus About the role could be:Host Healthcare is seeking a travel nurse RN Pediatrics for a travel nursing job in Hyannis, Massachusetts. Specialty: Pediatrics. Discipline: RN. Start date: October 13, 2026. Duration: 13 weeks. Hours: 36 hours per week. Shift: 12-hour nights. Employment type: Travel. Host Healthcare provides a comfortable travel nursing experience, handling details so you can focus on your assignment, with access to thousands of jobs, responsive recruiters, Day 1 medical benefits, 401K matching, travel reimbursements, housing support, 24/7 support, and on‑staff clinicians.
That captures the mission and benefits briefly, but we already have a Benefits section listing specifics. To avoid duplication, we could keep the About the role short and let Benefits section cover details. The Host Healthcare paragraph includes many of those benefits; but we already list them. Duplication is to be avoided per instruction: "Remove ... duplicated lines". So we should not duplicate benefit details. So we should keep About the role focused on role specifics, not repeat benefits. So we keep About the role as earlier short paragraph without repeating benefits. Thus final HTML as earlier. Check for any missing specifics: The posting also mentions "Posted job title: RN - Peds". That's just the title; we should not repeat job title as heading. We can ignore. Check for any other specifics: "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." We omitted Pay section because it's not specific. Good. Check for any other specifics: "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." This is part of Host Healthcare description; we omitted to avoid duplication. But we could incorporate a sentence about Day 1 medical etc in About the role if not duplicated in Benefits list. However Benefits list includes Medical benefits, 401k retirement plan, etc. Day 1 medical that continues up to 30 days between assignments is a specific detail about medical benefits not captured in the generic "Medical benefits". Should we include that as a separate benefit? The Benefits list we have includes "Medical benefits". That is generic; the posting also mentions Day 1 medical continues up to 30 days between assignments. That's more specific. Should we add that as a separate bullet? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should capture that detail. However we must not create filler/placeholder text. This detail is substantive. So we need to include it in Benefits section. We could either add a bullet: "Day 1 medical coverage (continues up to 30 days between assignments)". Or we could modify the Medical benefits bullet to include that detail. Since we already have a generic "Medical benefits" bullet, we could replace it with the more specific description. But we also have other benefits like "401K matching", "travel reimbursements", "dedicated housing support". Those are also mentioned in the Host Healthcare paragraph but not in our Benefits list. We should include them as separate bullets if they are substantive. Let's extract all benefits mentioned: From
- . Since it's not a list, we can use
- list.
- Pay: The posting says "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." This is vague; it's not a specific number, it's "subject to confirmation" and "tax-free stipend amount to be determined." According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "subject to confirmation" and "amount to be determined." That's placeholder-ish. So we should NOT create a Pay section because it's not specific. We could maybe include it as a short