Travel CT Technologist - $2,849 per week

We need to output HTML fragment with sections: 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. Let's parse the posting: - Job title: CT Technologist (travel) - Location: Jerome, Idaho - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: 10/12/2026 - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, nights - Employment Type: Travel - Description: 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. - Job ID #2191581 (metadata, drop) - 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 Technician (maybe duplicate) - About Trustaff Allied: description of company, benefits list. - Benefits list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus (and also earlier: 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). So we need to capture benefits specifics. We need sections: About the role (maybe description of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have limited specifics: responsibilities: capture diagnostic images, work directly with patient, need expert knowledge of imaging process, be well-versed in imaging equipment and its operation. That's responsibilities. Requirements/Qualifications/Skills: Not explicitly listed besides being a CT Technologist (specialty). Could infer requirement: CT Technologist certification, but not stated. We should not invent. So we should only include sections where there is real specific content. If no explicit requirements, we may omit Requirements, Qualifications, Skills sections. However we might include "About the role" as a prose paragraph summarizing role. Pay: we have "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." That's vague but it's specific about shift length and hours, and mentions tax-free stipend amount TBD. The instruction 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 Pay is stated but includes TBD for stipend amount. Is that considered filler? It says "tax-free stipend amount to be determined." That's TBD. The instruction 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. The Pay section would contain that statement, which includes TBD. Is that considered filler? The phrase "tax-free stipend amount to be determined" is TBD-like. Might be considered placeholder. Safer to omit Pay section because it's not concrete. However we could include Pay section with the statement about based on 10 hour shifts and 40 hours per week (subject to confirmation). That's somewhat specific but still includes "subject to confirmation". Might be okay? The instruction 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. The posting does state 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. That's stating something, albeit with uncertainty. I'd lean to include Pay section with that exact sentence. Schedule: we have Shift: 10 hours, nights; 40 hours per week; Duration: 13 weeks; Start Date: 10/12/2026. So schedule specifics: 10 hour night shifts, 40 hours per week. That's concrete. So we can include Schedule section. Benefits: we have list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus, plus earlier: Comprehensive benefits including medical, dental, vision; 401k with employer match; Assistance with travel, compliance, and housing; Great bonuses for completions, referring friends, and more. So we have specific benefits. We'll include Benefits section with a

• list. About the role: we can include a paragraph describing the role: capturing diagnostic images, working directly with patient, need expert knowledge of imaging process, well-versed in imaging equipment and its operation. That's from description. Responsibilities: maybe same as description? Could separate but we might combine. However we need to avoid duplication. Could put responsibilities as bullet list: capture diagnostic images, work directly with patient, maintain expert knowledge of imaging process, be well-versed in imaging equipment operation. That's derived. Requirements/Qualifications/Skills: Not given explicitly. Could we infer from "CT Technologist" specialty? Might be too speculative. Better to omit those sections if no concrete content. Thus sections: About the role (paragraph), Responsibilities (ul), Benefits (ul), Pay (p), Schedule (p). Possibly also include "About Trustaff Allied" as a section? Not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a section for company description. However we could incorporate company description into About the role? But About the role should be about the role, not company. The instruction says use those headings for section headings. It didn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It didn't say we cannot have other headings, but better to stick to those. The company description could be omitted as boilerplate? It's not boilerplate; it's substantive about Trustaff. But it's not in the list; maybe we should incorporate into About the role? However About the role is supposed to be about the role, not company. But we could treat it as "About the role" includes both role and company? Might be stretching. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not exclusive list. So we could add other headings if needed, but better to follow examples. However the company description is not boilerplate; it's substantive. Should we include it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info. If we don't have a heading for it, we could put it in a

  without a heading. That's allowed. So we can just include a paragraph about Trustaff Allied after the role description, without a heading. That preserves info. Thus final HTML:

  About the role

  ...

  Responsibilities

  • ...

  Benefits

  • ...

  Pay

  ...

  Schedule

  ...

  We must not repeat job title as heading. Not include Job ID. Now craft content: About the role paragraph: "As a CT Technologist, you will capture important diagnostic images by working directly with patients. You must be well‑versed in the imaging equipment and its operation and possess expert knowledge of the CT imaging process." Responsibilities bullet list: - Capture diagnostic images while working directly with patients. - Maintain expert knowledge of the CT imaging process. - Operate and be proficient with CT imaging equipment. - Ensure patient safety and comfort during scans. - Collaborate with radiologists and healthcare team to produce accurate images. But some of these may be inferred; we need to avoid inventing. The original only says: "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 it. So we should not add extra responsibilities like patient safety, collaboration unless stated. So we stick to exactly those two sentences. Could break into two bullets: capture images, be well-versed in equipment and have expert knowledge. But that's somewhat repetitive. Better to keep as prose? But we need
  • for any list of duties/requirements/benefits. The responsibilities are a list of duties. So we can make two bullets: "Capture important diagnostic images by working directly with patients." and "Be well‑versed in the imaging equipment and its operation, possessing expert knowledge of the CT imaging process." That's directly from text. Benefits: list from posting: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus, Comprehensive benefits including medical, dental, and vision (but that's duplicate), 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, not invent. We should not duplicate. So we can combine unique items: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus, 401k with employer match, Assistance with travel, compliance, and housing, Bonuses for completions, referring friends, and more. The phrase "Great bonuses for completions, referring friends, and more" is a benefit. We'll include as "Bonuses for completions, referring friends, and more". Also "Comprehensive benefits, including medical, dental, and vision" is essentially same as listing those three; we can omit to avoid duplication. Thus benefits list: - Dental benefits - Medical benefits - Vision benefits - Guaranteed Hours - Referral bonus - 401(k) with employer match - Assistance with travel, compliance, and housing - Bonuses for completions, referring friends, and more Pay: "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." Schedule: "Shift: 10 hours, nights; 40 hours per week; Start date: 10/12/2026; Duration: 13 weeks." We could also include "Employment Type: Travel" maybe as part of schedule or about role. But schedule section is for schedule specifics; employment type could be in About the role paragraph. We'll add a sentence about travel employment type in About the role maybe. But we must not invent. The posting includes "Employment Type: Travel". That's substantive. We could add to About the role: "This is a travel position." Or we could add a separate bullet? Not needed. Let's craft About the role paragraph: "This travel position for a CT Technologist in Jerome, Idaho involves capturing important diagnostic images by working directly with patients. You must be well‑versed in the imaging equipment and its operation and possess expert knowledge of the CT imaging process." Add mention of travel: "This is a travel assignment." Now produce HTML. Check for any boilerplate removal: We removed lines about Trustaff Allied description? We kept none