Travel X Ray Tech - $2,421 per week

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Let's parse the posting. Content: - Job: travel Radiology Technologist in Martinsburg, WV. - Specialty: Radiology Technologist - Discipline: Allied Health Professional - Start Date: ASAP - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, rotating - Employment Type: Travel - Job ID #1399760 (metadata, drop) - Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: Rad Tech (not needed) - About Anders Group: description of company, benefits, etc. We need to extract substantive info for sections. About the role: maybe description of role? Not explicit duties. Could include "Travel Radiology Technologist" location, start date, duration, hours, shift, employment type. That could be under About the role. Responsibilities: Not listed. No specific duties. So we should not create Responsibilities section if no content. Requirements: Not listed explicitly. Could infer specialty, discipline but not explicit requirements. Probably not enough. Qualifications: Not listed. Skills: Not listed. Benefits: The posting lists many 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, plus Anders Group benefits: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. So we have benefits content. Pay: The posting mentions "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 vague but it's some pay info. It says subject to confirmation, stipend TBD. According to rules: we should NOT create Pay section unless posting actually states them. It does state something about pay package based on shifts, but it's not specific amount. It says "subject to confirmation" and "tax-free stipend amount to be determined." This is somewhat vague but still mentions pay package. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay package, albeit not specific numbers. I'd argue we can include Pay section with that statement. Schedule: The posting states shift: 10 hours, rotating; 40 hours per week. That's schedule info. So we can include Schedule section. Now About the role: we can include location, start date, duration, hours, shift, employment type. We must not repeat job title as heading. Use

for section headings. We need to output only HTML fragment, no /. Use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information; do not invent or summarize away detail. Let's craft sections:

  About the role

  Travel Radiology Technologist position in Martinsburg, West Virginia. Start date: ASAP. Duration: 13 weeks. Schedule: 40 hours per week, 10‑hour rotating shifts. Employment type: Travel.

  That's prose. Benefits: we have a list. Use
  • . Need to combine both sets but avoid duplication. List unique items: - 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 (maybe redundant with Day One Health Insurance? but we can keep both? Might be duplicate. The Anders Group benefits list includes Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. Many overlap. To preserve all substantive information, we should include both sets but avoid exact duplicate lines. However "Medical benefits" is similar to "Day One Health Insurance". Might be considered duplicate but not exact same wording. Safer to include both as separate items? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we drop "Medical benefits" because it's similar to Day One Health Insurance, we might be summarizing away detail. But they are substantively similar; but we could keep both as they are distinct statements. However we might be repeating similar info. The rule about duplicated lines: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines refers to exact duplicates. Not similar. So we can keep both. Thus benefits 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 - Medical benefits - Dental benefits - Vision benefits - Life insurance (duplicate of Life Insurance? Slight case difference; but it's duplicate essentially. Might be considered duplicated line? It's same meaning but different case. Safer to keep only one? The instruction says duplicated lines; case-insensitive? Not sure. To be safe, we can keep only one Life Insurance entry. We'll keep the first "Life Insurance". We'll omit the later "Life insurance". Similarly Dental benefits vs Dental & Vision Insurance: not duplicate. Vision benefits vs Dental & Vision Insurance: not duplicate. We'll keep them. - 401k retirement plan (similar to 401(k) Retirement Plan). Might be duplicate. We'll keep the first. - License and certification reimbursement (similar to Licensure & CEU Reimbursement). Keep first. - Continuing Education (similar to Continuing Education Resources). Keep first. - Referral bonus (similar to Referral Bonuses). Keep first. Thus final benefits 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 - Medical benefits - Dental benefits - Vision benefits That seems okay. Pay section: we have statement: "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." We'll put that in

    . Schedule section: we have shift: 10 hours, rotating; 40 hours per week. We'll put that in

    . We should not include sections with no content: Responsibilities, Requirements, Qualifications, Skills. Thus output:

    About the role

    Travel Radiology Technologist position in Martinsburg, West Virginia. Start date: ASAP. Duration: 13 weeks. Schedule: 40 hours per week, 10‑hour rotating shifts. Employment type: Travel.

    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

    Pay

    Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

    Schedule

    40 hours per week, 10‑hour rotating shifts.

    Check: Are we repeating schedule info? Already in About the role we mentioned schedule. That's okay; we can have schedule section with more specific. The rule: Prefer a few substantive sections over many thin ones. But we have schedule separate; it's okay. We must not include job ID. Good. Check for any other substantive content: The Anders Group description about company values etc. That's not a section heading we have; could be considered "About Anders Group" but we don't have a heading for that. The instructions only list specific headings; we should not add other headings. So we should omit that descriptive prose unless it fits under a heading like About the role? It's about the company, not the role. The instructions say to use headings for those specific sections; we can include other prose outside headings? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says to use those for section headings. It also says "Output ONLY the HTML fragment". It didn't say we cannot have other headings, but we should follow the pattern. Probably better to only include those headings if we have content. The Anders Group description is not about the role, but could be considered "About the role"? No. It's about the company. There's no heading for company overview. Should we drop it? The instruction: "Preserve ALL substantive information". If we drop it, we lose substantive info about the company. But there is no appropriate heading to place it under. However we could put it under About the role as additional prose? That would be mixing company info with role info, but still substantive. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for sections. It might be okay to include a paragraph about Anders Group under About the role or maybe as a separate

    without heading? The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we could still have other headings but not necessary. To preserve all substantive info, we could add a paragraph about Anders Group under About the role or as a separate

    without heading. But the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should follow the pattern. Safer to include Anders Group description as a

    under About the role? That would be mixing but still under same heading. However the heading "About the role" suggests role-specific info; adding company description may be off-topic but still not violating. Alternatively we could create a heading "About Anders Group" but that's not in the list; risk of being considered not following instruction. I'd rather include it as a

    after the About the