Travel Radiology Technologist - $1,587 per week

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to extract substantive info. Let's parse the posting. Key info: - Focus Staff seeking travel Radiology Technologist (X-Ray Tech) for travel job in Hermitage, Tennessee. - Specialty: Radiology Technologist - Discipline: Allied Health Professional - Start Date: 09/28/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights (also later: Shift: 3x12 Nights) - Employment Type: Travel - Requirements: 1 Year of Experience, 2 Preferred (maybe they meant 2 years preferred? Actually "1 Year of Experience, 2 Preferred" ambiguous; but we keep as given) - Valid TN License - BLS - Eligible to work in the United States - Benefits for Travel X-Ray Techs: Health insurance, Vision insurance, Dental insurance, Life insurance, Licensure reimbursement, Travel reimbursement, Relocation assistance, 401(k), 401(k) matching, Competitive pay, Referral bonus, Holiday bonus - Also later: We Offer: Immediate Openings, Weekly Pay through Direct Deposits, Flexible Schedules, Day and Night Shifts Available, Competitive Compensation, Guaranteed Hours (based on employer), Travel Assistance, Dedicated/Responsive Recruiters, Day One Medical, Dental, Vision and Life Insurance, Generous Housing Stipend, 24/7 Support, Company Provided Housing Options, Referral Bonus ($600), Loyalty Bonus ($1,200), Discounts/Coupons to Hotels, Access to Jobs in all 50 States, Painless Credentialing Process, U.S.A.-based Company, Equal Opportunity Employer, Joint Commission Certified, Licensure Reimbursement, Pet-Friendly, Access to Discounts, Rewards, and more - Pay package: Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on several factors, including, but not limited to, guaranteed hours, travel distance, demand, experience, etc. Travel X-Ray Tech, X-Ray Technologist Contract, Allied Health Travel Positions, Travel Medical Imaging Jobs, Imaging Technologist Travel Assignments, Travel, Contract, Assignment, Traveling X-Ray Tech Assignment, X-Ray Tech, Contract X-Ray Tech, CT Tech, X-Ray, HealthcareFocus Staff Job ID #a0xVt00000Vuw98IAB. 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. We need to avoid boilerplate like EEO, etc. But we can keep some agency description if it's substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statements, but we can keep agency description about Focus Staff if it's not boilerplate? The "About Focus Staff" section includes mission etc. Might be considered boilerplate? It's somewhat promotional but maybe okay to keep as "About the role"? Actually we have heading "About the role". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role section describing the job. We should not repeat job title as heading. So we can put a paragraph about the role. We need to include sections only when posting has real, specific content for it. So we need to decide which sections to include. We have: - About the role: we can summarize the job description: travel Radiology Technologist in Hermitage, TN, start date, duration, hours, shift, etc. - Responsibilities: Not explicitly listed. The posting does not give specific duties beyond being a Radiology Technologist. Could infer but we should not invent. So we should not create Responsibilities section if no specific content. - Requirements: we have specific: 1 Year of Experience, 2 Preferred (maybe 2 years preferred?), Valid TN License, BLS, Eligible to work in US. We'll include that. - Qualifications: maybe overlapping with Requirements; but we could treat Requirements as qualifications. The instruction says we can have Requirements, Qualifications, Skills sections. We need to avoid duplication. We could put Requirements as a list, and maybe Qualifications as another list if distinct. But we have no separate qualifications beyond license etc. Could combine. - Skills: Not specified. Could infer but we should not invent. So skip. - Benefits: we have list: Health insurance, Vision insurance, Dental insurance, Life insurance, Licensure reimbursement, Travel reimbursement, Relocation assistance, 401(k), 401(k) matching, Competitive pay, Referral bonus, Holiday bonus, plus other benefits like Weekly Pay through Direct Deposits, Flexible Schedules, Day and Night Shifts Available, Guaranteed Hours, Travel Assistance, Dedicated/Responsive Recruiters, Day One Medical, Dental, Vision and Life Insurance (duplicate), Generous Housing Stipend, 24/7 Support, Company Provided Housing Options, Referral Bonus ($600), Loyalty Bonus ($1,200), Discounts/Coupons to Hotels, Access to Jobs in all 50 States, Painless Credentialing Process, Licensure Reimbursement (duplicate), Pet-Friendly, Access to Discounts, Rewards, etc. Many duplicates. We need to preserve all substantive information but remove duplicated lines. So we need to deduplicate. - Pay: we have mention of Competitive pay, but no specific numbers. The instruction: 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. For Pay, we have "Competitive pay" which is vague but maybe considered placeholder? It's not a specific number. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive pay" is somewhat vague but maybe acceptable? It's not a specific number but it's a statement. However they said never create Pay section unless posting actually states them. It does state "Competitive pay". That's a statement, albeit vague. Should we include? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Competitive pay, so we could include Pay section with that statement. However also they said "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". Competitive pay is not exactly those but still vague. Might be considered filler. Safer to omit Pay section if no concrete numbers. But we could include Pay with "Competitive pay" as content. I'd lean to include because it's stated. - Schedule: we have shift details: 36 hours per week, Shift: 12 hours, nights (3x12 Nights). So we can include Schedule section with that. Now we need to output HTML fragment only, no /, no markdown. We'll produce sections:

About the role

Focus Staff is seeking a travel Radiology Technologist (X‑Ray Tech) for a 13‑week contract in Hermitage, Tennessee. Start date: September 28, 2026. The position requires 36 hours per week on 12‑hour night shifts (3×12 nights).

Requirements

• Minimum 1 year of experience as an X‑Ray Tech (2 years preferred)
• Valid Tennessee license
• BLS certification
• Eligible to work in the United States

Benefits

• Health insurance
• Vision insurance
• Dental insurance
• Life insurance
• Licensure reimbursement
• Travel reimbursement
• Relocation assistance
• 401(k) plan
• 401(k) matching
• Competitive pay
• Referral bonus
• Holiday bonus
• Weekly pay via direct deposit
• Flexible schedules
• Day and night shifts available
• Guaranteed hours (based on employer)
• Travel assistance
• Dedicated/responsive recruiters
• Day‑one medical, dental, vision and life insurance
• Generous housing stipend
• 24/7 support
• Company‑provided housing options
• Referral bonus ($600)
• Loyalty bonus ($1,200)
• Discounts/coupons for hotels
• Access to jobs in all 50 states
• Painless credentialing process
• Pet‑friendly policy
• Access to discounts, rewards and more

Schedule

• 36 hours per week
• 12‑hour night shifts (3×12 nights)

We might also include Pay section: but we already have Competitive pay in Benefits. Could also separate Pay. But we already have Competitive pay listed under Benefits. Might be redundant. Better to have Pay section with "Competitive pay" and maybe note that exact package varies. But we should avoid filler. However we already have Competitive pay in Benefits; we could keep it there and not have separate Pay. The instruction: Prefer a few substantive sections over many thin ones. So we can keep Benefits inclusive of pay. We need to ensure no duplicated lines: we have Licensure reimbursement appears twice in original; we included once. Referral bonus appears twice (generic and $600). We included both generic Referral bonus and Referral bonus ($600). Might be considered duplicate but they differ in amount. Could combine? We could keep one entry: Referral bonus ($600). But we also have generic Referral bonus earlier. To avoid duplication, we can keep the specific amount. Similarly Loyalty bonus ($1,200). We'll keep those. We also have Day One Medical, Dental, Vision and Life Insurance which duplicates the earlier health insurance list. Might be considered duplicate but it's more specific about day-one coverage. Could keep both? Might be considered duplicate but it's additional detail. We'll keep it as separate line. We also have "Competitive pay" already in Benefits; we might also have "Competitive Compensation" in We Offer list. That's duplicate. We'll keep one. Now ensure we didn't include any boilerplate like EEO, Joint Commission Certified etc. We removed those. Check for any leftover boilerplate: "U.S.A.-based Company", "Equal Opportunity Employer", "Joint Commission Certified", "Licensure Reimbursement" (we kept), "Pet-Friendly" we kept, "Access to Discounts, Rewards, and more" we kept as "Access to discounts, rewards and more". That's okay. Now produce final HTML. Make sure to use proper HTML tags:

,

,

• . No extra whitespace