Travel X-Ray Technologist - $2,334 per week
Travel Nurses, Inc. · Des Moines, IA · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with headings for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
- About the role: Could include description of role: travel Radiology Technologist, specialty, discipline, start date, duration, hours, shift, employment type, location. That seems appropriate.
- Responsibilities: Not explicitly listed. The posting does not list duties. So we should not create Responsibilities section if no specific content.
- Requirements: Could include specialty, discipline, maybe license? Not given. Only specialty and discipline. Might be considered requirements. But we need specific content. The posting includes "Specialty: Radiology Technologist" and "Discipline: Allied Health Professional". Those could be considered requirements. However we need to decide if we should create a Requirements section with those items. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Requirements if we have specifics. We have specialty and discipline. That's specific. Could also include start date, duration, hours, shift, employment type. Those could be considered job details, maybe under About the role. But we could also put them under Requirements? Usually requirements are qualifications needed. But we can treat them as role details.
Better to have About the role containing description: travel Radiology Technologist in Des Moines, Iowa, start date, duration, hours, shift, employment type.
Then Requirements could list specialty and discipline (maybe also that they need to be allied health professional). But that seems redundant.
Qualifications: Not given.
Skills: Not given.
Benefits: we have Weekly pay, 401k retirement plan, Life insurance. That's specific.
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." That's somewhat vague but includes info: based on 8 hour shifts, 40 hrs/week, tax-free stipend TBD. It's not a specific number but it's still content. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The pay section includes "tax-free stipend amount to be determined" which is TBD. That's placeholder. Also "subject to confirmation". This might be considered filler. However we still have some concrete: based on 8 hour shifts and 40 hours per week. That's not a filler. But the pay amount is not given. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. So there is some content, albeit vague. Should we include Pay section? Probably yes, but we need to avoid filler placeholder text. We could phrase: Pay package based on 8‑hour shifts, 40 hours per week; tax‑free stipend to be determined. That's still includes TBD. Might be considered placeholder. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include the TBD phrase, that's filler. We could omit the TBD part and just say "Pay package based on 8‑hour shifts, 40 hours per week (subject to confirmation)". That still has "subject to confirmation" which is vague but not exactly TBD. Might be okay. However we must preserve ALL substantive information; we cannot invent or summarize away detail. The detail includes that tax-free stipend amount to be determined. If we omit that, we are summarizing away detail (the stipend TBD). But we could include it as is, but then we have TBD which is filler. The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include filler text within the section; it says never emit a heading followed by filler/placeholder text. That is, if the section only contains filler text, don't create it. If we have some substantive info plus filler, it's okay? The phrase "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")" suggests that if the content under that heading is just filler, don't create the heading. If we have some real info plus filler, it's ambiguous. Safer to include Pay section with the info we have, including the TBD note, as it's substantive that stipend TBD. But the TBD is filler. However the instruction says never emit a heading followed by filler/placeholder text. The heading would be followed by a paragraph that includes TBD. That's not purely filler; it's a sentence that includes TBD. I think it's acceptable.
Schedule: we have shift: 8 hours, 40 hours per week. That's schedule info. So we can create Schedule section.
Now Benefits: we have Weekly pay, 401k retirement plan, Life insurance. That's substantive.
Now About the role: we can include location, start date, duration, hours, shift, employment type, specialty, discipline maybe.
But we might duplicate some info across sections. We need to preserve all substantive information, not duplicate unnecessarily but it's okay if we repeat? Probably better to avoid duplication but not required. We'll try to organize.
Let's draft:
for sections: About the role, Responsibilities? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's parse the posting: - Travel Nurses, Inc. is seeking a travel Radiology Technologist for a travel job in Des Moines, Iowa. - Job Description & Requirements - Specialty: Radiology Technologist - Discipline: Allied Health Professional - Start Date: 10/19/2026 - Duration: 13 weeks - 40 hours per week - Shift: 8 hours - Employment Type: Travel - Travel Nurses, Inc. Job ID #353409. - 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. - Posted job title: Temp - Technologist - X-Ray (Afternoons) Des Moines, IA - About Travel Nurses, Inc. (company description) - Benefits: Weekly pay, 401k retirement plan, Life insurance We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So no heading for job title. We need to not put Job ID as heading; fold minor metadata into short
or drop it. We need to preserve all substantive information. We need to use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
- About the role: Could include description of role: travel Radiology Technologist, specialty, discipline, start date, duration, hours, shift, employment type, location. That seems appropriate.
- Responsibilities: Not explicitly listed. The posting does not list duties. So we should not create Responsibilities section if no specific content.
- Requirements: Could include specialty, discipline, maybe license? Not given. Only specialty and discipline. Might be considered requirements. But we need specific content. The posting includes "Specialty: Radiology Technologist" and "Discipline: Allied Health Professional". Those could be considered requirements. However we need to decide if we should create a Requirements section with those items. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Requirements if we have specifics. We have specialty and discipline. That's specific. Could also include start date, duration, hours, shift, employment type. Those could be considered job details, maybe under About the role. But we could also put them under Requirements? Usually requirements are qualifications needed. But we can treat them as role details.
Better to have About the role containing description: travel Radiology Technologist in Des Moines, Iowa, start date, duration, hours, shift, employment type.
Then Requirements could list specialty and discipline (maybe also that they need to be allied health professional). But that seems redundant.
Qualifications: Not given.
Skills: Not given.
Benefits: we have Weekly pay, 401k retirement plan, Life insurance. That's specific.
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." That's somewhat vague but includes info: based on 8 hour shifts, 40 hrs/week, tax-free stipend TBD. It's not a specific number but it's still content. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The pay section includes "tax-free stipend amount to be determined" which is TBD. That's placeholder. Also "subject to confirmation". This might be considered filler. However we still have some concrete: based on 8 hour shifts and 40 hours per week. That's not a filler. But the pay amount is not given. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. So there is some content, albeit vague. Should we include Pay section? Probably yes, but we need to avoid filler placeholder text. We could phrase: Pay package based on 8‑hour shifts, 40 hours per week; tax‑free stipend to be determined. That's still includes TBD. Might be considered placeholder. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include the TBD phrase, that's filler. We could omit the TBD part and just say "Pay package based on 8‑hour shifts, 40 hours per week (subject to confirmation)". That still has "subject to confirmation" which is vague but not exactly TBD. Might be okay. However we must preserve ALL substantive information; we cannot invent or summarize away detail. The detail includes that tax-free stipend amount to be determined. If we omit that, we are summarizing away detail (the stipend TBD). But we could include it as is, but then we have TBD which is filler. The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include filler text within the section; it says never emit a heading followed by filler/placeholder text. That is, if the section only contains filler text, don't create it. If we have some substantive info plus filler, it's okay? The phrase "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")" suggests that if the content under that heading is just filler, don't create the heading. If we have some real info plus filler, it's ambiguous. Safer to include Pay section with the info we have, including the TBD note, as it's substantive that stipend TBD. But the TBD is filler. However the instruction says never emit a heading followed by filler/placeholder text. The heading would be followed by a paragraph that includes TBD. That's not purely filler; it's a sentence that includes TBD. I think it's acceptable.
Schedule: we have shift: 8 hours, 40 hours per week. That's schedule info. So we can create Schedule section.
Now Benefits: we have Weekly pay, 401k retirement plan, Life insurance. That's substantive.
Now About the role: we can include location, start date, duration, hours, shift, employment type, specialty, discipline maybe.
But we might duplicate some info across sections. We need to preserve all substantive information, not duplicate unnecessarily but it's okay if we repeat? Probably better to avoid duplication but not required. We'll try to organize.
Let's draft:
About the role
Travel Nurses, Inc. seeks a travel Radiology Technologist for a 13‑week assignment in Des Moines, Iowa. The position starts 10/19/2026, requires 40 hours per week on 8‑hour shifts, and is a travel employment type.
That covers start date, duration, hours, shift, employment type, location. Now Responsibilities: none. Requirements: we could list Specialty and Discipline.Requirements
- Specialty: Radiology Technologist
- Discipline: Allied Health Professional
Benefits
- Weekly pay
- 401k retirement plan
- Life insurance
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.
Schedule:Schedule
40 hours per week, 8‑hour shifts.
We should also maybe include the posted job title? Not as heading. Could include in About the role? The posted job title: Temp - Technologist - X-Ray (Afternoons) Des Moines, IA. That's substantive. We could add that. Add to About the role: The posted job title is Temp - Technologist - X-Ray (Afternoons) in Des Moines, IA. Now check for any other info: Company description about Travel Nurses, Inc. That's boilerplate? It's about the company, not the role. Could be considered "About the company" but not a required heading. We could include it under About the role? Probably not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not boilerplate per se, but it's not about the role. It might be considered extra but not prohibited. However we might keep it as part of About the role? Might be irrelevant. Safer to omit because it's not about the role. The instruction says preserve ALL substantive information; does company description count as substantive? It's about the agency, not the job. Might be considered substantive but not required headings. Could include as a paragraph under About the role? Might be okay. But we might decide to omit to keep focused. However the instruction says preserve ALL substantive information; we should not discard company description unless it's boilerplate. It's not explicitly listed as boilerplate to remove. So we should keep it. Where to put? Could be a separate section like "About the company" but not in allowed headings. The allowed headings list does not include About the company. So we cannot create a heading not in list. We could incorporate it into About the role as a brief note: "Travel Nurses, Inc. is a nurse‑founded and operated healthcare staffing agency..." That would be okay. Thus About the role will include both role details and company description. Now check for duplication: we have start date, duration, etc. Also we have shift and hours in Schedule section. That's okay. Now ensure we don't have any empty sections. Now output only HTML fragment. Let's craft final HTML:About the role
Travel Nurses, Inc. is seeking a travel Radiology Technologist for a travel job in Des Moines, Iowa. The posted job title is Temp - Technologist - X-Ray (Afternoons). The assignment starts 10/19/2026, lasts 13 weeks, requires 40 hours per week on 8‑hour shifts, and is a travel employment type. Travel Nurses, Inc. is a nurse‑founded and operated healthcare staffing agency connecting nurses and allied health professionals with opportunities nationwide. Since 1988, we’ve grown from supporting operating room teams in the Mid‑South to serving a wide range of specialties across the country. At our core, we believe healthcare professionals are the foundation of care. That belief drives everything we do, from how we support our clinicians to how we build long‑term relationships. We are committed to making travel simple, transparent and rewarding. With clear pay packages, dedicated recruiter support and a focus on career mobility, our clinicians can move forward with confidence. Wherever your career takes you, you’ll never go alone.
Requirements
- Specialty: Radiology Technologist
- Discipline: Allied Health Professional
Benefits
- Weekly pay
- 401k retirement plan
- Life insurance