Travel Radiology Tech - $1,991 per week

We need to output HTML fragment with sections: About the role? Actually we have description, requirements, highlights, about Slate Healthcare. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content. We have: - Job description: "As an X-Ray Tech, you will conduct routine and complex X-ray exams and assist with fluoroscopy procedures in a fast-paced acute care environment. The role requires strong patient care and communication skills, ensuring quality imaging services for a diverse patient population. You will work in a Level II Trauma Center, floating between units as necessary, providing essential imaging support while maintaining high standards of care." That's prose; could be under

About the role

or

Responsibilities

. Since it's description of duties, we can use Responsibilities. - Highlights: bullet list: "Work in a Level II Trauma Center", "Strong emphasis on patient care and communication skills", "Float between units as needed". Could be under

Highlights

but not in allowed list; allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Highlights not listed; but we could incorporate into Responsibilities or About the role. Probably better to put under Responsibilities as bullet list. - Requirements: "MinExperienceRequired: 1 year", "Certifications: BLS, ARRT", "EMR System: Any". Also maybe "Specialty: Radiology Technologist", "Discipline: Allied Health Professional", "Start Date: 10/26/2026", "Duration: 13 weeks", "40 hours per week", "Shift: 8 hours, days", "Employment Type: Travel". Some of these are metadata; we should not put Job ID etc. We can include start date, duration, hours, shift, employment type maybe in a short

or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph with metadata like start date, duration, etc. But we should not create sections for Pay/Schedule/Benefits unless posting actually states them. Pay: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague; not specific amount. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 8 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's still vague but it's stating something about pay. However it says "subject to confirmation" and "amount to be determined". That might be considered not specific. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined" which is TBD. So we should not create a Pay section because it's placeholder. Similarly schedule: we have shift 8 hours, days, 40 hours per week. That's specific. Could we create a Schedule section? The posting states shift and hours. That's specific. So we could include a Schedule section with that info. However the instruction: Prefer a few substantive sections over many thin ones. We could incorporate schedule into Requirements or About the role. But we have a separate Schedule heading allowed. Might be okay to include Schedule section with the shift details. Benefits: not mentioned besides tax-free stipend amount to be determined (which is placeholder). So no Benefits. Qualifications/Skills: we have certifications BLS, ARRT, experience 1 year. Could be under Requirements or Qualifications. We'll use Requirements heading for experience and certifications, and maybe Qualifications for skills like patient care, communication. But we can combine. We need to avoid repeating job title as heading. So no heading for "Radiology Technologist". Use headings for sections. We must output only HTML fragment, no /, no markdown. Let's structure:

About the role

As an X-Ray Tech, you will conduct routine and complex X-ray exams and assist with fluoroscopy procedures in a fast-paced acute care environment. The role requires strong patient care and communication skills, ensuring quality imaging services for a diverse patient population. You will work in a Level II Trauma Center, floating between units as necessary, providing essential imaging support while maintaining high standards of care.

Responsibilities

• Conduct routine and complex X-ray exams
• Assist with fluoroscopy procedures
• Float between units as needed in a Level II Trauma Center
• Maintain high standards of patient care and communication

But we already described responsibilities in About the role; maybe we can combine. However we need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. We can keep both but ensure not duplicate same sentences. Could restructure: About the role as brief overview, Responsibilities as bullet list. We have highlights: "Work in a Level II Trauma Center", "Strong emphasis on patient care and communication skills", "Float between units as needed". Those are similar to responsibilities. Could incorporate. Requirements: experience 1 year, certifications BLS, ARRT, EMR System Any. Also maybe specialty Radiology Technologist, discipline Allied Health Professional. We'll put those under Requirements. Schedule: shift 8 hours, days, 40 hours per week. We'll put under Schedule. About Slate Healthcare: we can put under

About the employer

but not in allowed list. Allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No About the employer. However we could incorporate that into About the role? But it's about the company, not role. The instruction says use those headings for section headings (e.g., About the role, Responsibilities...). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when appropriate, but we could also use other headings? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings but better to stick to those. However we have info about Slate Healthcare that is substantive; we could put it under

About the role

but that's misleading. Maybe we can create a

About the employer

but it's not in list; risk of being considered not following instruction. Safer to incorporate that info into a

without a heading, or under a generic heading like

About Slate Healthcare

but that's not in list. The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but the examples are those. I'd think it's okay to use other headings as long as they are

. However to be safe, we could put that info under a

About the role

but that would be mixing role and employer. Better to add a

About Slate Healthcare

as it's still a heading; the instruction didn't say we cannot use other headings, just gave examples. I'll include it. We must not include boilerplate like EEO etc. There's none. Now ensure we don't include placeholder sections. Pay: we have "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This includes placeholder "tax-free stipend amount to be determined". That's TBD. So we should not create Pay section. We could mention pay in a short paragraph without heading? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Pay is metadata but includes placeholder; maybe we can drop it entirely? But we need to preserve ALL substantive information. The substantive part is "Pay package is based on 8 hour shifts and 40.0 hours per week". That's about schedule actually. The stipend amount TBD is not substantive. So we could incorporate the base pay info into Schedule section (since it's about hours). Or we could note that pay is based on 8 hour shifts and 40 hours per week (subject to confirmation) but we can't give amount. Since we cannot create Pay section due to placeholder, we can include that sentence in a

under Schedule or maybe under About the role. But we already have Schedule section with shift and hours; we can add note about pay being based on those hours. Thus Schedule section:

Schedule

8‑hour day shifts, 40 hours per week; pay package is based on this schedule (tax‑free stipend amount to be determined).

That preserves info. Now Requirements: include experience, certifications, EMR system, specialty, discipline, start date, duration? Start date and duration are metadata; we could fold into a short p under Requirements or separate. But we have no heading for metadata; we could add a

after Requirements heading with start date, duration, employment type. Or we could create a

Job details

but not in list. Better to fold into a short p under Requirements. Let's craft:

Requirements

Start date: 10/26/2026; Duration: 13 weeks; Employment type: Travel.

• Minimum 1 year of experience as a Radiology Technologist
• Current BLS and ARRT certification
• Any EMR system experience acceptable
• Specialty: Radiology Technologist; Discipline: Allied Health Professional

But we should avoid repeating "Specialty: Radiology Technologist" as it's the job title; but it's okay as requirement. Now About Slate Healthcare: we can put under

About Slate Healthcare

with paragraphs. Now ensure we don't repeat job title as heading. We have no heading that is exactly "Radiology Technologist". Good. Now output only HTML fragment. Let's produce:

About the role

As an X‑Ray Tech, you will conduct routine and complex X‑ray exams and assist with fluoroscopy procedures in a fast‑paced acute care environment. The role requires strong patient care and communication skills, ensuring quality imaging services for a diverse patient population. You will work in a Level II Trauma Center, floating between units as necessary, providing essential imaging support while maintaining high standards of care.

Responsibilities

• Perform routine and complex X‑ray examinations
• Assist with fluoroscopy procedures
• Float between units as needed in a Level II Trauma Center
• Maintain high standards of patient care and communication

Requirements

Start date: 10/26/2026; Duration: 13 weeks; Employment type: Travel.

• Minimum 1 year of