Travel ER RN - $2,074 per week

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract substantive info. Job posting: Title: travel nurse RN ED - Emergency Department. Location: Junction, Texas. Specialty: ED - Emergency Department. Discipline: RN. Start Date: 10/12/2026. Duration: 13 weeks (also says 13.14 weeks). 36 hours per week. Shift: 12 hours, nights. Employment Type: Travel. Summary: looking for ER RN assignment in Junction, Texas. Assignment lasts 13.14 weeks, start Oct 12, 2026. If start date, shift, or pay doesn’t line up... talk. We often have multiple openings... call opt 1. Job Details: Shift: 12H Nights, Total Weekly Hours: 36, Certifications: Trauma Level: Facility Specific. Job Notes: Thank you... If you need further assistance... When you apply with Junxion, you speak with a live U.S.-based recruiter... No call centers... Our team works directly with you throughout your assignment. 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. About the Company: Junxion Med Staffing partners with hospitals... goal: provide strong support, transparent communication, assignments that make sense for your career and life. *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... For all employees... EEO Employer... Junxion Med Staffing Job ID #1390843. 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. About Junxion Med Staffing: founded by former healthcare traveler... specialize in placing travel nurses... etc. bullet points: Transparent communication, Dedicated support, Competitive pay and benefits, A focus on your success. Benefits (again): Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Click here for licensing requirements". Remove EEO lines. Remove duplicated benefit lists? We need to preserve all substantive info, but we can combine duplicate benefit info into one Benefits section. We need sections only if real specific content. Let's decide which sections to include: - About the role: could include summary of role: ER RN assignment, location, specialty, discipline, start date, duration, shift, weekly hours, employment type. That seems appropriate. - Responsibilities: Not provided explicitly. The posting does not list duties/responsibilities. So we should not create Responsibilities section. - Requirements: Could include certifications: Trauma Level: Facility Specific. Also maybe RN license implied. But we have "Certifications: Trauma Level: Facility Specific". That's a requirement. Also maybe need RN license. Not explicitly stated but implied by discipline RN. Could include "RN license" as requirement? Might be considered inferred but we should not invent. Better to include only explicit: Certifications: Trauma Level: Facility Specific. Also maybe "RN" as discipline is a qualification. Could put under Qualifications. - Qualifications: Discipline: RN, maybe need active RN license. Not explicit. We'll include Discipline: RN as qualification. - Skills: Not listed. - Benefits: We have multiple benefit items: 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, Weekly pay (maybe part of pay), Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. Also "Competitive pay and benefits" but that's generic. We'll list specific benefits. - Pay: The posting mentions "Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems... Actual weekly pay may differ". Also "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." No specific numbers. Since we should not create Pay section unless posting actually states them. It does mention estimated weekly pay but no actual amount. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The posting says "Estimated weekly pay includes projected hourly wages..." but no actual number. That's somewhat vague but still mentions estimated weekly pay. However it's not a specific number; it's a description. Is that considered filler? It says "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 from the amount shown and may be subject to change during an assignment." This is not a specific number but it's describing how pay is calculated. It might be considered substantive? The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". This is not exactly those, but it's still vague. However we could include a Pay section with that description? Might be okay. But we also have "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." That's also vague. I'd lean to not include Pay section because no concrete numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Estimated weekly pay includes projected hourly wages..." which is a statement about pay, albeit not a number. I'd say it's stating something about pay, so we could include Pay section with that description. However the rule also says "Prefer a few substantive sections over many thin ones." If we include Pay with vague description, maybe it's thin. Might be better to omit Pay and incorporate pay info into About the role or Benefits? But Benefits already separate. The rule: "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The phrase "Estimated weekly pay includes projected hourly wages..." is not filler? It's a description but not a specific number. Could be considered real content. I'd include Pay section with that sentence. - Schedule: We have shift: 12 hours, nights; total weekly hours: 36; duration: 13 weeks; start date: Oct 12, 2026. That's schedule info. So we can have Schedule section with those details. Now we need to avoid duplication: The posting also mentions "Start Date: 10/12/2026", "Duration: 13 weeks", "36 hours per week", "Shift: 12 hours, nights". We'll put those in Schedule. Now About the role: Should include summary: "Junxion Med Staffing is looking for a ER RN to take an assignment in Junction, Texas. This assignment lasts 13.14 weeks and is scheduled to start on October 12, 2026." Also maybe mention specialty, discipline, location. Also mention employment type: Travel. Also maybe mention "If the start date, shift, or pay doesn’t line up with what you're looking for, let’s talk. We often have multiple openings in the same market. Give us a call opt 1". That's kinda application instruction? It's a call to action. Might be considered boilerplate? It's not exactly application instructions but it's a prompt to call. Might be considered a call to action; but we are to remove application instructions. This is more like a contact encouragement. Might be considered boilerplate? I'd drop it as it's not substantive job detail. Also "Job Details: Shift: 12H Nights Total Weekly Hours: 36 Certifications: Trauma Level: Facility Specific" we already captured shift/hours in Schedule, certifications in Requirements. Job Notes: Thank you... If you need further assistance... When you apply with Junxion, you speak with a live U.S.-based recruiter... No call centers... Our team works directly with you throughout your assignment. That's more about company process; could be considered boilerplate? It's describing recruiter support. Might be considered part of About the Company? Could be included in About the role? It's about support. Might be considered part of About the Company or Benefits? It's not a benefit per se. Could be omitted as it's more about process. However the rule says preserve ALL substantive information; do NOT invent or summarize away detail. This is substantive about recruiter support. Could be included in About the Company section? But we don't have a heading for About the Company; we only have allowed headings list. We could put that info under About the role? It's not exactly about the role but about the staffing agency. Might be better to include under About the role? The allowed headings are limited; we cannot add custom headings. So we must fit into those headings. The info about recruiter support could be considered part of Benefits? Not exactly. Could be part of About the role? It's about the role's support. Might be okay to put under About the role as additional detail. But we also have About the Company section later: "Junxion Med Staffing partners with hospitals...". That's also about the company. Could be placed under About the role? Might be better to have a section for About the Company but not allowed. So we need to incorporate that info into allowed headings. Perhaps we can put company description under About the role? Or maybe we can create a section "About the role" that includes both role and company info. That seems plausible. Now Benefits: we have many items. We'll list them as

• . Now Schedule: we have start date, duration, shift, weekly hours. Now Requirements: we have certifications: Trauma Level: Facility Specific. Also maybe need RN license (implied). We'll include "Active RN license" as requirement? Not explicit. Safer to only include explicit: "Trauma Level: Facility Specific (certification)". Also maybe "RN" discipline is a qualification. Qualifications: Discipline: RN. Also maybe "ER experience"? Not explicit. We'll just put "RN (Emergency Department)". Now we need to avoid repeating job title as heading. We'll not. Now we need to output only HTML fragment. Let's craft:

  About the role

  Junxion Med Staffing is seeking a travel nurse RN for the Emergency Department (ED) in Junction, Texas. This travel assignment is scheduled to start on October 12, 2026 and lasts approximately 13.14 weeks. The position is a 36‑hour per week role with 12‑hour night shifts.

  Maybe also include "Employment Type: Travel". Add that.

  Requirements

  • Trauma Level certification (facility‑specific)

  Qualifications

  • Registered Nurse (RN) license
  • Emergency Department experience (implied by specialty)
  But "Emergency Department experience" is not explicit; we might avoid. Better to just list RN license.

  Benefits

  • Insurance plans starting under $175/month for employees
  • Referral bonus
  • Additional contract bonus opportunities
  • Vacation incentives