Travel L&D RN - $2,766 per week
or drop it." So we can include a p with Job ID. We need to preserve all substantive information: specialty, discipline, start date, duration, hours per week, shift, employment type, location, license requirements, certifications, residence distance, shift pattern (3x12 Days), experience requirement, pay package details (based on 12 hour shifts and 36.0 hours per week, tax-free stipend amount to be determined). Also about Cure Healthcare Staffing description. We need to decide sections: About the role (maybe a brief description), Responsibilities (maybe not given explicitly; we have duties? Not listed; we could omit if no specific responsibilities). Requirements (license, certifications, experience, residence distance). Qualifications (maybe similar to requirements; but we can combine). Skills (maybe not given). Benefits (not given besides tax-free stipend amount to be determined; but that's pay/benefits? The stipend is part of pay package. Benefits section maybe not present; we can omit if no specific benefits. Pay: we have pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's specific enough? It says tax-free stipend amount to be determined (not specified). According to rule: "IMPORTANT: 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')". The stipend amount to be determined is placeholder; but the pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation). That's somewhat specific but still subject to confirmation. Might be considered not specific enough? The rule says avoid filler like "not specified". "tax-free stipend amount to be determined" is not specified. However we still have "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's somewhat specific about hours and shift length. Could we include Pay section with that? It might be okay as it's not just placeholder; it gives basis. But the stipend amount unknown. Might still be okay. Schedule: we have shift: 12 hours, days; 3x12 Days; also posted job title includes time 06:30:00-18:30:00. So we have schedule details. Thus we can have sections: About the role (maybe a brief paragraph describing the role), Requirements (license, certifications, experience, residence distance), Pay (based on 12 hour shifts and 36 hours per week, tax-free stipend TBD), Schedule (12-hour day shifts, 3x12, typical hours 06:30-18:30). Possibly also Qualifications (maybe same as Requirements). But we should avoid thin sections. Could combine Requirements and Qualifications into one section called "Requirements". Or we could have "Requirements" and "Qualifications" separate if we have distinct content. The posting lists: Current Washington license and AHA BLS and ACLS required and additional certifications related to this specialty. To qualify: residence at least 50 miles. Required: 2 years of recent experience. That's all requirements/qualifications. So we can put them under Requirements. Responsibilities: not given; we could omit. Skills: not given. Benefits: not given besides tax-free stipend (which is pay). Could omit Benefits. Thus we output sections: About the role, Requirements, Pay, Schedule. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info.
Let's craft:
About the role
Cure Healthcare Staffing is seeking a travel nurse RN specializing in Labor and Delivery for a 13‑week assignment in Silverdale, Washington. The position starts on October 12, 2026, requires 36 hours per week (12‑hour day shifts) and is a travel employment type.
That's prose.
Requirements
- Current Washington RN license
- AHA BLS and ACLS certifications (additional specialty‑related certifications may be required)
- Minimum 2 years of recent experience in Labor & Delivery
- Primary residence must be at least 50 miles from the facility
That's a list.
Pay
Pay package is based on 12‑hour shifts and 36.0 hours per week (subject to confirmation) and includes a tax‑free stipend (amount to be determined).
That's prose.
Schedule
- Shift pattern: 3×12‑hour day shifts
- Typical shift hours: 06:30 – 18:30
We could also mention duration 13 weeks, but that's more about assignment length; maybe we could include in About the role or Schedule. Could add to About the role: duration 13 weeks.
We need to ensure we didn't repeat job title as heading. We didn't.
We didn't include Job ID as heading; we could optionally include a short p with Job ID but not required. The instruction: fold minor metadata into a short or drop it. We could add a p at the end:
Job ID: 38178053
. That's minor metadata; we can include as a short p. It's not a heading. That seems okay.
We must not include boilerplate like About Cure Healthcare Staffing description? Actually we included some of that in About the role but we could also include a separate section about the company? The instruction: "Prefer a few substantive sections over many thin ones." The company description is substantive but not required for the job; but we could include it under About the role or maybe a separate section "About the employer". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list About the employer. So we should stick to those headings. The company description could be considered part of About the role? Not exactly. But we could incorporate some of it into About the role if relevant. However the About Cure Healthcare Staffing description is generic about the company; it's not specific to the role. Might be considered boilerplate? It's not navigation/legal/EEO, but it's still about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company description is not explicitly listed as boilerplate to remove, but it's not specific to the job posting; still it's substantive info about the employer. The instruction says "Prefer a few substantive sections over many thin ones." Could include a section "About the employer" but not in allowed headings. So we should not add a heading not in list. Could we incorporate into About the role? The About the role heading is for role description, not company. But we could add a paragraph about the employer inside About the role? Might be mixing. Better to keep About the role focused on the role; we can omit company description as it's not required for the job specifics. The instruction says preserve ALL substantive information; does company description count as substantive? It's about the employer, not the job. Might be considered substantive but not required for the applicant? However the instruction says preserve ALL substantive information; but also says "Prefer a few substantive sections over many thin ones." The company description is substantive but we could drop it if it's considered boilerplate? It's not explicitly listed as boilerplate to remove, but it's generic marketing fluff. Might be considered not essential. However to be safe, we could include a short paragraph about the employer under About the role? But the heading is About the role; we could add a sentence: "Cure Healthcare Staffing, a Joint Commission‑accredited agency with 20+ years of experience, provides flexible staffing solutions." That's still about the employer but could be considered part of the role context. I'd include it.
Thus About the role paragraph: "Cure Healthcare Staffing is seeking a travel nurse RN specializing in Labor and Delivery for a 13‑week assignment in Silverdale, Washington. The position starts on October 12, 2026, requires 36 hours per week (12‑hour
for prose. We need to preserve all substantive info. Let's craft:
About the role
Cure Healthcare Staffing is seeking a travel nurse RN specializing in Labor and Delivery for a 13‑week assignment in Silverdale, Washington. The position starts on October 12, 2026, requires 36 hours per week (12‑hour day shifts) and is a travel employment type.
That's prose.Requirements
- Current Washington RN license
- AHA BLS and ACLS certifications (additional specialty‑related certifications may be required)
- Minimum 2 years of recent experience in Labor & Delivery
- Primary residence must be at least 50 miles from the facility
Pay
Pay package is based on 12‑hour shifts and 36.0 hours per week (subject to confirmation) and includes a tax‑free stipend (amount to be determined).
That's prose.Schedule
- Shift pattern: 3×12‑hour day shifts
- Typical shift hours: 06:30 – 18:30
or drop it. We could add a p at the end:
Job ID: 38178053
. That's minor metadata; we can include as a short p. It's not a heading. That seems okay. We must not include boilerplate like About Cure Healthcare Staffing description? Actually we included some of that in About the role but we could also include a separate section about the company? The instruction: "Prefer a few substantive sections over many thin ones." The company description is substantive but not required for the job; but we could include it under About the role or maybe a separate section "About the employer". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list About the employer. So we should stick to those headings. The company description could be considered part of About the role? Not exactly. But we could incorporate some of it into About the role if relevant. However the About Cure Healthcare Staffing description is generic about the company; it's not specific to the role. Might be considered boilerplate? It's not navigation/legal/EEO, but it's still about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company description is not explicitly listed as boilerplate to remove, but it's not specific to the job posting; still it's substantive info about the employer. The instruction says "Prefer a few substantive sections over many thin ones." Could include a section "About the employer" but not in allowed headings. So we should not add a heading not in list. Could we incorporate into About the role? The About the role heading is for role description, not company. But we could add a paragraph about the employer inside About the role? Might be mixing. Better to keep About the role focused on the role; we can omit company description as it's not required for the job specifics. The instruction says preserve ALL substantive information; does company description count as substantive? It's about the employer, not the job. Might be considered substantive but not required for the applicant? However the instruction says preserve ALL substantive information; but also says "Prefer a few substantive sections over many thin ones." The company description is substantive but we could drop it if it's considered boilerplate? It's not explicitly listed as boilerplate to remove, but it's generic marketing fluff. Might be considered not essential. However to be safe, we could include a short paragraph about the employer under About the role? But the heading is About the role; we could add a sentence: "Cure Healthcare Staffing, a Joint Commission‑accredited agency with 20+ years of experience, provides flexible staffing solutions." That's still about the employer but could be considered part of the role context. I'd include it. Thus About the role paragraph: "Cure Healthcare Staffing is seeking a travel nurse RN specializing in Labor and Delivery for a 13‑week assignment in Silverdale, Washington. The position starts on October 12, 2026, requires 36 hours per week (12‑hour