Travel Endoscopy RN - $1,861 per week
ARMStaffing · Orangeburg, SC · 1 mo ago
On-siteHealthcareFull-time
We need to output HTML fragment with sections for headings present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Key info:
- Job title: travel nurse RN Endoscopy (but we don't repeat as heading)
- Location: Orangeburg, South Carolina.
- Specialty: Endoscopy
- Discipline: RN
- Start Date: 10/20/2026
- Duration: 13 weeks
- 40 hours per week
- Shift: 8 hours, days
- Employment Type: Travel
- Additional details: Schedule 5x8-hour shifts from 6:00 AM to 2:30 PM, with every third weekend on call from 3 PM Friday to 6 AM Monday.
- Responsibilities: list bullet points.
- Required Experience / Certifications / Licensure: Minimum 2 years Endoscopy experience; SC RN license or Compact; ACLS and BLS certifications.
- Why ARMStaffing? Benefits list: 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.
- Pay package: based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. So pay info is vague: "tax-free stipend amount to be determined". That's not specific; we should not create Pay section unless posting actually states them. It says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific amount; it's vague. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include Pay section because it's not specific.
- Schedule: we have specific schedule: 5x8-hour shifts from 6:00 AM to 2:30 PM, with every third weekend on call from 3 PM Friday to 6 AM Monday. That's specific. So we can include Schedule section.
- Benefits: we have specific benefits listed: 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. Also accolades but those are not benefits. So we can include Benefits section.
- About the role: we have job description prose: "The Endoscopy RN will be responsible for providing care and support during endoscopic procedures. The role requires the nurse to stay within a 30-minute radius of the facility to be available for call duties and to participate in weekend on-call rotations. The Endoscopy RN will work closely with a team and must manage various patient procedures and responsibilities effectively." That's substantive. So we can include About the role (or maybe "About the role" heading). The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we will use those headings if content exists.
- Responsibilities: list bullet points.
- Requirements: we have Required Experience / Certifications / Licensure. That's requirements. So we can include Requirements section.
- Qualifications: maybe overlapping with Requirements; but we could treat Requirements as qualifications. However we should not duplicate. The instruction says prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they are separate headings list. We have content for Requirements (experience, license, certifications). We don't have separate Qualifications beyond that. Could we put them under Requirements and skip Qualifications? Probably yes, as we should not create empty sections. So we will not include Qualifications if no distinct content.
- Skills: not explicitly listed; maybe implied but not specific. So skip.
- Benefits: we have content.
- Schedule: we have content.
- Pay: not specific, skip.
- About the role: we have content.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
We need to output HTML fragment only, no /. Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we will use those headings if content exists.
- Responsibilities: list bullet points.
- Requirements: we have Required Experience / Certifications / Licensure. That's requirements. So we can include Requirements section.
- Qualifications: maybe overlapping with Requirements; but we could treat Requirements as qualifications. However we should not duplicate. The instruction says prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they are separate headings list. We have content for Requirements (experience, license, certifications). We don't have separate Qualifications beyond that. Could we put them under Requirements and skip Qualifications? Probably yes, as we should not create empty sections. So we will not include Qualifications if no distinct content.
- Skills: not explicitly listed; maybe implied but not specific. So skip.
- Benefits: we have content.
- Schedule: we have content.
- Pay: not specific, skip.
- About the role: we have content.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
We need to output HTML fragment only, no /. Use for each heading, then content: either
for prose,
- for lists.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract details precisely.
About the role prose: combine sentences:
"The Endoscopy RN will be responsible for providing care and support during endoscopic procedures. The role requires the nurse to stay within a 30-minute radius of the facility to be available for call duties and to participate in weekend on-call rotations. The Endoscopy RN will work closely with a team and must manage various patient procedures and responsibilities effectively."
We could also include location? The location is Orangeburg, South Carolina. Could be part of About the role? Might be better to include location in About the role? The instruction: do not repeat job title as heading; location is not a heading. Could include in About the role paragraph. But we need to preserve all substantive information. So we should include location somewhere. Perhaps we can add a short paragraph after About the role? But we have no heading for location. Could incorporate into About the role: "Located in Orangeburg, South Carolina, the Endoscopy RN will be responsible..." That adds location. That's preserving info.
Also start date and duration: Start Date: 10/20/2026; Duration: 13 weeks; 40 hours per week; Shift: 8 hours, days. That's schedule info but we have schedule section with specifics. However start date and duration could be included in About the role or maybe a separate section? There's no heading for start date/duration. Could include in About the role as well. But we need to preserve all substantive info. Let's include them in About the role paragraph: "Start date: 10/20/2026; 13-week contract; 40 hours per week; 8-hour day shifts."
But schedule section already details shift times and on-call. Might be redundant but okay.
Better to keep About the role focusing on role description, and maybe add a separate paragraph for logistics? There's no heading for logistics. Could incorporate into About the role.
Let's craft About the role paragraph:
"Located in Orangeburg, South Carolina, this 13-week travel RN Endoscopy position starts on 10/20/2026, requiring 40 hours per week of 8‑hour day shifts. The Endoscopy RN will be responsible for providing care and support during endoscopic procedures, must stay within a 30‑minute radius of the facility for call duties and weekend on‑call rotations, and will work closely with a team to manage various patient procedures effectively."
That captures location, start date, duration, hours, shift, responsibilities essence.
Now Responsibilities list:
- Assist in endoscopic procedures such as bronchoscopies, ERCPs, and PEG tube placements.
- Administer conscious sedation and monitor patient recovery.
- Ensure patient safety and comfort during procedures.
- Handle specimen management and postoperative care.
We need to preserve exactly as given.
Requirements list:
- Minimum of 2 years of Endoscopy experience.
- South Carolina RN license or Compact license required prior to start.
- ACLS and BLS certifications required.
We could also include that it's RN discipline, but that's already known.
Benefits list: from "Why ARMStaffing?" section:
- 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
Also accolades but those are not benefits; we could optionally include them under Benefits? They are not benefits per se; but they are reasons to choose ARMStaffing. However the instruction: include a section ONLY when the posting has real, specific content for it. The accolades are specific content but not under a standard heading like Benefits. Could we create a separate section like "About ARMStaffing"? Not in allowed headings list. So we should not create extra headings. We could incorporate accolades into Benefits? Might be stretching. Better to omit accolades as they are not benefits, but we could include them in a paragraph under Benefits? Might be considered filler. Safer to omit them, as they are not explicitly benefits. However we might lose some substantive info. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to preserve accolades. Where to put them? There's no heading for "About the company" but we could put them under Benefits? Not accurate. Could we create a section "About ARMStaffing"? Not in allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should only use those headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; we shouldn't invent other headings. So we need to fit accolades into one of those sections. Perhaps we can put them under Benefits as extra points, though they are not benefits but could be considered "Why ARMStaffing?" which is akin to benefits/perks. The accolades are about the company's reputation; could be considered part of Benefits? Might be okay. Alternatively we could put them under About the role? Not appropriate. Thus we will include accolades as list items under Benefits. Let's list Benefits items: - 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 - Recognitions: 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; The Joint Commission’s Gold Seal of Approval for healthcare staffing – 15 years strong and counting We need to preserve the exact phrasing? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the text as close as possible. We can combine into list items; each item can be a sentence. Now Schedule section: specifics: - Schedule: 5x8-hour shifts from 6:00 AM to 2:30 PM, with every third weekend on call from 3 PM Friday to 6 AM Monday. Also note: 40 hours per week, 8 hour shifts, days. Already captured. We'll output as
- 5x8-hour shifts from 6:00 AM to