Travel MRI Technologist - $2,934 per week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- 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") and 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, map the content to appropriate sections.
The posting has:
- Job details: specialty, discipline, start date, duration, hours per week, shift, employment type, job ID, pay package info, posted job title. This could be "About the role" or "Job Details". The rule suggests headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". There's no explicit responsibilities or requirements listed beyond the basic details. The "Job Description & Requirements" heading in the source might be a section, but the content is mostly metadata. I'll create an "About the role" section with the details.
- About Anders Group: includes "Why Anders?" (prose), "What You Can Expect" (list of benefits), "The Anders Difference" (prose). This could be "About the company" or similar. But the rule says use headings like "About the role", "Responsibilities", etc. Not "About the company". However, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so other headings are allowed if they fit. But we should prefer those. The posting has a "Benefits" section at the end that duplicates some of the "What You Can Expect" list. The "Benefits" section at the end is a list: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. That's a clear Benefits section.
The "What You Can Expect" list includes: Day One Health Insurance (with buy-up options), Dental & Vision Insurance, Life Insurance, 401(k) Retirement Plan, Competitive, Premium Pay Packages, Licensure & CEU Reimbursement, Daily Per Diems & Travel Reimbursements, Rental Car Allowances, Continuing Education Resources, Referral Bonuses, And more. This is also benefits. The final "Benefits" section is a subset. I should combine or choose the more detailed one. The "What You Can Expect" is more detailed. The final "Benefits" is a shorter list. Since the rule says preserve ALL substantive information, I should include both? But they are duplicative. The final "Benefits" might be a summary. I'll include the "What You Can Expect" as the benefits list, and maybe note the final list as a summary? But the rule says remove duplicated lines. So I should deduplicate. I'll use the more detailed list from "What You Can Expect". The final "Benefits" section can be omitted as duplicate.
The "About Anders Group" section includes prose about the company. That could be an "About the company" section. But the rule doesn't list that as an example heading. However, the rule says "use for section headings (e.g. ...)" meaning those are examples, not exhaustive. But the instruction: "Prefer a few substantive sections over many thin ones." So I could have "About the role" and "Benefits". The company description might be considered boilerplate? It's not exactly boilerplate; it's about the agency. But the job posting is for a travel MRI Technologist position at Anders Group. The company description is part of the posting. I think it's substantive. I'll include an "About Anders Group" heading.
But the rule says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I'll fold the job ID and pay package info into a paragraph.
Let's structure:
1. About the role: includes the job details (specialty, discipline, start date, duration, hours per week, shift, employment type, posted job title). The pay package info: "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 pay information. Could be a Pay section. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state pay package info, but it's vague ("tax-free stipend amount to be determined"). That might be considered placeholder? It says "subject to confirmation" and "to be determined". That 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"). "Tax-free stipend amount to be determined" is similar to TBD. So maybe we should not create a Pay section. Instead, fold into About the role as a paragraph.
Schedule: The posting says "40 hours per week", "Shift: 8 hours, days". That's schedule info. Could be a Schedule section. But again, the rule says never create Schedule section unless the posting actually states them. It does state them. But the rule also says "never emit a heading followed by filler/placeholder text". The schedule info is specific: 40 hours per week, 8 hours, days. That's specific. So maybe a Schedule section is appropriate. However, the example headings include "Schedule". I'll include a Schedule section.
But the rule: "Prefer a few substantive sections over many thin ones." If I create Schedule and Pay, they might be thin. Pay is thin (mostly TBD). Schedule is thin but specific. I could combine into "Job Details" or "About the role". The example headings include "About the role". I'll put all job metadata into "About the role" as a list or paragraphs.
Let's decide on sections:
- About the role: includes specialty, discipline, start date, duration, hours per week, shift, employment type, posted job title, job ID (as minor metadata), pay package note.
- About Anders Group: includes Why Anders?, What You Can Expect (benefits list), The Anders Difference.
- Benefits: the final list? But duplicate. I'll omit the final Benefits section as duplicate. The "What You Can Expect" is essentially benefits. So I'll have a Benefits section under About Anders Group? Or separate Benefits section. The rule says use
for section headings like Benefits. So I could have a top-level Benefits section. But the "What You Can Expect" is under About Anders Group. The final "Benefits" heading is separate. I think the posting has two benefits lists: one under "What You Can Expect" and one under "Benefits". The final one is shorter. I'll combine into one Benefits section, using the more detailed list.
But the "What You Can Expect" includes "Competitive, Premium Pay Packages" which is pay, not benefits. And "Daily Per Diems & Travel Reimbursements", "Rental Car Allowances" which are compensation. The final Benefits list is more traditional benefits. I'll create a Benefits section with the final list (medical, dental, vision, life, 401k, license reimbursement, continuing education, referral bonus). And maybe include the other items as "Additional Perks" or something. But the rule says preserve ALL substantive information. So I should include all. I'll create a Benefits section with two sub-lists? But we only have h3 and ul/li. I could have a Benefits section with a paragraph introducing, then a list. I'll include all items from both lists, deduplicated.
Let's list all unique benefits/perks from both:
From "What You Can Expect":
- Day One Health Insurance (with buy-up options)
- Dental & Vision Insurance
- Life Insurance
- 401(k) Retirement Plan
- Competitive, Premium Pay Packages
- Licensure & CEU Reimbursement
- Daily Per Diems & Travel Reimbursements
- Rental Car Allowances
- Continuing Education Resources
- Referral Bonuses
- And more
From "Benefits":
- Medical benefits
- Dental benefits
- Vision benefits
- Life insurance
- 401k retirement plan
- License and certification reimbursement
- Continuing Education
- Referral bonus
These are largely the same. "Medical benefits" = "Day One Health Insurance". "Dental benefits" = "Dental & Vision Insurance" (but vision separate). "Vision benefits" = included. "Life insurance" same. "401k retirement plan" same. "License and certification reimbursement" = "Licensure & CEU Reimbursement". "Continuing Education" = "Continuing Education Resources". "Referral bonus" = "Referral Bonuses". The "What You Can Expect" adds "Competitive, Premium Pay Packages", "Daily Per Diems & Travel Reimbursements", "Rental Car Allowances", "And more". So I'll use the more detailed list.
Thus, I'll have a Benefits section with that list.
Now, the "About Anders Group" prose: "Why Anders?" and "The Anders Difference". That's company description. I'll create an "About Anders Group" section with those paragraphs.
Now, the job details: I'll create an "About the role" section with a paragraph summarizing the key details, and maybe a list for the specifics.
The rule: "Use - for any list of duties/requirements/benefits, and
for prose." So for job details, they are not duties/requirements/benefits, but metadata. Could be a list. I'll use a list for the key details.
Let's draft HTML:
About the role
Anders Group is seeking a travel MRI Technologist for a 13-week assignment in Milwaukee, Wisconsin.
- Specialty: MRI Technologist
- Discipline: Allied Health Professional
- Start Date: 11/09/2026
- Duration: 13 weeks
- Hours
for prose - Do NOT repeat job title as heading - 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") and 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, map the content to appropriate sections. The posting has: - Job details: specialty, discipline, start date, duration, hours per week, shift, employment type, job ID, pay package info, posted job title. This could be "About the role" or "Job Details". The rule suggests headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". There's no explicit responsibilities or requirements listed beyond the basic details. The "Job Description & Requirements" heading in the source might be a section, but the content is mostly metadata. I'll create an "About the role" section with the details. - About Anders Group: includes "Why Anders?" (prose), "What You Can Expect" (list of benefits), "The Anders Difference" (prose). This could be "About the company" or similar. But the rule says use headings like "About the role", "Responsibilities", etc. Not "About the company". However, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so other headings are allowed if they fit. But we should prefer those. The posting has a "Benefits" section at the end that duplicates some of the "What You Can Expect" list. The "Benefits" section at the end is a list: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. That's a clear Benefits section.
The "What You Can Expect" list includes: Day One Health Insurance (with buy-up options), Dental & Vision Insurance, Life Insurance, 401(k) Retirement Plan, Competitive, Premium Pay Packages, Licensure & CEU Reimbursement, Daily Per Diems & Travel Reimbursements, Rental Car Allowances, Continuing Education Resources, Referral Bonuses, And more. This is also benefits. The final "Benefits" section is a subset. I should combine or choose the more detailed one. The "What You Can Expect" is more detailed. The final "Benefits" is a shorter list. Since the rule says preserve ALL substantive information, I should include both? But they are duplicative. The final "Benefits" might be a summary. I'll include the "What You Can Expect" as the benefits list, and maybe note the final list as a summary? But the rule says remove duplicated lines. So I should deduplicate. I'll use the more detailed list from "What You Can Expect". The final "Benefits" section can be omitted as duplicate.
The "About Anders Group" section includes prose about the company. That could be an "About the company" section. But the rule doesn't list that as an example heading. However, the rule says "use for section headings (e.g. ...)" meaning those are examples, not exhaustive. But the instruction: "Prefer a few substantive sections over many thin ones." So I could have "About the role" and "Benefits". The company description might be considered boilerplate? It's not exactly boilerplate; it's about the agency. But the job posting is for a travel MRI Technologist position at Anders Group. The company description is part of the posting. I think it's substantive. I'll include an "About Anders Group" heading.
But the rule says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I'll fold the job ID and pay package info into a paragraph. Let's structure: 1. About the role: includes the job details (specialty, discipline, start date, duration, hours per week, shift, employment type, posted job title). The pay package info: "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 pay information. Could be a Pay section. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state pay package info, but it's vague ("tax-free stipend amount to be determined"). That might be considered placeholder? It says "subject to confirmation" and "to be determined". That 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"). "Tax-free stipend amount to be determined" is similar to TBD. So maybe we should not create a Pay section. Instead, fold into About the role as a paragraph. Schedule: The posting says "40 hours per week", "Shift: 8 hours, days". That's schedule info. Could be a Schedule section. But again, the rule says never create Schedule section unless the posting actually states them. It does state them. But the rule also says "never emit a heading followed by filler/placeholder text". The schedule info is specific: 40 hours per week, 8 hours, days. That's specific. So maybe a Schedule section is appropriate. However, the example headings include "Schedule". I'll include a Schedule section. But the rule: "Prefer a few substantive sections over many thin ones." If I create Schedule and Pay, they might be thin. Pay is thin (mostly TBD). Schedule is thin but specific. I could combine into "Job Details" or "About the role". The example headings include "About the role". I'll put all job metadata into "About the role" as a list or paragraphs. Let's decide on sections: - About the role: includes specialty, discipline, start date, duration, hours per week, shift, employment type, posted job title, job ID (as minor metadata), pay package note. - About Anders Group: includes Why Anders?, What You Can Expect (benefits list), The Anders Difference. - Benefits: the final list? But duplicate. I'll omit the final Benefits section as duplicate. The "What You Can Expect" is essentially benefits. So I'll have a Benefits section under About Anders Group? Or separate Benefits section. The rule says use
for section headings like Benefits. So I could have a top-level Benefits section. But the "What You Can Expect" is under About Anders Group. The final "Benefits" heading is separate. I think the posting has two benefits lists: one under "What You Can Expect" and one under "Benefits". The final one is shorter. I'll combine into one Benefits section, using the more detailed list.
But the "What You Can Expect" includes "Competitive, Premium Pay Packages" which is pay, not benefits. And "Daily Per Diems & Travel Reimbursements", "Rental Car Allowances" which are compensation. The final Benefits list is more traditional benefits. I'll create a Benefits section with the final list (medical, dental, vision, life, 401k, license reimbursement, continuing education, referral bonus). And maybe include the other items as "Additional Perks" or something. But the rule says preserve ALL substantive information. So I should include all. I'll create a Benefits section with two sub-lists? But we only have h3 and ul/li. I could have a Benefits section with a paragraph introducing, then a list. I'll include all items from both lists, deduplicated.
Let's list all unique benefits/perks from both:
From "What You Can Expect":
- Day One Health Insurance (with buy-up options)
- Dental & Vision Insurance
- Life Insurance
- 401(k) Retirement Plan
- Competitive, Premium Pay Packages
- Licensure & CEU Reimbursement
- Daily Per Diems & Travel Reimbursements
- Rental Car Allowances
- Continuing Education Resources
- Referral Bonuses
- And more
From "Benefits":
- Medical benefits
- Dental benefits
- Vision benefits
- Life insurance
- 401k retirement plan
- License and certification reimbursement
- Continuing Education
- Referral bonus
These are largely the same. "Medical benefits" = "Day One Health Insurance". "Dental benefits" = "Dental & Vision Insurance" (but vision separate). "Vision benefits" = included. "Life insurance" same. "401k retirement plan" same. "License and certification reimbursement" = "Licensure & CEU Reimbursement". "Continuing Education" = "Continuing Education Resources". "Referral bonus" = "Referral Bonuses". The "What You Can Expect" adds "Competitive, Premium Pay Packages", "Daily Per Diems & Travel Reimbursements", "Rental Car Allowances", "And more". So I'll use the more detailed list.
Thus, I'll have a Benefits section with that list.
Now, the "About Anders Group" prose: "Why Anders?" and "The Anders Difference". That's company description. I'll create an "About Anders Group" section with those paragraphs.
Now, the job details: I'll create an "About the role" section with a paragraph summarizing the key details, and maybe a list for the specifics.
The rule: "Use - for any list of duties/requirements/benefits, and
for prose." So for job details, they are not duties/requirements/benefits, but metadata. Could be a list. I'll use a list for the key details.
Let's draft HTML:
About the role
Anders Group is seeking a travel MRI Technologist for a 13-week assignment in Milwaukee, Wisconsin.
- Specialty: MRI Technologist
- Discipline: Allied Health Professional
- Start Date: 11/09/2026
- Duration: 13 weeks
- Hours
for prose." So for job details, they are not duties/requirements/benefits, but metadata. Could be a list. I'll use a list for the key details. Let's draft HTML:
About the role
Anders Group is seeking a travel MRI Technologist for a 13-week assignment in Milwaukee, Wisconsin.
- Specialty: MRI Technologist
- Discipline: Allied Health Professional
- Start Date: 11/09/2026
- Duration: 13 weeks
- Hours