Travel OR RN - $2,173 per week

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes: Benefits listed: 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. So we have benefits details. Pay: The posting mentions "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Also earlier: "*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." So we have some pay info but not a specific number. It says tax-free stipend amount to be determined. This is somewhat vague but still some content. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here we have "tax-free stipend amount to be determined" which is similar to TBD. Might be considered placeholder. Also "Estimated weekly pay includes projected hourly wages..." but no actual number. This might be considered not specific enough. The rule: "Prefer a few substantive sections over many thin ones." If pay info is not specific (no number), maybe we should omit Pay section. However we have some description about pay being based on shifts etc. But it's still vague. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 10 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That is stating something about pay, albeit not a number. Is that considered stating them? It states that pay package is based on shifts and hours, with stipend TBD. That's still some info. But the rule about filler/placeholder text: "tax-free stipend amount to be determined" is like TBD. Might be considered placeholder. Safer to omit Pay section? However we have Schedule: Shift: 10 hours, days; Total Weekly Hours: 40; Start Date: 09/21/2026; Duration: 13 weeks (13.14 weeks). So schedule info is specific: shift length, days, weekly hours, start date, duration. That's substantive. So we should include Schedule section. Responsibilities: The posting includes "Must have circulating skills". That's a skill requirement. Also "Certifications: RN". That's a qualification. There's not a explicit responsibilities list beyond that. Could treat "Must have circulating skills" as a skill. Responsibilities maybe not explicit. Could we infer responsibilities from OR RN? Not given. Better to not create Responsibilities section if no specific content. Requirements: Could include Certifications: RN, Must have circulating skills. Also maybe Trauma Level: Facility Specific (not a requirement). Could list under Requirements. Qualifications: Could be RN license, maybe experience? Not given. Might skip. Skills: Could list circulating skills. Benefits: we have details. Pay: uncertain. Schedule: we have details. About the role: Could be a summary: "Junxion Med Staffing is looking for a OR RN to take an assignment in Hendersonville, Tennessee. This assignment lasts 13.14 weeks and is scheduled to start on September 21, 2026." That's substantive. So we can have About the role section. We must not repeat job title as heading. So we can have

About the role

etc. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all specifics: start date, duration, shift, weekly hours, certifications, circulating skills, benefits details (insurance plans under $175/month, referral bonus, additional contract bonus opportunities, vacation incentives, EAP, 401k with access to financial advisors, weekly pay, 401k retirement plan, referral bonus, medical benefits, dental benefits, vision benefits, mileage reimbursement). Note some duplication: referral bonus appears twice; we should not duplicate lines. We need to remove duplicated lines. So we should combine unique benefits. List unique 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 - Weekly pay (mentioned as part of benefits list) - Medical benefits - Dental benefits - Vision benefits - Mileage reimbursement Also "401k retirement plan" appears similar to "401k with access to financial advisors". Might be duplicate; we can keep one. We need to avoid duplication. So we can list: - 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 - Medical benefits - Dental benefits - Vision benefits - Mileage reimbursement Now schedule details: - Shift: 10 hours, days - Total Weekly Hours: 40 - Start Date: September 21, 2026 - Duration: 13.14 weeks (or 13 weeks? The posting says "This assignment lasts 13.14 WEEKS". Also earlier "Duration: 13 weeks". We'll keep the more precise 13.14 weeks. Now About the role: include summary: "Junxion Med Staffing is looking for a OR RN to take an assignment in Hendersonville, Tennessee. This assignment lasts 13.14 weeks and is scheduled to start on September 21, 2026." Also maybe mention that they often have multiple openings; but that's not substantive? Could include but it's more about process. Might be okay. Requirements: list: - RN license (Certifications: RN) - Must have circulating skills Qualifications: maybe none specific beyond RN. Could omit. Skills: maybe "Circulating skills" (already in requirements). Could list under Skills. But we need to avoid duplication. Could combine Requirements and Skills? But we need to follow headings only if content exists. We could have Requirements section with list: RN license, Circulating skills. Skills section maybe not needed if same. But we could have Skills: Circulating skills. However that duplicates. Better to have Requirements include both, and omit Skills. But we need to follow instruction: Use

  • for any list of duties/requirements/benefits. So for Requirements we can list. Now Benefits: list as above. Pay: we might omit because it's vague. However we have "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's still some info but includes TBD. Might be considered placeholder. Safer to omit Pay section. Schedule: list as above. Now we need to ensure we don't include boilerplate like EEO, application instructions, etc. Now produce HTML fragment:

    About the role

    Junxion Med Staffing is looking for a OR RN to take an assignment in Hendersonville, Tennessee. This assignment lasts 13.14 weeks and is scheduled to start on September 21, 2026.

    Requirements

    • RN license
    • Must have circulating skills

    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
    • Weekly pay
    • Medical benefits
    • Dental benefits
    • Vision benefits
    • Mileage reimbursement

    Schedule

    • Shift: 10 hours, days
    • Total Weekly Hours: 40
    • Start Date: September 21, 2026
    • Duration: 13.14 weeks
    Check for any missing substantive info: The posting also mentions "Trauma Level: Facility Specific" - not a requirement, just info. Could we include under Requirements? It's not a requirement but a facility attribute. Probably not needed. Also "Certifications: RN Requested Skill Set: Must have circulating skills Certifications Required: RN" duplicates. Also "When you apply with Junxion, you speak with a live U.S.-based recruiter..." that's about process, maybe could be included in About the role? But it's about recruiter support. Could be considered substantive but maybe not required. The instruction: preserve ALL substantive information. That includes that info. Should we include? It's about the recruiter process, not the role itself. Might be considered substantive. However we have limited sections; we could add a section like "Support" but not in allowed headings. Allowed headings are only those listed. So we cannot create a new heading. We could fold into About the role as prose. That would preserve it. So we can add sentences about recruiter support. Similarly "Junxion was built by a traveler and designed to support travelers..." etc. That's about company. Could be included in About the role or maybe we could add a section "About the Company" but not allowed heading. So we fold into About the role. We must not create headings not listed. So we can only use the given headings. So we need to fit all substantive info into those sections. Thus About the role can include: summary, recruiter support, company mission, etc. Let's craft About the role paragraph(s) that include: - Junxion Med Staffing is looking for a OR RN to take an assignment in Hendersonville, Tennessee. - Assignment lasts 13.14 weeks, start Sep 21, 2026. - You will speak with a live U.S.-based recruiter, no call centers, dedicated recruiter and support team. - Junxion was built by a traveler, aims to provide strong support, transparent communication, assignments that make sense. - They partner with hospitals nationwide, etc. We need to avoid fluff but preserve details. Now Benefits: we have list. Now Requirements: we have list. Now Schedule: we have list. Now we need to ensure we don't include any boilerplate like EEO, duplicated lines, application instructions, etc. Check for any other substantive info: "Click here for licensing requirements" - that's a link, maybe not needed. "About Junxion Med Staffing" details about founders, specialties, etc. Could be included in About the role. We must not repeat job title as heading. Good. Now produce final HTML. Make sure no extra