Travel CT Technologist - $2,500 per week

We need to output HTML fragment with sections: About the role? Actually we have job description: "LanceSoft is seeking a travel CT Technologist for a travel job in Lusk, Wyoming." Then "Job Description & Requirements" then details: Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift, Employment Type, Pay package note. Then About LanceSoft paragraph. Then Benefits: Weekly pay, Medical benefits. We must not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have content: About LanceSoft (company description) could be "About the role"? Actually "About LanceSoft" is about company, not role. But we can use "About the role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have job description: maybe "About the role" could contain the description of the job: location, specialty, start date, duration, hours, shift, employment type. That seems appropriate. We have "Benefits" section: Weekly pay, Medical benefits. We have maybe "Pay" section? 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 pay info but vague (subject to confirmation, stipend TBD). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on shifts, but stipend TBD. It's somewhat vague but still mentions pay package. However "subject to confirmation" and "tax-free stipend amount to be determined" might be considered placeholder? It says "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 amount, but it's still stating that pay package is based on those parameters. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "subject to confirmation" and "tax-free stipend amount to be determined." That's somewhat placeholder. Might be better to omit Pay section because it's not specific. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Pay and Schedule sections if not specific. However we have schedule info: Shift: 12 hours, days; 36 hours per week. That's specific. Could we put that under Schedule heading? The schedule is given: 12 hour shifts, days, 36 hours per week. That's specific. So we could include a Schedule section with that info. We also have Requirements: maybe we can list Specialty, Discipline, etc. Under Requirements heading. We have Responsibilities? Not given explicitly. Could omit. Qualifications? Not given. Skills? Not given. Thus we can have sections: About the role (description), Requirements (specialty, discipline, start date, duration, hours, shift, employment type), Schedule (maybe redundant with requirements but we can include), Benefits (weekly pay, medical benefits), About LanceSoft? Actually we could put company info under About the role or maybe a separate section like "About the company". But allowed headings list does not include About the company. Could we use About the role for company? Not ideal. Perhaps we can include a paragraph about LanceSoft within About the role? But the instruction: Use headings for sections like About the role, Responsibilities, etc. It didn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we could also use other headings? Probably safer to stick to those. So we can put LanceSoft description under About the role as well (maybe combine). Or we could omit LanceSoft description? But we must preserve ALL substantive information. So we need to include LanceSoft info somewhere. Could put it in a

without heading? The instruction: Use

for section headings (e.g...). Use

• for any list... and

  for prose. It doesn't forbid having prose without heading. So we can have a

  describing LanceSoft after a heading or without heading. But we need to output only HTML fragment; we can have multiple sections each with heading and content. Thus structure:

  About the role

  LanceSoft is seeking a travel CT Technologist for a travel job in Lusk, Wyoming. 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.

  Requirements

  • 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
  But that duplicates info. Better to avoid duplication. Perhaps About the role includes narrative, Requirements includes list of requirements (maybe just specialty and discipline). However we have limited specifics. Could combine. We need to preserve all substantive information: location, specialty, discipline, start date, duration, hours, shift, employment type, pay package note, benefits, LanceSoft description. We can include pay package note under About the role or a separate Pay section if we deem it substantive enough. The note: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This includes some specifics (based on 12 hour shifts and 36 hours per week) but also placeholder. Might be okay to include in About the role. Schedule: we have shift and hours already; we could have Schedule section: 12 hour shifts, days, 36 hours per week. Benefits: Weekly pay, Medical benefits. LanceSoft description: we can put under About the role or maybe a separate section like "About LanceSoft" but not in allowed headings. Could we use About the role for that? Might be confusing. Perhaps we can include a

  without heading after the sections. But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but it's implied to use those for sections. Safer to stick to those. Thus we could have:

  About the role

  LanceSoft is seeking a travel CT Technologist for a travel job in Lusk, Wyoming. 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. Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

  Requirements

  • CT Technologist specialty
  • Allied Health Professional discipline
  But we lose start date etc. However those are already in About the role. That's okay; we preserve all info. Benefits:

  Benefits

  • Weekly pay
  • Medical benefits
  Schedule: we could include but it's already mentioned in About the role. Could still add Schedule section for clarity: 12 hour shifts, days, 36 hours per week. But to avoid duplication, maybe we include Schedule section with those details and remove from About the role? But we need to preserve all info; we can keep in both but duplication is okay? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be unnecessary. Better to avoid duplication but still preserve. Thus we could have About the role narrative without schedule details, and Schedule section with schedule specifics. But then we lose schedule from About the role? We could keep schedule in both but it's okay. Let's design:

  About the role

  LanceSoft is seeking a travel CT Technologist for a travel job in Lusk, Wyoming. Specialty: CT Technologist. Discipline: Allied Health Professional. Start Date: 11/02/2026. Duration: 13 weeks. Employment Type: Travel. Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

  Schedule

  12 hour shifts, days; 36 hours per week.

  Requirements

  • CT Technologist specialty
  • Allied Health Professional discipline

  Benefits

  • Weekly pay
  • Medical benefits
  We also need to include LanceSoft description. Could add a

  after sections without heading, or incorporate into About the role. Let's add a separate paragraph after Benefits:

  About LanceSoft: Established in 2000, LanceSoft is a Certified MBE and Woman-Owned organization. Lancesoft Inc. is one of the highest rated companies in the industry. We have been recognized as one of the Largest Staffing firms and ranked in the top 50 fastest Growing Healthcare Staffing firms in 2022. Lancesoft offers short- and long-term contracts, permanent placements, and travel opportunities to credentialed and experienced professionals throughout the United States. We pride ourselves on having industry leading benefits. We understand the importance of partnering with an expert who values your needs, which is why we’re 100% committed to finding you an assignment that best matches your career and lifestyle goals. Our team of experienced career specialists takes the time to understand your needs and match you with the right job Lancesoft has been chosen by Staffing Industry Analysts as one of the Best Staffing Firms to Work for.LanceSoft specializes in providing Registered Nurses, Nurse Practitioners, LPNs/LVNs, Social Workers, Medical Assistants, and Certified Nursing Assistants to work in Acute Care Centers, Skilled Nursing Facilities, Long-Term Care centers, Rehab Facilities, Behavioral Health Centers, Drug & Alcohol Facilities, Home Health & Community Health, Urgent Care Clinics, and many other provider-based facilities.

  That's a lot of prose; we keep as

  . Now ensure we didn't include any boilerplate like EEO etc. We removed. Check for any placeholder text: We have "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This includes "subject to confirmation" and "tax-free stipend amount to be determined." That's somewhat placeholder but still conveys that pay is based on those parameters. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have a sentence within a paragraph, not a heading followed by