Travel CT Tech - $2,882 per week

We need to output HTML fragment with sections for headings where content exists. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include only sections with real specific content. Let's parse the posting: - Job: Healthcare Support seeking a travel CT Technologist for a travel job in Minneapolis, Minnesota. - 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 Employment Type: Travel Healthcare Support Job ID #523801. 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 tech - About Healthcare Support: paragraph describing company. - Benefits list: License and certification reimbursement, Medical benefits, Dental benefits, Mileage reimbursement, Employee assistance programs, Referral bonus, 401k retirement plan, Holiday Pay, Weekly pay. We need to decide sections: About the role (maybe description of role?), Responsibilities (none given), Requirements (maybe specialty, discipline, start date, duration, hours, shift, employment type?), Qualifications (maybe none), Skills (none), Benefits (list), Pay (mention of pay package based on 10 hour shifts and 40 hours per week with tax-free stipend amount to be determined - but that's vague; "tax-free stipend amount to be determined" is not specific; "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation)" - not a specific amount. According to rules: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, we have mention of pay package based on shifts and hours but no actual amount. The rule says: never 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 placeholder. So we should not create a Pay section because it's not specific. Similarly Schedule: we have shift: 10 hours, 40 hours per week, duration 13 weeks. That's specific schedule info. So we could create a Schedule section with those details. Benefits: we have specific list, so Benefits section. About the role: we have a description of the job? The posting includes "Job Description & Requirements" but not detailed duties. It lists specialty, discipline, start date, duration, hours, shift, employment type. That's more like requirements. Could treat that as "Requirements" section. Also we have "About Healthcare Support" which is about the company, not the role. Could be "About the role"? Actually "About the role" would be description of the role responsibilities. Not present. So we might not have About the role. We could use "About Healthcare Support" as a section maybe "About the company"? But allowed headings are limited to those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add custom headings. So we need to map content to those headings. We have content that fits Requirements: specialty, discipline, start date, duration, hours, shift, employment type, job ID maybe minor metadata (should be folded into short p or dropped). So we can put that in Requirements. We have Benefits list. We have Schedule: shift 10 hours, 40 hours per week, duration 13 weeks. That's schedule info. We have Pay: not specific, so omit. We have About the role: not present, omit. Responsibilities: not present, omit. Qualifications: not present, omit. Skills: not present, omit. Thus we will output sections: Requirements, Benefits, Schedule. We need to use

for each heading, then content: for Requirements we can have a

• list of items. For Benefits also list. For Schedule maybe a

  with details or list. We must preserve all substantive information; do not invent or summarize away detail. So include start date, duration, hours per week, shift, employment type, specialty, discipline. Also maybe mention location Minneapolis, Minnesota. That's substantive. Should we include location in Requirements? Yes. Also note "Healthcare Support Job ID #523801." minor metadata, fold into short p or drop. We'll drop or include as short p maybe after heading? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short p after Requirements maybe? But better to drop it as it's minor. We'll drop. Also "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 pay info but not specific; we omit Pay section. However we might still mention it in Schedule? No, it's pay. Since it's not specific, we should not include it anywhere? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. This is substantive? It's vague but still info about pay package basis. However creating a Pay section would be placeholder. Could we include this info in a

  under Requirements or Schedule? It's not schedule. Could be under Requirements as additional note? But it's about pay, not requirements. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package basis, but it's not a specific amount. However it's still stating something about pay. The rule about not creating Pay section unless posting actually states them - it does state something about pay (though vague). But also rule: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The pay description includes "tax-free stipend amount to be determined" which is placeholder. So if we made a Pay section, we would have filler. So better to omit Pay section entirely, even though we lose some info. But the instruction says preserve ALL substantive information. This is a conflict. However the higher priority is to avoid placeholder headings. We could include the pay info as a

  under some other section like Requirements? But it's not a requirement. Could we put it under Benefits? No. Could we put it under Schedule? No. Perhaps we could include it as a brief

  after the Benefits section, without a heading, as "Pay info:" but that would be adding arbitrary text not under a heading. The instruction says output ONLY the HTML fragment, no extra text outside of elements? It didn't forbid stray text, but we should follow semantic HTML. Could we embed it in a

  without heading? That would be okay as long as we don't create a heading. The rule about sections: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having a

  with placeholder text. So we could add a

  with the pay info after Benefits or Schedule, without a heading. That would preserve info without creating a Pay heading. Let's do that. Similarly, we might have "Posted job title: ct tech" minor metadata, drop. Thus final HTML:

  Requirements

  • Specialty: CT Technologist
  • Discipline: Allied Health Professional
  • Location: Minneapolis, Minnesota
  • Start Date: October 5, 2026
  • Duration: 13 weeks
  • Hours: 40 hours per week
  • Shift: 10 hours
  • Employment Type: Travel

  Benefits

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

  Schedule

  Shift: 10 hours; 40 hours per week; Duration: 13 weeks.

  Then a

  for pay info:

  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.

  We need to ensure we don't repeat job title as heading. Good. Check for any boilerplate: we removed About Healthcare Support paragraph? That's substantive about company. Should we include it? It's not under allowed headings. Could we put it under "About the role"? No. Could we drop it? The instruction says preserve ALL substantive information. That paragraph is substantive about the company. But we have no heading for company info. However we could include it as a

  without heading, maybe after Benefits? The instruction didn't forbid stray paragraphs. It said output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we must wrap everything in sections. So we can include a

  for company description. However we must avoid cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Healthcare Support paragraph is not boilerplate; it's substantive. So we should preserve it. Thus we add a

  with that paragraph. Let's copy the paragraph: "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!" We need to ensure we don't include any duplicated lines. It's fine. Now final HTML fragment:

  Requirements

  ...

  Benefits

  ...

  Schedule

  ...

  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.

  Healthcare Support excels at providing a streamlined and red-carpet