Travel CT Technologist - $2,578 per week

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, identify the job title: "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 job title. Now, sections present in the posting: 1. Job Description & Requirements - includes specialty, discipline, start date, duration, hours per week, shift, employment type. This is metadata about the job. Could be a section "Job Details" or similar. But the rule says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. The Job ID is mentioned: "Trustaff Allied Job ID #2214359." That's minor metadata, can be folded into a paragraph. 2. About the role: There's a paragraph describing the role: "As a CT Technologist, you'll capture important diagnostic images..." That could be "About the role" section. 3. About Trustaff Allied: This is company description. Could be "About the company" or "About Trustaff Allied". But the rule says include a section ONLY when the posting has real, specific content for it. This is company boilerplate, but it's specific to the agency. Might be considered "About the company". However, the rule says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is company marketing, but it's part of the posting. I think we should include it as a section "About Trustaff Allied" or "About the company". But the rule says prefer a few substantive sections over many thin ones. This is somewhat substantive. 4. Benefits: There's a list of benefits: "Priority access to thousands of travel healthcare jobs, Industry-leading pay, Guaranteed weekly hours, Experienced recruiters, Comprehensive benefits, including medical, dental, and vision, 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more". Then later a separate "Benefits" heading with "Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus". This is duplicated. We should consolidate into one Benefits section with a list. 5. Pay: The posting says "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific pay amount, but it's information about pay structure. The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package details, so we could include a Pay section. But the pay amount is "to be determined". The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is essentially TBD. So maybe we should not create a Pay section. However, the pay package description is more than just TBD; it includes basis (10 hour shifts, 40 hours per week). Could be included in a "Pay" section with a paragraph. But the rule says never create Pay section unless the posting actually states them. It does state pay package details, but the amount is TBD. I think we can include a Pay section with the details given, but avoid placeholder. The rule says "never emit a heading followed by filler/placeholder text". If we include a Pay section, we must have substantive content. The content: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat substantive, but the stipend amount is TBD. Might be considered filler. I'll include it as a paragraph in a "Pay" section? Let's see. 6. Schedule: The posting includes shift: "Shift: 10 hours, nights" and "40 hours per week". That's schedule information. Could be a "Schedule" section. But again, the rule says never create Schedule section unless the posting actually states them. It does state shift and hours. So we could include a Schedule section. But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine Job Details, Schedule, Pay into one "Job Details" section? However, the rule says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect separate sections for Pay and Schedule if present. But only if substantive. Let's examine the content for each potential section: - About the role: There's a paragraph describing the role. That's substantive. - Responsibilities: Not explicitly listed. The role description mentions "capture important diagnostic images by working directly with the patient" and "expert knowledge of the imaging process, so you must be well-versed in the imaging equipment and its operation." That's more like requirements/qualifications. No explicit responsibilities list. - Requirements: The posting lists "Specialty: CT Technologist, Discipline: Allied Health Professional, Start Date: 11/16/2026, Duration: 13 weeks, 40 hours per week, Shift: 10 hours, nights, Employment Type: Travel". Also "CT Techs and Radiologists must have expert knowledge of the imaging process, so you must be well-versed in the imaging equipment and its operation." That's a requirement. Could be a Requirements section. - Qualifications: Not explicitly listed beyond the above. - Skills: Not listed. - Benefits: There is a list of benefits. That's substantive. - Pay: As discussed. - Schedule: Shift and hours. - About the company: The "About Trustaff Allied" section. Now, the rule: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So I'll create sections for: 1. About the role (h3) with the paragraph. 2. Requirements (h3) with a list of requirements (specialty, discipline, start date, duration, hours, shift, employment type, and the expertise requirement). But note: start date, duration, hours, shift, employment type are job details, not necessarily requirements for the candidate. However, they are requirements of the job. Could be "Job Details" but the example headings include "Requirements". The rule says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Requirements" is an example. I think "Requirements" is appropriate for candidate requirements. The job details like start date, duration, shift are more like "Job Details". But the rule doesn't list "Job Details" as an example. However, we can use "Job Details" as a heading if it's substantive. The rule says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." means examples, not exhaustive. So we can use other headings if needed. But we should prefer those standard ones. Maybe we can have: - About the role - Requirements (for candidate qualifications) - Job Details (for start date, duration, shift, etc.) - Benefits - About Trustaff Allied But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine Job Details and Requirements into one "Requirements" section? But they are different: one is candidate requirements, the other is job parameters. However, the posting doesn't have a clear candidate requirements list beyond the expertise. The "Job Description & Requirements" heading in the posting includes both. So we could have a "Job Description & Requirements" section with prose and list. Let's structure: - About the role: paragraph. - Job Details: list of job parameters (specialty, discipline, start date, duration, hours per week, shift, employment type). Also include the Job ID in a paragraph. - Requirements: list of candidate requirements (expert knowledge of imaging process, well-versed in imaging equipment). Could be a list. - Benefits: list of benefits. - About Trustaff Allied: paragraph(s) about the company. - Pay: paragraph about pay package. - Schedule: maybe included in Job Details. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated. Pay is stated but with TBD. Schedule is stated. So we could include Pay and Schedule sections. However, the Pay section would have only one paragraph with "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat thin but it's actual content. The rule says never emit a heading followed by filler/placeholder text. "tax-free stipend amount to be determined" is placeholder. But the rest is not. I think it's okay to include. Similarly, Schedule: "Shift: 10 hours, nights" and "40 hours per week". That's thin but specific. But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine Pay and Schedule into Job Details? Or include them as part of Job Details. Let's look at the example headings: they include Pay and Schedule as separate. But the rule says only include if substantive. I'll include them if they have specific info. Let's decide on sections: 1. About the role (h3) - paragraph. 2. Job Details (h3) - list of job parameters (specialty, discipline, start date, duration, hours per week, shift, employment type). Also include Job ID in a paragraph. 3. Requirements (h3) - list of candidate requirements (expert knowledge of imaging process, well-versed in imaging equipment operation). Could be a list. 4. Benefits (h3) - list of benefits (consolidated from both lists). 5. About Trustaff Allied (h3) - paragraph(s) about the company. 6. Pay (h3) - paragraph about pay package. 7. Schedule (h3) - maybe just shift and hours, but already in Job Details. Could omit Schedule section to avoid duplication. But the rule says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all. We'll use what's appropriate. I think the posting has: - About the role: yes. - Responsibilities: not explicitly. - Requirements: yes (candidate requirements). - Qualifications: not separate. - Skills: not. - Benefits: yes. - Pay: yes (though TBD). - Schedule: yes (shift and hours). - About the company: yes. But we need to avoid thin sections. Pay is thin. Schedule is thin and duplicates Job Details. I'll include Pay but not Schedule. I'll include Job Details as a section (maybe "Job Details" not in example but okay). Or we could call it "Position Details". The rule says "use

for section headings (e.g. ...)" so we can use other headings. Let's write the HTML. First, About the role:

About the role

As a CT Technologist, you'll capture important diagnostic images by working directly with the patient. CT Techs and Radiologists must have expert knowledge of the imaging process, so you must be well-versed in the imaging equipment and its operation.

Second, Job Details:

Job Details

• Specialty: CT Technologist
• Discipline: Allied Health Professional
• Start Date: 11/16/2026