Travel CT Technologist - $2,617 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 if posting has real specific content. We need to parse the job posting. Key details: - Job Title: travel CT Technologist (but we don't repeat as heading) - Location: Glens Falls, NY - 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 - Shift details: Days, Schedule: 3×12-hour shifts, 10:30 AM – 11:00 PM, Weekend: Every 3rd weekend, On-Call: None, Guaranteed Hours: 36 hours/week, Overtime/Holiday: 1.25× multiplier - Job Summary: description - Responsibilities: list bullet points - Required Qualifications: list bullet points - Preferred Qualifications: list bullet points - Required Certifications & Licensure: list bullet points - Compliance & Submission Requirements: list bullet points - Facility Information: description - Additional Assignment Details: COVID vaccination encouraged, personal scrubs permitted, orientation 8 hours non-billable, facility may cancel up to 5 shifts with 2 hours notice, traveler must have own reliable transportation. - About Talent4Health: description (company info) - Why Choose us? bullet points? Actually it's a paragraph with bullet-like sentences but not list. We need to decide sections: About the role (maybe job summary), Responsibilities, Requirements (maybe combine required qualifications?), Qualifications (maybe required certifications?), Skills (maybe preferred qualifications?), Benefits, Pay, Schedule. We need to include only sections with real specific content. We have schedule details: 3×12-hour shifts, 10:30 AM – 11:00 PM, weekend every 3rd, on-call none, guaranteed hours 36/week, overtime multiplier. So we can create a Schedule section. Pay: Overtime/Holiday: 1.25× multiplier. No base pay given. So we cannot create Pay section because no specific pay amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It states overtime multiplier, but not base pay. Is that enough? Probably not; we need actual pay rate. Since not given, we should omit Pay section. Benefits: Not mentioned. No benefits details. So omit Benefits. We have schedule details, so include Schedule. We have About the role: could be Job Summary. Use heading About the role. Responsibilities: list. Requirements: could be Required Qualifications (including experience, license, certifications). Could combine with Required Certifications & Licensure? But we can have Requirements section for required qualifications (experience, license, etc.) and Qualifications section for preferred qualifications? However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: Job Summary. - Responsibilities: bullet list. - Requirements: Required Qualifications (experience, license, etc.) maybe also Required Certifications & Licensure? Could combine. - Qualifications: Preferred Qualifications. - Skills: maybe from Required Qualifications like "Strong organizational, prioritization, communication, and interpersonal skills." Could be skills. But we could also put skills under Requirements. However we need to decide. Better: Use Requirements for mandatory qualifications (experience, license, certifications). Use Skills for abilities like communication, organizational, computer proficiency. Use Qualifications for preferred qualifications (GE CT scanner experience, previous travel assignment). That seems reasonable. Schedule: as above. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive info. We need to output only HTML fragment, no /, no markdown fences. Let's gather content. About the role (Job Summary): "Glens Falls Hospital is seeking an experienced CT Technologist to perform a variety of CT procedures using independent judgment, technical expertise, and established imaging protocols. The technologist will be responsible for routine diagnostic CT procedures, contrast administration, IV access, patient care, workflow prioritization, and maintaining accurate documentation while providing safe and high-quality imaging services." We can keep that as

. Responsibilities: list bullet points from the responsibilities list. Let's extract: - Perform a variety of CT procedures requiring independent judgment and technical expertise. - Complete all routine diagnostic CT examinations accurately and efficiently. - Administer IV contrast and obtain intravenous access as required. - Follow established CT protocols and prescribed imaging techniques. - Prioritize and organize daily workflow based on patient and department needs. - Provide safe, compassionate patient care throughout imaging procedures. - Maintain appropriate patient positioning and ensure patient safety during examinations. - Recognize and appropriately respond to patient needs or complications related to contrast administration. - Operate CT equipment and associated imaging technology safely and effectively. - Maintain accurate patient records and documentation. - Follow department, hospital, and radiation-safety policies. - Demonstrate strong oral and written communication with patients, physicians, and healthcare team members. - Utilize basic computer skills for documentation and departmental functions. We'll put each as

. Requirements: Required Qualifications list: - Minimum 1 year of CT/PET experience. - Previous experience working with EPIC EMR – REQUIRED. - Current New York State Radiologic Technologist License – REQUIRED. - ARRT – CT certification – REQUIRED. - BLS – AHA – REQUIRED. - Demonstrated contrast injection experience – REQUIRED. - Ability to obtain IV access. - Strong organizational, prioritization, communication, and interpersonal skills. - Basic computer proficiency. - Previous/current travel experience is strongly encouraged. - Own vehicle is REQUIRED for the assignment. - No block scheduling will be considered. Also maybe include "Required Certifications & Licensure" list: ARRT, ARRT-CT/CT Certification, BLS – American Heart Association, Current New York State Radiologic Technologist License. But these overlap with Required Qualifications. To avoid duplication, we can incorporate them. However we must preserve all substantive info; we can include them but avoid duplicate statements. We could merge: list required certifications/licensure as part of Requirements. We'll list: - Minimum 1 year of CT/PET experience. - Previous experience working with EPIC EMR (required). - Current New York State Radiologic Technologist License (required). - ARRT – CT certification (required). - BLS – AHA (required). - Demonstrated contrast injection experience (required). - Ability to obtain IV access. - Strong organizational, prioritization, communication, and interpersonal skills. - Basic computer proficiency. - Previous/current travel experience strongly encouraged. - Own vehicle required for the assignment. - No block scheduling will be considered. We could also note "ARRT" (general) but ARRT-CT covers that. Skills: maybe we extract skills from Required Qualifications: Strong organizational, prioritization, communication, interpersonal skills; basic computer proficiency; ability to obtain IV access; contrast injection experience; etc. But we already have those in Requirements. Perhaps better to put skills like "Strong organizational, prioritization, communication, and interpersonal skills", "Basic computer proficiency", "Ability to obtain IV access", "Demonstrated contrast injection experience". However that duplicates. Alternative: Use Skills for "Strong organizational, prioritization, communication, and interpersonal skills; Basic computer proficiency; Ability to obtain IV access; Demonstrated contrast injection experience". But we already have them in Requirements. Might be okay to have some overlap but we should avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we need to fill Skills section with something; if we put nothing, we shouldn't create the section. So maybe we skip Skills section if no distinct skill content beyond what's already in Requirements. But we could treat Skills as "Strong organizational, prioritization, communication, and interpersonal skills; Basic computer proficiency; Ability to obtain IV access; Demonstrated contrast injection experience". That is still substantive but duplicates. Might be acceptable. Qualifications: Preferred Qualifications: - GE CT scanner experience preferred. - Previous travel assignment experience preferred. We could also include "Previous/current travel experience is strongly encouraged" but that's already in Requirements as strongly encouraged; but we can keep. We'll list those. Schedule: details: - Shift: 12 hours, days. - Schedule: 3×12-hour shifts, 10:30 AM – 11:00 PM. - Weekend: Every 3rd weekend. - On-Call: None. - Guaranteed Hours: 36 hours/week. - Overtime/Holiday: 1.25× multiplier. We can present as

• ...

. We must not include Pay section. We must not include Benefits section. We must not include About Talent4Health? The instruction: "About the role" heading is for role summary, not company. The "About Talent4Health" is company info; maybe we could put under "About the role"? No, that's specific to role. The company description is not required; but we might include it as a separate section? Not in allowed headings. The allowed headings list does not include "About the company". So we should omit that content? The instruction says preserve ALL substantive information; but we cannot create headings not in list. However we could incorporate that info into a

without a heading? The instruction: "use

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

for section headings (e.g. those). It might be okay to use other headings but they gave examples. Safer to stick to those headings only. So we should omit the Talent4Health description because it's not about the role. However it's substantive info about the employer; but maybe considered boilerplate? It's not boilerplate; it's about the agency. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. But we have no heading for it. Could we put it under "About the role"? That would be misleading. Better to omit? The instruction says preserve ALL substantive information; but we cannot create a heading not allowed. Could we just put a

without heading? The instruction says use

for section headings (e.g...). It doesn't say you cannot have other headings, but they gave examples. It might be okay to have a

for "About Talent4Health". However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings; but not strictly forbidden to add others. However to be safe, we could include a section "About the agency" but not in list; risk. Given the instruction to prefer a few substantive sections over many thin ones, and they gave examples, I think we should stick to those headings only. So we will omit the Talent4Health description and the "Why Choose us?" etc. That's substantive but maybe considered boilerplate? It's promotional but still substantive. However the instruction says preserve ALL substantive information; but if we omit, we violate. However maybe they consider that as boilerplate? It's not legal/EEO but it's promotional. Hard to know. Given typical tasks, they'd want to keep the job description details, not the agency marketing. I'd lean to omit the Talent4Health blurb. Thus final HTML will have sections: About the role, Responsibilities, Requirements, Qualifications,