Travel MRI Technologist - $2,463 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") 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, parse the content:
The posting starts with "Healthcare Support is seeking a travel MRI Technologist for a travel job in Cincinnati, Ohio." That's an intro.
Then "Job Description & Requirements" with bullet-like lines: Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type, Job ID, Pay package info.
Then "About Healthcare Support" with a paragraph about the company.
Then "Benefits" with a list.
There's no explicit "Responsibilities" or "Requirements" sections beyond the metadata. The "Job Description & Requirements" seems to be metadata, not duties. The posting doesn't list specific duties or requirements beyond the metadata. So I should not create a Responsibilities or Requirements section unless there is content. The metadata can be folded into a short
or a list under "About the role" or "Job details".
The user says: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can include the metadata in a paragraph or list under a section like "Job details" or "About the role". But the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I can use "About the role" for the job description metadata.
Also, there is pay information: "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 pay info, but it's not a specific pay range; it's a description. The rule says never create Pay section unless the posting actually states them. It does state pay package details, but it's vague. However, it's substantive information about pay. I could include it under "About the role" or create a Pay section. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package info, so maybe include a Pay section. But the pay info is not a specific number; it's a description. The rule also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The pay info says "tax-free stipend amount to be determined." That's like TBD. So maybe better to fold into "About the role" and not create a separate Pay section.
Similarly, Schedule: shift and hours are given. Could create a Schedule section, but the rule says only if posting actually states them. It does state shift and hours. But again, prefer few substantive sections. I can include schedule details in "About the role".
Benefits are explicitly listed, so Benefits section is warranted.
About Healthcare Support is company description, could be "About the company" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Healthcare Support" is not in that list. But the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. However, the instruction: "include a section ONLY when the posting has real, specific content for it". The company description is real content. But the allowed headings might be limited to those examples? The user says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings. But we can use other headings if needed? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings". It doesn't forbid other headings. However, to be safe, I'll map "About Healthcare Support" to "About the role"? That doesn't fit. Maybe "About the company" but not in list. I think it's okay to have a heading "About Healthcare Support" as it's a section in the posting. But the user gave examples, not a strict whitelist. I'll include it as a section with heading "About Healthcare Support". But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings. However, the system prompt might be expecting only those headings. Let's see: The user says "Rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the typical sections. But the posting has "About Healthcare Support" which is a company description. I could treat it as "About the role"? No. I'll create a section "About Healthcare Support" as it's substantive.
But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine company description into a paragraph under "About the role"? That seems odd.
Let's structure:
1. About the role: includes the job description metadata (specialty, discipline, start date, duration, hours, shift, employment type, job ID, pay package info). Could be a list or paragraphs.
2. About Healthcare Support: company description.
3. Benefits: list.
No Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule sections because not explicitly detailed beyond metadata.
Pay info is in metadata, but not a separate pay section.
Schedule info is in metadata.
Thus, three sections.
Now, format:
- For "About the role": use About the role
then maybe a
for the intro sentence, then a
for the metadata? Or a with details. The metadata lines are like key-value pairs. Could use a
with - for each. But the rule says use
- for any list of duties/requirements/benefits. Metadata is not duties/requirements/benefits, but it's a list. Could use
for the job details. I'll use a for the job details.
- For "About Healthcare Support": About Healthcare Support
then for the paragraph.
- For "Benefits":
Benefits
then - for each benefit.
Now, ensure we don't include boilerplate: The posting has "Pst! Ask us about our Direct Hire Opportunities!" That's promotional, maybe keep? It's part of company description. I'll include it in the paragraph.
Also, "Posted job title: mri technologist" is redundant with job title, but it's in the metadata. I'll include it in the list.
Now, write HTML.
Let's draft:
About the role
Healthcare Support is seeking a travel MRI Technologist for a travel job in Cincinnati, Ohio.
- Specialty: MRI Technologist
- Discipline: Allied Health Professional
- Start Date: 10/26/2026
- Duration: 13 weeks
- Hours per week: 36
- Shift: 12 hours
- Employment Type: Travel
- Job ID: 527642
- Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined
- Posted job title: mri technologist
About Healthcare Support
Healthcare Support excels at providing a streamlined and red-carpet experience for our travelers. Whether you are a nurse, a therapist, or an allied health professional, our goal is to connect you with top-rated facilities throughout the country and get you on the road to your next adventure. We leverage 20 years of relationships with the industry’s most respectable companies across all 50 states, both through direct client partnerships and via national MSP programs. From health systems and hospitals to specialty clinics and post-acute facilities, you can work where you want to work and go where you want to go. Not only does HealthCare Support reimburse for relocation and travel costs on your first check, but we also offer license and certification reimbursements required for your assignments so that you can focus on building your career. During your assignment, you’ll have access to medical benefits, 24/7 support from our Clinical Advocacy Team, and a travel team with stateside operations. Your travel team will include a designated credentialing expert to help you navigate every step of the on-boarding process, a payroll specialist who you can communicate with directly, and a skilled recruiter who takes the time to understand your needs and works hard to find the right position for you. Don’t get lost in the shuffle of another overblown staffing agency. Choose HealthCare Support to be your trusted partner that you can rely on for all your travel assignments. We can’t wait to hear about the amazing adventures you’ll have! Pst! Ask us about our Direct Hire Opportunities!
Benefits
- License and certification reimbursement
- Medical benefits
- Dental benefits
- Mileage reimbursement
- Employee assistance programs
- Referral bonus
- 401k retirement plan
- Holiday Pay
- Weekly pay
Check rules: No markdown, no html/body. Only HTML fragment. Good.
But note: The rule says "Do NOT repeat the job title as a heading (the page already shows it)". I didn't. I used "About the role". Good.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." I put Job ID in the list, not as heading. Good.
"Preserve ALL substantive information; do NOT invent or summarize away detail." I preserved all.
"Remove cookie
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") 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, parse the content: The posting starts with "Healthcare Support is seeking a travel MRI Technologist for a travel job in Cincinnati, Ohio." That's an intro. Then "Job Description & Requirements" with bullet-like lines: Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type, Job ID, Pay package info. Then "About Healthcare Support" with a paragraph about the company. Then "Benefits" with a list. There's no explicit "Responsibilities" or "Requirements" sections beyond the metadata. The "Job Description & Requirements" seems to be metadata, not duties. The posting doesn't list specific duties or requirements beyond the metadata. So I should not create a Responsibilities or Requirements section unless there is content. The metadata can be folded into a short
or a list under "About the role" or "Job details". The user says: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can include the metadata in a paragraph or list under a section like "Job details" or "About the role". But the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I can use "About the role" for the job description metadata. Also, there is pay information: "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 pay info, but it's not a specific pay range; it's a description. The rule says never create Pay section unless the posting actually states them. It does state pay package details, but it's vague. However, it's substantive information about pay. I could include it under "About the role" or create a Pay section. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package info, so maybe include a Pay section. But the pay info is not a specific number; it's a description. The rule also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The pay info says "tax-free stipend amount to be determined." That's like TBD. So maybe better to fold into "About the role" and not create a separate Pay section. Similarly, Schedule: shift and hours are given. Could create a Schedule section, but the rule says only if posting actually states them. It does state shift and hours. But again, prefer few substantive sections. I can include schedule details in "About the role". Benefits are explicitly listed, so Benefits section is warranted. About Healthcare Support is company description, could be "About the company" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Healthcare Support" is not in that list. But the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. However, the instruction: "include a section ONLY when the posting has real, specific content for it". The company description is real content. But the allowed headings might be limited to those examples? The user says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings. But we can use other headings if needed? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings". It doesn't forbid other headings. However, to be safe, I'll map "About Healthcare Support" to "About the role"? That doesn't fit. Maybe "About the company" but not in list. I think it's okay to have a heading "About Healthcare Support" as it's a section in the posting. But the user gave examples, not a strict whitelist. I'll include it as a section with heading "About Healthcare Support". But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings. However, the system prompt might be expecting only those headings. Let's see: The user says "Rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the typical sections. But the posting has "About Healthcare Support" which is a company description. I could treat it as "About the role"? No. I'll create a section "About Healthcare Support" as it's substantive.
But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine company description into a paragraph under "About the role"? That seems odd.
Let's structure:
1. About the role: includes the job description metadata (specialty, discipline, start date, duration, hours, shift, employment type, job ID, pay package info). Could be a list or paragraphs.
2. About Healthcare Support: company description.
3. Benefits: list.
No Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule sections because not explicitly detailed beyond metadata.
Pay info is in metadata, but not a separate pay section.
Schedule info is in metadata.
Thus, three sections.
Now, format:
- For "About the role": use About the role
then maybe a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings. However, the system prompt might be expecting only those headings. Let's see: The user says "Rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the typical sections. But the posting has "About Healthcare Support" which is a company description. I could treat it as "About the role"? No. I'll create a section "About Healthcare Support" as it's substantive.
But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine company description into a paragraph under "About the role"? That seems odd.
Let's structure:
1. About the role: includes the job description metadata (specialty, discipline, start date, duration, hours, shift, employment type, job ID, pay package info). Could be a list or paragraphs.
2. About Healthcare Support: company description.
3. Benefits: list.
No Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule sections because not explicitly detailed beyond metadata.
Pay info is in metadata, but not a separate pay section.
Schedule info is in metadata.
Thus, three sections.
Now, format:
- For "About the role": use About the role
then maybe a
About the role
then maybe afor the intro sentence, then a
- for the metadata? Or a
- for each. But the rule says use
- for any list of duties/requirements/benefits. Metadata is not duties/requirements/benefits, but it's a list. Could use
- for the job details. I'll use a
- for each benefit.
Now, ensure we don't include boilerplate: The posting has "Pst! Ask us about our Direct Hire Opportunities!" That's promotional, maybe keep? It's part of company description. I'll include it in the paragraph.
Also, "Posted job title: mri technologist" is redundant with job title, but it's in the metadata. I'll include it in the list.
Now, write HTML.
Let's draft:
About the role
Healthcare Support is seeking a travel MRI Technologist for a travel job in Cincinnati, Ohio.
- Specialty: MRI Technologist
- Discipline: Allied Health Professional
- Start Date: 10/26/2026
- Duration: 13 weeks
- Hours per week: 36
- Shift: 12 hours
- Employment Type: Travel
- Job ID: 527642
- Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined
- Posted job title: mri technologist
About Healthcare Support
Healthcare Support excels at providing a streamlined and red-carpet experience for our travelers. Whether you are a nurse, a therapist, or an allied health professional, our goal is to connect you with top-rated facilities throughout the country and get you on the road to your next adventure. We leverage 20 years of relationships with the industry’s most respectable companies across all 50 states, both through direct client partnerships and via national MSP programs. From health systems and hospitals to specialty clinics and post-acute facilities, you can work where you want to work and go where you want to go. Not only does HealthCare Support reimburse for relocation and travel costs on your first check, but we also offer license and certification reimbursements required for your assignments so that you can focus on building your career. During your assignment, you’ll have access to medical benefits, 24/7 support from our Clinical Advocacy Team, and a travel team with stateside operations. Your travel team will include a designated credentialing expert to help you navigate every step of the on-boarding process, a payroll specialist who you can communicate with directly, and a skilled recruiter who takes the time to understand your needs and works hard to find the right position for you. Don’t get lost in the shuffle of another overblown staffing agency. Choose HealthCare Support to be your trusted partner that you can rely on for all your travel assignments. We can’t wait to hear about the amazing adventures you’ll have! Pst! Ask us about our Direct Hire Opportunities!
Benefits
- License and certification reimbursement
- Medical benefits
- Dental benefits
- Mileage reimbursement
- Employee assistance programs
- Referral bonus
- 401k retirement plan
- Holiday Pay
- Weekly pay
or drop it." I put Job ID in the list, not as heading. Good. "Preserve ALL substantive information; do NOT invent or summarize away detail." I preserved all. "Remove cookie
- for the job details.
- For "About Healthcare Support":
About Healthcare Support
thenfor the paragraph. - For "Benefits":
Benefits
then - for each benefit.
Now, ensure we don't include boilerplate: The posting has "Pst! Ask us about our Direct Hire Opportunities!" That's promotional, maybe keep? It's part of company description. I'll include it in the paragraph.
Also, "Posted job title: mri technologist" is redundant with job title, but it's in the metadata. I'll include it in the list.
Now, write HTML.
Let's draft:
- for any list of duties/requirements/benefits. Metadata is not duties/requirements/benefits, but it's a list. Could use
with details. The metadata lines are like key-value pairs. Could use a
- with