Associate Director, Global PV Product Complaint Management & Oversight
United Therapeutics Corporation · Raleigh-Durham-Chapel Hill Area · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to parse the job posting. It includes:
- Who We Are (company description) – could be "About the role"? Actually "Who We Are" is company overview. Could be placed under "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). Also remove "California, US residents click here." That's likely a navigation link; remove.
We need to keep the job details: Who We Are description, Who You Are (role description), responsibilities (the long list), Minimum Requirements, Preferred Qualifications, Job Location (Durham, NC hybrid schedule), Benefits mention (eligible employees may participate in comprehensive benefits suite...), also mention "At United Therapeutics, our mission..." maybe part of About the role? Could be included.
We must not repeat the job title as a heading. The job title is "Associate Director, Global PV Product Complaint Management & Oversight". Not to be used as heading.
We must not put Job ID/requisition numbers as headings – none present.
We need to decide sections:
- About the role: could contain "Who We Are" and maybe mission statement.
- Responsibilities: the bullet list of duties (the long paragraph after "Who You Are").
- Requirements: Minimum Requirements.
- Qualifications: Preferred Qualifications.
- Skills: maybe we could extract skills from requirements? But we have separate sections; we could put skills under Requirements or Qualifications. But we need to follow instruction: use sections only when posting has real specific content. The posting includes Minimum Requirements and Preferred Qualifications; we can map those to Requirements and Qualifications sections. Skills could be derived but not explicitly separate; maybe we can omit Skills section if not explicitly stated. However the posting includes many skill-like items within requirements (e.g., Strong written and verbal communication skills, Project management skills, etc.). Could create a Skills section but we must not invent or summarize away detail; we could extract those skill statements and put them under Skills. But the instruction says preserve ALL substantive information; we can keep them in Requirements or Qualifications. It's okay to have them there.
- Benefits: posting mentions "Eligible employees may participate in the Company’s comprehensive benefits suite of programs, including medical / dental / vision / prescription coverage, employee wellness resources, savings plans (401k and ESPP), paid time off & paid parental leave benefits, disability benefits, and more." Also link. So we can create Benefits section.
- Pay: not mentioned; omit.
- Schedule: mentions hybrid schedule: 3 days in office, option to work 2 days each week from home. Also "In office requirements could change based on business needs." So we can create Schedule section.
We also have Job Location: Durham, NC office. Could be part of Schedule or separate? Not a defined heading; we could include location within Schedule or maybe under About the role? Probably include location in Schedule section (or maybe a separate "Location" but not in allowed headings). Since only allowed headings are those listed, we can put location inside Schedule or Benefits? Better to put location inside Schedule as it's about work arrangement. Or we could add a brief paragraph under Schedule: "Located at Durham, NC office with hybrid schedule..."
We must not include boilerplate like EEO statement, etc. Remove "United Therapeutics Corporation is an Equal Opportunity Employer, including veterans and individuals with disabilities." Also remove the link to benefits maybe keep description but not the URL? The instruction: preserve ALL substantive information; the URL is substantive? It's a link for additional info; could be considered boilerplate? It's not navigation/legal/EEO; it's a link to benefits. Might keep but it's a URL; we can keep as plain text.
We must output only HTML fragment, no /, no markdown fences.
We'll structure:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). Also remove "California, US residents click here." That's likely a navigation link; remove.
We need to keep the job details: Who We Are description, Who You Are (role description), responsibilities (the long list), Minimum Requirements, Preferred Qualifications, Job Location (Durham, NC hybrid schedule), Benefits mention (eligible employees may participate in comprehensive benefits suite...), also mention "At United Therapeutics, our mission..." maybe part of About the role? Could be included.
We must not repeat the job title as a heading. The job title is "Associate Director, Global PV Product Complaint Management & Oversight". Not to be used as heading.
We must not put Job ID/requisition numbers as headings – none present.
We need to decide sections:
- About the role: could contain "Who We Are" and maybe mission statement.
- Responsibilities: the bullet list of duties (the long paragraph after "Who You Are").
- Requirements: Minimum Requirements.
- Qualifications: Preferred Qualifications.
- Skills: maybe we could extract skills from requirements? But we have separate sections; we could put skills under Requirements or Qualifications. But we need to follow instruction: use sections only when posting has real specific content. The posting includes Minimum Requirements and Preferred Qualifications; we can map those to Requirements and Qualifications sections. Skills could be derived but not explicitly separate; maybe we can omit Skills section if not explicitly stated. However the posting includes many skill-like items within requirements (e.g., Strong written and verbal communication skills, Project management skills, etc.). Could create a Skills section but we must not invent or summarize away detail; we could extract those skill statements and put them under Skills. But the instruction says preserve ALL substantive information; we can keep them in Requirements or Qualifications. It's okay to have them there.
- Benefits: posting mentions "Eligible employees may participate in the Company’s comprehensive benefits suite of programs, including medical / dental / vision / prescription coverage, employee wellness resources, savings plans (401k and ESPP), paid time off & paid parental leave benefits, disability benefits, and more." Also link. So we can create Benefits section.
- Pay: not mentioned; omit.
- Schedule: mentions hybrid schedule: 3 days in office, option to work 2 days each week from home. Also "In office requirements could change based on business needs." So we can create Schedule section.
We also have Job Location: Durham, NC office. Could be part of Schedule or separate? Not a defined heading; we could include location within Schedule or maybe under About the role? Probably include location in Schedule section (or maybe a separate "Location" but not in allowed headings). Since only allowed headings are those listed, we can put location inside Schedule or Benefits? Better to put location inside Schedule as it's about work arrangement. Or we could add a brief paragraph under Schedule: "Located at Durham, NC office with hybrid schedule..."
We must not include boilerplate like EEO statement, etc. Remove "United Therapeutics Corporation is an Equal Opportunity Employer, including veterans and individuals with disabilities." Also remove the link to benefits maybe keep description but not the URL? The instruction: preserve ALL substantive information; the URL is substantive? It's a link for additional info; could be considered boilerplate? It's not navigation/legal/EEO; it's a link to benefits. Might keep but it's a URL; we can keep as plain text.
We must output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
Who We Are paragraph(s) plus mission statement maybe.
Responsibilities
- ... each duty as list items.