Phlebotomy Technician

Here's a thinking process: 1. **Analyze the Request:** - Input: A job posting text for a "Phlebotomy Technician I" at Knapp Medical Center. - Task: Reformat into clean, well-structured semantic HTML. - Rules: - Use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). - Use `

• ` for lists of duties/requirements/benefits. - Use `

  ` for prose. - Do NOT repeat the job title as a heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `

  ` or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Analyze the Input Text:** Let me parse the input carefully. It's structured with sections like "Overview", "Responsibilities", "Qualifications", and then some boilerplate at the end ("Employment Status", "Equal Employment Opportunity Company is an equal employment opportunity employer...", "Know Your Rights: ..."). Let me break it down: - **Overview**: Starts with "Overview Join an award-winning team..." Actually, the first line says "Overview Join an award-winning team...". So "Overview" is a section heading. Content: description of Knapp Medical Center, Prime Healthcare Foundation, location, beds, specialties, status as only acute care hospital, Level III Trauma Center, etc., physicians, employees, contact info. - **Responsibilities**: Starts with "Responsibilities Phlebotomy Technician I primarily perform skin puncture..." Then lists 11 items. These are duties/responsibilities. - **Qualifications**: Starts with "Qualifications Education and Work Experience High School Diploma, or equivalent, required. BLS certification within 45 days of hire and maintained current, required. Minimum of one (1) year of clinical laboratory experience, preferred." Then "Employment Status Per Diem Shift Variable" seems part of qualifications or metadata. - Then boilerplate: "Equal Employment Opportunity Company is an equal employment opportunity employer. Company prohibits discrimination..." and "Know Your Rights: https://...". This is explicitly to be removed per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - Also "Employment Status Per Diem Shift Variable" - is this substantive? It's metadata about employment status and shift. The rules say: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." And: "never create Pay/Schedule/Benefits sections unless the posting actually states them." "Per Diem Shift Variable" could be considered minor metadata, but it's specific information. I need to decide whether to include it. The rules prefer a few substantive sections over many thin ones. "Employment Status" and "Shift" might be considered part of Qualifications or could be folded into a short

  . But the rule says "fold minor metadata into a short

  or drop it." I think I can fold it into a

  within Qualifications or maybe just drop it if it's not substantial. However, it is specific information: "Per Diem Shift Variable". I'll likely include it as a short

  maybe after Qualifications or within them, but need to see the section mapping. - Section headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I should only include sections that have real content. The posting has "Overview" (which maps to "About the role" or maybe just general info), "Responsibilities", "Qualifications". It does not have explicit "Skills", "Benefits", "Pay", "Schedule" sections with actual content. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." And "include a section ONLY when the posting has real, specific content for it". So I should NOT create Benefits, Pay, Schedule sections. I should only have sections where there's actual content. - Also, "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an

  for "Phlebotomy Technician I" as a heading. The headings are for sections like About the role, Responsibilities, etc. - "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So the EEO section and "Know Your Rights" must be removed. - "Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to include all the details from Overview and Responsibilities and Qualifications, but cleanly. - Structure mapping: - "Overview" -> could be "About the role" or maybe just keep as a section. The rules say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should map "Overview" to perhaps "About the role" or I could use "Overview" as the heading? The rules give examples but say "e.g." so I can use appropriate headings. I think "About the role" is suitable for the Overview content. But the original has "Overview" as a heading. I'll use "About the role" since that's one of the examples and fits. Or I could just use "Overview" as the

  . The rules don't forbid using the exact heading if it's from the posting, but they say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think it's safer to map to the semantic categories. The posting starts with "Overview", so I'll use "

  About the role

  " or maybe "

  Overview

  ". To be safe and follow "e.g.", I'll use "About the role" as the heading, but I need to preserve the content. Actually, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I can't use other headings, but it's suggesting those are the valid ones. I'll use "About the role" because the Overview is about the role and company. But the original has "Overview" as a distinct section. I'll just use "Overview" as the

  since it's the posting's own section title, and it's listed in the e.g. implicitly? Actually "Overview" isn't in the list, but "About the role" is. I'll use "About the role" and put the Overview content under it. Or I could use "Overview" as the h3. I think it's better to use the exact section titles from the posting where possible, but the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I'll interpret this as: use those semantic names for sections. So I'll map "Overview" -> "About the role", "Responsibilities" -> "Responsibilities", "Qualifications" -> "Qualifications". I won't create Skills, Benefits, Pay, Schedule since there's no content. - Let's outline the sections I'll include: 1. About the role (from Overview) 2. Responsibilities (from Responsibilities section) 3. Qualifications (from Qualifications section, but need to handle "Employment Status Per Diem Shift Variable") - For Responsibilities, the text lists 11 items starting with "The PT I; 1) performs computer data entry..." etc