Healthcare Project Delivery Consultant

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules carefully: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists,

  for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Prefer few substantive sections over many thin ones 10. Output ONLY HTML fragment — no /, no markdown code fences Let me analyze the posting: - Title: "Healthcare Project Delivery Consultant" (already shown on page, so don't repeat as heading) - "The Role" section: describes what the role is about - "What You'll Do": list of responsibilities - "What You Need": requirements/qualifications - "Location & Compensation": includes location (Hybrid- Dallas, Texas) and compensation range ($88,000-$132,000) - "Who We Are": company description (boilerplate? but it's specific to UST) - "Benefits": detailed benefits information - "Equal Employment Opportunity Statement": boilerplate, should remove - "Skills": listed at bottom (Project Management, Jira, Scrum) I need to structure this into appropriate sections. The rules say use

  for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". I should only include sections that have real content. Let me map: - "The Role" -> could be "About the role" (prose) - "What You'll Do" -> "Responsibilities" (list) - "What You Need" -> "Requirements" or "Qualifications" (list, includes both required and preferred) - "Location & Compensation" -> "Pay" (since it has compensation range) and maybe "Schedule" (location/hybrid) - "Who We Are" -> maybe "About the company" but not in the listed heading types. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is company description, not in list. Could fold into a paragraph under "About the role" or omit? The rule says preserve ALL substantive information. But also says prefer few substantive sections over many thin ones. I could include a "About the company" but not in allowed headings. The allowed headings are examples, but the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." meaning those are examples, but likely we should stick to those. However, "Who We Are" is substantive. I could include it as a paragraph under "About the role" or create a separate section with a heading not in list? The rule says "use

  for section headings (e.g. ...)" - it doesn't forbid other headings, but says "e.g." So I can use other headings if needed. But to be safe, I'll include "About the company" as a heading? The rule says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings". It doesn't forbid other headings. However, the instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I can include a section for "About the company" if there's real content. But the allowed headings list might be the only ones we should use. The user says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests those are the expected headings. I'll map accordingly. Let's decide sections: 1. About the role: from "The Role" paragraph. 2. Responsibilities: from "What You'll Do" list. 3. Requirements: from "What You Need" required items. 4. Qualifications: from "What You Need" preferred items (or combine with Requirements). The posting has "What You Need" with bullet points, some marked "(Preferred)". I could split into "Requirements" and "Qualifications" (preferred). Or keep as one "Requirements" list with notes. The rule says "Requirements, Qualifications" as separate headings. I'll do both: "Requirements" for required, "Qualifications" for preferred. 5. Skills: from the bottom "Skills" line (Project Management, Jira, Scrum). But also skills are embedded in requirements. The posting has a "Skills" line at the end. I'll include a "Skills" section with those three. 6. Pay: from "Compensation Range: $88,000-$132,000" 7. Schedule: from "Role Location: Hybrid- Dallas, Texas" (hybrid schedule) 8. Benefits: from "Benefits" section (detailed) "Who We Are" is company description. I could include as a paragraph under "About the role" or as a separate "About the company" heading. Since not in example list, I'll include as a paragraph under "About the role" or maybe as a separate section with heading "About the company". But the rule says "use

  for section headings (e.g. ...)" - it's not exhaustive. I'll include it as a separate section with heading "About the company" to preserve substantive info. However, the user might expect only those headings. Let's see: the posting has "Who We Are" which is company description. It's substantive. I'll include it as a section with heading "About the company". But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine "Who We Are" into "About the role" as a paragraph. I'll do that: after "The Role" paragraph, add a paragraph about the company. Also need to remove EEO statement, "UST reserves the right..." etc. Now, structure: -

  About the role

  The Role paragraph

  Who We Are paragraph

  -

  Responsibilities

  • ... each bullet from "What You'll Do"
  -

  Requirements

  • ... required items (without "(Preferred)")
  -

  Qualifications

  • ... preferred items (with "(Preferred)" removed or noted)
  -

  Skills

  • Project Management
  • Jira
  • Scrum
  -

  Pay

  Compensation Range: $88,000-$132,000

  -

  Schedule

  Hybrid - Dallas, Texas

  -

  Benefits

  • ... each benefit bullet
  But the benefits section is long prose with multiple sentences. I need to break into list items. The benefits paragraph describes multiple benefits: paid vacation, sick leave, holidays, bereavement, jury duty, 401(k) matching, medical/dental/vision, life insurance, disability, HSA, FSA, etc. Also different for part-time, temporary, etc. I'll create a list summarizing each distinct benefit. However, the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the detail. But using
  • for list of benefits. I can break the paragraph into multiple list items, each capturing a distinct benefit. But the paragraph is a block of text. I could keep as a single

    but the rule says "Use

    • for any list of duties/requirements/benefits". Benefits are a list, so I should use list. I'll parse the benefits text into individual bullet points. Let's parse benefits text: "Full-time, regular employees accrue a minimum of 10 days of paid vacation per year, receive 6 days of paid sick leave each year (pro-rated for new hires throughout the year), 10 paid holidays, and are eligible for paid bereavement leave and jury duty. They are eligible to participate in the Company’s 401(k) Retirement Plan with employer matching. They and their dependents residing in the US are eligible for medical, dental, and vision insurance, as well as the following Company-paid Employee Only benefits: basic life insurance, accidental death and disability insurance, and short- and long-term disability benefits. Regular employees may purchase additional voluntary short-term disability benefits, and participate in a Health Savings Account (HSA) as well as a Flexible Spending Account (FSA) for healthcare, dependent child care, and/or commuting expenses as allowable under IRS guidelines. Benefits offerings vary in Puerto Rico. Part-time employees receive 6 days of paid sick leave each year (pro-rated for new hires throughout the year) and are eligible to participate in the Company’s 401(k) Retirement Plan with employer matching. Full-time temporary employees receive 6 days of paid sick leave each year (pro-rated for new hires throughout the year) and are eligible to participate in the Company’s 401(k) program with employer matching. They and their dependents residing in the US are eligible for medical, dental, and vision insurance. Part-time temporary employees receive 6 days of paid sick leave each year (pro-rated for new hires throughout the year). All US employees who work in a state or locality with more generous paid sick leave benefits than specified here will receive the benefit of those sick leave laws." I'll create list items for each distinct benefit category, but preserve detail. Could be many list items. I'll group by employee type? Might be too many. The rule says "Preserve ALL substantive information". I'll create a list with each sentence as a bullet? But some sentences have multiple benefits. I'll break into logical bullets: - Full-time regular employees: minimum 10 days paid vacation per year - Full-time regular employees: 6 days paid sick leave per year (pro-rated for new hires) - Full-time regular employees: 10 paid holidays - Full-time regular employees: eligible for paid bereavement leave and jury duty - Full-time regular employees: eligible for 401(k) Retirement Plan with employer matching - Full-time regular employees and dependents in US: eligible for medical, dental, and vision insurance - Full-time regular employees: company-paid basic life insurance, accidental death and disability insurance, short- and long-term disability benefits - Regular employees: may purchase additional voluntary short-term disability benefits - Regular employees: may participate in Health Savings Account (HSA) - Regular employees: may participate in Flexible Spending Account (FSA) for healthcare, dependent child care, and/or commuting expenses per IRS guidelines - Benefits offerings vary in Puerto Rico - Part-time employees: 6 days paid sick leave per year (pro-rated), eligible for 401(k) with employer matching - Full-time temporary employees: 6 days paid sick leave per year (pro-rated),