Local Contract CT Tech - $66 per hour

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Content: - Job title: Computed Tomography Technologist (but we don't repeat as heading) - Location: Pickerington, Ohio - Specialty: CT Technologist - Discipline: Allied Health Professional - Duration: 13 weeks - Hours: 36 hours per week - Shift: 12 hours, nights - Employment Type: Local Contract - Description: "The Computed Tomography (CT) Technologist is a highly skilled professional who uses specialized computerized x-ray equipment to produce cross sectional images of the human anatomy which aid radiologists in diagnosing a wide variety of diseases and disorders." - Requirements: 2 years of experience required - Benefits listed: * $600 travel bonus * Day 1 health insurance with United Healthcare * PTO plan -- start accruing on day 1, use during contract or cash out at the end! * Guaranteed stipend if facility calls you off * Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours - Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Job ID: L-884571 (should be folded into short p or dropped) - About Stability Healthcare: description of company (maybe we can put under About the role? Actually "About Stability Healthcare" is company info; could be part of About the role or maybe separate but we only have headings list; we could put under About the role (maybe includes company description). The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings as appropriate. We need to include sections only when posting has real specific content. We have: - About the role: we have description of role (the CT Technologist description). Also maybe location, duration, shift, etc. Could be included. - Responsibilities: Not explicitly listed beyond description. The description is more of role overview. Could treat as Responsibilities? Might be okay. - Requirements: 2 years of experience required. - Qualifications: maybe not separate; could combine with Requirements. - Skills: Not listed. - Benefits: we have list of benefits. - Pay: we have pay package description (based on 12 hour shifts and 36.0 hours per week, tax-free stipend amount to be determined). That's somewhat vague but includes specifics: based on 12 hour shifts, 36 hrs/week, tax-free stipend amount TBD. The instruction 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. Here Pay section includes "tax-free stipend amount to be determined" which is TBD. That's placeholder. However we also have concrete: based on 12 hour shifts and 36.0 hours per week. That's specific. The stipend amount TBD is placeholder but we could still include the Pay section with the concrete info and note that stipend amount TBD? The instruction says never emit a heading followed by filler/placeholder text. If we include Pay heading, we must ensure the content under it is not just filler. We have some concrete info: based on 12 hour shifts and 36.0 hours per week. That's specific. The stipend amount TBD is filler; we could maybe omit that detail or phrase as "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." That includes TBD. Might be considered filler. Safer to omit Pay section if it's mostly TBD? But we do have concrete shift/hours info. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on 12 hour shifts and 36.0 hours per week. So we can include Pay section with that info, maybe omit the TBD stipend line or rephrase to avoid placeholder. Could say: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)." That removes TBD. That's acceptable. - Schedule: we have shift: 12 hours, nights; 36 hours per week; duration 13 weeks. That's schedule info. So we can include Schedule section. - Benefits: we have list. - About the role: we can include description, location, duration, etc. - Responsibilities: maybe we can use the description as responsibilities. - Requirements: 2 years experience. - Qualifications: maybe not needed. - Skills: none. We need to avoid repeating job title as heading. Also drop Job ID. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

Stability Healthcare is seeking a local contract CT Technologist in Pickerington, Ohio. The position is a 13‑week local contract requiring 36 hours per week on 12‑hour night shifts.

The Computed Tomography (CT) Technologist is a highly skilled professional who uses specialized computerized x‑ray equipment to produce cross sectional images of the human anatomy which aid radiologists in diagnosing a wide variety of diseases and disorders.

Responsibilities

Perform CT imaging procedures, ensure patient safety and comfort, operate computerized x‑ray equipment, produce diagnostic images for radiologist interpretation, and maintain equipment and supplies.

But we must not invent details. The responsibilities we just wrote may be invented. We should only use what's in posting. The posting only gave description of role, not a list of responsibilities. So we should not create a Responsibilities section with invented duties. Better to either not include Responsibilities section, or include it only if we can derive from description without adding. The description is basically a definition of role; we could treat that as About the role, not Responsibilities. So we may skip Responsibilities. Requirements: we have "2 years of experience required*". That's specific. So we can have Requirements section with that. Qualifications: maybe not needed. Skills: none. Benefits: we have list. Pay: we have shift/hours info. Schedule: we have shift/hours/duration. We need to avoid filler like "commensurate with experience". Not present. Let's craft sections: - About the role: include location, contract type, duration, hours, shift, description of role. - Requirements: 2 years of experience required. - Benefits: list bullet points. - Pay: based on 12 hour shifts and 36.0 hours per week (subject to confirmation). (We could mention tax-free stipend amount to be determined? Might be considered filler; better to omit that phrase.) - Schedule: 13‑week duration, 36 hours per week, 12‑hour night shifts. We need to use

• for any list of duties/requirements/benefits. So Benefits should be a
  . Requirements could be a
  if multiple items; we have just one item but could still be
  or

  . The rule says use

  • for any list of duties/requirements/benefits. If it's a single item, still a list? Might be okay to use

    . Safer to use

    • for requirements as well. We must not repeat job title as heading. Not include Job ID. Let's produce HTML. Check for any boilerplate: we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes "About Stability Healthcare" paragraph about company; that's not boilerplate? It's company description but could be considered boilerplate? It's not legal/EEO. It's about the company; maybe we can include under About the role or separate? The instruction says we can use About the role heading for section headings. The company description could be part of About the role. But we already have About the role with job specifics. Could we add company description there? It's not about the role but about the employer. Might be okay to include as part of About the role. However we must preserve ALL substantive information; we should not drop company description unless it's boilerplate. It's not boilerplate; it's substantive about the agency. So we should include it somewhere. Perhaps we can add a paragraph under About the role after the job specifics. Thus About the role section could contain: location, contract details, shift, description of role, and a brief about Stability Healthcare. Let's craft:

      About the role

      Stability Healthcare is seeking a local contract CT Technologist for a 13‑week local contract in Pickerington, Ohio. The position requires 36 hours per week on 12‑hour night shifts.

      The Computed Tomography (CT) Technologist is a highly skilled professional who uses specialized computerized x‑ray equipment to produce cross sectional images of the human anatomy which aid radiologists in diagnosing a wide variety of diseases and disorders.

      Stability Healthcare, founded in 2009, aims to be the best travel nursing agency, offering high‑paying travel assignments across the country and placing nurses in top hospitals and health systems.

      That preserves company info. Now Requirements: 2 years of experience required. We'll do:

      Requirements

      • Minimum 2 years of experience as a CT Technologist.
      Benefits: list: - $600 travel bonus - Day 1 health insurance with United Healthcare - PTO plan -- start accruing on day 1, use during contract or cash out at the end! - Guaranteed stipend if facility calls you off - Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours We need to keep the exact phrasing? Preserve ALL substantive information; do not invent or summarize away detail. So we should keep the benefit statements as they appear, maybe slightly trimmed but keep meaning. Let's copy them exactly: * $600 travel bonus * Day 1 health insurance with United Healthcare * PTO plan -- start accruing on day 1, use during contract or cash out at the end! * Guaranteed stipend if facility calls you off * Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours We'll put each as
    • . 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." We'll drop the TBD part maybe. But we need to preserve substantive information; the TBD part is not substantive; it's placeholder. We could keep it but it's placeholder; instruction says never emit a heading followed by filler/placeholder text. If we include the TBD phrase, that's filler under Pay heading. So better to omit that phrase. Keep: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)." That's substantive. Schedule: we have duration 13 weeks, 36 hours per week, shift 12 hours nights. We'll put:

      Schedule

      • Duration: 13 weeks
      • Hours per week: 36 hours
      • Shift: 12‑hour nights
      Alternatively we could combine into a paragraph. But rule: use
      • for any list