Travel Xray Tech - $2,350 per week

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate. We need to parse the posting. Content: - Anders Group is seeking a travel Radiology Technologist for a travel job in Gig Harbor, Washington. - Job Description & Requirements Specialty: Radiology Technologist Discipline: Allied Health Professional Start Date: 10/19/2026 Duration: 13 weeks 40 hours per week Shift: 10 hours, days Employment Type: Travel Anders Group Job ID #1403002. 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 - About Anders Group (some description) - Why Anders? ... (some prose) - What You Can Expect: list of benefits (Day One Health Insurance..., 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) - The Anders Difference (some prose) - Benefits (list: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus) We need to extract substantive info: role details: specialty, discipline, start date, duration, hours per week, shift, employment type, location (Gig Harbor, Washington). Also maybe job ID but we should not put as heading; can fold into short p. 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." This is vague; we should not create Pay section unless posting actually states them. It does mention pay package based on shifts, but stipend amount TBD. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's somewhat vague but still states something about pay. However "tax-free stipend amount to be determined" is not specific. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined" which is TBD-like. So we should not create a Pay section if it's just TBD. The phrase "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation)" is somewhat specific about basis but not amount. Might be considered filler. Safer to omit Pay section. Schedule: we have shift: 10 hours, days; 40 hours per week. That's specific. So we can include Schedule section with that info. Benefits: we have a list of benefits from Anders Group description: 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. Also later Benefits list: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. We need to preserve ALL substantive information; do not invent or summarize away detail. We should combine but not duplicate. We need to output a Benefits section with

• items. Should we include all distinct items? Let's list unique benefits: - Day One Health Insurance (with buy-up options) - Dental & Vision Insurance (or separate Dental benefits, Vision benefits) - Life Insurance - 401(k) Retirement Plan - Competitive, Premium Pay Packages (maybe duplicate with pay but it's a benefit) - Licensure & CEU Reimbursement - Daily Per Diems & Travel Reimbursements - Rental Car Allowances - Continuing Education Resources - Referral Bonuses - Medical benefits (maybe same as Health Insurance) - Dental benefits - Vision benefits - License and certification reimbursement (same as Licensure & CEU Reimbursement) - Continuing Education (similar to Continuing Education Resources) - Referral bonus (same as Referral Bonuses) We should avoid duplication but preserve all substantive info. Could combine similar items: Health Insurance (Medical), Dental, Vision, Life, 401k, Licensure/CEU reimbursement, Per diems/travel reimbursement, Rental car allowance, Continuing education, Referral bonus, Competitive premium pay packages. We need to decide what to include. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not omit any benefit mentioned. But we can combine duplicates if they are essentially same meaning. However "Day One Health Insurance (with buy-up options)" vs "Medical benefits" and "Health Insurance" maybe same. But to preserve detail, we could list both as separate items? That would be duplicative but not invented. Might be okay but could be seen as summarizing away detail? Not sure. Safer to list each distinct phrase as they appear, but avoid exact duplicates. Let's extract from the text: 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" later: - Medical benefits - Dental benefits - Vision benefits - Life insurance - 401k retirement plan - License and certification reimbursement - Continuing Education - Referral bonus We can combine: Medical benefits ~ Day One Health Insurance (with buy-up options). Dental benefits & Vision benefits vs Dental & Vision Insurance (similar). Life insurance same. 401k retirement plan same. License and certification reimbursement same as Licensure & CEU Reimbursement. Continuing Education vs Continuing Education Resources similar. Referral bonus same. Thus we could produce a Benefits section with 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 - Dental benefits - Vision benefits - License and certification reimbursement - Continuing Education - Referral bonus But that repeats many. Might be considered summarizing away detail? Actually we are preserving detail but repeating. Might be okay but could be seen as not optimal. The instruction: "Prefer a few substantive sections over many thin ones." Not about duplicates within a section. It doesn't forbid duplicates. However "do NOT invent or summarize away detail." Duplicates preserve detail but may be redundant. I'd lean to combine to avoid redundancy while preserving the substance: we can note that benefits include medical, dental, vision, life, 401k, licensure/CEU reimbursement, per diems/travel, rental car, continuing education, referral bonus, competitive premium pay packages. Also note Day One Health Insurance with buy-up options (that's medical). So we can phrase as: - 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 That covers all unique benefits. The later list's items are subsets of these. So we are not losing detail; we are summarizing but not losing any unique benefit. The instruction says do NOT summarize away detail. Summarizing could be considered losing detail if we combine "Medical benefits" and "Day One Health Insurance (with buy-up options)" into just "Health Insurance". But we kept Day One Health Insurance (with buy-up options) which is more specific than generic medical benefits. So we are preserving detail. The generic "Medical benefits" is less specific; we have the more specific. So it's fine. Thus Benefits section with those items. Schedule: we have shift: 10 hours, days; 40 hours per week. So we can put in

  or

  . Since it's a single statement, we can use

  . About the role: we need a section About the role (heading). Content: specialty, discipline, start date, duration, hours per week, shift, employment type, location. Also maybe job ID? We can include job ID in a short p. Responsibilities: The posting does not list specific responsibilities beyond generic? It says "Job Description & Requirements" then lists specialty etc. No explicit responsibilities list. So we should not create Responsibilities section if no specific content. Requirements: Not listed explicitly; we have specialty, discipline, etc. Those could be considered qualifications. But we have Qualifications section maybe. The posting does not have separate requirements list. So we can skip Requirements. Qualifications: Could include specialty, discipline, maybe licensure? Not explicit. But we have "Specialty: Radiology Technologist" and "Discipline: Allied Health Professional". That's more about the role. Could treat as Qualifications. But we need to decide if we have enough content. The instruction: include a section ONLY when the posting has real, specific content for it. So we can put Qualifications with those items. Skills: Not listed. Thus sections: About the role, Qualifications, Benefits, Schedule. Possibly also Pay? We decided not. We need to output HTML fragment with

  headings and

  • for lists,

    for prose. Let's craft:

    About the role

    Location: Gig Harbor, Washington. Specialty: Radiology Technologist. Discipline: Allied Health Professional. Start Date: October 19, 2026. Duration: 13 weeks. Hours: 40 hours per week. Shift: 10‑hour days. Employment Type: Travel. Anders Group Job ID #1403002.

    Qualifications

    • Radiology Technologist specialty
    • Allied Health Professional discipline
    But that seems thin. Maybe we can combine About the role and Qualifications? But we need separate headings only if content exists. Qualifications content is minimal but still specific. Could be okay. Alternatively we could omit Qualifications and put those details in About the role. That would reduce sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine into About the role and skip Qualifications. Thus we will have About the role with all details. Benefits section as list. Schedule section as

    . Let's verify we are not missing any other substantive content: The Anders Group description about company is not required for job posting? It's about the company, but could be considered "About Anders Group". However we only have headings for standard sections; we could include an "About Anders Group" section if we want, but not in the list of