Travel CT Technologist - $2,125 per week

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract from posting. Let's parse the posting: - Job title: travel CT Technologist for a travel job in Hamilton, Montana. - Job Description & Requirements Specialty: CT Technologist Discipline: Allied Health Professional Start Date: ASAP Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel Travel Radiology: CT Tech Hamilton, MT Location: Hamilton, MT Start Date: 9/23/2026 Shift Details: 12H Nights 36 hours per week Length: 13 WEEKS Apply for specific facility details. CT Tech Triage Staffing Job ID #LY7DPU4V. Posted job title: Radiology: CT Tech - About Triage Staffing: paragraph describing company. - Benefits: list of benefits. We need to include sections: maybe "About the role" (description), "Responsibilities" (maybe not explicit), "Requirements" (maybe specialty, discipline, etc.), "Qualifications" (maybe not explicit), "Skills" (maybe not explicit), "Benefits" (list), "Pay" (not given), "Schedule" (shift details, hours per week). We should only include sections with real specific content. We have schedule: 12 hours, nights, 36 hours per week. That's schedule info. We have pay: not given explicitly. No mention of pay amount. So we should NOT include Pay section. We have benefits: list given. We have responsibilities: not explicit; maybe job description includes duties? Not given. Could infer but we must not invent. So we should not include Responsibilities if no specific content. Requirements: we have Specialty: CT Technologist, Discipline: Allied Health Professional, maybe also location, start date, duration. Those could be considered requirements. We can put them under Requirements. Qualifications: not explicit separate from requirements; maybe we could combine but better to have Requirements. Skills: not explicit. About the role: we can have a paragraph summarizing the job description: travel CT Technologist in Hamilton, MT, 13 weeks, 36 hrs/week, 12hr night shifts, start ASAP (or 9/23/2026). That's specific. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID as heading. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to include the About Triage Staffing paragraph? That's about the company, not the role. Could be considered "About the company" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not include a section about the company unless we map it to About the role? But About the role is about the job, not the company. The company description may be considered boilerplate? It's not navigation/legal/EEO, but it's promotional. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company description is not explicitly listed to remove, but it's not part of the job description. However we might keep it as part of "About the role"? Might be considered extra but not prohibited. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive info about the staffing agency. Should we include it? Possibly under a section like "About the company" but not allowed heading. Could we incorporate it into "About the role" as a paragraph? That would be mixing. Better to include it as a

  after the headings? The instruction says output ONLY the HTML fragment, no extra wrappers. It didn't forbid extra paragraphs not under headings. But they said 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. So we can have prose paragraphs outside of sections? Probably they expect sections with headings and content. But we can also have a

    for general info not under a heading? Might be okay but safer to put company description under a heading like "About the role" or maybe "About Triage Staffing" but that's not in list. Could we treat it as "About the role" includes both role and company? Might be okay. But we need to preserve all substantive information; we can include the company description as a

    under a heading like "About the role" or maybe under a heading "About the company" but that would be a heading not in the list; risk of violating instruction to use those headings for section headings. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive list. So we could use other headings as long as they are

    . But they also say "Prefer a few substantive sections over many thin ones." So we could add a section "About the company". That seems okay. But to be safe, we can include the company description as a

    after a heading "About Triage Staffing". That is a heading, but not in the examples; still an

    . I think it's acceptable. We must not include duplicated lines. Ensure we don't repeat. Let's extract specifics: - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: ASAP (also later: Start Date: 9/23/2026) There's a conflict: ASAP vs specific date. Both are present. We should preserve both? The posting includes both: "Start Date: ASAP" and later "Start Date: 9/23/2026". We should keep both as they are substantive. Could combine? Better to keep both as separate statements. - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Location: Hamilton, MT - Facility details: "Apply for specific facility details." That's a boilerplate instruction to apply; we should remove application instructions. So we drop that line. - Job ID: Triage Staffing Job ID #LY7DPU4V. Posted job title: Radiology: CT Tech. This is metadata; we should drop Job ID/requisition numbers as headings, fold minor metadata into a short

    or drop it. So we can drop it entirely or put in a short p. Probably drop. - Benefits list: Day One comprehensive, nationwide insurance plans for health, vision and dental and life—including a HSA option; Day One 401(k) program with employer-matching contributions once eligible; Facility cancelling protection—your time is money on and off-the-clock; Guaranteed hours; Weekly paychecks via direct deposit; Earned vacation bonuses for time worked; Paid holidays; Employee assistance program (EAP)—your mental health is important, too; Continuing education, certification and licensing reimbursement; Workers comp—because accidents happen; Top-rated professional liability insurance; Company provided housing options; Referral bonus—$750 in your pocket after they’ve completed a 13-week assignment. We need to put these as

    • . - Schedule: we have shift details: 12 hours, nights; 36 hours per week; length 13 weeks. So schedule section can include shift, hours per week, duration. We also have start date info maybe in schedule? Could be in About the role. Now craft HTML:

      About the role

      Travel CT Technologist position in Hamilton, Montana. Specialty: CT Technologist; Discipline: Allied Health Professional. Assignment duration: 13 weeks, 36 hours per week, 12‑hour night shifts. Start date: ASAP (also listed as 9/23/2026). Employment type: Travel.

      But we must not invent or summarize away detail. We are summarizing start date as both ASAP and 9/23/2026; that's okay because we are preserving both. We are not adding new info. We could keep them separate sentences. Now Requirements section: list of requirements: Specialty: CT Technologist, Discipline: Allied Health Professional, Location: Hamilton, MT, Start Date: ASAP / 9/23/2026, Duration: 13 weeks, Hours: 36 per week, Shift: 12 hours nights, Employment Type: Travel. We can put as
      • . Benefits section: as list. Schedule section: maybe we already included schedule in About the role and Requirements; but we can still have a Schedule section with shift details: 12‑hour night shifts, 36 hours per week, 13‑week length. We must avoid duplication? The instruction didn't forbid duplication but we should preserve all info; duplication okay but maybe better to avoid redundancy. However we can keep schedule separate. Let's decide: We'll have About the role (prose), Requirements (list), Benefits (list), Schedule (list). That covers all. Now ensure we don't include Pay section. Now output HTML fragment only. Let's craft:

        About the role

        Travel CT Technologist position in Hamilton, Montana. Specialty: CT Technologist; Discipline: Allied Health Professional. Assignment length: 13 weeks, 36 hours per week, 12‑hour night shifts. Start date: ASAP (also noted as 9/23/2026). Employment type: Travel.

        Requirements

        • Specialty: CT Technologist
        • Discipline: Allied Health Professional
        • Location: Hamilton, MT
        • Start date: ASAP (also listed as 9/23/2026)
        • Duration: 13 weeks
        • Hours: 36 per week
        • Shift: 12 hours, nights
        • Employment type: Travel

        Benefits

        • Day One comprehensive, nationwide insurance plans for health, vision and dental and life—including a HSA option
        • Day One 401(k) program with employer‑matching contributions once eligible
        • Facility cancelling protection—your time is money on and off‑the‑clock
        • Guaranteed hours
        • Weekly paychecks via direct deposit
        • Earned vacation bonuses for time worked
        • Paid holidays
        • Employee assistance program (EAP)—your mental health is important, too
        • Continuing education, certification and licensing reimbursement
        • Workers comp—because accidents happen
        • Top‑rated professional liability insurance
        • Company provided housing options
        • Referral bonus—$750 in your pocket after they’ve completed a 13‑week assignment

        Schedule

        • Shift: 12‑hour nights