Travel CVOR Technologist - $1,932 per week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, parse the content:
Job posting:
- Title: "Slate Healthcare is seeking a travel CVOR Technologist for a travel job in Richmond, Virginia." (but we don't repeat title)
- Job Description & Requirements
- Specialty: CVOR Technologist
- Discipline: Allied Health Professional
- Start Date: ASAP
- Duration: 13 weeks
- 36 hours per week
- Shift: 8 hours, days
- Employment Type: Travel
- Description: "Join our team as a Certified Surgical Tech in the CVOR, where you will play a crucial role in assisting surgical teams with cardiac procedures. You will be responsible for maintaining sterile environments, preparing surgical instruments, and ensuring patient safety. This position offers a supportive work environment and the opportunity to work with advanced surgical technologies. Enjoy living in Richmond, VA, with its rich history and vibrant culture."
- Highlights:
- Located in a vibrant city with rich culture
- 2+ years of experience required
- Monday to Friday schedule
- Opportunity to work with advanced surgical technologies
- Requirements:
- ACLS certification required
- Must have NH license/compact at submission
- EMR system experience preferred
- BLS certification required
- 2 years of hospital experience required
- Slate Healthcare Job ID #ebc77fd4-17f1-4f3f-83e9-747d885906aa. Pay package is based on 8 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
- About Slate Healthcare: description of company.
Now, decide sections:
1. About the role (or Description) - includes the description paragraph and maybe highlights? Highlights are bullet points, could be part of description or separate. Since highlights are specific bullet points, maybe include as a list under "Highlights" or "Details". But rule: use h3 for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Highlights" is not in the list, but could be considered part of "About the role". However, the highlights include "2+ years of experience required" which is also in requirements. Might be duplication. Better to include highlights as a list under "About the role" or separate "Highlights" section? The rule says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but prefer those. I think "Highlights" could be a subsection, but maybe just incorporate into description.
But the highlights are bullet points: "Located in a vibrant city with rich culture", "2+ years of experience required", "Monday to Friday schedule", "Opportunity to work with advanced surgical technologies". Some are descriptive, some are requirements. The schedule info is also in the main details (Shift: 8 hours, days, Monday to Friday). The experience requirement is also in requirements. So maybe we can fold highlights into the description or create a "Highlights" section if it adds value. However, the rule: "Prefer a few substantive sections over many thin ones." So maybe just have "About the role" with description and highlights as a list.
2. Requirements - clear list.
3. About Slate Healthcare - company description.
Also, there is metadata: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. These are details about the job. Could be included in "About the role" as a list or paragraph. The rule: "fold minor metadata into a short
or drop it." But these are substantive details about the job (duration, hours, shift). Should include them. Could create a "Job Details" section? But not in the example headings. Could include as a list under "About the role". Or as a separate "Details" section. Since the rule says use h3 for section headings like About the role, Responsibilities, Requirements, etc. "Details" not listed, but we can use "About the role" to encompass.
Also, Pay package info: "Pay package is based on 8 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is pay information but not specific (amount to be determined). Rule: never create Pay section unless posting actually states them. It states pay package basis but not actual pay. It says "tax-free stipend amount to be determined." That's placeholder. So we should NOT create a Pay section. Could mention in a short paragraph under "About the role" or drop. But it's substantive info about pay structure. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package basis, but not actual numbers. Might be considered not specific enough. I'd fold into a short paragraph.
Schedule: Shift: 8 hours, days, Monday to Friday, 36 hours per week. That's schedule info. Could create a Schedule section? The rule says never create Schedule section unless posting actually states them. It does state shift and hours. But the example headings include Schedule. However, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule details. So we could create a Schedule section. But the posting also has "36 hours per week" and "Shift: 8 hours, days" and "Monday to Friday schedule". That's specific. So we can create a Schedule section.
Benefits: Not mentioned. So no Benefits section.
Now, structure:
- About the role (description, highlights, maybe job details)
- Schedule (shift, hours, days)
- Requirements (list)
- About Slate Healthcare (company description)
But also there is "Specialty", "Discipline", "Start Date", "Duration", "Employment Type". Could be in About the role.
Let's craft HTML.
First, About the role: include description paragraph, then maybe a list of highlights? But highlights include duplicate info. I'll include the description paragraph, then a list of key details (specialty, discipline, start date, duration, employment type, hours per week). Then maybe highlights as a separate list? But highlights are partly duplicate. I'll combine.
Better: Under About the role, have a paragraph for the description, then a
for key details (specialty, discipline, start date, duration, employment type, hours per week, shift). Then maybe another for highlights? But highlights are also details. Could just have one list.
But the rule: use - for any list of duties/requirements/benefits. The key details are not duties/requirements/benefits, but metadata. Could be a
with comma separated. But the rule says fold minor metadata into a short
or drop it. However, these are not minor; they are important job parameters. I think a list is fine.
Let's see example: they didn't give example, but we can decide.
I'll create:
About the role
Join our team as a Certified Surgical Tech in the CVOR, where you will play a crucial role in assisting surgical teams with cardiac procedures. You will be responsible for maintaining sterile environments, preparing surgical instruments, and ensuring patient safety. This position offers a supportive work environment and the opportunity to work with advanced surgical technologies. Enjoy living in Richmond, VA, with its rich history and vibrant culture.
- Specialty: CVOR Technologist
- Discipline: Allied Health Professional
- Start date: ASAP
- Duration: 13 weeks
- Employment type: Travel
- Hours per week: 36
- Shift: 8 hours, days (Monday–Friday)
But the shift is also in Schedule section. Could duplicate. Better to have Schedule section separate.
Let's create Schedule section:
Schedule
- Shift: 8 hours, days
- Hours per week: 36
- Schedule: Monday–Friday
But the posting says "36 hours per week" and "Shift: 8 hours, days" and "Monday to Friday schedule". That's good.
Now Requirements section:
Requirements
- ACLS certification required
- Must have NH license/compact at submission
- EMR system experience preferred
- BLS certification required
- 2 years of hospital experience required
Now About Slate Healthcare:
About Slate Healthcare
Slate Healthcare is a premier travel healthcare staffing agency, connecting healthcare professionals with thousands of opportunities at top-tier hospitals and facilities across the country.
We’re committed to supporting nurses and allied health professionals in building stable, fulfilling careers—while embracing the freedom and excitement that comes with travel. Our goal is simple: to offer flexibility, competitive pay, and personalized placements that align with each clinician’s lifestyle and career goals.
At Slate, we empower our professionals to choose when and where they work, while ensuring they receive the highest compensation possible—because we believe that exceptional care starts with empowered caregivers.
Now, the Job ID and pay package info: "Slate Healthcare Job ID #ebc77fd4-17f1-4f3f-83e9-747d885906aa. Pay package is based on 8 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is minor metadata and pay info not specific. Rule: fold minor metadata into a short or drop it. Could include a short paragraph at end of About the role or separate. But we already have schedule and hours. The pay package line is about pay, but not specific. Since we are not creating Pay section, we could mention in a paragraph: "Pay package is based on 8-hour shifts and 36 hours per week (subject to confirmation) with a tax-free stipend amount to be determined." That's substantive. I'll include it in About the role as a paragraph after the list.
But the Job ID is minor metadata, drop it.
Now, check for any other sections: Responsibilities? The description includes responsibilities:
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, parse the content: Job posting: - Title: "Slate Healthcare is seeking a travel CVOR Technologist for a travel job in Richmond, Virginia." (but we don't repeat title) - Job Description & Requirements - Specialty: CVOR Technologist - Discipline: Allied Health Professional - Start Date: ASAP - Duration: 13 weeks - 36 hours per week - Shift: 8 hours, days - Employment Type: Travel - Description: "Join our team as a Certified Surgical Tech in the CVOR, where you will play a crucial role in assisting surgical teams with cardiac procedures. You will be responsible for maintaining sterile environments, preparing surgical instruments, and ensuring patient safety. This position offers a supportive work environment and the opportunity to work with advanced surgical technologies. Enjoy living in Richmond, VA, with its rich history and vibrant culture." - Highlights: - Located in a vibrant city with rich culture - 2+ years of experience required - Monday to Friday schedule - Opportunity to work with advanced surgical technologies - Requirements: - ACLS certification required - Must have NH license/compact at submission - EMR system experience preferred - BLS certification required - 2 years of hospital experience required - Slate Healthcare Job ID #ebc77fd4-17f1-4f3f-83e9-747d885906aa. Pay package is based on 8 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - About Slate Healthcare: description of company. Now, decide sections: 1. About the role (or Description) - includes the description paragraph and maybe highlights? Highlights are bullet points, could be part of description or separate. Since highlights are specific bullet points, maybe include as a list under "Highlights" or "Details". But rule: use h3 for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Highlights" is not in the list, but could be considered part of "About the role". However, the highlights include "2+ years of experience required" which is also in requirements. Might be duplication. Better to include highlights as a list under "About the role" or separate "Highlights" section? The rule says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but prefer those. I think "Highlights" could be a subsection, but maybe just incorporate into description. But the highlights are bullet points: "Located in a vibrant city with rich culture", "2+ years of experience required", "Monday to Friday schedule", "Opportunity to work with advanced surgical technologies". Some are descriptive, some are requirements. The schedule info is also in the main details (Shift: 8 hours, days, Monday to Friday). The experience requirement is also in requirements. So maybe we can fold highlights into the description or create a "Highlights" section if it adds value. However, the rule: "Prefer a few substantive sections over many thin ones." So maybe just have "About the role" with description and highlights as a list. 2. Requirements - clear list. 3. About Slate Healthcare - company description. Also, there is metadata: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. These are details about the job. Could be included in "About the role" as a list or paragraph. The rule: "fold minor metadata into a short
or drop it." But these are substantive details about the job (duration, hours, shift). Should include them. Could create a "Job Details" section? But not in the example headings. Could include as a list under "About the role". Or as a separate "Details" section. Since the rule says use h3 for section headings like About the role, Responsibilities, Requirements, etc. "Details" not listed, but we can use "About the role" to encompass. Also, Pay package info: "Pay package is based on 8 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is pay information but not specific (amount to be determined). Rule: never create Pay section unless posting actually states them. It states pay package basis but not actual pay. It says "tax-free stipend amount to be determined." That's placeholder. So we should NOT create a Pay section. Could mention in a short paragraph under "About the role" or drop. But it's substantive info about pay structure. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package basis, but not actual numbers. Might be considered not specific enough. I'd fold into a short paragraph. Schedule: Shift: 8 hours, days, Monday to Friday, 36 hours per week. That's schedule info. Could create a Schedule section? The rule says never create Schedule section unless posting actually states them. It does state shift and hours. But the example headings include Schedule. However, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule details. So we could create a Schedule section. But the posting also has "36 hours per week" and "Shift: 8 hours, days" and "Monday to Friday schedule". That's specific. So we can create a Schedule section. Benefits: Not mentioned. So no Benefits section. Now, structure: - About the role (description, highlights, maybe job details) - Schedule (shift, hours, days) - Requirements (list) - About Slate Healthcare (company description) But also there is "Specialty", "Discipline", "Start Date", "Duration", "Employment Type". Could be in About the role. Let's craft HTML. First, About the role: include description paragraph, then maybe a list of highlights? But highlights include duplicate info. I'll include the description paragraph, then a list of key details (specialty, discipline, start date, duration, employment type, hours per week). Then maybe highlights as a separate list? But highlights are partly duplicate. I'll combine. Better: Under About the role, have a paragraph for the description, then a
- for key details (specialty, discipline, start date, duration, employment type, hours per week, shift). Then maybe another
- for any list of duties/requirements/benefits. The key details are not duties/requirements/benefits, but metadata. Could be a
with comma separated. But the rule says fold minor metadata into a short
or drop it. However, these are not minor; they are important job parameters. I think a list is fine. Let's see example: they didn't give example, but we can decide. I'll create:
About the role
Join our team as a Certified Surgical Tech in the CVOR, where you will play a crucial role in assisting surgical teams with cardiac procedures. You will be responsible for maintaining sterile environments, preparing surgical instruments, and ensuring patient safety. This position offers a supportive work environment and the opportunity to work with advanced surgical technologies. Enjoy living in Richmond, VA, with its rich history and vibrant culture.
- Specialty: CVOR Technologist
- Discipline: Allied Health Professional
- Start date: ASAP
- Duration: 13 weeks
- Employment type: Travel
- Hours per week: 36
- Shift: 8 hours, days (Monday–Friday)
Schedule
- Shift: 8 hours, days
- Hours per week: 36
- Schedule: Monday–Friday
Requirements
- ACLS certification required
- Must have NH license/compact at submission
- EMR system experience preferred
- BLS certification required
- 2 years of hospital experience required
About Slate Healthcare
Slate Healthcare is a premier travel healthcare staffing agency, connecting healthcare professionals with thousands of opportunities at top-tier hospitals and facilities across the country.
We’re committed to supporting nurses and allied health professionals in building stable, fulfilling careers—while embracing the freedom and excitement that comes with travel. Our goal is simple: to offer flexibility, competitive pay, and personalized placements that align with each clinician’s lifestyle and career goals.
At Slate, we empower our professionals to choose when and where they work, while ensuring they receive the highest compensation possible—because we believe that exceptional care starts with empowered caregivers.
Now, the Job ID and pay package info: "Slate Healthcare Job ID #ebc77fd4-17f1-4f3f-83e9-747d885906aa. Pay package is based on 8 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is minor metadata and pay info not specific. Rule: fold minor metadata into a shortor drop it. Could include a short paragraph at end of About the role or separate. But we already have schedule and hours. The pay package line is about pay, but not specific. Since we are not creating Pay section, we could mention in a paragraph: "Pay package is based on 8-hour shifts and 36 hours per week (subject to confirmation) with a tax-free stipend amount to be determined." That's substantive. I'll include it in About the role as a paragraph after the list. But the Job ID is minor metadata, drop it. Now, check for any other sections: Responsibilities? The description includes responsibilities:
- for highlights? But highlights are also details. Could just have one list.
But the rule: use