Travel CT Technologist - $2,725 per week

We need to output HTML fragment with sections: About the role? The posting includes description: Host Healthcare is seeking a travel CT Technologist for a travel job in Reston, Virginia. Then Job Description & Requirements: Specialty: CT Technologist, Discipline: Allied Health Professional, Start Date: 10/05/2026, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, days, Employment Type: Travel, Host Healthcare Job ID #... 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. Posted job title: CT Technologist. Then About Host Healthcare paragraph. Then Benefits list. We must not repeat job title as heading. No Job ID heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real, specific content. Let's see what we have: - About the role: we have description of job: travel CT Technologist in Reston, Virginia. Could be considered About the role. Provide paragraph. - Responsibilities: Not explicitly listed. No duties listed. So we should not create Responsibilities section. - Requirements: We have Specialty: CT Technologist, Discipline: Allied Health Professional. Could be considered requirements. Also maybe license/certification? Not explicit. We'll include Requirements with those items. - Qualifications: Not explicit separate from requirements. Could combine? But we should not create empty sections. If we have content for Qualifications, we could list maybe none. Better to skip Qualifications. - Skills: Not listed. - Benefits: We have a list of benefits: 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. Also Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on-staff clinicians. Many of these are in the About Host Healthcare paragraph. We need to preserve all substantive information. So we should include benefits section with list items. - Pay: The posting mentions "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 not a specific number, but it's mention of pay package. It says "subject to confirmation" and "tax-free stipend amount to be determined." This is vague but still some content. According to rule: do NOT emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined" which is TBD-like. Also "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)" is somewhat vague but still mentions basis. Is that considered filler? It's not a specific amount, but it's describing how pay is calculated. Might be considered substantive? The rule says avoid headings with filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Tax-free stipend amount to be determined" is similar to TBD. So maybe we should not create Pay section because it's not specific. However we could include Pay section with that sentence? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay package is based on... So it does state something about pay. But it's not a specific amount. The rule about filler/placeholder text is about headings followed by filler/placeholder text. If we put a Pay heading and then a paragraph that says "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 is not filler like "TBD"? It includes "to be determined". Might be considered placeholder. Safer to omit Pay section. - Schedule: We have Shift: 12 hours, days, 36 hours per week. That's schedule info. So we can create Schedule section with that detail. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. For Benefits we have a list; we should output
  • items. For Requirements we have Specialty and Discipline; could be list. For About the role we have prose: maybe a paragraph. For Schedule we have details: Shift: 12 hours, days; 36 hours per week; Start Date: 10/05/2026; Duration: 13 weeks; Employment Type: Travel; Location: Reston, Virginia. Also maybe we could include those as list? The rule: Use
    • for any list of duties/requirements/benefits. Schedule is not a list but could be presented as

      . We'll use

      . We must not include Job ID or requisition numbers as headings; we can fold minor metadata into a short

      or drop it. The Job ID is minor metadata; we can drop it. We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present. We must preserve ALL substantive information; do not invent or summarize away detail. Let's extract all substantive info: - Host Healthcare is seeking a travel CT Technologist for a travel job in Reston, Virginia. - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: 10/05/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - 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. - Posted job title: CT Technologist (but we shouldn't repeat job title as heading) - About Host Healthcare paragraph: "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." - 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. Also note that some benefits already mentioned in paragraph: Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on-staff clinicians. Should we include those in benefits list? Yes, to preserve all substantive information. We should combine them, avoid duplication? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The paragraph mentions Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on-staff clinicians. The benefits list includes Medical benefits (maybe includes Day 1 medical?), 401k retirement plan (similar to 401K matching), Company provided housing options (dedicated housing support), etc. There's overlap but we should not remove duplicates if they are substantively different phrasing? The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. If the same benefit appears both in paragraph and list, we should deduplicate. We'll combine into a single benefits list, ensuring each unique benefit appears once. Let's list unique benefits: From paragraph: - Day 1 medical that continues up to 30 days between assignments - 401K matching - Travel reimbursements - Dedicated housing support - 24/7 support - Access to on-staff clinicians From benefits list: - Referral bonus - School loan reimbursement - Vision benefits - Wellness and fitness programs - Company provided housing options (similar to dedicated housing support; we can keep one) - License and certification reimbursement - Life insurance - Medical benefits (maybe overlapping with Day 1 medical; but we can keep generic Medical benefits) - Mileage reimbursement - Pet insurance - Discount program - Employee assistance programs - Guaranteed Hours - Health savings account - Holiday Pay - 401k retirement plan (similar to 401K matching) - Continuing Education - Dental benefits We need to deduplicate: 401K matching vs 401k retirement plan: they are similar but not identical; one is matching, the other is plan. Could keep both? Might be considered duplicate? The rule says remove duplicated lines. If they are essentially same concept, we could keep one. But to be safe, we could keep both as they are slightly different wording. However "401K matching" is a specific benefit; "401k retirement plan" is generic. Might be considered duplicate. I'd keep one: "401K matching". Similarly "Dedicated housing support" vs "Company provided housing options": similar; keep one: "Company provided housing options". "Medical benefits" vs "Day 1 medical that continues up to 30 days between assignments": the latter is more specific; we could keep the specific description and drop generic Medical benefits. Or keep both? I'd keep the specific description and drop generic Medical benefits. Thus final benefits list unique items: - Day 1 medical that continues up to 30 days between assignments - 401K matching - Travel reimbursements - Company provided housing options - 24/7 support - Access to on-staff clinicians - Referral bonus - School loan reimbursement - Vision benefits - Wellness and fitness programs - License and certification reimbursement - Life insurance - Mileage reimbursement - Pet insurance - Discount program - Employee assistance programs - Guaranteed Hours - Health savings account - Holiday Pay - Continuing Education - Dental benefits Also maybe "Guaranteed Hours" already covered by 36 hours per week? But it's a benefit. Now schedule section: include Start Date, Duration, 36 hours per week, Shift: 12 hours, days, Employment Type: Travel, Location: Reston, Virginia. We could format as

      with sentences. Now About the role: we have the first sentence: "Host Healthcare is seeking a travel CT Technologist for a travel job in Reston, Virginia." Could also include that it's a travel job. We'll put that as

      . Requirements: Specialty: CT Technologist; Discipline: Allied Health Professional