Travel CVOR Technologist - $2,459 per week
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove "About ARMStaffing" maybe? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have job description: "We are seeking an experienced Surgical Tech with a focus on Cardiovascular Operating Room (CVOR) procedures. The ideal candidate will possess the requisite skills and certifications to perform in a high-pressure environment, including the ability to care for COVID patients."
That's about the role. Could be "About the role" paragraph.
Responsibilities: bullet list: Assist with open heart surgeries and other cardiovascular procedures. Ensure a sterile environment and adhere to infection control protocols. Participate in alternating days off, and on-call duties with a 30-minute response requirement. Work weekends every third or fourth week, with holiday assignments as needed.
Requirements: Minimum of 2 years of CVOR experience required. Current certifications: NBSTSA, BLS; EPIC experience preferred. Level I trauma experience is mandatory. Ability to float as needed.
Qualifications? Might be same as requirements? Could separate: maybe "Qualifications" includes certifications and experience. But we have both Requirements and Qualifications sections; we need to decide what goes where. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those that have content. We have content for About the role, Responsibilities, Requirements (experience, certifications). Qualifications maybe same as Requirements? Could combine? But we should not create empty sections. If we have both Requirements and Qualifications, we need distinct content. Could treat Requirements as experience/years, and Qualifications as certifications/licensure. Or we could put certifications under Qualifications. Let's decide:
- About the role: paragraph describing role.
- Responsibilities: bullet list.
- Requirements: Minimum of 2 years of CVOR experience required. Ability to float as needed. (maybe also Level I trauma experience mandatory? That's a qualification.)
- Qualifications: Current certifications: NBSTSA, BLS; EPIC experience preferred. Level I trauma experience is mandatory.
- Skills: maybe not explicitly listed; we could infer skills: ability to care for COVID patients, sterile technique, infection control, etc. But we should not invent. If not explicit, we should not create Skills section. The posting didn't list skills separately. So we omit Skills.
- Benefits: The posting lists 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 mentions SIA rankings etc but those are boastful but still benefits? Might be considered benefits. We'll include Benefits section with bullet list of those benefits.
- Pay: The posting 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 not a specific number, but it's mention of pay package. 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." This is somewhat vague but still mentions pay. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package based on shifts and hours, stipend TBD. That's still stating something about pay, albeit not a number. Should we include? 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 a statement about pay. So we can include Pay section with that sentence.
- Schedule: The posting includes schedule details: Start Date: 10/19/2026; Duration: 13 weeks; 40 hours per week; Shift: 10 hours, days; "Schedule Day shift, 4x10 hours (06:00 - 16:30)." Also "40 hours per week". So we have schedule info. So we can include Schedule section with those details.
We must not include Job ID etc. Also remove duplicated lines, boilerplate like "About ARMStaffing" maybe? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About ARMStaffing" paragraph is not boilerplate but is company description. Should we keep? It's not explicitly listed as a section heading we must use, but could be considered "About the role"? Actually "About the role" is about the job, not the company. The company description might be considered extra but not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep substantive info. The company description is substantive? It describes ARMStaffing. Might be considered not directly about the job but still part of posting. However the instruction to use headings for sections like About the role, Responsibilities, etc. It didn't forbid other headings, but says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but we should follow the pattern. Probably better to include company description under a heading like "About ARMStaffing"? But not in list. Could we incorporate into About the role? Might be redundant. Safer to include as a paragraph without heading? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also have other headings if needed? It says "Use for section headings (e.g. ...)" meaning those are examples; we can use other headings if appropriate? However they say "Prefer a few substantive sections over many thin ones." So we likely should stick to those headings and incorporate company description into maybe About the role or Benefits? But company description is not a benefit. Could add a section "About the company" but not in list; maybe we should omit it to avoid extra thin section. However the instruction says preserve ALL substantive information. If we omit company description, we lose info. But maybe it's considered boilerplate? It's not navigation/legal/EEO etc. It's descriptive but could be considered "About ARMStaffing" which is akin to "About the role"? Not exactly. The posting includes a paragraph about ARMStaffing after the "Why ARMStaffing?" section. That's definitely substantive. We could incorporate that into Benefits? Not really. Could we add a section "About ARMStaffing" using even though not in the examples? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings as needed, but we should follow the pattern. I'd include a heading "About ARMStaffing". That seems reasonable.
But we must not repeat the job title as a heading. That's fine.
We must not put Job ID/requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. ...)" meaning those are examples; we can use other headings if appropriate? However they say "Prefer a few substantive sections over many thin ones." So we likely should stick to those headings and incorporate company description into maybe About the role or Benefits? But company description is not a benefit. Could add a section "About the company" but not in list; maybe we should omit it to avoid extra thin section. However the instruction says preserve ALL substantive information. If we omit company description, we lose info. But maybe it's considered boilerplate? It's not navigation/legal/EEO etc. It's descriptive but could be considered "About ARMStaffing" which is akin to "About the role"? Not exactly. The posting includes a paragraph about ARMStaffing after the "Why ARMStaffing?" section. That's definitely substantive. We could incorporate that into Benefits? Not really. Could we add a section "About ARMStaffing" using even though not in the examples? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings as needed, but we should follow the pattern. I'd include a heading "About ARMStaffing". That seems reasonable.
But we must not repeat the job title as a heading. That's fine.
We must not put Job ID/requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings as needed, but we should follow the pattern. I'd include a heading "About ARMStaffing". That seems reasonable. But we must not repeat the job title as a heading. That's fine. We must not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop Job ID. We must not include application instructions. Now let's extract content. From posting: - Start Date: 10/19/2026 - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, days - Schedule Day shift, 4x10 hours (06:00 - 16:30). Also mention "Posted job title: CVOR Tech:CVOR Tech,07:00:00-17:00:00" maybe ignore. Responsibilities list as above. Requirements: Minimum of 2 years of CVOR experience required. Ability to float as needed. Qualifications: Current certifications: NBSTSA, BLS; EPIC experience preferred. Level I trauma experience is mandatory. Benefits: 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 mention "We're not the only ones who think ARMStaffing should be your first choice. Here’s why: 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 We've earned The Joint Commission’s Gold Seal of Approval for healthcare staffing 15 years strong and counting!" This is more about company reputation; could be part of About ARMStaffing. Also "Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details!" That's maybe a note about pay; could be included in Pay section. 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." plus the contract & local rates note. Schedule section: include start date, duration, hours per week, shift, schedule details. Now craft HTML. We'll have:
About the role
We are seeking an experienced Surgical Tech with a focus on Cardiovascular Operating Room (CVOR) procedures. The ideal candidate will possess the requisite skills and certifications to perform in a high-pressure environment, including the ability to care for COVID patients.
Responsibilities
- Assist with open heart surgeries and other cardiovascular procedures.
- Ensure a sterile environment and adhere to infection control protocols.
- Participate in alternating days off, and on-call duties with a 30‑minute response requirement.
- Work weekends every third or fourth week, with holiday assignments as needed.
Requirements
- Minimum of 2 years of CVOR experience required.
- Ability to float as needed.
Qualifications
- Current certifications: NBSTSA, BLS; EPIC experience preferred.
- Level I trauma experience is mandatory.
Benefits
- 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