Travel Cath Lab Tech - $3,484 per week

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Job description: "PRIDE Health is seeking a travel Cath Lab Technologist for a travel job in Baltimore, Maryland." Then "Job Description & Requirements Specialty: Cath Lab Technologist Discipline: Allied Health Professional Start Date: 10/12/2026 Duration: 16 weeks 40 hours per week Shift: 10 hours, days Employment Type: Travel" Then description: "A Radiology Technician operates imaging equipment to capture X-rays, MRIs, CT scans, and other diagnostic images. Responsibilities include preparing patients for imaging procedures, operating equipment, and ensuring proper documentation and safety protocols. Apply for specific facility details." Then "PRIDE Health Job ID #19209276. 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: Rad Tech:Cath Lab,07:00:00-17:00:00" Then About PRIDE Health paragraph. Then Benefits list: Weekly pay Holiday Pay Guaranteed Hours 401k retirement plan Cancelation protection Referral bonus Medical benefits Dental benefits Vision benefits We need to remove boilerplate (EEO, Fair Chance, Accommodations, etc). Also remove duplicated lines. We need to produce sections only if real specific content. Let's identify content: - About the role: maybe description of role: "A Radiology Technician operates imaging equipment..." That's about role. Could be placed under About the role. - Responsibilities: "Responsibilities include preparing patients for imaging procedures, operating equipment, and ensuring proper documentation and safety protocols." - Requirements: maybe specialty, discipline, start date, duration, hours, shift, employment type. Those are job details. Could be under Requirements or Qualifications. The posting includes "Specialty: Cath Lab Technologist Discipline: Allied Health Professional Start Date: 10/12/2026 Duration: 16 weeks 40 hours per week Shift: 10 hours, days Employment Type: Travel". Those are job specifics, not necessarily requirements but could be considered Requirements. - Qualifications: maybe none explicit beyond being a Cath Lab Technologist? Not given. - Skills: none explicit. - Benefits: list given. - Pay: "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 vague but mentions pay package based on shifts and hours, stipend TBD. It's not a specific number, but it's still content about pay. The rule: do NOT emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined." That's TBD. Also "subject to confirmation". This might be considered placeholder. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state 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 stating something, albeit vague. But it's not a specific number; still it's stating that pay package is based on those shifts/hours. Might be acceptable. However the rule says: do NOT emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is TBD. So that is placeholder. The Pay section would contain that placeholder text; maybe we should omit Pay section because it's mostly placeholder. However we could still include the part about "based on 10 hour shifts and 40.0 hours per week". That's specific. But the stipend amount TBD is placeholder. The instruction: never emit a heading followed by filler/placeholder text. If we include Pay section, we would have some specific content plus placeholder. Might be okay? Safer to omit Pay section if it's mostly placeholder. But we could include a short paragraph: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation)." That's not placeholder; it's stating basis. The stipend amount TBD could be omitted? But we must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the stipend amount TBD, we are summarizing away detail (the stipend amount to be determined). That's a detail, albeit placeholder. But we could include it as is; it's still substantive (they say amount to be determined). That's not invented. It's okay to include placeholder text as long as we don't create a heading with only filler. The heading would have some content: the sentence. So it's okay. Similarly Schedule: we have shift: 10 hours, days. Also start date, duration, hours per week. That's schedule info. So we can include Schedule section. Benefits: we have list. Now we need to avoid repeating job title as heading. Not include Job ID. We need to output only HTML fragment. Let's craft sections:

About the role

A Radiology Technician operates imaging equipment to capture X-rays, MRIs, CT scans, and other diagnostic images. Responsibilities include preparing patients for imaging procedures, operating equipment, and ensuring proper documentation and safety protocols.

But we also have Responsibilities separate. Could combine? Better to separate.

Responsibilities

• Preparing patients for imaging procedures
• Operating equipment
• Ensuring proper documentation and safety protocols

Requirements

We have specialty, discipline, start date, duration, hours per week, shift, employment type. Could list as

. But also we have location: Baltimore, Maryland. Could include. Let's list:
• Specialty: Cath Lab Technologist
• Discipline: Allied Health Professional
• Location: Baltimore, Maryland
• Start Date: October 12, 2026
• Duration: 16 weeks
• Hours per week: 40
• Shift: 10 hours, days
• Employment Type: Travel
That seems fine. Qualifications: none specific beyond being a Cath Lab Technologist (which is specialty). Could omit. Skills: none. Benefits: list.

Benefits

• Weekly pay
• Holiday Pay
• Guaranteed Hours
• 401k retirement plan
• Cancelation protection
• Referral bonus
• Medical benefits
• Dental benefits
• Vision benefits
Pay: we have sentence.

Pay

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.

Schedule: we could include shift details again, but we already have shift in Requirements. However schedule section could include start date, duration, hours per week, shift. But to avoid duplication, maybe we keep schedule separate with shift details. But the instruction: prefer a few substantive sections over many thin ones. We already have Requirements covering schedule info. Could we omit Schedule section? The posting does state shift, hours, etc. If we put them in Requirements, that's fine. The rule: include a section ONLY when the posting has real, specific content for it. We have content for Schedule (shift, hours). But we already placed that content in Requirements. Could we still have Schedule section with same info? That would duplicate. Better to keep schedule info under Requirements and not create a separate Schedule section to avoid thin sections. However the instruction says: "Prefer a few substantive sections over many thin ones." So we can combine schedule info into Requirements. Then we don't need Schedule section. Pay section: we have content; it's not thin? It's a single sentence but still substantive. Could we combine Pay into Requirements? Probably not; it's distinct. We'll keep Pay. Now About PRIDE Health: that's about the company, not the role. Should we include? The sections list includes About the role, not About the company. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About PRIDE Health is not one of those headings. Should we include it? The instruction says to use those headings for section headings. It doesn't forbid other headings, but says use those for section headings. Likely we should only include those headings if relevant. About PRIDE Health is not about the role; it's about the company. Could be considered boilerplate? It's descriptive but not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About PRIDE Health is not boilerplate but it's not a required section. However we could include it as a paragraph without heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't say we cannot have other headings, but we should follow the pattern. Probably we should omit About PRIDE Health because it's not requested heading and could be considered boilerplate-ish. However it's substantive about the employer. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit it, we lose substantive info about the employer. But maybe it's considered boilerplate? It's a description of the company, similar to "About PRIDE Health". Might be considered not required for the job posting core. The instruction says to remove boilerplate, but this is not typical boilerplate like EEO. It's still promotional. Might be okay to keep as a paragraph without a heading? But the instruction says use

for section headings (list). It doesn't say we cannot have other headings, but we should follow that pattern for sections we include. Could we include a heading like

About PRIDE Health

? That's not in the list but similar to About the role. Might be acceptable. However the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could use About PRIDE Health as a heading. But to be safe, maybe we include it as a paragraph without heading? The instruction says use

for section headings (e.g...). It doesn't forbid other headings, but we should follow that pattern for sections we include. I'd include About PRIDE Health as a heading because it's substantive. But we need to decide: The user likely expects only those sections. The prompt: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. They didn't mention About the company. So better to omit About PRIDE Health to adhere to the instruction. However they said "Preserve ALL substantive information". If we omit About PRIDE Health, we lose that info. But maybe they consider that boilerplate? It's not legal boilerplate, but it's still promotional. Might be considered not essential for the job posting core. I'd risk omitting it to follow the heading list.