Travel CT Technologist - $2,757 per week

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Let's parse the posting: - Host Healthcare is seeking a travel CT Technologist for a travel job in High Point, North Carolina. - Job Description & Requirements - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: 10/05/2026 - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, days - Employment Type: Travel - Host Healthcare Job ID #a1fVX0000042RMnYAM. - 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: CT Technologist - About Host Healthcare: description. - 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 remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So no heading for "CT Technologist". Use headings for sections only if content. We need to include sections: About the role (maybe description of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have some info: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. Those could be considered "About the role" or "Job Details". Could be placed under "About the role". Responsibilities: not given explicitly. Requirements: maybe specialty, discipline? Qualifications: maybe license/certification? Not explicit. Skills: not explicit. Benefits: we have list. Pay: we have mention of pay package based on 10 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's vague but it's actual statement. Should we include Pay section? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. 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." This is somewhat vague but it's still stating something about pay package. It's not a specific amount, but it's stating basis. Is that considered filler? It says "tax-free stipend amount to be determined." That's vague. However, they do mention pay package based on 10 hour shifts and 40 hours per week. That's somewhat specific. I'd say we can include Pay section with that sentence. Schedule: we have Shift: 10 hours, days; 40 hours per week. That's schedule info. So we can include Schedule section. Benefits: we have a list, so include Benefits. About the role: we can include description: Host Healthcare seeking travel CT Technologist in High Point, NC; specialty, discipline, start date, duration, hours, shift, employment type. That seems appropriate. Responsibilities: not given. Could we infer? Probably not; we should not create Responsibilities section if no specific content. So omit. Requirements: maybe specialty and discipline? But those are more about role. Could we put them under About the role? Probably yes. If we want a Requirements section, we need specific requirements like certification, experience. Not given. So omit. Qualifications: not given. Omit. Skills: not given. Omit. Thus we will have sections: About the role, Benefits, Pay, Schedule. We must use

for section headings. Use

• for any list of duties/requirements/benefits. Benefits list should be
  • . For About the role, we can use

    prose. Pay and Schedule: we can use

    prose. We must output only HTML fragment, no /, no markdown. Let's craft:

    About the role

    Host Healthcare is seeking a travel CT Technologist for a travel assignment in High Point, North Carolina. The position is for an Allied Health Professional specializing in CT, with a start date of October 5, 2026, a duration of 13 weeks, 40 hours per week on 10‑hour day shifts, and is a travel employment type.

    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

    Pay

    Pay package is based on 10‑hour shifts and 40.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.

    Schedule

    Shift: 10 hours, days; 40 hours per week.

    Check for any repeated content: we included start date, duration etc in About the role. Good. We removed Job ID line. Good. We removed "Posted job title: CT Technologist". Good. We removed "About Host Healthcare" description? Actually we didn't include that. The posting includes a paragraph about Host Healthcare. Should we include that? It's about the company, not the role. The instruction: "Prefer a few substantive sections over many thin ones." Could we include that under About the role? Possibly but it's more about the company. However, we could incorporate it as part of About the role or maybe a separate section like "About the employer". But we only have allowed headings list; we could still use About the role to include that description. But the instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could also use other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should stick to those headings. So we cannot add a heading like "About Host Healthcare". We could incorporate that description into About the role paragraph. That would be okay. Thus we should add the Host Healthcare description to About the role paragraph. Let's rewrite About the role to include both the job details and the company description. Paragraph: "Host Healthcare is seeking a travel CT Technologist for a travel assignment in High Point, North Carolina. The position is for an Allied Health Professional specializing in CT, with a start date of October 5, 2026, a duration of 13 weeks, 40 hours per week on 10‑hour day shifts, and is a travel employment type. 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 benefits description duplicates some of the benefits list. However, we must preserve ALL substantive information; we cannot omit details. The benefits list includes many items; the paragraph mentions Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on‑staff clinicians. Those are also substantive. Should we include them? They are not in the benefits list but are mentioned. We should preserve them. However, we already have a Benefits section with a list; we could add those items to the list as well. But the list we have from the posting includes many items; we could augment it with those extra benefits. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include those extra benefits somewhere. The Benefits section is appropriate. We can add them to the

    list. Thus Benefits list should include: - 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 - Day 1 medical (continues up to 30 days between assignments) - 401K matching (maybe duplicate of 401k retirement plan? but we can keep both) - Travel reimbursements - Dedicated housing support (maybe duplicate of company provided housing options) - 24/7 support - Access to on‑staff clinicians We need to avoid duplication? The instruction says preserve ALL substantive information; duplication is okay if it's in the source. But we could combine similar items to avoid redundancy but not lose info. However, "Company provided housing options" and "Dedicated housing support" are similar but not identical; we could keep both. "401k retirement plan" and "401K matching" are related but distinct; we can keep both. Thus Benefits list will be long but okay. Now About the role paragraph: we can keep a concise description of the role and maybe mention the company mission briefly, but we already put many details in Benefits. To avoid duplication, we could keep About the role short: just the job specifics. The company description could be moved to Benefits? Not appropriate. But we could keep a brief sentence about Host Healthcare's mission in About the role. However, the instruction says preserve ALL substantive information; we can't omit the company description. So we need to include it somewhere. Since we don't have a section for "About the company", we could incorporate it into About the role paragraph. That would cause duplication with Benefits list (some benefits mentioned). That's okay. Thus About the role paragraph will include both role details and company description. Let's craft:

    About the role

    Host Healthcare is seeking a travel CT Technologist for a travel assignment in High Point, North Carolina. The position is for an Allied Health Professional specializing in CT, with a start date of October 5, 2026, a duration of