Local Contract Cath Lab Technologist - $47-51 per hour

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, etc. Let's parse the posting. Content: - Host Healthcare is seeking a local contract Cath Lab Technologist for a local contract job in Hershey, Pennsylvania. - Job Description & Requirements - Specialty: Cath Lab Technologist - Discipline: Allied Health Professional - Start Date: 10/20/2026 - Duration: 14 weeks - 40 hours per week - Shift: 10 hours, evenings - Employment Type: Local Contract - Host Healthcare Job ID #La1fVX0000045mRVYAY. - 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. - Posted job title: Cath Lab Tech - Allied - About Host Healthcare: paragraph about company. - Benefits list: Referral bonus, School loan reimbursement, Vision benefits, Wellness and fitness programs, Company provided housing options, License and certification reimbursement, Life insurance, Medical benefits, Mileage reimbursement, Pet insurance, Discount program, Employee assistance programs, Guaranteed Hours, Health savings account, Holiday Pay, 401k retirement plan, Continuing Education, Dental benefits. We need to produce sections: About the role (maybe description of role?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract from posting any responsibilities, requirements, qualifications, skills. The posting includes specialty, discipline, start date, duration, hours, shift, employment type. Those could be considered role details. There's no explicit responsibilities list. There's no explicit requirements beyond specialty and discipline. There's no explicit qualifications beyond maybe being a Cath Lab Technologist. There's no explicit skills list. We must not create sections with filler text. So we should only include sections where we have real specific content. We have: - About the role: we could include description: "Host Healthcare is seeking a local contract Cath Lab Technologist for a local contract job in Hershey, Pennsylvania." plus maybe details: Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type. That seems like role info. - Responsibilities: none given. So we should not include Responsibilities heading. - Requirements: maybe we have "Specialty: Cath Lab Technologist", "Discipline: Allied Health Professional". Could be considered requirements. But we need to see if that's substantive. It is specific. So we could include Requirements section with those items. - Qualifications: none explicit besides maybe being a Cath Lab Technologist (same as specialty). Could be considered qualification but might duplicate. Safer to not include Qualifications if no distinct content. - Skills: none explicit. - Benefits: we have a list of benefits. So include Benefits section with ul. - Pay: we have "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 specific enough? It mentions basis but not actual amount. It says "tax-free stipend amount to be determined." That's somewhat vague but still mentions pay package based on shifts and hours. It's not a specific number, but it's still info about pay. 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 we have "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." This includes some specifics (based on 10 hour shifts and 40 hours per week) but the amount is TBD. Is that considered placeholder? It says "tax-free stipend amount to be determined." That's TBD. The phrase "based on 10 hour shifts and 40.0 hours per week (subject to confirmation)" is somewhat specific but still says subject to confirmation. Might be considered not a concrete pay amount. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Here we have "tax-free stipend amount to be determined" which is TBD. So maybe we should not include Pay section because the actual amount is not specified. However we do have basis: 10 hour shifts, 40 hours per week. That's more like schedule info. But the Pay section is meant for pay details. Since no concrete pay, maybe omit Pay. - Schedule: we have shift: 10 hours, evenings; 40 hours per week. That's specific schedule info. So we can include Schedule section. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. For About the role we can use

  for prose. For Requirements we can list items: Specialty: Cath Lab Technologist; Discipline: Allied Health Professional; Start Date: 10/20/2026; Duration: 14 weeks; 40 hours per week; Shift: 10 hours, evenings; Employment Type: Local Contract; Host Healthcare Job ID #La1fVX0000045mRVYAY. Should we include Job ID? The instruction says: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include Job ID in a short p within About the role or Requirements as minor metadata. Probably better to include in About the role as minor metadata. We need to preserve all substantive information. So we must include Start Date, Duration, etc. We need to avoid boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes About Host Healthcare paragraph which is not boilerplate? It's descriptive about the company. That's substantive? It's about the company, not the role. Should we include it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Host Healthcare paragraph is substantive info about the company. Should we include it? Possibly yes, as part of About the role or maybe a separate section like "About the Company". But we only have allowed headings list; we could put it under About the role as prose. That seems okay. We must not include duplicated lines. The Benefits list appears as a list; we need to output each as

• . We must not include application instructions (none present). Now construct HTML. We'll start with

  About the role

  then

  containing description: Host Healthcare is seeking a local contract Cath Lab Technologist for a local contract job in Hershey, Pennsylvania. Also include minor metadata: Job ID etc. Maybe better:

  Host Healthcare is seeking a local contract Cath Lab Technologist for a local contract job in Hershey, Pennsylvania. Host Healthcare Job ID #La1fVX0000045mRVYAY.

  Then maybe another paragraph for details: Start Date, Duration, etc. Could be a
  but those are not duties/requirements/benefits; they are role details. Could be

  with semicolons. But we could also treat them as Requirements. Let's decide: We'll put role details in Requirements section as list. Thus About the role: just the brief description. Requirements: list of Specialty, Discipline, Start Date, Duration, 40 hours per week, Shift, Employment Type. Benefits: list. Schedule: maybe we already included shift and hours in Requirements; but Schedule section could contain shift details: 10 hour shifts, evenings; 40 hours per week. However we already included those in Requirements. To avoid duplication, we could move shift/hours to Schedule and keep other details in Requirements. Let's see. We need to avoid duplicate lines. The posting mentions "40 hours per week" and "Shift: 10 hours, evenings". Those are schedule info. So we could put them in Schedule section. Then Requirements would contain Specialty, Discipline, Start Date, Duration, Employment Type, Job ID maybe. Let's do that. Thus: About the role:

  Host Healthcare is seeking a local contract Cath Lab Technologist for a local contract job in Hershey, Pennsylvania.

  Requirements:
  • Specialty: Cath Lab Technologist
  • Discipline: Allied Health Professional
  • Start Date: 10/20/2026
  • Duration: 14 weeks
  • Employment Type: Local Contract
  • Host Healthcare Job ID #La1fVX0000045mRVYAY
  Schedule:
  • 40 hours per week
  • Shift: 10 hours, evenings
  Benefits:
  • Referral bonus
  • School loan reimbursement
  • Vision benefits
  • Wellness and fitness programs
  • Company provided housing options
  • License and certification reimbursement
  • Life insurance
  • Medical benefits
  • Mileage reimbursement
  • Pet insurance
  • Discount program
  • Employee assistance programs
  • Guaranteed Hours
  • Health savings account
  • Holiday Pay
  • 401k retirement plan
  • Continuing Education
  • Dental benefits
  We should not include Pay section because amount TBD. Check for any other substantive info: The paragraph about Host Healthcare (the company description) is not included yet. Should we include it? It's substantive about the company. Could be placed under About the role as additional paragraph. Let's add another

  after the first: describing Host Healthcare mission etc. We need to ensure we don't include boilerplate like "During your assignment, get access to premium benefits..." that is essentially benefits but we already have benefits list. That paragraph includes some benefit details but we already captured them in list. It's okay to include that prose as part of About the role or maybe separate. But we must not duplicate benefit items. The paragraph includes: "During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment." This includes some benefits not in the list: Day 1 medical up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, access to on-staff clinicians. Those are substantive and not in the benefits list. We must preserve ALL substantive information. So we need to include those details somewhere. They are benefits-related. We could add them to the Benefits section as additional list items. Or we could include a prose paragraph about benefits. The instruction says use

  • for any list of duties/requirements/benefits. So we should add those as list items. Thus Benefits list should include: - Day 1 medical that continues up to 30 days between assignments - 401K matching - Travel reimbursements - Dedicated housing support - 24/7 support from our team - Access to on-staff clinicians