Travel CT Technologist - $1,977 per week

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, etc. Preserve all substantive info. Let's parse the posting. Content: - Trustaff Allied is seeking a travel CT Technologist for a travel job in Brevard, North Carolina. - Job Description & Requirements - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: 10/11/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - As a CT Tech, you'll capture important diagnostic images by working directly with the patient. CT Techs and Radiologists must have expert knowledge of the imaging process, so you must be well-versed in the imaging equipment and its operation. - Trustaff Allied Job ID #2194091. 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 Technician - About Trustaff Allied: paragraphs about company. - Benefits list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus (maybe also 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more). Actually earlier they listed: Comprehensive benefits, including medical, dental, and vision; 401k with employer match; Assistance with travel, compliance, and housing; Great bonuses for completions, referring friends, and more. Then later they have a Benefits section list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. We need to include sections only if real specific content. We have: - About the role: Could be the description of role: "As a CT Tech, you'll capture important diagnostic images by working directly with the patient. CT Techs and Radiologists must have expert knowledge of the imaging process, so you must be well-versed in the imaging equipment and its operation." That's substantive. - Responsibilities: Not explicitly listed; maybe we can infer from description? But we should not invent. The posting does not list responsibilities separate. So we should not create Responsibilities section unless there is explicit list. There's no bullet list of duties. So skip. - Requirements: Not explicit list; maybe they mention "must be well-versed in imaging equipment". That's more a requirement. But it's not a list. Could we treat as Requirements? The instruction: Use sections only when posting has real, specific content for it. The posting includes "Specialty: CT Technologist", "Discipline: Allied Health Professional", "Start Date", "Duration", "36 hours per week", "Shift: 12 hours, nights", "Employment Type: Travel". Those could be considered qualifications or job details. But we have sections for Qualifications, Skills, Benefits, Pay, Schedule. We have Pay: "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 specific enough? It says amount to be determined, but still mentions basis. It's not a specific number. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here "tax-free stipend amount to be determined" is placeholder. So we should not create Pay section if it's just placeholder. However we have "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's still somewhat vague but maybe acceptable? It says based on 12 hour shifts and 36 hours per week. That's not a monetary amount. It's not a specific pay. So likely we should omit Pay section. Schedule: We have shift details: 12 hours, nights; 36 hours per week; duration 13 weeks. That's schedule info. So we can create Schedule section with those specifics. Benefits: We have list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus, plus earlier mention of 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more. That's substantive. So Benefits section. About the role: we have description. Qualifications: Could include Specialty, Discipline, maybe requirement to be well-versed in imaging equipment. But we need to see if there is explicit qualifications list. Not really. However we could combine into About the role? But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine role description and qualifications into About the role? But they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We have explicit content for About the role (description). We have Benefits list. We have Schedule details. Possibly we have Qualifications: "Specialty: CT Technologist", "Discipline: Allied Health Professional". Also maybe "must be well-versed in the imaging equipment and its operation." That's a qualification. Could be included. We also have Start Date, Duration. Those could be part of Schedule or maybe separate but we can include in Schedule. Thus sections: About the role, Qualifications, Benefits, Schedule. We should not include Responsibilities, Requirements, Skills, Pay. Now format: Use

for each heading. Use

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

  for prose. We need to preserve all substantive information. Let's extract: About the role prose: "As a CT Tech, you'll capture important diagnostic images by working directly with the patient. CT Techs and Radiologists must have expert knowledge of the imaging process, so you must be well-versed in the imaging equipment and its operation." Also maybe include location: Brevard, North Carolina. And that it's a travel job. Could be part of About the role? Might be better to include location in About the role as prose. We also have: "Trustaff Allied is seeking a travel CT Technologist for a travel job in Brevard, North Carolina." That's also role info. Combine: "Trustaff Allied is seeking a travel CT Technologist for a travel job in Brevard, North Carolina. As a CT Tech, you'll capture important diagnostic images by working directly with the patient. CT Techs and Radiologists must have expert knowledge of the imaging process, so you must be well-versed in the imaging equipment and its operation." That's good. Qualifications: list items: Specialty: CT Technologist; Discipline: Allied Health Professional; Must be well-versed in imaging equipment and its operation (maybe duplicate). Also maybe Start Date and Duration? Those are more schedule. But we could include Start Date and Duration as qualifications? Probably better in Schedule. But we have Start Date: 10/11/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel. We'll put those in Schedule. Thus Qualifications list: Specialty: CT Technologist; Discipline: Allied Health Professional; Must be well-versed in imaging equipment and its operation. We could also include that it's a travel position? But that's more job type. Now Benefits list: Dental benefits; Medical benefits; Vision benefits; Guaranteed Hours; Referral bonus; 401k with employer match; Assistance with travel, compliance, and housing; Great bonuses for completions, referring friends, and more. We need to preserve all substantive info. The posting also mentions "Industry-leading pay, benefits, and bonuses" but that's vague. We'll stick to concrete list. Now Schedule: Start Date: 10/11/2026; Duration: 13 weeks; Hours per week: 36 hours; Shift: 12 hours, nights; Employment Type: Travel. We can format as list. Now ensure we don't include any boilerplate like "About Trustaff Allied" paragraphs about company. That's not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Trustaff Allied" paragraphs are promotional but not boilerplate? They are about the company. Might be considered substantive? The instruction says preserve ALL substantive information. So we should include that info? It's about the company, not the job. But it's still substantive. However we have limited sections; we could include an "About Trustaff Allied" section but not in the predefined headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should not create a heading outside those. We could fold that info into About the role? But it's not about the role. The instruction says prefer a few substantive sections over many thin ones. We could include that info as a paragraph under About the role? Might be stretching. But maybe we can incorporate some of that as part of Benefits? Not really. Given the instruction to preserve ALL substantive information, we need to include that company description somewhere. Since we cannot create arbitrary headings, we could put it as a

  after the headings? The instruction says output ONLY the HTML fragment, no /. It didn't forbid extra paragraphs not under headings. It says 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 say we cannot have prose outside headings. But likely they expect sections with headings and content under them. However we could add a

    about Trustaff Allied after the headings as a general paragraph. That would preserve info. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we can incorporate that company description into Benefits? Not appropriate. Better to add a section "About Trustaff Allied" but that's not in allowed headings list. The list says e.g., meaning examples, not exclusive? 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, but likely they expect only those headings. Safer to stick to those. Thus we may drop the company description. But that would lose substantive info. However maybe it's considered boilerplate? It's promotional but still substantive. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it. We could incorporate it into About the role as a paragraph: "Trustaff Allied is a travel healthcare agency..." etc. That would be about the role? Slightly off but maybe acceptable. Let's try: About the role paragraph includes both job description and company info. Thus About the role: "Trustaff Allied is seeking a travel CT Technologist for a travel job in Brevard, North Carolina. As a CT Tech, you'll capture important diagnostic images by working directly with the patient. CT Techs and Radiologists must have expert knowledge of the imaging process, so you must be well-versed in the imaging equipment and its operation. Trustaff Allied's traveler-first attitude has set us apart from other travel healthcare agencies. When you join the Trustaff family, you’re more than just a body filling a role—you're a vibrant individual with dreams and aspirations. As one of the nation's leading travel healthcare companies, your recruiter will work with you one-on-one to