Travel CT Technologist - $2,493 per week

We need to output HTML fragment with sections as per rules. Use

for section headings 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, etc. Also remove 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 posting. Content: - Title: ALOIS Healthcare is seeking a travel CT Technologist for a travel job in West Glens Falls, New York. - Job Description & Requirements - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: 10/15/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - A CT scan technologist must be able to accurately interpret a physician's scanning instructions, administer contrast materials, prepare and operate the CT scan equipment, and position the patient to capture the appropriate images. - ALOIS Healthcare Job ID #19168390. - 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 Tech Acute - About ALOIS Healthcare - Why ALOIS Healthcare? ALOIS means “brave warrior” and that’s what you are- Warrior in Scrubs! Just as you advocate for your patients, we will advocate for you. The pay you deserve. The support you need. We’re in your corner for every battle – because you shouldn’t settle for anything less when it comes to your career. We offer: - Industry-leading pay - Generous cost of living and housing stipends - Opportunities for referral, sign-on, and extension bonuses - Weekly health insurance or health insurance Marketplace weekly bonus - Continuing education credits - We’re proud to be recognized globally as a certified minority-owned staffing supplier. - At ALOIS Healthcare: - Everyone Matters - We are Performance Driven - We are Open, Honest and Direct - We are Transparent - We are Inclusive - We Do the Right Thing - We care about you - and your success is our success. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit application instructions but we can ignore. We need to include sections only if there is real specific content. Potential sections: - About the role: Could include description of role: "A CT scan technologist must be able to accurately interpret a physician's scanning instructions, administer contrast materials, prepare and operate the CT scan equipment, and position the patient to capture the appropriate images." Also maybe include specialty, discipline, start date, duration, hours, shift, employment type, location? The location is West Glens Falls, New York. That could be part of About the role. - Responsibilities: Could be the same as above? Might be considered responsibilities. But we need to avoid duplication. The posting includes a description of what the technologist must be able to do. That could be responsibilities. We could put that under Responsibilities. - Requirements: Could include specialty, discipline, maybe certification? Not given. Not much. - Qualifications: Not given. - Skills: Not given. - Benefits: The "We offer:" list includes industry-leading pay, generous cost of living and housing stipends, opportunities for referral, sign-on, and extension bonuses, weekly health insurance or health insurance Marketplace weekly bonus, continuing education credits. Also mention certified minority-owned staffing supplier? That's more about company. Benefits section could include those. - Pay: The posting 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's vague; we should not create a Pay section if it's not specific (like "tax-free stipend amount to be determined" is not specific). The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week, but stipend amount TBD. Is that enough? It 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's not a specific number, but it's still stating pay package basis. 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. Here we have "tax-free stipend amount to be determined" which is TBD. That's placeholder. So we should not create a Pay section because it's not specific. Similarly schedule: we have shift: 12 hours, days; 36 hours per week; duration 13 weeks. That's specific. So we could create a Schedule section with those details. The rule: never create Schedule section unless posting actually states them. It does state shift, hours per week, duration. So we can include Schedule. - Benefits: we have specific benefits list. So we can include Benefits. - About the role: we can include location, specialty, discipline, start date, duration, employment type, maybe a brief description. - Responsibilities: we have the description of what the technologist must be able to do. - Requirements: maybe we could include specialty and discipline as requirements? But those are already in About the role. Might be duplication. Better to not create Requirements if not specific. - Qualifications: none. - Skills: none. Thus we will output sections: About the role, Responsibilities, Benefits, Schedule. Check if any other sections like "About ALOIS Healthcare" could be considered "About the company" but not required. We could incorporate that into Benefits or maybe a separate section "About ALOIS Healthcare" but not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. The company description could be placed under Benefits? Not exactly. Could be omitted? But we must preserve ALL substantive information. The company description includes mission statement, values, etc. That's substantive. Where to put? Could be under About the role? Not ideal. Could be under Benefits? Not exactly. Could be under a generic

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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Thus we can have multiple

  sections with those headings. For content that doesn't fit those headings, we can just put in

  without a heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests to use those for sections. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections. It doesn't say we cannot have other headings, but to follow the pattern. Probably we should only use those headings. For company description, we could put it under About the role? Or we could create a

  without heading after the sections. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must have a heading for every block, but we should use

  for section headings. So we can have

  blocks without heading for miscellaneous info. Thus we can output:

  About the role

  ALOIS Healthcare is seeking a travel CT Technologist for a travel job in West Glens Falls, New York. Specialty: CT Technologist. Discipline: Allied Health Professional. Start Date: 10/15/2026. Duration: 13 weeks. 36 hours per week. Shift: 12 hours, days. Employment Type: Travel.

  Responsibilities

  A CT scan technologist must be able to accurately interpret a physician's scanning instructions, administer contrast materials, prepare and operate the CT scan equipment, and position the patient to capture the appropriate images.

  Benefits

  • Industry-leading pay
  • Generous cost of living and housing stipends
  • Opportunities for referral, sign-on, and extension bonuses
  • Weekly health insurance or health insurance Marketplace weekly bonus
  • Continuing education credits

  Schedule

  Shift: 12 hours, days. Hours per week: 36. Duration: 13 weeks.

  We might also include the Pay package note? Since it's not specific, we should not create Pay section. Could we include it as a

  under About the role or Schedule? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state 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 somewhat stated but includes TBD. 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. Since the stipend amount is TBD, that's placeholder. So we should avoid Pay section. Could we include the pay basis as a note in Schedule? Possibly but schedule already covers shift and hours. Pay note about stipend TBD is not schedule. Could we include it as a

  without heading? The instruction says preserve ALL substantive information. The pay package statement is substantive, albeit includes TBD. We could include it as a

  under About the role or maybe a separate

  without heading. But we must not create a Pay heading. So we can add a

  after Schedule: "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 preserves info. Also we have posted job title: CT Tech Acute and Job ID. Those are minor metadata; we can fold into a short

  or drop. 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

  with that info, maybe at end. Also we have "About ALOIS Healthcare" content: the mission, values, etc. That's substantive. Where to put? Could be under About the role? Not exactly. Could be a

  without heading after Benefits or Schedule. We'll include a

  with that content. We must remove boilerplate: cookie