Product Lifecycle Compliance Team Leader
GSK · Zebulon, NC · 1 mo ago
RemoteRemoteProductFull-time
We need to output HTML fragment with sections: headings for sections present with real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve substantive info.
We need to parse the posting: It includes Business Introduction, Position Summary, Responsibilities, Why You? (maybe includes Work arrangement, Basic Qualification, Preferred Qualification), How To Apply (should be removed), About The Zebulon Site (maybe keep as part of description?), Skills, Benefits (link to GSK US Benefits Summary but no details), Why GSK? (maybe keep?), plus some other sections like Work arrangement, Basic Qualification, Preferred Qualification.
We need to decide which sections to include based on real specific content.
We must include sections only when posting has real, specific content for it. Use
for sections present with real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve substantive info.
We need to parse the posting: It includes Business Introduction, Position Summary, Responsibilities, Why You? (maybe includes Work arrangement, Basic Qualification, Preferred Qualification), How To Apply (should be removed), About The Zebulon Site (maybe keep as part of description?), Skills, Benefits (link to GSK US Benefits Summary but no details), Why GSK? (maybe keep?), plus some other sections like Work arrangement, Basic Qualification, Preferred Qualification.
We need to decide which sections to include based on real specific content.
We must include sections only when posting has real, specific content for it. Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can use other headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those exact headings if applicable. But we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Probably they expect we use those headings when appropriate. However we can also have other headings like "Business Introduction" maybe not needed. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use other headings if needed but likely they want those standard headings. We'll map content to these sections.
We need to decide what goes where.
- About the role: Could be Position Summary + Business Introduction? Probably "About the role" corresponds to Position Summary and maybe Business Introduction. We'll put Position Summary content there.
- Responsibilities: list of duties.
- Requirements: maybe Basic Qualification.
- Qualifications: maybe Preferred Qualification.
- Skills: list of skills.
- Benefits: we have link to GSK US Benefits Summary but no details; we should not create Benefits section unless posting actually states them. It only says "Please visit GSK US Benefits Summary to learn more about the comprehensive benefits program GSK offers US employees." That's not specific benefits; it's a referral. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Since it doesn't state specific benefits, we should omit Benefits section.
- Pay: not stated; omit.
- Schedule: Work arrangement is hybrid; that's schedule info. So we can include Schedule section with that content.
We also have "Why You?" which includes Work arrangement, Basic Qualification, Preferred Qualification. We'll split.
We also have "About The Zebulon Site" which is descriptive; could be part of About the role or maybe separate but not a standard heading. Could be included in About the role.
We also have "Skills" list.
We also have "Why GSK?" which is fluff; maybe we can omit as it's boilerplate? It's somewhat generic but maybe considered boilerplate? It's about company mission; could be considered boilerplate but it's specific to GSK. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why GSK?" might be considered boilerplate but it's not legal; it's marketing. Might be okay to keep? However they said prefer a few substantive sections over many thin ones. Might be better to omit "Why GSK?" as it's not directly about the role. But we could include as part of About the role? Not sure.
We also have "How To Apply" which must be removed.
We also have "Important notice to Employment businesses/ Agencies" etc - legal boilerplate; remove.
We also have "If you require an accommodation..." etc - remove.
We also have "GSK is an Equal Opportunity Employer." - remove.
We also have "Please note that if you are a US Licensed Healthcare Professional..." - remove.
Thus we keep: Business Introduction (maybe as part of About the role), Position Summary, Responsibilities, Work arrangement (Schedule), Basic Qualification (Requirements), Preferred Qualification (Qualifications), Skills, About The Zebulon Site (maybe part of About the role), maybe we can keep as a separate section "About the site" but not in list; but we could incorporate.
We need to output only HTML fragment, no markdown fences.
We'll structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those exact headings if applicable. But we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Probably they expect we use those headings when appropriate. However we can also have other headings like "Business Introduction" maybe not needed. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use other headings if needed but likely they want those standard headings. We'll map content to these sections.
We need to decide what goes where.
- About the role: Could be Position Summary + Business Introduction? Probably "About the role" corresponds to Position Summary and maybe Business Introduction. We'll put Position Summary content there.
- Responsibilities: list of duties.
- Requirements: maybe Basic Qualification.
- Qualifications: maybe Preferred Qualification.
- Skills: list of skills.
- Benefits: we have link to GSK US Benefits Summary but no details; we should not create Benefits section unless posting actually states them. It only says "Please visit GSK US Benefits Summary to learn more about the comprehensive benefits program GSK offers US employees." That's not specific benefits; it's a referral. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Since it doesn't state specific benefits, we should omit Benefits section.
- Pay: not stated; omit.
- Schedule: Work arrangement is hybrid; that's schedule info. So we can include Schedule section with that content.
We also have "Why You?" which includes Work arrangement, Basic Qualification, Preferred Qualification. We'll split.
We also have "About The Zebulon Site" which is descriptive; could be part of About the role or maybe separate but not a standard heading. Could be included in About the role.
We also have "Skills" list.
We also have "Why GSK?" which is fluff; maybe we can omit as it's boilerplate? It's somewhat generic but maybe considered boilerplate? It's about company mission; could be considered boilerplate but it's specific to GSK. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why GSK?" might be considered boilerplate but it's not legal; it's marketing. Might be okay to keep? However they said prefer a few substantive sections over many thin ones. Might be better to omit "Why GSK?" as it's not directly about the role. But we could include as part of About the role? Not sure.
We also have "How To Apply" which must be removed.
We also have "Important notice to Employment businesses/ Agencies" etc - legal boilerplate; remove.
We also have "If you require an accommodation..." etc - remove.
We also have "GSK is an Equal Opportunity Employer." - remove.
We also have "Please note that if you are a US Licensed Healthcare Professional..." - remove.
Thus we keep: Business Introduction (maybe as part of About the role), Position Summary, Responsibilities, Work arrangement (Schedule), Basic Qualification (Requirements), Preferred Qualification (Qualifications), Skills, About The Zebulon Site (maybe part of About the role), maybe we can keep as a separate section "About the site" but not in list; but we could incorporate.
We need to output only HTML fragment, no markdown fences.
We'll structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use other headings if needed but likely they want those standard headings. We'll map content to these sections.
We need to decide what goes where.
- About the role: Could be Position Summary + Business Introduction? Probably "About the role" corresponds to Position Summary and maybe Business Introduction. We'll put Position Summary content there.
- Responsibilities: list of duties.
- Requirements: maybe Basic Qualification.
- Qualifications: maybe Preferred Qualification.
- Skills: list of skills.
- Benefits: we have link to GSK US Benefits Summary but no details; we should not create Benefits section unless posting actually states them. It only says "Please visit GSK US Benefits Summary to learn more about the comprehensive benefits program GSK offers US employees." That's not specific benefits; it's a referral. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Since it doesn't state specific benefits, we should omit Benefits section.
- Pay: not stated; omit.
- Schedule: Work arrangement is hybrid; that's schedule info. So we can include Schedule section with that content.
We also have "Why You?" which includes Work arrangement, Basic Qualification, Preferred Qualification. We'll split.
We also have "About The Zebulon Site" which is descriptive; could be part of About the role or maybe separate but not a standard heading. Could be included in About the role.
We also have "Skills" list.
We also have "Why GSK?" which is fluff; maybe we can omit as it's boilerplate? It's somewhat generic but maybe considered boilerplate? It's about company mission; could be considered boilerplate but it's specific to GSK. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why GSK?" might be considered boilerplate but it's not legal; it's marketing. Might be okay to keep? However they said prefer a few substantive sections over many thin ones. Might be better to omit "Why GSK?" as it's not directly about the role. But we could include as part of About the role? Not sure.
We also have "How To Apply" which must be removed.
We also have "Important notice to Employment businesses/ Agencies" etc - legal boilerplate; remove.
We also have "If you require an accommodation..." etc - remove.
We also have "GSK is an Equal Opportunity Employer." - remove.
We also have "Please note that if you are a US Licensed Healthcare Professional..." - remove.
Thus we keep: Business Introduction (maybe as part of About the role), Position Summary, Responsibilities, Work arrangement (Schedule), Basic Qualification (Requirements), Preferred Qualification (Qualifications), Skills, About The Zebulon Site (maybe part of About the role), maybe we can keep as a separate section "About the site" but not in list; but we could incorporate.
We need to output only HTML fragment, no markdown fences.
We'll structure:
About the role
Business Introduction paragraph(s) + Position Summary paragraph(s) maybe combined.
Responsibilities
- ... each responsibility.
Schedule
Work arrangement: hybrid, expected to work on-site regularly, with flexibility for remote work as agreed with your manager.
Requirements
- 8+ years experience in a GMP-regulated pharmaceutical environment, with 5+ years of relevant experience in a quality or compliance role.
- Experience leading people and cross-functional activities.
- Bachelor’s degree in Pharmaceutical Sciences, Chemistry, Biology, Engineering, or other relevant scientific or technical discipline or sufficient technical depth or professional experience.
- Demonstrated experience with US regulatory requirements, experience supporting regulatory inspections, and strong experience with good manufacturing practices.
- Knowledge of product lifecycle compliance activities, including regulatory commitments, submissions, registrations, license renewals, change controls, product reviews, stability programs, and associated reporting requirements.
Qualifications
- Advanced degree in a scientific, technical, or regulatory discipline.
- Experience managing quality agreements and supplier or third-party oversight.
- Experience with periodic product review programs and product lifecycle compliance activities.
- Good working knowledge of GSK marketed products (US & International) with emphasis on Chemistry, Manufacturing and Controls (CMC).
- Strong written and verbal communication skills and comfort preparing leadership reports and dashboards.
- Experience in continuous improvement or operational excellence programs.
Skills
- Data Integrity
- Digital Fluency
- GxP Regulations
- Influencing Without Authority
- Lean Management
- Pharmaceutical Regulatory Compliance
- Problem Solving
- Quality Assurance (QA)
- Risk Awareness
- Technical Writing