Travel MRI Technologist - $3,077 per week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- 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")
- Never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no /, no markdown code fences
Now, parse the content:
Job title: "ALOIS Healthcare is seeking a travel MRI Technologist for a travel job in Wausau, Wisconsin." - This is the title, but we shouldn't repeat as heading.
Job Description & Requirements section:
- Specialty: MRI Technologist
- Discipline: Allied Health Professional
- Start Date: 11/09/2026
- Duration: 13 weeks
- 40 hours per week
- Shift: 8 hours, flexible
- Employment Type: Travel
Then a paragraph describing MRI technologists role.
Then "ALOIS Healthcare Job ID #19381897. Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: MRI Tech Acute"
About ALOIS Healthcare section:
- Why ALOIS Healthcare? paragraph
- "We offer:" with bullet points:
- Industry-leading pay
- Generous cost of living and housing stipends
- Opportunities for referral, sign-on, and extension bonuses
- Weekly health insurance or health insurance Marketplace weekly bonus
- Continuing education credits
- Then values list:
- Everyone Matters
- We are Performance Driven
- We are Open, Honest and Direct
- We are Transparent
- We are Inclusive
- We Do the Right Thing
- Final paragraph: "We care about you - and your success is our success."
Now, decide sections:
1. About the role (or Job Description) - include the description paragraph and maybe the metadata (specialty, discipline, etc.) as a list? The metadata is specific: start date, duration, hours, shift, employment type. Could be a "Requirements" or "Details" section. The rules suggest headings like "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include if real content.
We have:
- Job details (start date, duration, hours, shift, employment type) - could be "Schedule" or "Details". The rules mention "Schedule" as a possible heading. Since shift and hours are given, we can create a Schedule section.
- Requirements? The posting doesn't list specific requirements like certifications, experience, etc. Only the specialty and discipline. Might not be enough for a Requirements section.
- Benefits: The "We offer" list is clearly benefits. So Benefits section.
- Pay: The posting says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague, but it does mention pay package and tax-free stipend. However, the rule says never create Pay section unless the posting actually states them. It does state something about pay, but it's not specific (amount to be determined). The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Amount to be determined" is similar to TBD. So maybe we should not create a Pay section. But we could include the pay info in a short paragraph under About the role or Schedule? The rule says fold minor metadata into a short
or drop it. Job ID is minor metadata. Pay info might be considered substantive? But it's vague. I think we can include a short paragraph about pay in the About the role section or a separate "Pay" section? The rule says never create Pay section unless the posting actually states them. It does state something, but it's not concrete. I'd lean to not create a Pay section, but include the pay info in a paragraph.
- About ALOIS Healthcare: This is company description and values. Could be "About the Company" or "Why ALOIS Healthcare". The rules don't have a specific heading for company description, but we can use "About the Company" or "About ALOIS Healthcare". The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer those. However, "About the Company" is not listed, but we can use a relevant heading. The example includes "About the role". Could use "About ALOIS Healthcare". I think it's fine.
Now, structure:
- About the role: include the description paragraph and maybe the job details as a list? Or separate Schedule section for hours/shift.
Let's create sections:
1. About the role: includes the MRI technologist description paragraph.
2. Schedule: includes shift, hours per week, duration, start date, employment type. Could be a list.
3. Benefits: includes the "We offer" bullet points.
4. About ALOIS Healthcare: includes the why paragraph and values list.
But the values list is not benefits, it's company values. Could be part of About ALOIS Healthcare.
Also, the job metadata (specialty, discipline) could be in About the role or a separate "Requirements" section? But no specific requirements listed. Might just include in About the role as a list.
Let's see: The posting has "Specialty: MRI Technologist Discipline: Allied Health Professional". That's more like classification. Could be in a "Position Details" list.
I'll create:
About the role
MRI technologists specialize in magnetic resonance imaging scanners. They inject patients with contrast media, such as a dye, so that the images will show up on the scanner. The scanners use magnetic fields in combination with the contrast agent to produce images that a physician can use to diagnose medical problems.
- Specialty: MRI Technologist
- Discipline: Allied Health Professional
- Start Date: 11/09/2026
- Duration: 13 weeks
- Hours per Week: 40
- Shift: 8 hours, flexible
- Employment Type: Travel
But the rules say use - for any list of duties/requirements/benefits. This is a list of details, okay.
Then Schedule? The shift and hours are already in the list. Could have a separate Schedule section, but that would duplicate. Better to keep in one section.
Maybe "Position Details" but not a standard heading. The rules suggest "Schedule" for schedule info. Since we have shift and hours, we could make a Schedule section with those details. But then the other details (start date, duration) are not schedule. Could be "Assignment Details". However, the rules say prefer a few substantive sections over many thin ones. So maybe combine into "About the role" with a list.
But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use Schedule as a heading if we have schedule info. We have shift and hours per week. That's schedule. Start date and duration are assignment length. Could be under Schedule or separate.
I think we can create a "Schedule" section for shift and hours, and maybe include duration and start date there. But the list above includes all. Let's see: The posting has "40 hours per week Shift: 8 hours, flexible". That's schedule. "Duration: 13 weeks" is assignment length. "Start Date: 11/09/2026" is start. Could be "Assignment Details". But not a standard heading.
I'll create two sections: "About the role" for the description, and "Assignment Details" for the metadata? But the rules don't mention "Assignment Details". However, we can use "Schedule" for schedule-related, and maybe "Requirements" for specialty/discipline? Not really requirements.
Alternatively, we can put all metadata in a list under "About the role". That's simpler and avoids thin sections.
Now, Benefits section: clear.
About ALOIS Healthcare: include the why paragraph and the values list. The values list is a list of bullet points. Could be a separate "Values" section? But again, prefer few sections. Could include in "About ALOIS Healthcare" as a list.
Pay: The posting mentions pay package and tax-free stipend amount to be determined. Since it's vague, we should not create a Pay section. But we could include a short paragraph in "About the role" or "Assignment Details". The rule says fold minor metadata into a short
or drop it. Job ID is minor metadata. Pay info might be considered substantive? But it's not specific. I'll include a short paragraph in "About the role" after the description: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's a prose paragraph.
Job ID: "ALOIS Healthcare Job ID #19381897." and "Posted job title: MRI Tech Acute". These are minor metadata. Fold into a short
or drop. I'll drop Job ID, but maybe include posted job title? Not needed. The page already shows job title. So drop.
Now, the "Why ALOIS Healthcare?" paragraph and the values. The values are bullet points in the original: "· Everyone Matters· We are Performance Driven· We are Open, Honest and Direct· We are Transparent· We are Inclusive· We Do the Right Thing". They are separated by middle dots. We'll make a list.
Also the "We offer:" bullet points are benefits.
Now, ensure we don't duplicate lines. The posting has "ALOIS Healthcare Job ID #19381897. Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: MRI Tech Acute" - we'll use the pay part, drop the rest.
Now, write HTML.
Sections:
1. About the role
2. Benefits
3. About ALOIS Healthcare
Maybe also "Schedule" if we want to separate schedule. But the schedule info is minimal. I'll include schedule details in About the role list.
Let's draft:
About the role
MRI technologists specialize in magnetic resonance imaging scanners. They inject patients with contrast media, such as a dye, so
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - 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") - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, parse the content: Job title: "ALOIS Healthcare is seeking a travel MRI Technologist for a travel job in Wausau, Wisconsin." - This is the title, but we shouldn't repeat as heading. Job Description & Requirements section: - Specialty: MRI Technologist - Discipline: Allied Health Professional - Start Date: 11/09/2026 - Duration: 13 weeks - 40 hours per week - Shift: 8 hours, flexible - Employment Type: Travel Then a paragraph describing MRI technologists role. Then "ALOIS Healthcare Job ID #19381897. Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: MRI Tech Acute" About ALOIS Healthcare section: - Why ALOIS Healthcare? paragraph - "We offer:" with bullet points: - Industry-leading pay - Generous cost of living and housing stipends - Opportunities for referral, sign-on, and extension bonuses - Weekly health insurance or health insurance Marketplace weekly bonus - Continuing education credits - Then values list: - Everyone Matters - We are Performance Driven - We are Open, Honest and Direct - We are Transparent - We are Inclusive - We Do the Right Thing - Final paragraph: "We care about you - and your success is our success." Now, decide sections: 1. About the role (or Job Description) - include the description paragraph and maybe the metadata (specialty, discipline, etc.) as a list? The metadata is specific: start date, duration, hours, shift, employment type. Could be a "Requirements" or "Details" section. The rules suggest headings like "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include if real content. We have: - Job details (start date, duration, hours, shift, employment type) - could be "Schedule" or "Details". The rules mention "Schedule" as a possible heading. Since shift and hours are given, we can create a Schedule section. - Requirements? The posting doesn't list specific requirements like certifications, experience, etc. Only the specialty and discipline. Might not be enough for a Requirements section. - Benefits: The "We offer" list is clearly benefits. So Benefits section. - Pay: The posting says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague, but it does mention pay package and tax-free stipend. However, the rule says never create Pay section unless the posting actually states them. It does state something about pay, but it's not specific (amount to be determined). The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Amount to be determined" is similar to TBD. So maybe we should not create a Pay section. But we could include the pay info in a short paragraph under About the role or Schedule? The rule says fold minor metadata into a short
or drop it. Job ID is minor metadata. Pay info might be considered substantive? But it's vague. I think we can include a short paragraph about pay in the About the role section or a separate "Pay" section? The rule says never create Pay section unless the posting actually states them. It does state something, but it's not concrete. I'd lean to not create a Pay section, but include the pay info in a paragraph. - About ALOIS Healthcare: This is company description and values. Could be "About the Company" or "Why ALOIS Healthcare". The rules don't have a specific heading for company description, but we can use "About the Company" or "About ALOIS Healthcare". The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer those. However, "About the Company" is not listed, but we can use a relevant heading. The example includes "About the role". Could use "About ALOIS Healthcare". I think it's fine.
Now, structure:
- About the role: include the description paragraph and maybe the job details as a list? Or separate Schedule section for hours/shift.
Let's create sections:
1. About the role: includes the MRI technologist description paragraph.
2. Schedule: includes shift, hours per week, duration, start date, employment type. Could be a list.
3. Benefits: includes the "We offer" bullet points.
4. About ALOIS Healthcare: includes the why paragraph and values list.
But the values list is not benefits, it's company values. Could be part of About ALOIS Healthcare.
Also, the job metadata (specialty, discipline) could be in About the role or a separate "Requirements" section? But no specific requirements listed. Might just include in About the role as a list.
Let's see: The posting has "Specialty: MRI Technologist Discipline: Allied Health Professional". That's more like classification. Could be in a "Position Details" list.
I'll create:
About the role
MRI technologists specialize in magnetic resonance imaging scanners. They inject patients with contrast media, such as a dye, so that the images will show up on the scanner. The scanners use magnetic fields in combination with the contrast agent to produce images that a physician can use to diagnose medical problems.
- Specialty: MRI Technologist
- Discipline: Allied Health Professional
- Start Date: 11/09/2026
- Duration: 13 weeks
- Hours per Week: 40
- Shift: 8 hours, flexible
- Employment Type: Travel
- for any list of duties/requirements/benefits. This is a list of details, okay.
Then Schedule? The shift and hours are already in the list. Could have a separate Schedule section, but that would duplicate. Better to keep in one section.
Maybe "Position Details" but not a standard heading. The rules suggest "Schedule" for schedule info. Since we have shift and hours, we could make a Schedule section with those details. But then the other details (start date, duration) are not schedule. Could be "Assignment Details". However, the rules say prefer a few substantive sections over many thin ones. So maybe combine into "About the role" with a list.
But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use Schedule as a heading if we have schedule info. We have shift and hours per week. That's schedule. Start date and duration are assignment length. Could be under Schedule or separate. I think we can create a "Schedule" section for shift and hours, and maybe include duration and start date there. But the list above includes all. Let's see: The posting has "40 hours per week Shift: 8 hours, flexible". That's schedule. "Duration: 13 weeks" is assignment length. "Start Date: 11/09/2026" is start. Could be "Assignment Details". But not a standard heading. I'll create two sections: "About the role" for the description, and "Assignment Details" for the metadata? But the rules don't mention "Assignment Details". However, we can use "Schedule" for schedule-related, and maybe "Requirements" for specialty/discipline? Not really requirements. Alternatively, we can put all metadata in a list under "About the role". That's simpler and avoids thin sections. Now, Benefits section: clear. About ALOIS Healthcare: include the why paragraph and the values list. The values list is a list of bullet points. Could be a separate "Values" section? But again, prefer few sections. Could include in "About ALOIS Healthcare" as a list. Pay: The posting mentions pay package and tax-free stipend amount to be determined. Since it's vague, we should not create a Pay section. But we could include a short paragraph in "About the role" or "Assignment Details". The rule says fold minor metadata into a short
or drop it. Job ID is minor metadata. Pay info might be considered substantive? But it's not specific. I'll include a short paragraph in "About the role" after the description: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's a prose paragraph. Job ID: "ALOIS Healthcare Job ID #19381897." and "Posted job title: MRI Tech Acute". These are minor metadata. Fold into a short
or drop. I'll drop Job ID, but maybe include posted job title? Not needed. The page already shows job title. So drop. Now, the "Why ALOIS Healthcare?" paragraph and the values. The values are bullet points in the original: "· Everyone Matters· We are Performance Driven· We are Open, Honest and Direct· We are Transparent· We are Inclusive· We Do the Right Thing". They are separated by middle dots. We'll make a list. Also the "We offer:" bullet points are benefits. Now, ensure we don't duplicate lines. The posting has "ALOIS Healthcare Job ID #19381897. Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: MRI Tech Acute" - we'll use the pay part, drop the rest. Now, write HTML. Sections: 1. About the role 2. Benefits 3. About ALOIS Healthcare Maybe also "Schedule" if we want to separate schedule. But the schedule info is minimal. I'll include schedule details in About the role list. Let's draft:
About the role
MRI technologists specialize in magnetic resonance imaging scanners. They inject patients with contrast media, such as a dye, so