Travel Radiology Technician - $2,050 per week

We need to output HTML fragment with sections for headings present: About the role? The posting includes "Job Description & Requirements" but not explicit headings. We need to infer sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must only include sections when posting has real specific content. Let's parse content: - Job title: travel Radiology Technician. - Specialty: Radiology Technician - Discipline: Allied Health Professional - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Benefits listed: 401k with 100% match, Guaranteed hours pay, Weekly pay & tax-free stipends, & more! - Then "7A-7P THURS-SAT 3X12S RAD TECH DAYS Position ID 1025827" - Then description about HealthTrust Workforce Solutions HCA (mission etc.) - Then Benefits list: Dental benefits, Vision benefits, Referral bonus, Continuing Education, Life insurance We need to avoid repeating job title as heading. No Job ID as heading. Remove boilerplate, navigation, legal, EEO, etc. There's none. We need to produce sections with headings where content exists. Potential sections: - About the role: could include description of role: Specialty, Discipline, Duration, Hours, Shift, Employment Type, Shift schedule (7A-7P THURS-SAT 3X12S RAD TECH DAYS). That's specifics. - Responsibilities: Not explicitly listed. The posting doesn't list duties. So we should not create Responsibilities section if no specific content. - Requirements: Not listed explicitly besides specialty/discipline? Might be considered requirements but not detailed. Probably better to not create Requirements unless we have specifics like certifications, experience. Not present. - Qualifications: Not present. - Skills: Not present. - Benefits: We have benefits list: 401k with 100% match, Guaranteed hours pay, Weekly pay & tax-free stipends, Dental benefits, Vision benefits, Referral bonus, Continuing Education, Life insurance. Also "& more!" but we should not include vague. We'll list the specific ones. - Pay: Not explicitly stated aside from "Weekly pay & tax-free stipends". That's pay info. Could be considered Pay section. The phrase "Weekly pay & tax-free stipends" indicates pay structure. We can include Pay section with that detail. - Schedule: We have shift details: 12 hours, days; 7A-7P THURS-SAT 3X12S RAD TECH DAYS. Also 36 hours per week. So we can include Schedule section. We must not create sections with filler like "commensurate with experience". We have actual specifics. Thus sections: About the role, Benefits, Pay, Schedule. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information. Let's craft. About the role: include Specialty, Discipline, Duration, Hours per week, Shift, Employment Type, Shift schedule (7A-7P THURS-SAT 3X12S RAD TECH DAYS). Also maybe mention Position ID? We should not put Job ID as heading but can fold minor metadata into short

  or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include Position ID in a short paragraph maybe under About the role or separate small paragraph. Probably include as a short

  after the list. We need to avoid repeating job title as heading. So we won't have heading "Radiology Technician". We'll just have sections. We need to output only HTML fragment, no /, no markdown. Let's draft:

  About the role

  Specialty: Radiology Technician; Discipline: Allied Health Professional; Duration: 13 weeks; Hours: 36 hours per week; Shift: 12‑hour days; Employment Type: Travel.

  Typical schedule: 7 A.M.–7 P.M., Thursday‑Saturday (3×12‑hour shifts). Position ID: 1025827.

  But we need to use
  • for any list of duties/requirements/benefits. For About the role, it's not a list but prose; we can use

    . That's fine. Benefits: list specific benefits: 401k with 100% match, Guaranteed hours pay, Weekly pay & tax-free stipends, Dental benefits, Vision benefits, Referral bonus, Continuing Education, Life insurance. Also "& more!" but we should not include vague. We'll list the specific ones. Pay: we have "Weekly pay & tax-free stipends". That's already in benefits but could be separate Pay section. However we might combine Pay into Benefits? The instruction: prefer few substantive sections over many thin ones. Could combine Pay and Benefits? But they ask to use headings for Benefits, Pay, Schedule if posting actually states them. The posting states "Weekly pay & tax-free stipends" and also "401k with 100% match" and "Guaranteed hours pay". Those are pay/benefits. Could create a Benefits section that includes all those. Pay section might be redundant. Since they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay info (Weekly pay & tax-free stipends). So we could have a Pay section with that detail. But we also have benefits like 401k, dental, vision etc. So we could have both Pay and Benefits sections. However to avoid thin sections, we could combine pay info into Benefits section as part of benefits. But the instruction says "Prefer a few substantive sections over many thin ones." If we make both Pay and Benefits, that's two sections; maybe still okay. But we could also have just Benefits that includes pay-related items. However they specifically mention Pay as a possible heading; if we omit Pay, we might be missing that specific info. But we could include pay info inside Benefits as a bullet. That would still preserve the info. The instruction: "include a section ONLY when the posting has real, specific content for it". Pay section would have content: Weekly pay & tax-free stipends. That's specific. So we could include Pay section. But then Benefits section would also have content. That's okay. But we need to avoid duplication: Weekly pay & tax-free stipends appears in both Pay and Benefits if we list it there. Better to not duplicate. So we could put pay info in Pay section, and other benefits in Benefits section. Thus:

    Pay

    • Weekly pay & tax-free stipends

    Benefits

    • 401k with 100% match
    • Guaranteed hours pay
    • Dental benefits
    • Vision benefits
    • Referral bonus
    • Continuing Education
    • Life insurance
    Schedule: we have shift details: 12 hours, days; 36 hours per week; 7A-7P THURS-SAT 3X12S RAD TECH DAYS. We'll put in
    maybe.

    Schedule

    • 36 hours per week
    • 12‑hour day shifts
    • Typical schedule: 7 A.M.–7 P.M., Thursday‑Saturday (3×12‑hour shifts)
    Now About the role: we could also include list? But it's fine as

    . We need to ensure we don't include any boilerplate like mission statement? The mission statement is part of the description about HealthTrust. That is substantive? It's about the company. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The mission statement is substantive about the company. Should we include it? It's not a standard heading but could be part of About the role or a separate section like "About the company". However headings list only includes specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". So we should not create a heading outside those. We could fold the mission statement into About the role as prose? But About the role is supposed to be about the role, not company. However we could include it as a short paragraph under About the role? Might be stretching. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings for sections. It doesn't forbid other headings, but says use those for section headings. Likely we should stick to those headings. So we should not add a heading for company mission. We could incorporate that info into About the role as a short paragraph? Might be considered not about role but still we can include as part of description. The instruction: "Preserve ALL substantive information". If we omit mission statement, we lose info. So we need to include it somewhere. Perhaps we can include it as a

    after About the role without a heading, just a paragraph. That's allowed because we can have prose outside headings. The instruction only says to use those headings for sections; doesn't forbid extra paragraphs. So we can have a paragraph describing the company after About the role. Thus structure:

    About the role

    Specialty: Radiology Technician; Discipline: Allied Health Professional; Duration: 13 weeks; Hours: 36 hours per week; Shift: 12‑hour days; Employment Type: Travel.

    Typical schedule: 7 A.M.–7 P.M., Thursday‑Saturday (3×12‑hour shifts). Position ID: 1025827.

    Pay

    • Weekly pay & tax-free stipends

    Benefits

    • 401k with 100% match
    • Guaranteed hours pay
    • Dental benefits
    • Vision benefits
    • Referral bonus
    • Continuing Education
    • Life insurance

    Schedule

    • 36 hours per week
    • 12‑hour day shifts
    • Typical schedule: 7 A.M.–7 P.M., Thursday‑Saturday (3×12‑hour shifts)
    Then we can add a paragraph about HealthTrust mission etc. as a

    after sections. Let's craft that paragraph: "At HealthTrust Workforce Solutions, healthcare is not just about the four walls of a facility but about the people who provide and receive care. Our focus is on empowering healthcare professionals to deliver exceptional patient experiences by providing them with the necessary skills, tools, and support. We partner with healthcare facilities nationwide to ensure that the right professionals are in the right roles. We prioritize our clinicians by giving them a voice and access to opportunities to fulfill their mission of improving lives by providing quality patient care. We are committed to our core values of Trust, Innovation, Adaptability, Courage, and Accountability. We are dedicated