Travel CT Technologist - $2,674 per week

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and apply the rules. First, identify the job title: "travel CT Technologist" - but the rule says do NOT repeat the job title as a heading (the page already shows it). So I won't include an h3 for the title. Now, sections to consider: - About the role / Job Description - Requirements / Qualifications - Benefits - Pay / Schedule - About the company (Anders Group) The posting has: - Job details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Job ID, Pay package info, Posted job title, Shift times. - About Anders Group section (company description) - Benefits list (appears twice: once in "What You Can Expect" and again at the end under "Benefits") I need to structure into semantic HTML with h3 headings for sections, ul/li for lists, p for prose. Rules: - Use h3 for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use ul/li for any list of duties/requirements/benefits - Use p for prose - Do NOT repeat job title as heading - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short p or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Let's parse the content: The posting starts with: "Anders Group is seeking a travel CT Technologist for a travel job in Shelton, Washington." That's a prose intro. Then "Job Description & Requirements" but no actual description of duties? It lists: - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: 11/02/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Anders Group Job ID #1414308 - Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: Imaging Technologist - X-Ray/CT - 7:00am-7:30pm: 7:00 AM - 7:30 PM This is metadata about the job. Could be under "Job Details" or "About the role". Since there's no explicit responsibilities list, maybe we can create a "Job Details" section with a list. Then "About Anders Group" with subsections: "Why Anders?", "What You Can Expect", "The Anders Difference". This is company info. Could be under "About the Company". Then "Benefits" list (duplicated). We'll include a Benefits section with the list. Pay: The posting mentions "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific pay rate, but it's information about pay structure. The rule says never create Pay section unless the posting actually states them. It does state something about pay package, but it's vague. However, it's substantive info about pay structure. I think we can include a "Pay" section with that info. Schedule: The posting includes shift details: "Shift: 12 hours, days", "36 hours per week", "7:00am-7:30pm: 7:00 AM - 7:30 PM". That's schedule info. Could be under "Schedule" section. Requirements/Qualifications: Not explicitly listed. The posting doesn't have a list of requirements. So we shouldn't create a Requirements section. Skills: Not listed. Thus, sections to include: 1. About the role (or Job Details) - with list of job metadata 2. Schedule - with shift details 3. Pay - with pay package description 4. About the Company - with company description 5. Benefits - with benefits list But the rule: "Prefer a few substantive sections over many thin ones." Could combine Job Details and Schedule? But they are distinct. However, schedule is part of job details. Might keep separate. Let's structure:

About the role

Anders Group is seeking a travel CT Technologist for a travel job in Shelton, Washington.

• Specialty: CT Technologist
• Discipline: Allied Health Professional
• Start Date: 11/02/2026
• Duration: 13 weeks
• Hours per week: 36
• Shift: 12 hours, days
• Employment Type: Travel
• Posted job title: Imaging Technologist - X-Ray/CT

Note: Job ID #1414308 is minor metadata, fold into a short p or drop. I'll drop it.

Schedule

• Shift: 12 hours, days
• Hours per week: 36
• Shift times: 7:00 AM - 7:30 PM

But shift already mentioned in About the role. Could avoid duplication. But the rule says preserve ALL substantive information. Duplication across sections is okay if it's in different contexts. However, we can include schedule details in About the role and not have a separate Schedule section. But the rule says include a section ONLY when the posting has real, specific content for it. The posting has specific shift times. Could be a Schedule section.

Pay

Pay package is based on 12 hour shifts and 36 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.

Why Anders?

Anders Group is committed to delivering exceptional customer service, personalized support, and access to some of the best-paying travel opportunities nationwide. Travelers are treated as partners, not just placements.

What You Can Expect

From your very first assignment, you’ll have access to a comprehensive benefits package designed to support you both professionally and personally:

• 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

The Anders Difference

You’re committed to providing exceptional patient care and we’re committed to supporting you every step of the way. By aligning your goals with the needs of top healthcare facilities across the country, we create assignments that truly fit, professionally and personally.

But note: The benefits list appears again at the end under "Benefits". That's duplicate. We should include benefits only once. The "What You Can Expect" list is essentially benefits. The final "Benefits" list is a subset. We'll include a Benefits section with the combined unique benefits. Better to have a Benefits section separate from About the Company. The rule says use h3 for section headings like Benefits. So we can have:

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 many are duplicates. We should deduplicate. The first list is more detailed. The second list is generic. We'll keep the first list and maybe add any unique from second. The second list items are already covered. So just use the first list. But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include all benefits mentioned. The second list might be considered a summary. But it's duplicate. I think we can include the more detailed list from "What You Can Expect". That's substantive. Now, the About the Company section could include the company description and the "Why Anders?" and "The Anders Difference". But we might not need subheadings (h4) because the rule only mentions h3 for section headings. It doesn't forbid h4, but it says use h3 for section headings. We can use h3 for main sections and maybe h4 for subsections? The rule doesn't explicitly forbid h4, but it says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use h4. However, to keep it simple, we can use h3 for main sections and use p for prose. The "Why Anders?" and "The Anders Difference" are part of the company description. We can incorporate them as paragraphs. Let's structure:

About the role

Anders Group is seeking a travel CT Technologist for a travel job in Shelton, Washington.

• Specialty: CT Technologist
• Discipline: Allied Health Professional
• Start Date: 11/02/2026
• Duration: 13 weeks
• Hours per week: 36
• Shift: 12 hours, days
• Employment Type: Travel
• Posted job title: Imaging Technologist - X-Ray/CT

Schedule

• Shift: 12 hours, days
• Hours per week: 36
• Shift times: 7:00 AM - 7:30 PM

Pay

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

About the Company

Anders Group