Phlebotomist Hiring Event

We need to output HTML fragment with sections: About the role? Actually the posting includes "JOB DESCRIPTION Greater Minneapolis Phlebotomist Hiring Event" and details about event, positions, pay, benefits, responsibilities, qualifications, about the team (but that includes EEO etc). We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "About the Team" if it's mostly EEO? The "About the Team" includes statements about veterans, staffing partners, equal opportunity employer. That's boilerplate; we should drop it. Also remove "RESponsibilities" and "QUALIFICATIONS" sections but keep content. Also need to include sections only when posting has real specific content. We have event details: location, date, time. Also positions: Phlebotomy Technician and Sr. Phlebotomy Technician with requirements. Also list of locations. Also shifts available. Also pay range. Also benefits info. Also responsibilities (detailed). Also qualifications (detailed). Also maybe "About the role"? Not present. Could use "About the role" heading? Not in posting. Better to use headings that match content: maybe "Event Details", "Positions", "Locations", "Shifts", "Pay", "Benefits", "Responsibilities", "Qualifications". However instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use those headings if appropriate. They said: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when we have content. If we don't have content for a heading, we should not include it. So we need to map content to these headings. We have: - About the role: could be a brief description of the role? The posting includes event description and positions. Could treat "About the role" as overview of positions. Might be okay. - Responsibilities: we have detailed responsibilities for both positions. - Requirements: could be qualifications? They gave "Requirements" as example. We have qualifications section. Could use "Requirements" heading for qualifications. - Qualifications: maybe duplicate? But we can choose either Requirements or Qualifications. Since they gave both as examples, we need to decide which to use. Probably use "Qualifications" for the qualifications content. "Requirements" could be for experience/education needed? But qualifications already includes that. Safer to use "Qualifications" heading for the qualifications content, and maybe not use "Requirements". Or we could split: "Requirements" for experience/education, "Qualifications" for certifications etc. But to keep simple, we can use "Qualifications" for the qualifications block. - Skills: we could extract skills from responsibilities? Not explicitly listed as skills. Might be thin. Better not to include if not specific. - Benefits: we have benefits info. - Pay: we have pay range. - Schedule: we have shifts available (6:00 AM to 8:30 PM). Could use Schedule heading. Also we have event details: location, date, time. Could be under "About the role" or maybe a separate heading like "Event Details" but not in list. Could fold into About the role. We must not repeat job title as heading. The page already shows it, so we don't add a heading for "Greater Minneapolis Phlebotomist Hiring Event". We'll just start with sections. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, etc. Also remove duplicated lines, application instructions (like "Please bring a resume and join us...") maybe that's part of event description but could be considered application instruction? It's about bringing resume to event. Might be considered application instruction; but it's part of event description. The instruction says remove application instructions. That line is basically "Please bring a resume and join us to learn about our open positions and a career with Quest Diagnostics!" That's an instruction for attendees. Might be considered application instruction. Safer to remove it. Also "Walk-Ins are welcome!" maybe also instruction. Could keep as part of event details? Might be considered instruction. Safer to remove. We need to preserve location, date, time. Also positions available list. Also list of locations (many). Also shifts available. Also pay range. Also benefits. Also responsibilities. Also qualifications. We must not include "Other locations" duplicate. Now craft HTML. We'll start with

About the role

then a

summarizing event: Quest Diagnostics is hosting a hiring event for Phlebotomist on Wednesday, October 21, 2026 at Hilton Minneapolis/Bloomington - 3900 American Blvd West, Bloomington 55437 from 2:00 PM to 7:00 PM. (We removed the "Please bring a resume..." line.) Then maybe

Positions

with

• Phlebotomy Technician (1 year phlebotomy experience required)
• Sr. Phlebotomy Technician (Floater-travel required, 1 year phlebotomy experience required, 1 year pediatrics experience required)

Then

Locations

with

• Bloomington
... etc. Need to list all locations given: Bloomington Buffalo Cambridge Coon Rapids Cottage Grove Crystal Eagan Eden Prairie Edina Forest Lake Fridley Hastings Isanti Lakeville Maple Grove Minneapolis Plymouth Ramsey Richfield Saint Michael Saint Paul Shakopee Vadnais Heights. Also "Other locations" maybe not needed. We'll list those. Then

Schedule

with

Shifts available between 6:00 AM to 8:30 PM.

Then

Pay

with

Pay Range: $24.00 - $29.00 / hour (Dependent on position selected for). Salary offers are based on a wide range of factors including relevant skills, training, experience, education, and, where applicable, certifications obtained. Market and organizational factors are also considered. Successful candidates may be eligible to receive annual performance bonus compensation.

Then

Benefits

with
• Day 1 Medical, supplemental health, dental & vision for FT employees who work 30+ hours
• Best-in-class well-being programs
• Annual, no-cost health assessment program
• Blueprint for Wellness®
• healthyMINDS mental health program
• Vacation and Health/Flex Time
• 6 Holidays plus 1 "MyDay" off
• FinFit financial coaching and services
• 401(k) pre-tax and/or Roth IRA with company match up to 5% after 12 months of service
• Employee stock purchase plan
• Life and disability insurance, plus buy-up option
• Flexible Spending Accounts
• Annual incentive plans
• Matching gifts program
• Education assistance through MyQuest for Education
• Career advancement opportunities
• and so much more!
(We need to keep the content as is, not summarizing.) Then

Responsibilities

with two sub-sections? Could just list all responsibilities combined? But we have separate for Phlebotomy Technician and Sr. Phlebotomy Technician. Could keep as
• Phlebotomy Technician: ...
• Sr. Phlebotomy Technician: ...
but each item is long; better to use

for each role's responsibilities. Could do

Phlebotomy Technician

but we shouldn't add extra headings beyond h3? Not prohibited but we should follow instruction: use

for section headings. It didn't forbid other headings, but to be safe we can just use

with bold? But we cannot use markdown. We can use inside

. That's okay. We'll output:

Responsibilities

Phlebotomy Technician: Collects blood and/or perform POC as assigned... (full text)

Sr. Phlebotomy Technician: Prepares staff schedule to provide adequate coverage and updates changes daily... (full text)

Similarly for Qualifications. We must ensure we preserve all substantive details from responsibilities and qualifications sections exactly as given (no omission). Need to copy the text exactly. Let's extract responsibilities text from posting. Phlebotomy Technician responsibilities block: "Phlebotomy Technician: Collects blood and/or perform POC as assignedCleans and re-stocks POC supplies and prepares phlebotomy carts/trays. Assists coworkers with draws and POC testing.Draws venous or capillary blood from newborn through geriatric aged patients using proper aseptic collection techniques.Draws and delivers (where applicable) all blood work (stat, timed, routine) within established departmental policy time frames.Draws venous and capillary blood into proper tubes and culture vials according to the purpose for which the blood is to be tested.Performs and processes all POC tests on patients ranging from newborn to geriatrics.Completes clerical functions associated with POC testing documents.Reports incidents/issues regarding patients or employees timely to group leader or supervisorReports supply needs and equipment defects in a timely fashion.Logs refrigerator temperatures daily and reports if falls out range to group leader or supervisor.Travels and performs phlebotomy duties and POC testing, as needed, at Health fair sand PSA testing sites and delivers specimens to laboratory.Identifies the needs of the patient population served and modifies and delivers care that is specific to those needs (i.e., age, culture, language, hearing and/or visually impaired, etc). This process includes communicating with the patient, parent, and/or primary caregiver(s) at their level (developmental/age, educational, literacy, etc.).Adheres to the standards identified in the clinics Organizational Competencies.Regular contact with clinic personnel, patients and visitors." Note there are missing spaces after colons and periods; we should preserve as is? The original had no spaces after some punctuation. We should keep exactly as given? Probably we should keep the text but we can add spaces for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't require exact formatting, but we should not change meaning. Adding spaces is okay but might be considered altering. Safer to keep as is, but it's hard to read. However we can keep the original text but we need to ensure it's readable. I think we can keep as is but maybe add spaces after periods where missing? That would be altering. I'd rather keep exactly as given, even if it's run-on. But we can insert line breaks for readability but not change words. The original had no spaces after some periods; we could keep that. Similarly Sr. Phlebotomy Technician responsibilities block: "Sr. Phlebotomy Technician: Prepares staff schedule to provide adequate coverage and updates changes dailyEnsures equitable distribution of workload.Troubleshoots and resolves issues with technicians, clinic staff etc. as needed in conjunction with the Supervisor.Monitors to ensure work is being performed efficiently.Establishes in conjunction with the Supervisor an onboarding program for new employees.Performs phlebotomy and POC testing as needed.Maintains drawing and POC testing carts/trays with necessary supplies.Maintains all necessary supplies and places orders in a timely fashion. Displays need for cost-effectiveness in the use of supplies and materials.Sorts timed specimen requis