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.
Job title: HCS 247 is seeking a travel CT Technologist for a travel job in Tulsa, Oklahoma.
Job Description & Requirements:
Specialty: CT Technologist
Discipline: Allied Health Professional
Start Date: 10/05/2026
Duration: 13 weeks
40 hours per week
Shift: 8 hours, nights
Employment Type: Travel
Aggressive Compensation Packages
Lodging Per-Diem for those who qualify
Meals and Incidentals Allowance for those who qualify
Travel Expense Allowance for those who qualify
Medical Dental and Vision Benefits available (For you and family)
Day 1 Medical and Voluntary Insurance eligibility for all full-time contracted professionals
401K
Daily Pay Available
Direct deposit
Free CEUs
24/7 Clinical Support
Professional and General Liability Coverage
Accident Insurance
Critical Illness Insurance
Disability Insurance
Term Life Insurance
Bridge Insurance
Identity Theft Protection
State License Assistance
New graduates are welcome to apply (HCS Only)
Unlimited Referral Bonus Program
Personal Staffing Assistance and Large Support Staff
Exceptional Customer Service (available 24 hours)
Travel Tax Filing Resources
Then later: HCS 24/7 is currently looking for Computed Tomography Tech in Tulsa, OK. This will be a 13-week assignment, 6P-2A shift starting 10/05/2026 working 40 hours per week. This will be a Local/Travel Contract and will offer the most competitive rates in the industry. Compensation will include great rates as well as maximum subsidies to those who qualify. HCS 24/7 offers both daily and weekly pay through direct deposit or cash cards as well as DAY 1 Health Benefits. You will be supported by our Clinical Director and our 24-hour support team. 1 Year of Experience Required, No New Grads.
Then: HCS 247 Job ID #1481510. Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
Then About HCS 247 description.
Then Benefits section: Holiday Pay, Guaranteed Hours, Continuing Education, Mileage reimbursement, Referral bonus, Medical benefits, Dental benefits, Vision benefits, License and certification reimbursement, Life insurance, Benefits start day 1, Weekly pay.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Job ID as heading; we can fold into short p.
We need to preserve all substantive information. Not invent or summarize away detail. Use headings only for sections with real specific content.
We need to decide which sections to include.
We have content for:
- About the role: description of job, location, shift, start date, duration, hours, employment type, etc. Could be "About the role".
- Responsibilities: Not explicitly listed; there is no list of duties. Might be omitted.
- Requirements: We have "1 Year of Experience Required, No New Grads." Also "New graduates are welcome to apply (HCS Only)" contradictory? Actually earlier says new graduates welcome (HCS Only) then later says No New Grads. Might be contradictory but we must preserve both. Could list as requirements: 1 year of experience required; new graduates welcome (HCS Only) maybe contradictory but we keep both.
- Qualifications: Could include specialty CT Technologist, Allied Health Professional, state license assistance, etc. Might be overlapping.
- Skills: Not explicit.
- Benefits: Many listed: Lodging Per-Diem, Meals and Incidentals Allowance, Travel Expense Allowance, Medical Dental Vision Benefits, Day 1 Medical and Voluntary Insurance, 401K, Daily Pay Available, Direct deposit, Free CEUs, 24/7 Clinical Support, Professional and General Liability Coverage, Accident Insurance, Critical Illness Insurance, Disability Insurance, Term Life Insurance, Bridge Insurance, Identity Theft Protection, State License Assistance, Unlimited Referral Bonus Program, Personal Staffing Assistance, Exceptional Customer Service 24/7, Travel Tax Filing Resources, Holiday Pay, Guaranteed Hours, Continuing Education, Mileage reimbursement, Referral bonus, Medical benefits, Dental benefits, Vision benefits, License and certification reimbursement, Life insurance, Benefits start day 1, Weekly pay.
We need to avoid duplication. Many items repeated. We should consolidate unique benefits.
- Pay: "Aggressive Compensation Packages", "Compensation will include great rates as well as maximum subsidies to those who qualify", "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined.", also "Daily Pay Available", "Weekly pay". So we can include Pay section with details: competitive rates, maximum subsidies, daily and weekly pay via direct deposit or cash cards, tax-free stipend TBD.
- Schedule: "40 hours per week", "Shift: 8 hours, nights", "6P-2A shift". So schedule: 40 hrs/week, 8-hour night shifts (6P-2A). Could include.
We need to avoid placeholder text like "commensurate with experience", "not specified", etc. We have "tax-free stipend amount to be determined" - that is somewhat placeholder but it's actual statement that amount TBD. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says never create Pay/Schedule/Benefits sections unless posting actually states them. It does not say we cannot include statements that include TBD inside the section; but we should avoid a heading with only filler. Since we have other substantive content besides TBD, it's okay.
We need to output only HTML fragment, no html/body tags, no markdown fences.
We'll structure:
About the role
...
Maybe
Requirements
with
Benefits
with
...
Pay
with ...
Schedule
with ...
We should not include sections that are empty or only filler.
Let's extract substantive content for each.
About the role: combine location, specialty, start date, duration, hours, shift, employment type, travel nature.
Sentence: HCS 247 is seeking a travel CT Technologist for a travel job in Tulsa, Oklahoma. Specialty: CT Technologist. Discipline: Allied Health Professional. Start Date: 10/05/2026. Duration: 13 weeks. 40 hours per week. Shift: 8 hours, nights. Employment Type: Travel. Also later: 13-week assignment, 6P-2A shift starting 10/05/2026 working 40 hours per week. Local/Travel Contract. So we can write a paragraph.
Requirements: "1 Year of Experience Required, No New Grads." Also "New graduates are welcome to apply (HCS Only)" contradictory but we keep both. Also maybe "State License Assistance" is a benefit not requirement. We'll list requirements as:
- 1 year of experience required.
- New graduates welcome to apply (HCS Only) [though also says no new grads; we keep both as per posting].
We could also include "Must hold CT Technologist certification" but not explicitly stated. So we stick to what's given.
Benefits: compile unique items:
- Lodging Per-Diem (for those who qualify)
- Meals and Incidentals Allowance (for those who qualify)
- Travel Expense Allowance (for those who qualify)
- Medical, Dental, and Vision Benefits (for you and family)
- Day 1 Medical and Voluntary Insurance eligibility for all full-time contracted professionals
- 401K
- Daily Pay Available
- Direct deposit
- Free CEUs
- 24/7 Clinical Support
- Professional and General Liability Coverage
- Accident Insurance
- Critical Illness Insurance
- Disability Insurance
- Term Life Insurance
- Bridge Insurance
- Identity Theft Protection
- State License Assistance
- Unlimited Referral Bonus Program
- Personal Staffing Assistance and Large Support Staff
- Exceptional Customer Service (available 24 hours)
- Travel Tax Filing Resources
- Holiday Pay
- Guaranteed Hours
- Continuing Education
- Mileage reimbursement
- Referral bonus
- License and certification reimbursement
- Life insurance
- Benefits start day 1
- Weekly pay
Some duplicates: Medical benefits already covered; Life insurance appears multiple times; we can deduplicate.
We'll produce a
with each distinct benefit as - .
Pay: Content: "Aggressive Compensation Packages", "Compensation will include great rates as well as maximum subsidies to those who qualify", "HCS 24/7 offers both daily and weekly pay through direct deposit or cash cards as well as DAY 1 Health Benefits.", "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Also "Daily Pay Available". We'll write a paragraph summarizing.
Schedule: "40 hours per week", "Shift: 8 hours, nights", "6P-2A shift". We'll write a paragraph.
Now ensure we don't repeat job title as heading. We'll not.
We'll not include Job ID as heading; we can include it in a short p maybe under About the role or separate small p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can add a
with Job ID: HCS 247 Job ID #1481510.
We should also remove duplicated lines and boilerplate like "About HCS 247" description (that's about the company, not the role). The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About HCS 247" is not boilerplate but it's company description; maybe we can keep as part of About the role? The instruction says "Prefer a few substantive sections over many thin ones." Could include a short paragraph about the company under About the role or maybe separate section "About the company". But they only listed allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings like About the company. We can incorporate relevant company info into About the role if it's substantive. The About HCS 247 paragraph describes the organization; could be considered part of About the role (context). We'll include a short sentence.
We must not include navigation etc.
Now produce HTML.
We'll open with
About the role
then ...
Then maybe Requirements