Travel MRI Technologist - $3,000 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 that have real specific content. We must not repeat job title. Remove boilerplate, navigation, etc. Must preserve all substantive info. Let's parse the posting: - Sunbelt Staffing seeking travel MRI Technologist for travel job in Minneapolis, Minnesota. - Job Description & Requirements - Specialty: MRI Technologist - Discipline: Allied Health Professional - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, nights - Employment Type: Travel - Minneapolis, MN – Night Shift MRI Tech Opportunity - Quick Glance: Schedule: Thurs–Sun | 8:30 PM – 7:00 AM | 40 hrs/week - Shift: Nights - Scope: MRI imaging with a focus on Philips systems in a collaborative, fast-paced setting - Environment: Team-based workflow alongside another technologist - Scope of Responsibilities: list of duties (bulleted) - Must-Have Credentials: list - Preferred Qualifications: list - Why Sunbelt: bullet points about recruiter, pay+benefit suite, contract flexibility - About Sunbelt Staffing: paragraph about mission etc. - Benefits: Medical benefits Dental benefits Vision benefits (list) Also there is "Robust pay + benefit suite — nationwide medical, dental, vision, and 401(k) options travel with you". So pay info: not specific numbers, but mention robust pay + benefit suite. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention pay: "Robust pay + benefit suite". That's vague but still states pay exists. However we should avoid filler like "commensurate with experience". "Robust pay + benefit suite" is not a specific number but indicates pay is provided. Should we include Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Robust pay + benefit suite". That's a statement about pay and benefits. So we could include a Benefits section (we have benefits list). Pay section maybe we could include but we have no specific pay amount. Might be considered filler? The rule says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Robust pay + benefit suite" is not exactly filler but it's vague. Might be considered placeholder? It's not a specific number but it's a statement that pay is robust. Could be considered non-specific. Safer to omit Pay section because we don't have specific pay. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine pay info into Benefits or About? Probably better to include Benefits section (we have specific benefits). Pay we could mention in Benefits? Not needed. Schedule: we have schedule details: Thurs–Sun | 8:30 PM – 7:00 AM | 40 hrs/week. Also shift: nights, 10 hours. So we can create Schedule section. We need sections: About the role (maybe a brief description), Responsibilities, Requirements (maybe Must-Have Credentials), Qualifications (Preferred Qualifications), Skills (maybe from Preferred Qualifications like communication, teamwork, fast-paced), Benefits, Schedule. Also maybe "About Sunbelt Staffing" could be About the role? The instruction: About the role heading for section like About the role, Responsibilities, etc. So we can put the description of the role (specialty, discipline, duration, etc.) under About the role. We must not repeat job title. So no heading for "MRI Technologist". Use

for each section. We need to use

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

  for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to include all details: location Minneapolis, MN; duration 13 weeks; 40 hours per week; shift 10 hours nights; employment type travel; schedule Thurs-Sun 8:30PM-7:00AM; scope MRI imaging with focus on Philips systems; environment team-based workflow alongside another technologist; responsibilities list; must-have credentials: ARRT (MR) certification, BLS (AHA) certification, minimum 2 years recent MRI experience, no licensure restrictions; preferred qualifications: experience with Philips MRI scanners, ability to thrive in fast-paced high-volume environment, strong communication and teamwork skills; Why Sunbelt: dedicated recruiter & 24-7 support, robust pay + benefit suite (nationwide medical, dental, vision, 401(k) options travel with you), contract flexibility; About Sunbelt Staffing paragraph; Benefits: medical, dental, vision. We should not include boilerplate like EEO etc. There's none. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  Sunbelt Staffing is seeking a travel MRI Technologist for a 13‑week assignment in Minneapolis, Minnesota. The position is for an Allied Health Professional working 40 hours per week on night shifts (10‑hour shifts) as a travel employee.

  Maybe also include schedule details? But schedule separate. Better to put schedule in its own section.

  Schedule

  Shift: Thurs–Sun, 8:30 PM – 7:00 AM (40 hours/week).

  But also mention 10‑hour nights. Could combine.

  Responsibilities

  • Perform high-quality MRI scans in accordance with physician orders and established protocols
  • Operate primarily Philips MRI equipment to produce accurate diagnostic images
  • Ensure patient safety, comfort, and proper positioning throughout procedures
  • Collaborate with fellow technologists and clinical staff to maintain workflow efficiency
  • Monitor patients during scans and respond appropriately to any adverse reactions
  • Maintain imaging equipment and report any malfunctions or issues
  • Adhere to all safety standards, including MRI safety and infection control protocols

  Requirements

  • ARRT (MR) certification
  • BLS (AHA) certification
  • Minimum 2 years of recent MRI experience
  • No licensure restrictions

  Preferred Qualifications

  • Experience working with Philips MRI scanners
  • Ability to thrive in a fast‑paced, high‑volume environment
  • Strong communication and teamwork skills
  Maybe we could split Skills separate but we can include these under Preferred Qualifications. The instruction: use headings for Skills if we have content. We could create Skills section from those items. But we already have Preferred Qualifications. Could also have Skills section listing communication, teamwork, fast-paced. However to avoid thin sections, we could combine Preferred Qualifications and Skills into one? But we need to follow headings: we can have Preferred Qualifications and Skills separate if we have content. The Preferred Qualifications list includes experience with Philips, ability to thrive, strong communication and teamwork. Those could be split: Experience with Philips as qualification, communication/teamwork as skills, fast-paced as ability. But we can keep as Preferred Qualifications and maybe Skills separate for communication and teamwork. However we risk thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to have just Preferred Qualifications covering all three, and not create a separate Skills section. That's fine. Now Benefits:

  Benefits

  • Medical benefits
  • Dental benefits
  • Vision benefits
  • 401(k) options (nationwide, travel with you)
  But the posting also mentions "Robust pay + benefit suite — nationwide medical, dental, vision, and 401(k) options travel with you". So we can include 401(k) as part of benefits. We also have "Dedicated Recruiter & 24-7 support — one contact backed by round-the-clock help" and "Contract flexibility built around you — choose assignments that fit your life and move your career forward". Those could be under a section like "Why Sunbelt" but we don't have a heading for that in the list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Why Sunbelt". So we need to incorporate that info somewhere else, maybe under About the role or Benefits? The instruction: "Prefer a few substantive sections over many thin ones." We could add a section like "About Sunbelt Staffing" but not in allowed headings. However the instruction says: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections, but maybe we can also use other headings if needed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they want us to use those headings for sections, but not strictly limited to those. However they also say: "IMPORTANT: 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 create sections for any meaningful content, using

  . The examples are just typical headings. So we could add a section like "Why Sunbelt" or "About Sunbelt Staffing". But to be safe, we could incorporate that info into About the role or Benefits. However the "Why Sunbelt" content is substantive: dedicated recruiter, 24-7 support, contract flexibility. It's not covered elsewhere. We could add a section "Why Sunbelt" with

  . That seems reasonable. Similarly "About Sunbelt Staffing" paragraph is also substantive. Could be "About Sunbelt Staffing". But we already have About the role. Might be redundant. Could combine. Better to have sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Benefits, Schedule, Why Sunbelt, About Sunbelt Staffing. That's many sections but each substantive. But the instruction: "Prefer a few substantive sections over many thin ones." So we should try to combine where possible. We could combine "Why Sunbelt" and "About Sunbelt Staffing" into a section "About Sunbelt". Or we could put the recruiter/support info under Benefits? Not really. Maybe we create a section "About Sunbelt Staffing" that includes both the descriptive paragraph and the recruiter/support/contract flexibility points. That would be substantive. Thus sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Benefits, Schedule, About Sunbelt Staffing. We need to ensure we don't miss any info: location, duration, 40h/week, shift 10hr nights, employment type travel, schedule Thurs-Sun 8:30PM-7:00AM, scope Philips, environment team-based, responsibilities list, must-have credentials, preferred qualifications, benefits (medical, dental, vision, 401k), recruiter