Travel L&D RN - $2,482 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. Key details: - Job: travel nurse RN Labor and Delivery in Del Rio, Texas. - Specialty: Labor and Delivery - Discipline: RN - Start Date: 10/19/2026 - Duration: 13 weeks (also says 12.86 weeks) - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Summary: L&D RN assignment in Del Rio, Texas. Assignment lasts 12.86 weeks, start Oct 19, 2026. If start date, shift, or pay doesn’t line up, talk. Often multiple openings. - Job Details: Shift: 12H Days, Total Weekly Hours: 36 - Certifications: Fetal Monitoring, NRP, ACLS, BLS - Trauma Level: Facility Specific - Job Notes: Must have 2 years experience and prior travel. Must have TX or compact license on file at time of submission. Cert Req: Fetal Monitoring, NRP, ACLS, BLS. Preferred: Stable. - When you apply with Junxion, you speak with a live U.S.-based recruiter... (this is more about company, maybe about support) - Benefits: Insurance Plans starting under $175/month for employees, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors. - Also later: Benefits list: Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. - Pay: "Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems for eligible clinicians based on nationally published GSA rates. Actual weekly pay and per diems may differ... 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." So pay info is not specific numbers, just mention of estimated weekly pay based on GSA rates, tax-free stipend TBD. This is vague; we should not create Pay section unless posting actually states them. It says "Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems..." That's some info but not a specific number. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Since pay amount is TBD, we should not create a Pay section. However we could include a Pay section if we have some info like "Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems..." That's still not a specific number but it's some description. The rule says avoid filler/placeholder text like "TBD". The phrase "tax-free stipend amount to be determined" is TBD. So better to omit Pay section. - Schedule: we have shift: 12 hours, days; 36 hours per week. That's specific. So we can include a Schedule section. - Benefits: we have specific benefits: Insurance Plans starting under $175/month, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors. Also later list: Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. Some overlap. We should combine and list unique benefits. Avoid duplication. We'll list: Insurance plans starting under $175/month, Referral bonus, Additional contract bonus opportunities, Vacation incentives, Employee Assistance Program (EAP), 401k with access to financial advisors, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. Weekly pay is mentioned but it's part of pay; we already decided not to include Pay section. However weekly pay is a benefit? It's compensation. Might be considered pay. Since we omitted Pay, we might not list weekly pay as benefit. But the benefits list includes "Weekly pay". However that is essentially compensation; but we could still list as a benefit if we want. But given we omitted Pay section due to lack of specific numbers, we could still mention weekly pay as a benefit? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated, so we can include Benefits section. Within that we can list items; we can include "Weekly pay" as a benefit item if it's stated. It is stated: "BenefitsWeekly pay401k retirement planReferral bonusMedical benefitsDental benefitsVision benefitsMileage reimbursement". So we can include that. Thus Benefits section will have a list. - About the role / Responsibilities: The posting includes a summary and job notes. Could treat as About the role (description). We'll create an

About the role

with paragraphs describing the assignment: L&D RN in Del Rio, Texas, start date, duration, hours, shift, etc. - Requirements / Qualifications: Must have 2 years experience and prior travel, TX or compact license, certifications: Fetal Monitoring, NRP, ACLS, BLS. Preferred: Stable (maybe meaning stable work history?). We'll put Requirements. - Skills: Could list certifications as skills? But we already have them in Requirements. Could also list skills like L&D nursing, fetal monitoring, etc. But to avoid thin sections, maybe combine Requirements and Skills? The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Requirements, Benefits, Schedule. That's four sections. - Schedule: we have shift and hours. - Pay: omitted. Now we need to ensure we don't repeat job title as heading. Not include Job ID. We need to remove boilerplate: EEO, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions ("Click here for licensing requirements", "Give us a call opt 1", etc). Also remove "About the Company:" and "About Junxion Med Staffing" sections? Those are about company; could be considered boilerplate but they contain some substantive info about company mission. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About the Company:" might be considered company description, not strictly boilerplate. However it's somewhat generic but still specific to Junxion. Might be okay to keep as part of About the role? But we already have About the role describing the job. The company description could be considered extra but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company description if it's substantive. However the sections we can use are limited to the headings list. We could put company description under About the role or maybe under a separate section like "About the company" but that's not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit company description into one of those. Probably About the role can include both job and company info. Or we could put under Responsibilities? Not ideal. We'll incorporate company description into About the role paragraph. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must output only HTML fragment, no /, no markdown. Let's craft:

  About the role

  Junxion Med Staffing is seeking a travel nurse RN specializing in Labor and Delivery for an assignment in Del Rio, Texas. The assignment starts on October 19, 2026 and lasts approximately 12.86 weeks (13 weeks) with a schedule of 12‑hour day shifts, totaling 36 hours per week. Junxion Med Staffing partners with hospitals nationwide to provide transparent communication, dedicated recruiter support, and competitive pay and benefits, aiming to match clinicians with meaningful opportunities that fit their career and life.

  Requirements

  • Active RN license in Texas or a compact state (must be on file at submission)
  • Minimum 2 years of Labor and Delivery experience
  • Prior travel nursing experience
  • Current certifications: Fetal Monitoring, NRP, ACLS, BLS

  Benefits

  • Insurance plans starting under $175 per month for employees
  • Referral bonus
  • Additional contract bonus opportunities
  • Vacation incentives
  • Employee Assistance Program (EAP)
  • 401(k) plan with access to financial advisors
  • Medical, dental, and vision benefits
  • Mileage reimbursement
  • Weekly pay (based on projected hourly wages and GSA meal/lodging per diems)

  Schedule

  12‑hour day shifts, 36 hours per week.

  Check for any duplicated content: We included weekly pay in benefits; it's okay. We need to ensure we didn't include any filler like "commensurate with experience". Not present. We didn't include Pay section. We didn't include Job ID. We didn't include application instructions like "Click here for licensing requirements" or "Give us a call opt 1". Good. We didn't include EEO boilerplate. We didn't include navigation. Now ensure we didn't miss any substantive info: Start date, duration, shift, hours, location, specialty, discipline, certifications, experience, license, recruiter support, company mission, benefits list. We captured most. We didn't explicitly mention "Trauma Level: Facility Specific". That's minor; could be omitted as not critical? It's substantive but minor. Could we add to About the role? Possibly add a sentence: "The facility’s trauma level is specific to the hospital." Might be okay. But we can leave it out; the instruction says preserve ALL substantive information. So we should include it. Let's add to About the role: "The assignment is at a facility with a trauma level that is specific to the hospital." Or we could add a separate line in Requirements? Not exactly a requirement. We'll add to About the role. Also we didn't mention "Preferred: Stable." That's vague; maybe means stable work history. Could be considered a preference but it's vague; we might omit as it's not specific. The instruction says avoid filler like "N/A", "TBD". "Stable" is vague but maybe it's a preference for stable employment history. Could be considered substantive but vague. Safer to omit? It's a preference but not specific. I'd omit. We didn't mention "Cert Req: Fetal Monitoring, NRP, ACLS, BLS." Already captured. We didn't mention "Must have 2 years experience and prior travel." captured. We didn't mention "When you apply with Junxion, you speak with a live U.S.-based recruiter..." we captured recruiter support. We didn't mention "Junxion was built by a traveler and designed to support travelers." captured in company mission. We didn't mention "Click here for licensing requirements" - removed. We didn't mention "About Junxion Med Staffing" paragraphs; we incorporated mission. We didn't mention "BenefitsWeekly pay401k retirement planReferral bonusMedical benefitsDental benefitsVision benefitsMileage reimbursement" - we listed those. We didn't