Travel MRI Tech - $2,283 per week

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key details: - Job: travel MRI Technologist in Wilmington, NC. - Specialty: MRI Technologist - Discipline: Allied Health Professional - Start Date: 10/12/2026 - Duration: 13 weeks (also says 13.14 weeks) - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Summary: assignment lasts 13.14 weeks, start Oct 12 2026. - Job Details: Shift: 12H Nights, Total Weekly Hours: 36 - Certifications: BLS, ARRT MR - Trauma Level: Facility Specific - Required Skills / Certifications / Experience: - Minimum Years of Experience: 2 Years - Traveler Experience: Unit WILL NOT Accept 1st Time Travelers - Skills: abdomen, pelvis, head and neck, spine, musculoskeletal, diffusion (non-brain), gradient echo imaging, MIP, MRP, peripheral magnetic resonance, spin echo images, surface coils, T1 and T2, CINE - Certifications: BLS, ARRT - Preferred Skills / Certifications / Experience: - Skills: chest, image post-processing - Special Skills / Equipment: - GE, Siemens - Patient Diagnoses Familiarity: - Preferred: neonates, infants, peds - Required: adolescent, adults, geriatrics - Charting System: EPIC - Other Details: - Recent hospital experience required - ARRT-MR certification required - Benefits: Insurance Plans starting under $175/month for employees, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors. - Also later Benefits list: Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. - Pay: "Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems for eligible clinicians based on nationally published GSA rates. Actual weekly pay and per diems may differ... 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." So we have some pay info but not exact numbers. The rule: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (list). It does mention weekly pay but not a specific amount. It says "Estimated weekly pay includes projected hourly wages..." but no number. Should we include Pay section? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state "Estimated weekly pay includes projected hourly wages..." but not a specific number. That could be considered placeholder? It's not a specific number, but it's stating that pay is based on something. Might be considered not specific enough. Safer to omit Pay section because no concrete figure. However we could include a short paragraph about pay being based on 12 hour shifts etc. But that might be considered filler. I'd omit Pay. Schedule: we have shift details: 12 hour nights, 36 hours per week. That's specific. So we can include a Schedule section with that info. Benefits: we have specific benefits list. So include Benefits section. About the role: we could include a summary paragraph about the assignment. That's substantive. Responsibilities: not explicitly listed; we have skills and duties but not explicit responsibilities. Could we treat skills as responsibilities? Probably not. Better to omit Responsibilities if not explicit. Requirements: we have required experience, certifications, etc. Could be Requirements section. Qualifications: similar to Requirements; maybe combine. But we need to decide which sections to include. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Requirements, Skills, Benefits, Schedule. Possibly Qualifications not needed if covered. We must not repeat job title as heading. So no heading for "MRI Technologist". Use headings for sections. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate etc. Let's extract substantive content: - Location: Wilmington, North Carolina (maybe include in About the role paragraph) - Start Date: October 12, 2026 - Duration: 13 weeks (or 13.14 weeks) - Hours per week: 36 - Shift: 12 hours, nights - Employment Type: Travel - Required: Minimum 2 years experience, no first-time travelers, ARRT-MR certification, BLS, recent hospital experience. - Required Skills: abdomen, pelvis, head and neck, spine, musculoskeletal, diffusion (non-brain), gradient echo imaging, MIP, MRP, peripheral magnetic resonance, spin echo images, surface coils, T1 and T2, CINE. - Preferred Skills: chest, image post-processing. - Special Skills/Equipment: GE, Siemens. - Patient Diagnoses Familiarity: Required: adolescent, adults, geriatrics; Preferred: neonates, infants, peds. - Charting System: EPIC. - Benefits: Insurance Plans starting under $175/month, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors. Also later: Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. We need to combine without duplication. Let's list unique benefits: - Insurance plans starting under $175/month for employees - Referral bonus - Additional contract bonus opportunities - Vacation incentives - Employee Assistance Program (EAP) - 401k with access to financial advisors - Weekly pay (mentioned) - Medical benefits - Dental benefits - Vision benefits - Mileage reimbursement We should keep all. - Pay: Not specific; we may omit. - Schedule: Shift: 12 hours nights, 36 hours per week. Now craft HTML. We'll have sections:

  About the role

  Travel MRI Technologist position in Wilmington, North Carolina. Assignment starts October 12, 2026, lasting approximately 13 weeks (13.14 weeks) with 36 hours per week on 12‑hour night shifts. Employment type is travel.

  Requirements

  • Minimum 2 years of MRI technologist experience
  • Unit does not accept first‑time travelers
  • ARRT‑MR certification required
  • BLS (Basic Life Support) certification required
  • Recent hospital experience required

  Skills

  Required skills include imaging of abdomen, pelvis, head and neck, spine, musculoskeletal, diffusion (non‑brain), gradient echo imaging, MIP, MRP, peripheral magnetic resonance, spin echo images, surface coils, T1 and T2 weighting, and CINE.

  Preferred skills: chest imaging and image post‑processing.

  Special equipment experience: GE and Siemens scanners.

  Patient diagnosis familiarity: required for adolescent, adult, and geriatric patients; preferred for neonates, infants, and pediatric patients.

  Charting system: EPIC.

  We could also put skills as list but it's long; but rule: use
  • for any list of duties/requirements/benefits. Skills is a list; we could break into
    . However we have required skills list and preferred skills list. Could do two lists. Better to use
    for required skills and another for preferred skills. Let's do:

    Skills

    Required

    • Abdomen
    • Pelvis
    • Head and neck
    • Spine
    • Musculoskeletal
    • Diffusion (non‑brain)
    • Gradient echo imaging
    • MIP
    • MRP
    • Peripheral magnetic resonance
    • Spin echo images
    • Surface coils
    • T1 and T2 weighting
    • CINE

    Preferred

    • Chest imaging
    • Image post‑processing
    But we must only use

    for section headings, not

    . The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could avoid

    . We could embed the required/preferred within

    or

    with a preceding sentence. Use

    to introduce then

    . That's fine. Thus:

    Skills

    Required skills:

    ...

    Preferred skills:

    ...
    Similarly for Patient Diagnoses Familiarity and Charting System maybe under Skills or separate section? Could be part of Skills or a separate section like "Qualifications". But we already have Skills; we could add another section "Qualifications" for certifications and experience. However we already have Requirements for experience/certs. Could combine. We have Benefits section. We have Schedule section. Let's structure:

    About the role

    ...

    Requirements

    ...

    Skills

    Required skills:

    ...

    Preferred skills:

    ...

    Patient diagnosis familiarity: required for adolescent, adult, and geriatric patients; preferred for neonates, infants, and pediatric patients.

    Charting system: EPIC.

    Benefits

    ...

    Schedule

    12‑hour night shifts, 36 hours per week.

    We need to ensure we don't repeat job title as heading. Good. Now check for any boilerplate removed: we removed EEO, call to action, application instructions, etc. Check for any placeholder text: we have no "commensurate with experience" etc. Now ensure we preserve all substantive information: Did we miss any? - Start date: included in About the role. - Duration: included. - Hours per week: included in About the role and Schedule. - Shift: included. - Employment type: included. - Required experience: 2 years, no first-time travelers: in Requirements. - Certifications: ARRT-MR, BLS: in Requirements. - Recent hospital experience: in Requirements. - Skills: we listed required and preferred. - Special Skills/Equipment: GE, Siemens: we included under Skills as special equipment experience. - Patient Diagnoses Familiarity: included. - Charting System: EPIC: included. - Benefits: we listed many. - Pay: we omitted as not specific. - Additional details