Travel Radiology Technologist - $1,801 per week
describing requirements? The rule: Use
- for any list of duties/requirements/benefits, and
for prose. If we have no list, we could still put prose in
. But we should only include a section if posting has real, specific content for it. The posting does have some specifics: Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel. That could be considered requirements or about the role. We'll decide. - Qualifications: Not explicit. - Skills: Not explicit. - Benefits: We have a list: Day 1 Insurance Cigna medical, MetLife dental and vision insurance, License reimbursement for new licenses needed for each assignment, Discounts with hotels and rental cars, A dedicated recruiter and support team..., Referral bonus up to $700. Also later "Benefits Referral bonus Benefits start day 1 Employee assistance programs". So we have benefits content. - 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 vague; stipend amount TBD. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention pay package based on shifts and hours, but stipend amount TBD. Is that considered stating pay? It says "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 not a specific amount; it's vague. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a Pay section because the stipend amount is TBD (placeholder). However we could still include the info that pay package is based on shifts and hours, but that's still vague. Better to omit Pay section. - Schedule: We have shift: 12 hours, nights; 36 hours per week. That's schedule info. It's specific: 12 hour shifts, nights, 36 hours per week. That's not placeholder. So we can include Schedule section. - About the role: Could include specialty, discipline, start date, duration, etc. That's specific. - About the Company: There's a paragraph about Uniti Med. That could be "About the Company" but not in our list of allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About the Company. Could fold that into About the role? Possibly but it's about company, not role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and 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 about company maybe under About the role? But better to keep only sections with real content that match allowed headings. We could treat the company description as part of About the role? Might be okay. Or we could drop it. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that company description somewhere. If we don't have a heading for it, we could put it as a
before any sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we must use only those headings; we can have other headings? It says: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections, but we could also have other headings? Probably not; they want us to use those headings for sections. But we could also have a
for prose outside sections. So we could include a
with the company description before sections. Similarly, the "About Uniti Med" paragraph later is similar. We also have "Benefits" repeated. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's none evident. We need to preserve all substantive information: specialty, discipline, start date, duration, hours, shift, employment type, benefits list, pay package note, company description, etc. We need to format using
for section headings,
- for any list,
for prose. We'll create sections: - About the role: include specialty, discipline, start date, duration, hours per week, shift, employment type. Could be a
with those details. - Benefits: list as
- .
- Schedule: include shift details and hours per week. Could be a
. - Pay: we have stipend TBD, which is placeholder; we should not create Pay section because it's placeholder. But we could still mention that pay package is based on shifts and hours with tax-free stipend TBD? That's still placeholder. Better to omit Pay section. - Responsibilities, Requirements, Qualifications, Skills: no specific content, so omit. Now we need to include company description somewhere. Could be a
before sections: maybe a brief intro about Uniti Med. We have two similar paragraphs: "About the Company: Finding the right role..." and "About Uniti Med Uniti Med meticulously matches your talents...". They are somewhat redundant but both substantive. We'll combine or keep both as separate
paragraphs. We need to avoid duplication: they are similar but not identical; we can keep both. Now construct HTML:
About the Company: Finding the right role is about more than just matching skills to a job—it’s about aligning with your goals, values, and the way you want to work. As an award-winning talent partner, we support healthcare professionals through every step of that process, offering meaningful opportunities, clear guidance, and long-term partnership. From our first conversation to your first day on the job (and beyond!), we’re here to help you move forward with confidence.
Uniti Med meticulously matches your talents to our open needs to ensure the ultimate travel experience. Tell us where you want to go and let our experienced staff lead the way!
About the role
Specialty: Radiology Technologist; Discipline: Allied Health Professional; Start Date: 10/20/2026; Duration: 14 weeks; Hours: 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel.
Benefits
- Day 1 Insurance: Cigna medical, MetLife dental and vision
- License reimbursement for new licenses needed for each assignment
- Discounts with hotels and rental cars
- A dedicated recruiter and support team to help you every step of the way to ensure you start on time and have an exceptional experience
- Referral bonus up to $700
- Employee assistance programs
Schedule
Shift: 12 hours, nights; 36 hours per week.
We also have "Benefits start day 1" already covered. "Referral bonus" covered. "Employee assistance programs" added. We also have "Benefits Referral bonus Benefits start day 1 Employee assistance programs" which is redundant. We also have "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." Since we omitted Pay section, we could incorporate that info into Schedule or About the role? It's about pay, but it's placeholder. Better to omit entirely? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. This is substantive but vague. However it's not placeholder like "TBD"? It says stipend amount to be determined, which is TBD. That's placeholder. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). It doesn't say we cannot include placeholder text inside a paragraph if we have a heading for something else. But we are not creating a Pay heading. We could include that sentence as asomewhere, maybe under About the role or Schedule? But it's about pay, not schedule. Could add a
under About the role? Might be okay. However the rule about not creating Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package based on shifts and hours with stipend TBD. That's stating something about pay, albeit incomplete. So we could include a Pay section but we must avoid filler placeholder text. The stipend amount TBD is placeholder. If we include Pay section, we would have heading Pay and then a paragraph containing "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 includes placeholder "to be determined". That's dis
- .
- Schedule: include shift details and hours per week. Could be a
- for any list,