Travel Nuclear Medicine Technologist - $2,846 per week
About the role
with paragraphs containing that info. - Responsibilities: Not explicitly listed. The posting does not list responsibilities. So we should not create a Responsibilities section. - Requirements: Not explicitly listed. There's no bullet list of requirements. So skip. - Qualifications: Not listed. Skip. - Skills: Not listed. Skip. - Benefits: Yes, there is a Benefits section with list. So we needBenefits
with- each benefit.
- Pay: The posting mentions "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague but it's specific: says pay package based on 8 hour shifts and 40 hrs/week, tax-free stipend amount to be determined. It's not a specific number, but it's still content. The rule: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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 placeholder. Also "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation)". That's somewhat vague but still says it's based on those. Is that considered filler? It's not a specific amount, but it's still some info. The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "tax-free stipend amount to be determined" is similar to TBD. So maybe we should not include Pay section because it's not specific. However we could include a short paragraph stating that pay package is based on 8 hour shifts and 40 hrs/week with tax-free stipend TBD. But that includes TBD. The rule says never emit a heading followed by filler/placeholder text. If we include Pay section with that text, it's filler. So better to omit Pay section.
- Schedule: The posting includes "40 hours per week", "Shift: 8 hours, days". That's schedule info. So we can include Schedule section with that info.
Thus sections: About the role, Benefits, Schedule.
We need to use
for section headings. Use
- for any list of duties/requirements/benefits. Benefits is a list, so use ul/li.
For About the role and Schedule, we can use
for prose. We must not include any boilerplate like EEO etc. Already removed. We need to preserve all substantive information. Let's extract About the role content: - Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Minot, North Dakota. - Specialty: Nuclear Medicine Technologist - Discipline: Allied Health Professional - Start Date: 11/02/2026 - Duration: 13 weeks - 40 hours per week - Shift: 8 hours, days - Employment Type: Travel - Location: Minot, North Dakota (already mentioned) - Job ID: a1fVX0000044PDdYAM (maybe we can include as minor metadata in a short p or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include Job ID in a short p within About the role or maybe separate small p. Probably include as a short p. We should not repeat the job title as heading. Already not. We need to avoid duplication. The posting also includes "Posted job title: Nuclear Medicine Technologist - Nuclear Medicine Nuclear Med" which is redundant; we can ignore. Now Benefits list: we have many items. Let's list them exactly as given: - 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 need to output each as
- .
Schedule: we have "40 hours per week" and "Shift: 8 hours, days". Also maybe "Start Date" and "Duration" could be considered schedule? But they are more about timing. However we already used Start Date and Duration in About the role. Could also include them in Schedule but better to keep them in About the role. The Schedule section should contain shift and hours.
Thus Schedule:
40 hours per week, 8‑hour day shifts.
Now we need to output only HTML fragment, no /, no markdown. Thus:About the role
Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Minot, North Dakota. Specialty: Nuclear Medicine Technologist. Discipline: Allied Health Professional. Start Date: 11/02/2026. Duration: 13 weeks. Employment Type: Travel. Job ID: a1fVX0000044PDdYAM.
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
Schedule
40 hours per week, 8‑hour day shifts.
Check if any other sections like Pay? We omitted. Check if any duplication: we included Job ID in About the role. That's okay. Check if any content missing: we didn't include the description about Host Healthcare mission etc. That's more about the company, not the role. Could be considered "About the role"? The instruction: "About the role" section heading for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "About Host Healthcare" paragraph is more about the company, not the role. Should we include it? Possibly not, as it's not about the role. The rule: "Prefer a few substantive sections over many thin ones." The About Host Healthcare is substantive but not about the role. However the instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but the list is examples. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. The About Host Healthcare content could be considered part of About the role? Might be okay to include as part of About the role, but it's more about the company. However we could incorporate a brief sentence about Host Healthcare's support. But we already have a paragraph about the role; we could add a sentence: "Host Healthcare provides a comfortable travel experience with Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, etc." But those are benefits already listed. Might be duplication. Better to keep About the role focused on the job specifics. The Host Healthcare description is more about the company; but we could still include it as part of About the role if we want to preserve all substantive information. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the Host Healthcare description somewhere. Where? Could be a separate section like "About the company" but not in allowed headings. However we could put it in About the role as extra prose. That would preserve it. Thus we can add after the job details a sentence: "Host Healthcare provides a comfortable travel experience, offering Day 1 medical coverage up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, and access to on‑staff clinicians." That's from the text. We need to ensure we don't repeat benefits list; but it's okay to mention some. Let's craft About the role paragraph: "Host Healthcare is seeking a travel Nuclear Medicine Technologist for a travel job in Minot, North Dakota. Specialty: Nuclear Medicine Technologist. Discipline: Allied Health Professional. Start Date: 11/02/2026. Duration: 13 weeks. Employment Type: Travel. Job ID: a1fVX0000044PDdYAM. Host Healthcare provides a
- for any list of duties/requirements/benefits. Benefits is a list, so use ul/li.
For About the role and Schedule, we can use