Travel Nuclear Medicine Technologist - $2,081 per week
for each section heading. Only include sections with real specific content.
We have: About the role: we can summarize the role description: Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Tucson, Arizona. That's about the role.
Responsibilities: Not explicitly listed. The posting doesn't list duties. So we should not create Responsibilities section.
Requirements: They list Specialty: Nuclear Medicine Technologist, Discipline: Allied Health Professional, Start Date: 11/02/2026, Duration: 13 weeks, 40 hours per week, Shift: 12 hours, days, Employment Type: Travel. Those could be considered requirements. We can put them in Requirements section.
Qualifications: Not given separately; maybe same as requirements. But we could combine. Better to have Requirements include those details.
Skills: Not listed.
Benefits: They list many benefits. So Benefits section.
Pay: They mention pay package based on 12 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's vague; not a specific amount. According to rule: never create Pay section unless posting actually states them. It does state something about pay package but not specific amount. It says "Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a concrete figure; it's still vague. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "tax-free stipend amount to be determined" which is TBD. So we should not create Pay section.
Schedule: They gave shift and hours. That's specific. So Schedule section.
We also need to include minor metadata like Job ID folded into short p or dropped. We'll include a short p at top maybe.
We must not include boilerplate like EEO etc. The posting includes a lot about Host Healthcare description and benefits. That's okay.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details: location Tucson, Arizona; start date; duration; hours per week; shift; employment type; benefits list; Host Healthcare description; etc.
We need to format as HTML fragment: use for section headings, - for lists,
for prose.
We must not repeat job title as heading. The job title is Nuclear Medicine Technologist; we should not use that as heading.
We'll start with a
containing location and maybe job ID? 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 p: "Host Healthcare Job ID #a1fVX0000046FrnYAE." Also location: Tucson, Arizona.
We'll then have About the role section:
About the role
Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Tucson, Arizona.
Then Requirements section: Requirements
- Specialty: Nuclear Medicine Technologist
- Discipline: Allied Health Professional
- Start Date: November 2, 2026
- Duration: 13 weeks
- 40 hours per week
- Shift: 12 hours, days
- Employment Type: Travel
We could also include the start date format as given: 11/02/2026. Keep as is.
Then Benefits section: Benefits
- Referral bonus
- School loan reimbursement
- Vision benefits
- Wellness and fitness programs
- Company provided housing options
- License and certification reimbursement
- Life insurance
- Medical benefits
- Mileage reimbursement
- Pet insurance
- Discount program
- Employee assistance programs
- Guaranteed Hours
- Health savings account
- Holiday Pay
- 401k retirement plan
- Continuing Education
- Dental benefits
We also have Host Healthcare description paragraphs: At Host Healthcare, we provide a truly comfortable experience... etc. That's substantive; we should include that as prose maybe under About the role or a separate section? There's no specific heading for company overview. Could be part of About the role or we could add a section like "About Host Healthcare". But the allowed headings list does not include that; we could still use About Host Healthcare
but not in the list. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we could add others? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect only those headings. Better to stick to those. So we can incorporate the Host Healthcare description into About the role paragraph or maybe a separate
after About the role.
We'll put About the role paragraph includes both the seeking line and the Host Healthcare description.
Thus:
About the role
Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Tucson, Arizona. At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare.
But note that the benefits description duplicates some of the benefits list; we should not duplicate content? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that description as is, even if it mentions some benefits. Then we also have a Benefits section list. That's okay; it's not duplicate but overlapping. It's fine.
We also need to include the Pay package line? We decided not to create Pay section. Should we include that info somewhere? It's minor metadata about pay package; we could fold into a short p maybe under About the role or Requirements. The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. Pay package info is not Job ID; it's substantive? It says "Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague but still info. We could include it in a short p under Requirements or About the role. Since it's about pay, but we are not making a Pay section. We'll include a short p: "Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined."
We also need Schedule section: we have shift and hours already in Requirements; but we could also move schedule details to Schedule section and remove from Requirements to avoid duplication. However the rule: Prefer a few substantive sections over many thin ones. We have Requirements already with many items; we could keep schedule there. But we also need a Schedule section if we want to include it. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state shift and hours, so we can create Schedule section. But we already have schedule info in Requirements; we could move it to Schedule and keep Requirements without schedule. Let's decide: We'll create Schedule section with the shift/hours info. Then Requirements will exclude schedule.
Thus Requirements: Specialty, Discipline, Start Date, Duration, Employment Type.
Schedule: 12 hour shifts, days, 40 hours per week.
We'll also keep the pay package line maybe in a short p under Requirements or separate? Could be under Requirements as well.
Let's structure:
Host Healthcare Job ID #a1fVX0000046FrnYAE.
About the role
Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Tucson, Arizona. At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare.
Requirements
- Specialty: Nuclear Medicine Technologist
- Discipline: Allied Health Professional
- Start Date: 11/02/
- for lists,
for prose. We must not repeat job title as heading. The job title is Nuclear Medicine Technologist; we should not use that as heading. We'll start with a
containing location and maybe job ID? 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 p: "Host Healthcare Job ID #a1fVX0000046FrnYAE." Also location: Tucson, Arizona. We'll then have About the role section:
About the role
Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Tucson, Arizona.
Then Requirements section:Requirements
- Specialty: Nuclear Medicine Technologist
- Discipline: Allied Health Professional
- Start Date: November 2, 2026
- Duration: 13 weeks
- 40 hours per week
- Shift: 12 hours, days
- Employment Type: Travel
Benefits
- Referral bonus
- School loan reimbursement
- Vision benefits
- Wellness and fitness programs
- Company provided housing options
- License and certification reimbursement
- Life insurance
- Medical benefits
- Mileage reimbursement
- Pet insurance
- Discount program
- Employee assistance programs
- Guaranteed Hours
- Health savings account
- Holiday Pay
- 401k retirement plan
- Continuing Education
- Dental benefits
About Host Healthcare
but not in the list. The instruction: usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we could add others? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect only those headings. Better to stick to those. So we can incorporate the Host Healthcare description into About the role paragraph or maybe a separate
after About the role. We'll put About the role paragraph includes both the seeking line and the Host Healthcare description. Thus:
About the role
Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Tucson, Arizona. At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare.
But note that the benefits description duplicates some of the benefits list; we should not duplicate content? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that description as is, even if it mentions some benefits. Then we also have a Benefits section list. That's okay; it's not duplicate but overlapping. It's fine. We also need to include the Pay package line? We decided not to create Pay section. Should we include that info somewhere? It's minor metadata about pay package; we could fold into a short p maybe under About the role or Requirements. The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. Pay package info is not Job ID; it's substantive? It says "Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague but still info. We could include it in a short p under Requirements or About the role. Since it's about pay, but we are not making a Pay section. We'll include a short p: "Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." We also need Schedule section: we have shift and hours already in Requirements; but we could also move schedule details to Schedule section and remove from Requirements to avoid duplication. However the rule: Prefer a few substantive sections over many thin ones. We have Requirements already with many items; we could keep schedule there. But we also need a Schedule section if we want to include it. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state shift and hours, so we can create Schedule section. But we already have schedule info in Requirements; we could move it to Schedule and keep Requirements without schedule. Let's decide: We'll create Schedule section with the shift/hours info. Then Requirements will exclude schedule. Thus Requirements: Specialty, Discipline, Start Date, Duration, Employment Type. Schedule: 12 hour shifts, days, 40 hours per week. We'll also keep the pay package line maybe in a short p under Requirements or separate? Could be under Requirements as well. Let's structure:
Host Healthcare Job ID #a1fVX0000046FrnYAE.
About the role
Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Tucson, Arizona. At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare.
Requirements
- Specialty: Nuclear Medicine Technologist
- Discipline: Allied Health Professional
- Start Date: 11/02/