Travel Cath Lab Technologist - $2,507 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. Content: - Job details: - Travel Cath Lab Technologist in Snellville, Georgia. - Specialty: Cath Lab Technologist - Discipline: Allied Health Professional - Start Date: 10/05/2026 - Duration: 14 weeks - 40 hours per week - Shift: 10 hours, days - Employment Type: Travel - IMPORTANT – TRAVEL ELIGIBILITY: Applicants must reside more than 50 miles from the facility to qualify for the travel stipend and travel-related benefits. - Meda Health is looking for an Cath Lab Tech to work a travel assignment in an acute care hospital setting. Must have at least two years of experience, state licensure (if applicable) and BLS. - Competitive and Transparent Pay ... coverage starts when you do. Benefits: Health Vision Dental Life insurance - Meda Health Job ID #18998729. - 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 Tech,07:00:00-17:00:00 (maybe shift times) - About Meda Health: mission etc. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to produce sections only if real content. Let's map: About the role: Could be description of role: travel Cath Lab Technologist, acute care hospital setting, etc. We have that. Responsibilities: Not explicitly listed. The posting does not list duties. So we should not create Responsibilities section. Requirements: Must have at least two years of experience, state licensure (if applicable) and BLS. Also travel eligibility >50 miles. Also maybe discipline Allied Health Professional. So we can put Requirements. Qualifications: Could be similar to requirements; but we might combine. The instruction: prefer few substantive sections over many thin ones. So we could have Requirements covering experience, licensure, BLS, travel eligibility. Qualifications maybe not needed if overlapping. But we could still include Qualifications if there is distinct content like "Cath Lab Technologist specialty". However that's more about role. Might be better to have Requirements and Qualifications separate? The posting does not list separate qualifications beyond requirements. So we can skip Qualifications. Skills: Not listed explicitly. Could infer but not given. So skip. Benefits: Health Vision Dental Life insurance. Also coverage starts when you do. Also travel stipend and travel-related benefits (if >50 miles). Also maybe tax-free stipend amount to be determined. So we have benefits. Pay: "Competitive and Transparent Pay" but no specific amount. It says 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. No actual numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package based on shifts and hours, but no actual pay amount. Is that enough? It says "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 still some info about pay structure, though not a number. The rule: never 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" which is TBD-like. Also "subject to confirmation". This might be considered placeholder. Safer to omit Pay section because no concrete pay figure. However we could include Pay section with the info we have? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package based on shifts and hours, but it's vague. Might be considered stating them, albeit not a number. The rule about filler/placeholder text: we should not emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "tax-free stipend amount to be determined" is similar to TBD. So better to omit Pay section. Schedule: We have shift: 10 hours, days; 40 hours per week; start date; duration. That's schedule info. So we can include Schedule section with those details. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Let's extract specifics: About the role: - Meda Health is seeking a travel Cath Lab Technologist for a travel job in Snellville, Georgia. - Specialty: Cath Lab Technologist - Discipline: Allied Health Professional - Start Date: 10/05/2026 - Duration: 14 weeks - 40 hours per week - Shift: 10 hours, days - Employment Type: Travel - Meda Health is looking for an Cath Lab Tech to work a travel assignment in an acute care hospital setting. We could combine into prose. Requirements: - Must have at least two years of experience. - State licensure (if applicable). - BLS certification. - Applicants must reside more than 50 miles from the facility to qualify for the travel stipend and travel-related benefits. Benefits: - Health insurance - Vision insurance - Dental insurance - Life insurance - Coverage starts when you do (immediate coverage) - Travel stipend and travel-related benefits (for those >50 miles) - Tax-free stipend amount to be determined (maybe mention but it's TBD; maybe we can include as part of benefits but it's TBD; better to omit? It's still a benefit albeit unspecified. The rule about filler/placeholder text: "tax-free stipend amount to be determined" is TBD-like. Might be considered placeholder. Safer to omit that line. But we can still mention that there is a travel stipend (though amount TBD). The rule says never emit a heading followed by filler/placeholder text; but we can include a benefit that is known (travel stipend) even if amount unspecified? The benefit itself is known: travel stipend. The amount TBD is detail about the stipend. Might be okay to include "travel stipend" as benefit without amount. We'll include travel stipend as benefit. Schedule: - Start Date: 10/05/2026 - Duration: 14 weeks - 40 hours per week - Shift: 10 hours, days - Employment Type: Travel We could also include shift times 07:00:00-17:00:00 from posted job title line. That's shift time. Let's include that. Now produce HTML. Structure:

  About the role

  ... prose ...

  Requirements

  • ...

  Benefits

  • ...

  Schedule

  • ...
  Make sure no extra sections. Now craft prose for About the role: combine details. "Meda Health is seeking a travel Cath Lab Technologist for a 14‑week assignment in Snellville, Georgia. The role is for an Allied Health Professional specializing in Cath Lab technology, working 40 hours per week on 10‑hour day shifts (07:00–17:00) as a travel employee in an acute care hospital setting. The position starts on October 5, 2026." That seems good. Requirements list: - Minimum of two years of experience as a Cath Lab Technologist. - Current state licensure (if required in Georgia). - BLS certification. - Must reside more than 50 miles from the facility to be eligible for the travel stipend and travel‑related benefits. Benefits list: - Health insurance - Vision insurance - Dental insurance - Life insurance - Immediate coverage (benefits effective on start date) - Travel stipend and travel‑related benefits (for qualifying candidates) Schedule list: - Start date: October 5, 2026 - Assignment duration: 14 weeks - 40 hours per week - 10‑hour day shifts (07:00–17:00) - Travel employment type Check for any leftover info: Posted job title line includes "Rad Tech:Cath Lab Tech,07:00:00-17:00:00". We used shift times. Meda Health Job ID #18998729: we should drop minor metadata per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can drop it. About Meda Health mission: that's boilerplate? It's about the company, not the role. Could be considered "About Meda Health" but not a required section. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement is not boilerplate but it's about the company. Could be considered part of "About the role"? Not really. It's extra info about the company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. Where? Could be part of About the role? Might be better to add a separate section "About Meda Health" but we only have predefined headings list; we could add a section with heading

  About Meda Health

  if we want to preserve that info. However the instruction says: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings, but not obligated to limit to those. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section "About Meda Health" if there is real content. The posting includes a paragraph about Meda Health mission. That's substantive. So we should include it. Thus we add another section: About Meda Health. But the examples list "About the role" not "About Meda Health". However we can still use

  for any heading. The instruction didn't forbid other headings. It gave examples. So we can add About Meda Health. We need to ensure we don't repeat the job title as a heading (the page already shows it). That's fine. Thus sections: About the role, Requirements, Benefits, Schedule, About Meda Health. Now craft About Meda Health paragraph: "Meda Health’s mission is to bring positive change in communities by connecting dedicated and skilled healthcare professionals to facilities in different parts of the country. They believe in the transformative power of mutual respect, valuing healthcare professionals’ substantial contributions to the industry and the communities they serve, and are dedicated to helping employees work toward achieving their dreams in a way that builds a better world for all." Now ensure we