Travel CT Technologist - $3,691 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 sections: - Job details: specialty, discipline, start date, duration, hours per week, shift, employment type - Job description: "As a CT Technologist, you'll capture important diagnostic images..." - About Trustaff Allied: company description - Benefits: listed at the end Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Do NOT repeat job title as heading - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text - 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 Now, let's structure: The posting has: - Job details (metadata): specialty, discipline, start date, duration, hours per week, shift, employment type, job ID, pay package note - Job description: one paragraph about role - About Trustaff Allied: company description - Benefits: list of benefits I need to decide on sections. The rules suggest headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But only include if there's real content. The job description is about the role, so "About the role" could be a heading with the paragraph. There's no explicit responsibilities list, requirements list, qualifications list, skills list. The description is generic. There is a benefits list at the end: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. So Benefits section is appropriate. There is pay information: "Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's specific enough for a Pay section? The rule says never create Pay section unless the posting actually states them. It does state pay package details, though stipend amount is TBD. But it's still information. However, the rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The pay package says "tax-free stipend amount to be determined." That's TBD. But there is other info: based on 12 hour shifts and 48 hours per week. Could include that in a Pay section, but maybe better to fold into a short

  in About the role or a separate Details section? The rules say use

  for section headings like Pay, Schedule. But only if real content. Since stipend is TBD, maybe not create a Pay section. However, the schedule info is there: 48 hours per week, shift: 12 hours, days. That could be a Schedule section. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule: 48 hours per week, shift: 12 hours, days. So Schedule section could be created. Pay: states pay package based on shifts and hours, but stipend TBD. Might still be considered stating pay structure. But the example filler includes "TBD". So maybe avoid Pay section. Better to create a "Job Details" section? But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "Job Details". However, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, but we should stick to those? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those. However, we should only include sections when there's real content. The job details metadata could be folded into a short

  at the top or under About the role. Let's think: The posting starts with "Trustaff Allied is seeking a travel CT Technologist for a travel job in Turnersville, New Jersey." Then "Job Description & Requirements" then list of specialty, discipline, start date, duration, hours per week, shift, employment type. Then "Trustaff Allied Job ID #2214522. Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: CT Technologist" Then "About Trustaff Allied" with description and bullet points (reasons people choose us). Then "Benefits" with list. So I can structure as: - About the role: includes the description paragraph and maybe the job details metadata in a paragraph. - Schedule: includes hours per week, shift details. - About Trustaff Allied: company description and the bullet points (reasons people choose us) as a list. - Benefits: list of benefits. But the bullet points under "About Trustaff Allied" are "Some of the other reasons people choose us include:" then list. That's essentially benefits/perks. But there is a separate Benefits section later. The later Benefits list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. The earlier list includes: 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. That's more like company perks. Could combine into Benefits section? But the posting separates them. The rule: preserve ALL substantive information. So include both. Maybe create two sections: "About Trustaff Allied" for the company description and the reasons list, and "Benefits" for the benefits list. Also, the job details metadata: I'll put them in a paragraph under "About the role" or a separate "Job Details" heading? Since not in the example headings, maybe just a paragraph. Let's draft:

  About the role

  Trustaff Allied is seeking a travel CT Technologist for a travel job in Turnersville, New Jersey.

  Specialty: CT Technologist; Discipline: Allied Health Professional; Start Date: 11/30/2026; Duration: 13 weeks; 48 hours per week; Shift: 12 hours, days; Employment Type: Travel.

  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.

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

  Schedule

  • 48 hours per week
  • Shift: 12 hours, days

  About Trustaff Allied

  Our traveler-first attitude has set us apart from other travel healthcare agencies. When you join the Trustaff family, you’re more than just a body filling a role—you're a vibrant individual with dreams and aspirations. As one of the nation's leading travel healthcare companies, your recruiter will work with you one-on-one to guide your career and help you achieve your goals.

  You decide when and where you want to work. Enjoy industry-leading pay, benefits, and bonuses. Experience new people and places. Grow your clinical skills and expand your experience. Travel healthcare lets you take your professional career to the next level while maintaining your flexibility and freedom. At Trustaff, we put you first, so you never have to compromise your work or pay. We are proud to have one of the highest nurse retention rates in the country.

  Reasons to choose Trustaff

  • 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

  Benefits

  • Dental benefits
  • Medical benefits
  • Vision benefits
  • Guaranteed Hours
  • Referral bonus
  But note: The "Reasons to choose Trustaff" is not a standard heading. The rule says use

  for section headings. Could use

  for "Why Trustaff" or keep as

  ? The rule doesn't forbid

  , but says use

  for section headings. Might be okay to use

  for "About Trustaff Allied" and then a list without subheading. But the list is part of that section. Could just include the list under the same section. Better to keep it simple: Under "About Trustaff Allied", include the prose and then the list as a

  without subheading. Also, the Benefits section: the list is short. That's fine. Now, check for boilerplate: The posting includes "About Trustaff Allied" which is company description, not boilerplate. The benefits list is specific. No EEO/legal boilerplate. The job ID and pay package note: I included in About the role paragraph. That's fine. Now, ensure no duplicate info: The schedule info appears in both About the role and Schedule section. That's okay, but maybe avoid duplication. The rule: preserve ALL substantive information. Duplication is okay if it's in different contexts. But we can remove from About the role if we have Schedule section. However, the About the role paragraph includes the metadata list. I'll keep the metadata list in About the role and also have Schedule section with the same info? Might be redundant. Better to have Schedule section only for schedule details, and in About the role just mention the role description. But the metadata includes start date, duration, employment type, which are not schedule. So maybe keep metadata in About the role, and Schedule section only for hours and shift. Let's adjust: In About the role, include the metadata list but not the hours and shift? Actually the metadata list includes "48 hours per week; Shift: 12 hours, days". That's schedule. Could keep there and not create a separate Schedule section? But the rule says use

  for Schedule if posting states them. It does state them. But the rule also says "Prefer a few substantive sections over many thin ones." Schedule section with two bullet points is thin. Could fold into About the role. However, the example headings include Schedule. I think it's okay to have a Schedule section if there is specific schedule info. But the posting also has "Duration: 13 weeks