Travel CT Technologist - $2,480 per week

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions? The instruction says remove application instructions. The posting includes "Submission Process" which is application instructions; we should remove that. Also remove "About Wellspring Nurse Source" maybe considered boilerplate? It's company description; not required but could be considered not essential? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly prohibited, but we might keep if it's substantive? However they said prefer a few substantive sections over many thin ones. The company description may be considered not essential to the job posting; but it's not boilerplate like EEO. It's okay to keep maybe as a paragraph under About the role? But we have to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put company description under About the role maybe. We need to extract specifics: - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: ASAP - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Travel radius: 75 miles - Qualifications: Registered by ARRT, Valid WV state license, Minimum 2 years hands-on experience in CT imaging, First-time travelers not accepted. - Responsibilities: Perform high-quality CT scans while ensuring patient safety and comfort; Evaluate images for technical quality and take corrective action if needed; Collaborate with medical staff to provide quality patient care; Maintain and operate imaging equipment according to safety standards. - Pay: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is vague; we should not create Pay section unless posting actually states them. It does state pay package based on shifts and hours, but stipend amount TBD. It's somewhat vague but still mentions pay package. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on 12 hour shifts and 36 hours per week, with tax-free stipend amount to be determined. That's stating something about pay, albeit not specific numbers. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on shifts and hours. So we can include Pay section with that info. However we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "tax-free stipend amount to be determined" is TBD. That's like TBD. Might be considered filler. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we must not have placeholder text. The posting says "tax-free stipend amount to be determined." That's TBD. So we should avoid including Pay section if it would contain only placeholder. However we could include the part about "based on 12 hour shifts and 36.0 hours per week" which is specific. But the stipend amount TBD is placeholder. We could phrase: "Pay package is based on 12‑hour shifts and 36 hours per week." That's specific, not placeholder. We could omit the stipend part. But we must preserve ALL substantive information; we cannot invent or summarize away detail. If we omit the stipend part, we are summarizing away detail (the stipend amount TBD). That's detail but it's placeholder. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The stipend amount TBD is not substantive? It's basically unknown. Might be considered not substantive. But it's still info: they say stipend amount to be determined. That's not a concrete number. Might be considered placeholder. The instruction about not creating Pay section unless posting actually states them. It does state pay package based on shifts and hours, so we can include Pay section with that detail, and we could include the stipend note but that's TBD. Might be considered filler. Safer to omit Pay section entirely? But then we lose the info about pay package being based on 12 hour shifts and 36 hours per week. That is substantive. Could we put that info under About the role or Schedule? Schedule section could include shift details. The posting already has Shift: 12 hours, days; Duration: 13 weeks; 36 hours per week. That's schedule info. So we could put schedule details under Schedule section. Pay could be omitted if we consider stipend TBD as not substantive. But we lose the mention of pay package being based on shifts. However schedule already includes hours per week. The pay package being based on those hours is implied. Might be okay. Benefits: Not mentioned. So no Benefits section. Skills: Not explicitly listed separate from qualifications. Could combine qualifications and skills. But we have separate headings for Qualifications and Skills. The posting lists qualifications (ARRT, license, experience, no first-time travelers). Skills maybe not separate. Could we put skills under Qualifications? Or we could create Skills section with nothing? Better to not create Skills if no specific content. Thus sections: About the role (maybe includes company overview and role summary), Responsibilities, Requirements (maybe includes start date, duration, shift, travel radius), Qualifications (ARRT, license, experience, first-time travelers not accepted). Could also include Requirements as separate from Qualifications? The posting has "Job Description & Requirements" then later "Qualifications". So we can treat Requirements as the job details (start date, duration, hours, shift, travel radius, employment type). Qualifications as the certifications etc. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. So no heading with "CT Technologist". Good. We must not put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can drop Job ID. We must remove boilerplate etc. So we remove "Submission Process", "About Wellspring Nurse Source" maybe? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Wellspring Nurse Source" is not those, but could be considered company description; not prohibited. However they said prefer a few substantive sections over many thin ones. Including a company description may add a thin section. Could we incorporate it into About the role as a paragraph? That would be okay. Thus About the role: include a brief description: "Wellspring Nurse Source is seeking a travel CT Technologist for a travel job in Kingwood, West Virginia." plus maybe company overview. But we must not repeat job title. So we can start with that sentence. Let's craft:

  About the role

  Wellspring Nurse Source is seeking a travel CT Technologist for a 13‑week contract in Kingwood, West Virginia. The position requires three 12‑hour day shifts per week (36 hours weekly) with a travel radius of 75 miles. Wellspring One (formerly Wellspring Nurse Source) is a nurse‑owned and operated healthcare staffing company focused on clinician support.

  That's substantive. Responsibilities: list.

  Responsibilities

  • Perform high‑quality CT scans while ensuring patient safety and comfort
  • Evaluate images for technical quality and take corrective action if needed
  • Collaborate with medical staff to provide quality patient care
  • Maintain and operate imaging equipment according to safety standards
  Requirements: maybe include start date, duration, shift, hours, travel radius, employment type.

  Requirements

  • Start date: ASAP
  • Duration: 13 weeks
  • Shift: 12‑hour day shifts, three per week (36 hours weekly)
  • Travel radius: 75 miles
  • Employment type: Travel
  Qualifications: ARRT, WV license, 2 years experience, no first-time travelers.

  Qualifications

  • Registered by the American Registry of Radiologic Technologists (ARRT)
  • Valid West Virginia state license
  • Minimum of 2 years of hands‑on experience in CT imaging
  • First‑time travelers are not accepted
  Skills: Not present; we skip. Benefits: none. Pay: we could include but risk placeholder. Let's see if we can include Pay section with substantive info: "Pay package is based on 12‑hour shifts and 36 hours per week." That's substantive. We could add that as a

  . Avoid mention of stipend TBD. So:

  Pay

  Pay package is based on 12‑hour shifts and 36 hours per week.

  Schedule: we already have shift details in Requirements; but we could also have Schedule section with shift details. However we must avoid duplication. The instruction says remove duplicated lines. So we should not duplicate same info in multiple sections. We already have shift details in Requirements. So we could omit Schedule section. Or we could move shift details to Schedule and keep Requirements more about start date, duration, travel radius, employment type. Let's think: Requirements could be about eligibility (start date, duration, travel radius, employment type). Schedule could be about shift pattern. That avoids duplication. Let's do that. Thus: Requirements section: start date, duration, travel radius, employment type. Schedule section: shift pattern (12‑hour day shifts, three per week, 36 hours weekly). Pay section: as above. Now ensure we don't have any placeholder text like "ASAP" is okay. Not placeholder like TBD. "ASAP" is okay. Check for any other boilerplate: "This is a great opportunity for skilled professionals looking to expand their experience in a dynamic environment. We look forward to your application!" That's promotional; we should remove as it's fluff? It's not boilerplate but could be considered filler. The instruction says remove duplicated lines, application instructions, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not those. It's a generic encouraging statement. Might be considered filler but not explicitly prohibited. However they said prefer a few substantive sections over many thin ones. This statement is thin. Better to omit. Also "Wellspring Nurse Source Job ID #38270472." we drop. Now produce HTML fragment only. Let's craft final HTML:

  About the role

  Wellspring Nurse Source is seeking a travel CT Technologist for a 13‑week contract in Kingwood, West Virginia. The position requires three 12‑hour day shifts per week (36 hours weekly) with a travel radius of 75 miles. Wellspring One (formerly Wellspring Nurse Source) is a nurse‑owned and operated healthcare staffing company focused on clinician support.

  Responsibilities

  • Perform high‑quality CT scans while ensuring patient safety and comfort
  • Evaluate images for technical quality and take corrective action if needed
  • Collaborate with medical staff to