Travel CT Tech - $2,632 per week

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Job title: travel CT Technologist. Not to repeat as heading. We need to extract sections: - About the role: maybe description of role? The posting includes "Job Description & Requirements" then details: Specialty: CT Technologist, Discipline: Allied Health Professional, Start Date: 10/12/2026, Duration: 26 weeks, 40 hours per week, Shift: 8 hours, evenings, Employment Type: Travel. Also description about LRS Healthcare. But "About the role" could be the description of the job: maybe the paragraph after "Job Description & Requirements". Let's see: after that heading, they list bullet-like lines: Specialty: CT Technologist, Discipline: Allied Health Professional, Start Date: 10/12/2026, Duration: 26 weeks, 40 hours per week, Shift: 8 hours, evenings, Employment Type: Travel. Then a paragraph about LRS Healthcare connecting professionals etc. That's more about the company. Could be "About LRS Healthcare - Allied". But we need to decide. We have also a separate "About LRS Healthcare - Allied" section later. Thus we can have sections: - About the role: maybe the description of the role (Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type). Could be presented as list. - Responsibilities: Not explicitly listed. The posting does not list specific duties. So we should not create Responsibilities section if no specific content. - Requirements: maybe the qualifications? Not explicit. There's "Certification & License Reimbursement" in benefits but not requirements. No explicit requirements like "must have ARRT certification". Not present. So we skip Requirements. - Qualifications: Not present. - Skills: Not present. - Benefits: There are benefits listed twice: first bullet list: Streamlined, simple credentialing process through the LRS Connect App; Health, Dental, and Vision Insurance; Life and Disability Insurance; 401(k) with Employer Match; Generous Referral Bonus Program; Employee Assistance Program (EAP); Weekly Direct Deposit; 24/7/365 Support. Then later another Benefits list: Medical, Dental, and Vision; Short-Term Disability; Long-Term Disability; Life Insurance; 401(k); Certification & License Reimbursement; Refer-a-friend Bonus Program; Direct Deposit - Weekly; 24-Hour Support. We need to combine and preserve all substantive info, no duplication? We should preserve all but avoid duplicate lines. We'll combine unique items. - Pay: The posting says: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific number, it's vague. According to rule: do NOT create Pay section unless posting actually states them. It states something but it's not a specific amount; it's "based on 8 hour shifts and 40 hours per week ... tax-free stipend amount to be determined." That's still not a concrete figure. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it's "tax-free stipend amount to be determined." That's similar to TBD. So we should not create Pay section. - Schedule: The posting includes Shift: 8 hours, evenings; 40 hours per week. That's schedule info. So we can create Schedule section with those details. - Also we have Start Date, Duration. Could be part of About the role or maybe a separate section like "Assignment Details". But we only allowed headings from list. Could put them under About the role as list. Thus sections: About the role (contains Start Date, Duration, Hours, Shift, Employment Type, Specialty, Discipline). Benefits (combined). Schedule (maybe just shift/hours). Could also include Pay? No. We must not repeat job title as heading. Use

for each section. We need to output only HTML fragment. Let's craft:

About the role

Specialty: CT Technologist

Discipline: Allied Health Professional

Start Date: 10/12/2026

Duration: 26 weeks

Hours: 40 hours per week

Shift: 8 hours, evenings

Employment Type: Travel

Alternatively could use

• for list. The rule: Use
  • for any list of duties/requirements/benefits, and

    for prose. For About the role, it's not a list of duties/requirements/benefits, but it's metadata. Could be prose. But we can also use

    lines. Probably fine. Better to use

    for each line? Might be okay. Or we could combine into a

    with line breaks
    . But using multiple

    is okay. Benefits: need to list items. Use

    • . Combine benefits: - Streamlined, simple credentialing process through the LRS Connect App - Health, Dental, and Vision Insurance - Life and Disability Insurance - 401(k) with Employer Match - Generous Referral Bonus Program - Employee Assistance Program (EAP) - Weekly Direct Deposit - 24/7/365 Support - Medical, Dental, and Vision (duplicate of Health, Dental, and Vision? Slightly different wording; but we can keep both? Might be duplicate. We'll deduplicate: Health, Dental, and Vision Insurance covers medical, dental, vision. So we can keep one.) - Short-Term Disability - Long-Term Disability - Life Insurance (already covered by Life and Disability Insurance? That includes life and disability. We'll keep Life Insurance separate? Might be duplicate. We'll keep Life and Disability Insurance as one.) - Certification & License Reimbursement - Refer-a-friend Bonus Program (similar to Generous Referral Bonus Program) - Direct Deposit - Weekly (same as Weekly Direct Deposit) - 24-Hour Support (same as 24/7/365 Support) We need to preserve all substantive information; but we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly say to deduplicate, but we should not repeat duplicated lines. It says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate. Thus final benefits list unique items: - Streamlined, simple credentialing process through the LRS Connect App - Health, Dental, and Vision Insurance - Life and Disability Insurance - 401(k) with Employer Match - Generous Referral Bonus Program - Employee Assistance Program (EAP) - Weekly Direct Deposit - 24/7/365 Support - Short-Term Disability - Long-Term Disability - Certification & License Reimbursement - Refer-a-friend Bonus Program (maybe same as Generous Referral Bonus Program; we consider duplicate; remove) Actually "Generous Referral Bonus Program" and "Refer-a-friend Bonus Program" are same; keep one. Thus final list: - Streamlined, simple credentialing process through the LRS Connect App - Health, Dental, and Vision Insurance - Life and Disability Insurance - 401(k) with Employer Match - Generous Referral Bonus Program - Employee Assistance Program (EAP) - Weekly Direct Deposit - 24/7/365 Support - Short-Term Disability - Long-Term Disability - Certification & License Reimbursement Check if any missing: The first list had "Life and Disability Insurance". The second had "Short-Term Disability", "Long-Term Disability", "Life Insurance". We kept Life and Disability Insurance (covers both). Could also keep Short-Term and Long-Term as separate but they'd be duplicate of Life and Disability? Actually Life and Disability Insurance likely includes both life and disability (maybe short and long). To be safe, we could keep both Life and Disability Insurance and Short-Term Disability and Long-Term Disability as separate? But that might be redundant. The instruction: remove duplicated lines. If they are substantively different (short-term vs long-term), they are not duplicates. However "Life and Disability Insurance" is ambiguous; could be a combined plan. The second list separates them. To preserve all substantive info, we should include both the combined and the separate? That might be duplication but not exactly same text. Safer to include all three: Life and Disability Insurance, Short-Term Disability, Long-Term Disability. But that could be considered overlapping. However we are not told to merge semantics; just remove duplicated lines (identical lines). Since lines are not identical, we keep them. Thus benefits list: - Streamlined, simple credentialing process through the LRS Connect App - Health, Dental, and Vision Insurance - Life and Disability Insurance - Short-Term Disability - Long-Term Disability - 401(k) with Employer Match - Generous Referral Bonus Program - Employee Assistance Program (EAP) - Weekly Direct Deposit - 24/7/365 Support - Certification & License Reimbursement Check also "Refer-a-friend Bonus Program" duplicate of Generous Referral Bonus Program; we keep one. Now Schedule section: we have Shift: 8 hours, evenings; Hours: 40 hours per week. Could present as list. Thus:

      Schedule

      • Shift: 8 hours, evenings
      • Hours: 40 hours per week
      Now About the role: we could also include Start Date, Duration, etc as list. Thus:

      About the role

      • Specialty: CT Technologist
      • Discipline: Allied Health Professional
      • Start Date: 10/12/2026
      • Duration: 26 weeks
      • Hours: 40 hours per week
      • Shift: 8 hours, evenings
      • Employment Type: Travel
      But note Hours and Shift duplicated in Schedule section. That's duplication across sections; but the instruction about duplicated lines refers to within the posting, not across our output? It says remove duplicated lines (presumably from the source). It's okay to have same info in multiple sections if needed? Might be considered duplication but we are structuring. However we could avoid duplication by not repeating Hours and Shift in About the role if we put them in Schedule only. But About the role could contain other details like Specialty, Discipline, Start Date, Duration, Employment Type. We'll keep Hours and Shift only in Schedule to avoid duplication. Thus About the role list: - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: 10/12/2026 - Duration: 26 weeks - Employment Type: Travel Now Schedule list as above. Now Benefits list as above. Now we need to ensure we don't include empty sections. Thus final HTML:

      About the role

      • Specialty: CT Technologist
      • Discipline: Allied Health Professional
      • Start Date: 10/12/202