Local Contract CVOR Technologist - $47-51 per hour

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. We need to parse the posting. Job description: "Host Healthcare is seeking a local contract CVOR Technologist for a local contract job in Colorado Springs, Colorado." Then "Job Description & RequirementsSpecialty: CVOR TechnologistDiscipline: Allied Health ProfessionalStart Date: 10/20/2026Duration: 14 weeks40 hours per weekShift: 10 hours, daysEmployment Type: Local ContractHost Healthcare Job ID #La1fVX0000042ugXYAQ. 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. Posted job title: Surgical Technician - CVOR" Then "About Host Healthcare" paragraph. Then "Benefits" list: Referral bonus, School loan reimbursement, Vision benefits, Wellness and fitness programs, Company provided housing options, License and certification reimbursement, Life insurance, Medical benefits, Mileage reimbursement, Pet insurance, Discount program, Employee assistance programs, Guaranteed Hours, Health savings account, Holiday Pay, 401k retirement plan, Continuing Education, Dental benefits. We need to extract substantive info. We need sections: About the role (maybe description of role). Responsibilities (maybe none). Requirements (maybe specialty, discipline). Qualifications (maybe none). Skills (maybe none). Benefits (list). Pay (pay package based on 10 hour shifts and 40 hours per week, tax-free stipend amount to be determined). Schedule (40 hours per week, shift: 10 hours, days). Also start date, duration. We must not include placeholder like "tax-free stipend amount to be determined" - that is vague but still specific? It says amount to be determined, which is not a specific number. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is similar to TBD. So we should not include Pay section if it only contains that vague statement? However we have "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation)". That's somewhat specific: based on 10 hour shifts and 40 hours per week. But still not a numeric pay. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "tax-free stipend amount to be determined" is TBD-like. So maybe we should omit Pay section entirely because no concrete pay amount. However we could include Pay section with the info we have: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation)". That is not a placeholder but a description of basis. Might be acceptable. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay package is based on... So we can include Pay section with that sentence. Schedule: we have "40 hours per week", "Shift: 10 hours, days". That's specific. So include Schedule section. Benefits: we have list. Include Benefits section. About the role: we can use the introductory sentence: "Host Healthcare is seeking a local contract CVOR Technologist for a local contract job in Colorado Springs, Colorado." plus maybe the About Host Healthcare paragraph? That's about the company, not role. The About the role section should describe the role. We have specialty, discipline, start date, duration, employment type. Could be placed in About the role or Requirements. Let's think. We need to avoid repeating job title as heading. Already not. We need to use

for section headings. We need to use

• for any list of duties/requirements/benefits. We need to use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none. We need to output only HTML fragment. Let's decide sections: - About the role: include description: "Host Healthcare is seeking a local contract CVOR Technologist for a local contract job in Colorado Springs, Colorado." plus maybe the specialty and discipline? Could be part of About the role. - Responsibilities: not provided; we should not create empty. - Requirements: could include "Specialty: CVOR Technologist", "Discipline: Allied Health Professional", "Start Date: 10/20/2026", "Duration: 14 weeks", "Employment Type: Local Contract". Also maybe "Posted job title: Surgical Technician - CVOR". But that's similar to role. - Qualifications: not provided. - Skills: not provided. - Benefits: list as above. - 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." Might be considered placeholder due to stipend amount TBD. But we could still include the first part: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation)". The stipend amount TBD is filler; maybe we should omit that part? But we cannot invent or summarize away detail; we must preserve ALL substantive information. The stipend amount to be determined is substantive? It's saying amount TBD, which is not a specific number but it's info. However instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is similar to TBD. So we should not include Pay section if it only contains that placeholder? But we have also the basis. Could we split? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay package is based on... So we can include Pay section with that sentence, but we must avoid filler. The sentence includes filler "tax-free stipend amount to be determined". That is filler. Should we remove that part? We cannot invent or summarize away detail, but we can omit filler? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove the stipend amount TBD, we are summarizing away detail (the stipend amount TBD). However that detail is filler/placeholder. The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we must include filler if it's placeholder. It says we should not create sections that end up with filler/placeholder text. So better to omit Pay section entirely because the only substantive info is the basis, but that is coupled with filler. Could we include just the basis and drop the stipend part? That would be summarizing away detail (the stipend amount TBD). But maybe that's acceptable because it's placeholder. The instruction says "do NOT invent or summarize away detail." Summarizing away detail could be considered removing the stipend amount TBD, which is detail but placeholder. I'd lean to include Pay section with the basis only, but that is summarizing away the stipend part. However the stipend part is not substantive; it's placeholder. So maybe it's okay to omit it. The instruction says "never emit a heading followed by filler/placeholder text". If we include Pay section with only the basis, we are not emitting filler/placeholder text. So that seems compliant. Thus Pay section:

  Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation).

  Schedule: we have "40 hours per week" and "Shift: 10 hours, days". Also maybe "Local Contract". We'll put:

  40 hours per week, 10‑hour day shifts.

  Benefits: list each item as
• . Now About the role: we can combine the initial sentence and maybe the About Host Healthcare paragraph? That's about company, not role. But we could include a short paragraph about the role: "Host Healthcare is seeking a local contract CVOR Technologist for a local contract job in Colorado Springs, Colorado." That's it. Requirements: list specialty, discipline, start date, duration, employment type. Also maybe "Posted job title: Surgical Technician - CVOR". But that's essentially same as role. We'll include. We must not repeat job title as heading; we are not. Now ensure we don't include any boilerplate like "About Host Healthcare" paragraph? That's not boilerplate; it's descriptive of company. Should we include? It's substantive info about the company, maybe relevant. The instruction says preserve ALL substantive information. So we could include a section "About Host Healthcare" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Host Healthcare". So we cannot add a custom heading. We could fold that info into About the role or Requirements? It's not about role. But we could include it as a paragraph under About the role? Might be stretching. However 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)." Likely they expect us to use those headings only. So we should not add other headings. So we need to fit the Host Healthcare description somewhere, maybe under About the role as a paragraph describing the employer. That's acceptable. Thus About the role section will have two paragraphs: first about seeking CVOR Technologist, second about Host Healthcare description. Now we must not include duplicated lines. Ensure we don't repeat. Now produce HTML. Let's craft:

  About the role

  Host Healthcare is seeking a local contract CVOR Technologist for a local contract job in Colorado Springs, Colorado.

  At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on‑staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare.

  But note that the second paragraph includes benefits description that overlaps with Benefits section. Might be duplication. The Benefits section already lists specific benefits. The paragraph mentions some benefits (Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on‑staff clinicians). That's substantive and not duplicated in the list? The list includes many but not those specific. However to avoid duplication, we could keep the paragraph as it's about the company, not just benefits. It's okay. Now Requirements section:

  Requirements

  • Specialty: CVOR Technologist