Travel Radiology Technologist - $2,536 per week

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Content: - Uniti Med is seeking a travel Radiology Technologist for a travel job in Minot, North Dakota. - Job Description & Requirements - Specialty: Radiology Technologist - Discipline: Allied Health Professional - Start Date: 10/05/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours - Employment Type: Travel - Benefits: 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 that will help you every step of the way to sure you start on time and have an exceptional experience Referral bonus up to $700 - About the Company: ... (some prose) - Uniti Med Job ID #860224. 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. - About Uniti Med (some prose) - Benefits (list again): Referral bonus, Benefits start day 1, Employee assistance programs We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive info. We need to format sections: maybe "About the role" (job description), "Responsibilities" (maybe not present), "Requirements" (maybe not present), "Qualifications" (maybe not present), "Skills" (maybe not present), "Benefits", "Pay", "Schedule". We need to include only sections with real specific content. We have details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. Those could go under "About the role" or maybe "Job Details". But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put the job details under "About the role". Provide prose or list? The instruction: Use

• for any list of duties/requirements/benefits, and

  for prose. So for list items we use ul/li. For prose we use p. We have list of benefits: 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 that will help you every step of the way to sure you start on time and have an exceptional experience; Referral bonus up to $700. Also later: Referral bonus, Benefits start day 1, Employee assistance programs. We need to combine and avoid duplication. We should preserve all substantive info, not invent. So we need to list each benefit exactly as mentioned, but we can combine duplicates. Let's extract benefits list: From first benefits paragraph: - 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 that will help you every step of the way to sure you start on time and have an exceptional experience - Referral bonus up to $700 Later "Benefits" list: - Referral bonus - Benefits start day 1 - Employee assistance programs Note "Benefits start day 1" maybe same as Day 1 Insurance? Actually "Benefits start day 1" is a generic statement; but we already have Day 1 Insurance. Could be separate: benefits start day 1 (maybe meaning all benefits start day 1). We'll keep as separate item. "Employee assistance programs" is new. We need to avoid filler like "commensurate with experience". Not present. 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." This is vague; we have specifics: based on 12 hour shifts and 36 hours per week. Tax-free stipend amount to be determined (not specific). According to rule: do NOT create Pay section unless posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week, but stipend amount TBD. Is that enough? 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 some info about pay structure but not actual pay rate. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The stipend amount TBD is placeholder. However the heading Pay would have content that includes TBD. Might be considered filler? The rule says never emit a heading followed by filler/placeholder text. If we include Pay section, we would have to include the statement which includes TBD. That might be considered filler. Safer to omit Pay section because the actual pay amount is not specified. However we could include the info about shift/hours as part of Schedule maybe. But Schedule section is for schedule details. We have shift: 12 hours, 36 hours per week. That's schedule info. So we can put Schedule section with those details. Thus we will have: - About the role: includes Specialty, Discipline, Start Date, Duration, Employment Type (Travel). Could be a list. - Responsibilities: not present, skip. - Requirements: not present, skip. - Qualifications: not present, skip. - Skills: not present, skip. - Benefits: list as above. - Schedule: Shift: 12 hours, 36 hours per week. - Pay: maybe omit because stipend TBD. We also have location: Minot, North Dakota. Could be part of About the role. We also have "About the Company" and "About Uniti Med" prose. Those could be placed under About the role? Or maybe we could create a section "About the Company". But allowed headings list does not include About the Company. Only those headings. So we must fit that prose into allowed sections. Perhaps we can put it under About the role as prose. Thus About the role will contain prose about the role, company, etc. We need to not repeat job title as heading. We need to output only HTML fragment. Let's craft:

  About the role

  Uniti Med is seeking a travel Radiology Technologist for a travel job in Minot, North Dakota. Specialty: Radiology Technologist; Discipline: Allied Health Professional; Start Date: 10/05/2026; Duration: 13 weeks; Employment Type: Travel.

  Maybe better to use list for details? The rule: Use
  • for any list of duties/requirements/benefits. This is not a list of duties/requirements/benefits, it's details. Could be prose. We could also make a list:
    • Specialty: Radiology Technologist
    ...
    . That is a list of details; but rule says for any list of duties/requirements/benefits. This is not exactly those categories, but it's still a list. Safer to use

    for prose. Now Benefits section:

    Benefits

    • 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 that will help you every step of the way to ensure you start on time and have an exceptional experience
    • Referral bonus up to $700
    • Benefits start day 1
    • Employee assistance programs
    Note: I corrected typo "to sure you start" to "to ensure you start". Should we keep original wording? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Changing wording could be considered altering. Better to keep original: "A dedicated recruiter and support team that will help you every step of the way to sure you start on time and have an exceptional experience". That's grammatically odd but it's what's there. We must preserve exactly. So keep that phrase. Thus:
  • A dedicated recruiter and support team that will help you every step of the way to sure you start on time and have an exceptional experience
  Now Schedule section:

  Schedule

  Shift: 12 hours; 36 hours per week.

  We could also list:
  • Shift: 12 hours
  • 36 hours per week
  . But it's not a list of duties/requirements/benefits; it's schedule details. Use

  . Now we need to ensure we didn't include Pay section. Check for any other substantive content: "About the Company" and "About Uniti Med" prose. We haven't included them. Should we include them somewhere? The rule: Preserve ALL substantive information. If we omit that prose, we lose substantive info. We need to include it somewhere. Since we cannot create new headings outside allowed list, we must incorporate it into an existing heading, like About the role. So we can add that prose to About the role section. Thus About the role will include the job details plus the company description. Let's extract the company description: "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." Then later: "About Uniti MedUniti 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!" We need to preserve that exactly, but we can combine into prose. We must be careful not to lose any punctuation. Let's combine: About the role section will have a

  containing: "Uniti Med is seeking a travel Radiology Technologist for a travel job in Minot, North Dakota. Specialty: Radiology Technologist; Discipline: Allied Health Professional; Start Date: 10/05/2026; Duration: 13 weeks; Employment Type: Travel. 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.About Uniti MedUniti 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!" But that's a huge run-on. Maybe better to separate sentences with spaces. We'll keep as is. We need to ensure we didn't miss any other substantive info: "BenefitsReferral bonusBenefits start day 1Employee assistance programs" appears as a line without spaces. We already captured those as separate list items. Now check for any other info: "Job ID #860224." That's minor metadata;