Travel CT Tech - $2,244 per week

We need to output HTML fragment with sections: About the role? Actually we have job description: "Healthcare Support is seeking a travel CT Technologist for a travel job in Poplar Bluff, Missouri." Then "Job Description & Requirements" with details: Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift: 12 hours, Employment Type: Travel, Job ID #522846. 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: ct tech. Then "About Healthcare Support" paragraph. Then Benefits list. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content for it. We have no explicit responsibilities list; we have job description details but not bullet list of duties. We have requirements: specialty, discipline, start date, duration, hours, shift, employment type. Could treat as Requirements. Could also have Qualifications? Not given. Skills? Not given. Pay: we have pay package 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 it's actual content: pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount TBD. Since "tax-free stipend amount to be determined" is vague but still we have some pay info. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is TBD-like. Might be considered placeholder. However we have "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's specific: based on 12 hour shifts and 36 hours per week. That's substantive. So we can include Pay section with that sentence. Schedule: we have shift: 12 hours, 36 hours per week. That's schedule info. So we can include Schedule section. Benefits: we have list: License and certification reimbursement, Medical benefits, Dental benefits, Mileage reimbursement, Employee assistance programs, Referral bonus, 401k retirement plan, Holiday Pay, Weekly pay. That's substantive. About the role: we could have a paragraph describing the role: "Healthcare Support is seeking a travel CT Technologist for a travel job in Poplar Bluff, Missouri." plus maybe description from About Healthcare Support? Actually About Healthcare Support is about the company, not role. Could treat as About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to include based on content. We have: - About the role: could be the initial sentence about seeking a travel CT Technologist in Poplar Bluff, Missouri. Could also include specialty, discipline? But those are more requirements. - Responsibilities: not provided. - Requirements: we have specialty, discipline, start date, duration, hours, shift, employment type, job ID maybe. - Qualifications: not given separate. - Skills: not given. - Benefits: list. - Pay: pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Schedule: shift: 12 hours, 36 hours per week. We should not repeat job title as heading. Do not put Job ID as heading; fold minor metadata into short

or drop it. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include start date, duration, etc. We need to avoid filler placeholder text. The Pay section includes "subject to confirmation" and "tax-free stipend amount to be determined". The latter is TBD-like; maybe we should omit that part? But we must preserve all substantive information; we cannot invent or summarize away detail. If we omit the stipend part, we lose info. However the rule says: 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. It says do not create a section if the posting only has filler/placeholder text. But if we have some substantive plus some placeholder, we can still include the section but we should not include filler/placeholder text? The rule: "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That suggests we should not have a heading where the content under it is just filler/placeholder. If we have mixed content, we could include the substantive parts and omit the placeholder? But that would be summarizing away detail (removing the stipend info). However the stipend info is placeholder; maybe we can drop it as it's not substantive. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing away detail would be removing the stipend info, which is detail but it's placeholder. Is placeholder considered detail? It's not substantive; it's basically unknown. So we could drop it. The phrase "tax-free stipend amount to be determined" is not substantive; it's unknown. So we could omit it. The phrase "subject to confirmation" is also somewhat qualifier but still substantive: pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation). That's substantive. Thus Pay section content: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)." That's good. Schedule: "Shift: 12 hours, 36 hours per week." That's substantive. Now Benefits: list items. Now About the role: we can include a paragraph: "Healthcare Support is seeking a travel CT Technologist for a travel job in Poplar Bluff, Missouri." Requirements: we need to list specialty, discipline, start date, duration, hours per week, shift, employment type, maybe job ID as minor metadata in a short p. We should not repeat job title as heading. So no

for CT Technologist. We need to output only HTML fragment, no /, no markdown. Let's structure:

About the role

Healthcare Support is seeking a travel CT Technologist for a travel job in Poplar Bluff, Missouri.

Requirements

• Specialty: CT Technologist
• Discipline: Allied Health Professional
• Start Date: October 19, 2026
• Duration: 13 weeks
• Hours per week: 36
• Shift: 12 hours
• Employment Type: Travel

Job ID #522846

maybe as short p. But we said do NOT put Job ID as heading; fold minor metadata into a short

or drop it. So we can include a

after the list. Now Benefits:

Benefits

• License and certification reimbursement
• Medical benefits
• Dental benefits
• Mileage reimbursement
• Employee assistance programs
• Referral bonus
• 401k retirement plan
• Holiday Pay
• Weekly pay

Pay:

Pay

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

Schedule:

Schedule

Shift: 12 hours, 36 hours per week.

We might also include About Healthcare Support as a section? Not in the list of allowed headings; but we could treat as About the role? Actually we already used About the role for the job. The About Healthcare Support paragraph is about the company; maybe we could include as a separate section like "About Healthcare Support" but not in allowed headings list. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? 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 like "About Healthcare Support". Instead we could incorporate that paragraph into About the role or maybe as a separate

without heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose." It doesn't forbid other headings, but suggests to use those for sections. Safer to stick to those. Thus we can include the Healthcare Support description as a

  under About the role maybe after the initial sentence. Or we could add a separate

  without heading, but that might be considered stray prose. Probably okay to include as part of About the role. Thus About the role section could have two paragraphs: first about seeking CT Technologist, second about Healthcare Support's services. Let's craft:

  About the role

  Healthcare Support is seeking a travel CT Technologist for a travel job in Poplar Bluff, Missouri.

  Healthcare Support excels at providing a streamlined and red-carpet experience for our travelers. Whether you are a nurse, a therapist, or an allied health professional, our goal is to connect you with top-rated facilities throughout the country and get you on the road to your next adventure. We leverage 20 years of relationships with the industry’s most respectable companies across all 50 states, both through direct client partnerships and via national MSP programs. From health systems and hospitals to specialty clinics and post-acute facilities, you can work where you want to work and go where you want to go. Not only does HealthCare Support reimburse for relocation and travel costs on your first check, but we also offer license and certification reimbursements required for your assignments so that you can focus on building your career. During your assignment, you’ll have access to medical benefits, 24/7 support from our Clinical Advocacy Team, and a travel team with stateside operations. Your travel team will include a designated credentialing expert to help you navigate every step of the on-boarding process, a payroll specialist who you can communicate with directly, and a skilled recruiter who takes the time to understand your needs and works hard to find the right position for you. Don’t get lost in the shuffle of another overblown staffing agency. Choose HealthCare Support to be your trusted partner that you can rely on for all your travel assignments. We can’t wait to hear about the amazing adventures you’ll have! Pst! Ask us about our Direct Hire Opportunities!

  That seems fine. Now we need to ensure we didn't include any boilerplate like cookie/navigation/legal/EEO etc. The text we used doesn't contain those. Now check for any filler placeholder text: In About the role we have no placeholder. In Requirements we have concrete data. In Benefits list we