Travel Radiologic Technologist - $2,664 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
- Remove boilerplate, duplicated lines, application instructions
- Include section ONLY when posting has real, specific content
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment
Let me structure this:
The posting has:
- Job details (metadata) - should be in a
or maybe a "Job Details" section? The rules say use
for section headings like "About the role", "Responsibilities", etc. But "Job Details" isn't listed as a standard heading. However, the rules say "e.g." so it's not exhaustive. But also "Prefer a few substantive sections over many thin ones." The job details are metadata, not really a section. I'll fold into a short
at the beginning.
- About Anders Group - this is company description, could be "About the Company" or similar. But the rules list specific headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the company" isn't listed. However, the content is substantive. I could use "About the Company" as a heading, but the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." meaning examples. But also "include a section ONLY when the posting has real, specific content for it". The posting has "About Anders Group" with real content. I think I should include it with a heading like "About the Company" or "About Anders Group". But the rules might expect only those listed headings. However, the user said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests those are the typical headings, but not exclusive. But to be safe, I'll map the content to the most appropriate standard heading.
Let's see: "About Anders Group" could be "About the Role"? No, it's about the company. "What You Can Expect" is benefits. "The Anders Difference" is company philosophy. "Benefits" is another benefits list.
The posting doesn't have explicit "Responsibilities", "Requirements", "Qualifications", "Skills" sections. It's a travel job posting with company info and benefits.
The rules: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I should only create sections for which there is content.
Potential sections:
- Job Details (metadata) - but not a standard heading. Could be a
.
- About the Company (or About Anders Group) - substantive content.
- Benefits - there are two benefits lists: "What You Can Expect" and "Benefits". They overlap. I should combine them into one Benefits section.
Also, there is pay information: "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's pay info, but it's vague. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package info, but it's not detailed. However, it's specific: based on 10 hour shifts, 40 hours per week, tax-free stipend amount to be determined. That's some info. But "amount to be determined" is placeholder-like. The rules say "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 I should not create a Pay section, but include the pay info in a Job Details paragraph.
Schedule: "40 hours per week Shift: 10 hours, flexible" - that's schedule info. Could be a Schedule section. But again, the rules say only if posting actually states them. It does state schedule. But "flexible" is vague. However, it's specific: 40 hours per week, 10 hour shifts. I could include in Job Details.
Let me decide on sections:
1. Job Details (as a paragraph) - include start date, duration, hours, shift, employment type, pay package note.
2. About the Company (or About Anders Group) - with the description.
3. Benefits - combine the two lists.
But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Benefits" is an allowed heading. "About the role" is allowed, but this is about the company. Could use "About the Company" but not listed. However, the example includes "About the role". Might be okay to use "About the Company". But to follow the spirit, maybe I should not create a heading for company description? But it's substantive content. The rules say "Preserve ALL substantive information". So I need to include it. I'll use "About the Company" as an .
Alternatively, I could put the company description under "About the Role"? But that would be inaccurate.
Let's look at the user's instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This is a list of examples. It doesn't forbid other headings. But "Prefer a few substantive sections over many thin ones." So I'll create sections for substantive content.
I'll create:
- Job Details
(though not in example, but it's a section heading)
- About the Company
- Benefits
But the rules say "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 Job ID should be folded into a paragraph. So I'll put all metadata in a paragraph under Job Details or just a paragraph at top.
Maybe I should not have a "Job Details" heading, just a paragraph. Then "About the Company" heading, then "Benefits" heading.
Let's structure:
Travel Radiology Technologist position in Lebanon, New Hampshire. Start date: 11/09/2026. Duration: 13 weeks. 40 hours per week, 10-hour flexible shifts. Employment type: Travel. Pay package based on 10-hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
About the Company
Anders Group is a Joint Commission–accredited healthcare staffing agency founded in 2010 by experienced healthcare recruiters. The company focuses on relationships, quality placements, and long-term success for travelers, aligning clinician goals with top healthcare facilities nationwide.
Anders Group offers comprehensive support from the first assignment, including personalized service and access to high-paying travel opportunities.
Benefits
- 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
- Medical benefits
- Dental benefits
- Vision benefits
- Life insurance
- 401k retirement plan
- License and certification reimbursement
- Continuing Education
- Referral bonus
But there is duplication in the two benefits lists. The first list ("What You Can Expect") includes items like "Competitive, Premium Pay Packages", "Daily Per Diems & Travel Reimbursements", "Rental Car Allowances", "Continuing Education Resources", "Referral Bonuses". The second list ("Benefits") includes "Medical benefits", "Dental benefits", "Vision benefits", "Life insurance", "401k retirement plan", "License and certification reimbursement", "Continuing Education", "Referral bonus". Some are duplicates (Life insurance, 401k, License reimbursement, Continuing Education, Referral bonus). I should combine and deduplicate. But the rules say "Preserve ALL substantive information". Does that mean keep duplicates? Probably not, but we should not lose any unique items. I'll combine into a single list with unique items.
Let's list unique benefits from both:
From first list:
- 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
From second list:
- Medical benefits (same as Health Insurance)
- Dental benefits (same as Dental & Vision)
- Vision benefits (same)
- Life insurance (same)
- 401k retirement plan (same)
- License and certification reimbursement (same as Licensure & CEU Reimbursement)
- Continuing Education (same as Continuing Education Resources)
- Referral bonus (same as Referral Bonuses)
So the second list is essentially a subset. I'll keep the more detailed first list. But the second list might be a summary. I'll include all unique items from both, but avoid exact duplicates. I'll keep the more descriptive ones.
I'll create a combined list.
Also, note "And more" from first list - that's filler, I'll omit.
Now, the "The Anders Difference" section: it's company philosophy. Could be part of About the Company. I'll include it in the About the Company section as a paragraph.
Now, check for any responsibilities, requirements, qualifications, skills - none in the posting. So no those sections.
Pay: only the note about pay package. Since it's vague (amount to be determined), I'll not create a Pay section, but include in Job Details paragraph.
Schedule: included in Job Details.
Thus final HTML:
Travel Radiology Technologist position in Lebanon, New Hampshire. Start date: 11/09/2026. Duration: 13 weeks. 40 hours per week, 10-hour flexible shifts. Employment type: Travel. Pay package based on 10-hour shifts and 40 hours per week (subject to confirmation) with tax-free
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 - Remove boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment Let me structure this: The posting has: - Job details (metadata) - should be in a
or maybe a "Job Details" section? The rules say use
for section headings like "About the role", "Responsibilities", etc. But "Job Details" isn't listed as a standard heading. However, the rules say "e.g." so it's not exhaustive. But also "Prefer a few substantive sections over many thin ones." The job details are metadata, not really a section. I'll fold into a short
at the beginning. - About Anders Group - this is company description, could be "About the Company" or similar. But the rules list specific headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the company" isn't listed. However, the content is substantive. I could use "About the Company" as a heading, but the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." meaning examples. But also "include a section ONLY when the posting has real, specific content for it". The posting has "About Anders Group" with real content. I think I should include it with a heading like "About the Company" or "About Anders Group". But the rules might expect only those listed headings. However, the user said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests those are the typical headings, but not exclusive. But to be safe, I'll map the content to the most appropriate standard heading.
Let's see: "About Anders Group" could be "About the Role"? No, it's about the company. "What You Can Expect" is benefits. "The Anders Difference" is company philosophy. "Benefits" is another benefits list.
The posting doesn't have explicit "Responsibilities", "Requirements", "Qualifications", "Skills" sections. It's a travel job posting with company info and benefits.
The rules: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I should only create sections for which there is content.
Potential sections:
- Job Details (metadata) - but not a standard heading. Could be a
. - About the Company (or About Anders Group) - substantive content. - Benefits - there are two benefits lists: "What You Can Expect" and "Benefits". They overlap. I should combine them into one Benefits section. Also, there is pay information: "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's pay info, but it's vague. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package info, but it's not detailed. However, it's specific: based on 10 hour shifts, 40 hours per week, tax-free stipend amount to be determined. That's some info. But "amount to be determined" is placeholder-like. The rules say "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 I should not create a Pay section, but include the pay info in a Job Details paragraph. Schedule: "40 hours per week Shift: 10 hours, flexible" - that's schedule info. Could be a Schedule section. But again, the rules say only if posting actually states them. It does state schedule. But "flexible" is vague. However, it's specific: 40 hours per week, 10 hour shifts. I could include in Job Details. Let me decide on sections: 1. Job Details (as a paragraph) - include start date, duration, hours, shift, employment type, pay package note. 2. About the Company (or About Anders Group) - with the description. 3. Benefits - combine the two lists. But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Benefits" is an allowed heading. "About the role" is allowed, but this is about the company. Could use "About the Company" but not listed. However, the example includes "About the role". Might be okay to use "About the Company". But to follow the spirit, maybe I should not create a heading for company description? But it's substantive content. The rules say "Preserve ALL substantive information". So I need to include it. I'll use "About the Company" as an .
Alternatively, I could put the company description under "About the Role"? But that would be inaccurate.
Let's look at the user's instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This is a list of examples. It doesn't forbid other headings. But "Prefer a few substantive sections over many thin ones." So I'll create sections for substantive content.
I'll create:
- Job Details
(though not in example, but it's a section heading)
- About the Company
- Benefits
But the rules say "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
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This is a list of examples. It doesn't forbid other headings. But "Prefer a few substantive sections over many thin ones." So I'll create sections for substantive content.
I'll create:
- Job Details
(though not in example, but it's a section heading)
- About the Company
- Benefits
But the rules say "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 Job ID should be folded into a paragraph. So I'll put all metadata in a paragraph under Job Details or just a paragraph at top. Maybe I should not have a "Job Details" heading, just a paragraph. Then "About the Company" heading, then "Benefits" heading. Let's structure:
Travel Radiology Technologist position in Lebanon, New Hampshire. Start date: 11/09/2026. Duration: 13 weeks. 40 hours per week, 10-hour flexible shifts. Employment type: Travel. Pay package based on 10-hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
About the Company
Anders Group is a Joint Commission–accredited healthcare staffing agency founded in 2010 by experienced healthcare recruiters. The company focuses on relationships, quality placements, and long-term success for travelers, aligning clinician goals with top healthcare facilities nationwide.
Anders Group offers comprehensive support from the first assignment, including personalized service and access to high-paying travel opportunities.
Benefits
- 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
- Medical benefits
- Dental benefits
- Vision benefits
- Life insurance
- 401k retirement plan
- License and certification reimbursement
- Continuing Education
- Referral bonus
Travel Radiology Technologist position in Lebanon, New Hampshire. Start date: 11/09/2026. Duration: 13 weeks. 40 hours per week, 10-hour flexible shifts. Employment type: Travel. Pay package based on 10-hour shifts and 40 hours per week (subject to confirmation) with tax-free