Travel L&D OR RN - $3,241 per week

We need to output HTML fragment only, with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must parse the job posting. Key info: - Focus Staff seeking travel nurse RN Labor and Delivery for travel nursing job in Raleigh, NC. - Specialty: Labor and Delivery - Discipline: RN - Start Date: 10/12/2026 - Duration: 13 weeks - 48 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Contract Length: 13 (weeks) - Start Date: 10/12/2026 - Shift: 4x12 Nights - Why L&D Nurses choose Focus Staff: Rewarding Your Commitment: Weekly direct deposits, housing stipends, 401(k) with matching, and loyalty/referral bonuses. - Your Wellbeing, Our Priority: Medical, dental, vision, and life insurance from day one, no waiting period. - Journey Made Simple: Travel assistance, relocation support, licensure reimbursement, and exclusive hotel discounts. - Flexibility Meets Support: Dedicated recruiters, 24/7 support, flexible scheduling, and pet-friendly accommodations. - Labor & Delivery RN Requirements: Minimum of 1-2 years of experience in a cardiac catheterization lab setting. (Note: This seems odd: L&D RN requiring cardiac cath lab experience; but we must preserve as is.) - Valid Registered Nurse (RN) license in the state of practice - Current Basic Life Support (BLS) and Advanced Cardiac Life Support (ACLS) certification. - About Focus Staff: description. - Job Type: Contract/Temporary/Travel - Location: Raleigh, NC - Date Posted: 09/01/2026 12:00:00 AM - Valid Through: 01/09/2027 - Job City: Raleigh - Job State: NC - Job Country: USA - Shift: 4x12 Nights - Job ID: a0xVt00000UDcj0IAD - Hiring Organization: Focus Staff - EEO statement (remove) - Estimated pay package based on bill rate... (Pay info: mention pay package based on bill rate, tax-free stipend amount to be determined, based on 12 hour shifts and 48.0 hours per week). This is vague but includes some pay info. However rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention pay package based on bill rate, tax-free stipend amount to be determined. That's somewhat vague but still mentions pay. Should we include Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay package, albeit not specific numbers. It says "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on several factors, including, but not limited to, guaranteed hours, travel distance, demand, experience, etc." Also "Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's some info about pay. So we can include a Pay section with that info. Schedule: The posting states shift: 4x12 Nights, 48 hours per week, 12 hour shifts nights. So we have schedule info. So we can include Schedule section. Benefits: The posting lists benefits: weekly direct deposits, housing stipends, 401(k) with matching, loyalty/referral bonuses; medical, dental, vision, life insurance from day one; travel assistance, relocation support, licensure reimbursement, exclusive hotel discounts; dedicated recruiters, 24/7 support, flexible scheduling, pet-friendly accommodations. So we have benefits. Thus we can include Benefits, Pay, Schedule sections. Also we need About the role (maybe a summary). Responsibilities? Not explicitly listed; we have description about providing exceptional support and care to expectant mothers and families. Could be considered responsibilities. But we need to see if there is specific content for Responsibilities. The posting says: "Start your next rewarding travel Labor and Delivery (L&D) RN assignment with Focus Staff in Raleigh, NC. Bring your expertise and passion for maternal and newborn care to diverse environments, where you will provide exceptional support and care to expectant mothers and their families. Design your travel nurse career path, one delivery at a time." That's more about role. Could be About the role. Responsibilities maybe not explicit. We could skip Responsibilities if no explicit list. Qualifications: The requirements list could be considered Qualifications. But we have Requirements section already. The rules: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have Requirements (experience, license, certifications). We could also have Qualifications (maybe same as Requirements). Better to not duplicate. We'll include Requirements. Skills: Not explicitly listed; maybe we could infer but better not to invent. So skip Skills. About the role: we have a paragraph describing the role. So include About the role. Thus sections: About the role, Requirements, Benefits, Pay, Schedule. We must not repeat job title as heading. Not include Job ID etc as headings; we can fold minor metadata into a short

or drop it. We could include a short paragraph with location, start date, duration, shift etc maybe in About the role or separate? But we should preserve all substantive information. So we need to include location, start date, duration, shift, etc somewhere. We can incorporate them into About the role paragraph or a separate

maybe under About the role. But we must not create extra headings for minor metadata. So we can embed them in About the role paragraph. Let's craft About the role paragraph: "Focus Staff is seeking a travel nurse RN Labor and Delivery for a travel nursing job in Raleigh, North Carolina. Specialty: Labor and Delivery; Discipline: RN; Start Date: 10/12/2026; Duration: 13 weeks; 48 hours per week; Shift: 12 hours, nights (4x12 Nights). Employment Type: Travel." That preserves. Then Requirements: list items. Benefits: list items grouped maybe as subpoints but we can just list all benefits in a

• . Could categorize but not required. Pay: include paragraph about estimated pay package based on bill rate, tax-free stipend to be determined, based on 12 hour shifts and 48 hours per week. Schedule: include paragraph about shift: 4x12 Nights, 48 hours per week, 12 hour shifts nights. We must not include boilerplate like EEO, application instructions, etc. Now produce HTML fragment. We need to use

  for each section heading. Structure:

  About the role

  ...

  Requirements

  • Minimum of 1-2 years of experience in a cardiac catheterization lab setting.
  • Valid Registered Nurse (RN) license in the state of practice.
  • Current Basic Life Support (BLS) and Advanced Cardiac Life Support (ACLS) certification.

  Benefits

  • Weekly direct deposits
  • Housing stipends
  • 401(k) with matching
  • Loyalty/referral bonuses
  • Medical, dental, vision, and life insurance from day one, no waiting period
  • Travel assistance
  • Relocation support
  • Licensure reimbursement
  • Exclusive hotel discounts
  • Dedicated recruiters
  • 24/7 support
  • Flexible scheduling
  • Pet-friendly accommodations

  Pay

  Estimated pay package based on bill rate at time of posting; exact package may vary based on guaranteed hours, travel distance, demand, experience, etc. Pay package is based on 12‑hour shifts and 48.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.

  Schedule

  Shift: 4×12‑hour nights (48 hours per week).

  Make sure to use proper HTML entities? Use plain text. Check for any repeated content: we included shift info both in About the role and Schedule; that's okay but maybe redundant. However we need to preserve all substantive information; duplication is okay but maybe we could avoid duplication by moving shift info only to Schedule and not repeat in About the role. But About the role already includes start date, duration, etc. We could keep shift info only in Schedule and not repeat. Let's adjust About the role to exclude shift (maybe mention "Shift: 12 hours, nights" but we can keep it brief. However we need to preserve all substantive info; if we mention it only in Schedule, it's still preserved. So we can omit from About the role. Thus About the role: "Focus Staff is seeking a travel nurse RN Labor and Delivery for a travel nursing job in Raleigh, North Carolina. Specialty: Labor and Delivery; Discipline: RN; Start Date: 10/12/2026; Duration: 13 weeks; 48 hours per week; Employment Type: Travel." Now Schedule: "Shift: 4×12‑hour nights (48 hours per week)." Now ensure we didn't miss any substantive info: Job location (Raleigh, NC) included. Start date, duration, hours per week, employment type. Also we have "Contract Length: 13" (same as duration). Good. We also have "Job Type: Contract/Temporary/Travel" - we included Employment Type: Travel; maybe also mention Contract/Temporary. Could add "Contract/Temporary/Travel". Let's incorporate in About the role: "Employment Type: Travel (Contract/Temporary)". Or we can add separate line. Let's add: "Employment Type: Travel (Contract/Temporary)". Good. Also we have "Job ID: a0xVt00000UDcj0IAD" - minor metadata; we can drop or fold into a short p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could add a small paragraph at end maybe not under a heading. But we should avoid extra headings. Could add a

  with Job ID and posting date etc. However that might be considered boilerplate? It's not navigation/legal/EEO; it's metadata. The instruction says fold minor metadata into a short

  or drop it. So we can include a short p at the end (outside any heading) with Job ID and date posted. But we must ensure we don't create a heading for it. It's okay to have a stray

  not under a heading? The instruction says output only HTML fragment; we can have

  elements anywhere. However typical sections are headed by

  . Having a stray

  without heading might be okay but could be considered not part of a section. Safer to fold it into About the role paragraph as a short note? But that might be weird. Perhaps better to add a

  after the sections with the metadata. It's not a heading, so it's allowed. The instruction says "fold minor metadata into a short

  or drop it." So we can add a

  containing Job ID, date posted,