Travel OR RN - $2,401 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 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 like cookie/navigation/legal/EEO etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: Start Date, Duration, 40 hours per week, Shift: 10 hours, days, Employment Type: Travel. Also schedule description: "This position requires flexibility to work daytime shifts from 7 AM to 5:30 PM, with the possibility of evening shifts as needed." So schedule info present. Pay: "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 vague but it's still some pay info. It says tax-free stipend amount to be determined. That's not specific amount, but it's still mention of pay. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on shifts, tax-free stipend amount to be determined. That's still stating something about pay, albeit not specific numbers. Should we include Pay section? It says "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 some info. I'd include a Pay section with that sentence. Benefits: The posting lists "Why ARMStaffing?" with bullet list of benefits: Health Benefits: Medical, Dental, Vision, Life, and more; Onboarding Made Easy; Clinical Support; 401k Retirement Plan; Recruiter Matching; Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more; plus accolades. So we have benefits content. So include Benefits section. Requirements: There's "Required Experience / Certifications / Licensure" list. Also "Job Description" prose. Also "Operating Room Nurse - Surgical Specialty Schedule" maybe part of schedule. Also "Job Description" heading? The posting includes "Job Description" as a heading but we should not repeat job title as heading; but we can use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has "Job Description & Requirements" then "Specialty: OR - Operating Room", "Discipline: RN", "Start Date: 10/15/2026", "Duration: 13 weeks", "40 hours per week", "Shift: 10 hours, days", "Employment Type: Travel", then "Operating Room Nurse - Surgical Specialty Schedule" then "Job Description" paragraph, then "Responsibilities" list, then "Required Experience / Certifications / Licensure" list, then "Why ARMStaffing?" with benefits, then accolades, then contract & local rates may vary..., then Job ID line, then Pay package line, then Posted job title line, then About ARMStaffing paragraph. We need to extract substantive info and put into appropriate sections. We should not include headings like "About the role" if we don't have that content; we could use "About the role" for the About ARMStaffing paragraph? Actually "About the role" could be the job description summary. The posting has a "Job Description" paragraph describing role responsibilities. That could go under "About the role" or maybe "Responsibilities". But we already have Responsibilities list. The "Job Description" paragraph is more of an overview. Could put under

About the role

with that paragraph. Responsibilities: we have list. Requirements: we have list of required experience/certifications/licensure. Could also include "Required Experience / Certifications / Licensure". That is requirements. Qualifications: maybe same as requirements? But we can combine. The instruction: prefer few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Skills? The posting mentions "Utilize strong skills in vascular and orthopedic surgery, primarily in a circulating role." That's a skill. Could be included in Responsibilities or Requirements. Probably not need separate Skills. Schedule: we have shift details and flexibility. Pay: we have pay package line. Benefits: we have list. We must not include headings with filler. Ensure we don't include empty sections. Now produce HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information. Let's extract. About the role paragraph: "The Operating Room Nurse is responsible for providing comprehensive surgical patient care by assessing, planning, and implementing nursing care throughout the surgical process. This includes both pre-operative and post-operative stages, ensuring patient safety and a sterile environment." That's from Job Description. Responsibilities list items: - Conduct patient assessments and develop appropriate care plans. - Maintain a sterile and safe environment in the operating room. - Provide pre and post-operative patient education. - Monitor patients' physical and emotional well-being. - Coordinate care with interdisciplinary team members throughout the surgical process. - Utilize strong skills in vascular and orthopedic surgery, primarily in a circulating role. - Assist in a variety of surgical specialties, excluding cardiac and ophthalmology. Note: The last two are maybe skills but we keep as responsibilities. Requirements list items (from Required Experience / Certifications / Licensure): - 2+ years of current Operating Room (OR) nursing experience. - Experience in floating to vascular, orthopedic, trauma, general surgery, robotics, urology, and ENT. - Travel experience is required. - EPIC experience is mandatory. - Current BLS and ACLS certifications are required. - Must possess both scrub and circulate experience. - A valid New York Temporary Health Care Service Agency License/Registration Certificate is required. - Must be able to lift up to 50 lbs. Also maybe include Start Date, Duration, 40 hours per week, Shift: 10 hours, days, Employment Type: Travel. Those could go under Schedule or maybe a separate "Job Details" but we only have allowed headings. Could put under Schedule: include shift details, hours per week, start date, duration, employment type. Schedule section content: maybe a paragraph: "Start Date: 10/15/2026. Duration: 13 weeks. 40 hours per week. Shift: 10 hours, days. Employment Type: Travel. This position requires flexibility to work daytime shifts from 7 AM to 5:30 PM, with the possibility of evening shifts as needed." Pay section: "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." Benefits section: list items from Why ARMStaffing? plus accolades? The accolades are also part of why ARMStaffing? but they are more about company reputation. Could include as part of benefits? Might be considered "Why ARMStaffing?" but we can treat as benefits/perks. The list: - Health Benefits: Medical, Dental, Vision, Life, and more - Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care - Clinical Support: In-house clinical team available to assist and advocate - 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution - Recruiter Matching: Get paired with a recruiter based on your location and specialty - Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more - SIA’s Top-50 Fastest Growing Healthcare Staffing Firms – 2019 - SIA’s Largest Healthcare Staffing Agencies in the U.S. – 2023 - Top Workplace in the Lehigh Valley – 2022, 2023 - Perfect scores for 'Name, Not a Number' and 'Recruiters' Personalities' on Highway Hypodermics - Earned The Joint Commission’s Gold Seal of Approval for healthcare staffing 15 years strong and counting! We could keep as list items. Now ensure we don't include duplicated lines. Also remove boilerplate like "Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details!" That's somewhat about pay but it's vague; maybe we can include in Pay section? It's not specific pay. Might be considered boilerplate. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That line is not exactly boilerplate but it's about rates varying. Could be considered part of Pay info. However it's vague. Might be okay to include but it's not specific. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package line; the extra line about rates may vary is also stating something about pay. I'd include it in Pay section as a sentence. Also remove "Posted job title: RN:OR,07:00:00-17:00:00" etc. That's metadata. Also remove "About ARMStaffing" long paragraph? That's about company, not necessarily benefits. Could be considered boilerplate? It's describing the company. Might be considered not substantive to the job. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The About ARMStaffing paragraph is about the company, not the job. Might be considered boilerplate? It's not navigation/legal/EEO but it's generic company description. Could be considered not needed for job posting? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove company description. However earlier they said "Prefer a few substantive sections over many thin ones." The About ARMStaffing paragraph is not about the role; could be omitted as not substantive to the job? But it's still information about the employer. Might be considered part of Benefits? Not really. I'd keep it maybe under a section "About the company"? Not allowed headings. Could incorporate into Benefits? Not ideal. Safer to omit because it's not directly about the role, responsibilities, requirements, benefits, pay, schedule. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit it, we are losing info. But is it substantive? It's describing the company's services, experience, etc. Might be considered fluff but still info. However the allowed headings are limited; we could add a section "About the company" but not in allowed list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. So we should only use those headings. So we cannot add a heading like "About the company". So we must fit that info into one of those allowed sections. Could fit into Benefits? Not really. Could fit into About the role? That section is about the role, not company. Could we put company info under About the role? That would be mixing. Probably better to omit company description as it's not directly about the role and not fitting allowed headings. The instruction says preserve ALL substantive information; but if we cannot fit it into allowed headings without violating the heading rule, maybe