Travel CT Technologist - $2,914 per week
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove Job ID / requisition numbers as headings; fold minor metadata into short
or drop it. We need to parse the job posting. Key details: - Voca Healthcare seeking travel CT Technologist for travel job in Neillsville, Wisconsin. - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: 11/16/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Benefits available on 1st of the month after start: - Holiday pay - Weekly pay - Retention bonus - 401k retirement plan - Medical benefits - Dental benefits - Vision benefits - Referral bonus - Qualifications: - Minimum of 2 years of recent experience as a CT Technologist preferred, but we are open to exceptional candidates with a strong passion. - Valid certification and/or licensure in the state of practice, if applicable. - Demonstrated ability to maintain a high level of professionalism and composure, especially during stressful and fast-paced moments in the healthcare setting. - Valid Driver’s License and the ability to travel between assignment locations. - Ability to pass a background check and drug screen to meet healthcare industry standards. - Why Choose Voca? (list of benefits): - Comprehensive Benefits Package: Health, Dental, Vision Insurance. - Life and Disability Insurance. - 401(k) options with employer matching. - Certification and Licensure Reimbursement. - Generous Referral Bonus Program. - Weekly Direct Deposit. - At Voca, You Are Our Priority: - Travel-First Culture: flexible supportive work environment. - Personalized Support: dedicated recruiter. - Strong Relationships: long-term relationships. - We care about your career, needs, future. - Additional text about Voca Healthcare: As a Voca Traveler, you will gain new clinical skills, visit amazing places and meet awesome healthcare professionals... etc. - Benefits section repeated: Holiday Pay, 401k retirement plan, Medical benefits, Dental benefits, Vision benefits, Guaranteed Hours. - Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: Allied Health Professional:CT Tech,07:00:00-19:00:00 (maybe shift times) - About Voca Healthcare paragraph. We need to produce sections: maybe About the role (description), Responsibilities (maybe not explicit), Requirements (maybe qualifications), Qualifications (maybe same as requirements), Skills (maybe not explicit), Benefits, Pay, Schedule. We must not repeat job title as heading. The page already shows it, so we don't output a heading for job title. We need to include sections only when posting has real specific content. Let's identify content for each possible section: - About the role: Could be description of role: "As a CT Technologist with Voca, you’ll have the opportunity to work in dynamic healthcare settings, gaining valuable experience while receiving competitive compensation and support every step of the way." Also earlier: "Voca Healthcare is seeking a travel CT Technologist for a travel job in Neillsville, Wisconsin." Also description of duties? Not explicit duties but we can infer responsibilities: performing CT scans, ensuring patient safety, etc. Not given. So maybe we should not create Responsibilities if not explicit. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine role description and qualifications into sections like "About the role" and "Qualifications". Responsibilities may be omitted if not explicit. - Requirements: Could be the qualifications list (experience, certification, professionalism, driver's license, background check). That's specific. - Qualifications: Might duplicate requirements; maybe we can combine. But we need to decide: maybe "Requirements" for mandatory items, "Qualifications" for preferred/experience. However the posting lumps them together. We could have a single "Requirements" section covering both mandatory and preferred. Or we could have "Qualifications" for the list and "Requirements" for something else (like shift, hours). But we have schedule info: 36 hours per week, shift 12 hours days, start date, duration. That could go under "Schedule" and maybe "Pay". Pay: we have mention of weekly pay, retention bonus, tax-free stipend amount to be determined, but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (holiday pay, weekly pay, retention bonus, 401k, medical, dental, vision, referral bonus). Also mentions "Benefits available on 1st of the month after start". So we can create Benefits section with those items. Pay: The posting mentions "Weekly pay" as a benefit, but not specific amount. Also "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague but still mentions pay package. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Weekly pay" as a benefit, and mentions pay package based on hours. So we could include Pay section with that info (though no specific numbers). However also instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The Pay section would have placeholder like "tax-free stipend amount to be determined" which is TBD. That's filler. So we should avoid Pay section if it only contains unspecified amounts. The posting does not give actual pay rate or stipend amount. So better to omit Pay section. Schedule: We have start date, duration, 36 hours per week, shift 12 hours days. That's specific. So we can create Schedule section with those details. Benefits: We have specific list: Holiday pay, Weekly pay, Retention bonus, 401k retirement plan, Medical benefits, Dental benefits, Vision benefits, Referral bonus. Also later: Life and Disability Insurance, Certification and Licensure Reimbursement, Weekly Direct Deposit, Travel-First Culture, Personalized Support, Strong Relationships, etc. Some are more like perks. But we can list the benefits explicitly stated. We also have "Guaranteed Hours" mentioned in Benefits repeated section. So include that. Thus sections: About the role (description), Requirements (qualifications list), Benefits (list), Schedule (start date, duration, hours, shift). Possibly also "About Voca Healthcare" could be part of About the role or separate section like "About the company". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role or maybe under a generic section not listed; but we should stick to allowed headings. Could put company description in About the role as well. Responsibilities: Not explicit; we could omit. Qualifications: Could be same as Requirements; but we could split: Requirements = mandatory items (certification, license, background check, driver's license). Qualifications = preferred experience, professionalism, passion. However the posting lumps them. To avoid thin sections, we could combine into one section called "Requirements" and include all. Or we could have "Qualifications" for the experience and professionalism, and "Requirements" for mandatory items. But that may create two thin sections. Better to have one "Requirements" section with all bullet points. Skills: Not explicit; maybe we could infer skills like CT imaging, patient care, etc. Not given; better to omit. Thus final HTML:
About the role
... description ...
Requirements
- ... ...
Benefits
- ... ...
Schedule
- ... ...