Jobs · Information Technology · South Carolina

Visual Inspector Program Manager

Nephron Pharmaceuticals · West Columbia, SC · 3 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role? The description includes Job Purpose and Essential Duties and Responsibilities, Requirements, Knowledge & Skills, Education/Experience, Working Conditions / Physical Requirements. Also Salary range: Based on experience. That is not specific; it's "Based on experience" which is vague; we should not create Pay section unless posting actually states them. It says "Salary range: Based on experience." That's not a specific range; it's basically "Based on experience". According to instruction: 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. "Based on experience" is similar to "commensurate with experience". So we should NOT create a Pay section. Similarly no Schedule or Benefits given. So we will have sections: About the role (maybe Job Purpose), Responsibilities, Requirements (maybe combine Knowledge & Skills and Education/Experience?), Qualifications? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have Job Purpose (could be About the role). Essential Duties And Responsibilities -> Responsibilities. Requirements Knowledge & Skills -> maybe Skills? Or Requirements. Education/Experience -> Qualifications. Working Conditions / Physical Requirements -> maybe Working Conditions (but not in list). Could use a heading like Working Conditions (not in prescribed list but we can still use? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we should map content to those headings. We have About the role (Job Purpose). Responsibilities (Essential Duties). Requirements (maybe combine Knowledge & Skills and Education/Experience?). Skills (maybe separate Knowledge & Skills?). Qualifications (Education/Experience). We could have both Requirements and Skills and Qualifications. But we must avoid thin sections. Let's see content: Knowledge & Skills is a list of technical knowledge and abilities. Education/Experience is separate. Could combine them under Requirements? But we have both Requirements and Qualifications headings available. Perhaps we put Knowledge & Skills under Skills heading, and Education/Experience under Qualifications heading. And the generic Requirements heading could be omitted if we don't have distinct content. The "Requirements" heading could be used for the "Requirements Knowledge & Skills:" but that is essentially Skills. However the heading "Requirements" could be used for the list of requirements (knowledge & skills, education/experience). But we already have Skills and Qualifications. To avoid duplication, we could use Requirements for the combined list of knowledge & skills and education/experience, and skip Skills and Qualifications. But the instruction says prefer a few substantive sections over many thin ones. So maybe we use About the role, Responsibilities, Requirements (which includes knowledge & skills and education/experience), and Working Conditions (though not in list). But Working Conditions is not in the examples; but we could still use it as a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. We could put Working Conditions under Requirements? Not ideal. Could omit Working Conditions section entirely? But we must preserve ALL substantive information; we cannot drop Working Conditions. So we need a section for it. Could use a heading like Working Conditions (not in list but still an h3). The instruction didn't say we cannot use other headings; just gave examples. So we can use Working Conditions. Thus sections: About the role (Job Purpose), Responsibilities (Essential Duties And Responsibilities), Skills (Knowledge & Skills), Qualifications (Education/Experience), Working Conditions (Working Conditions / Physical Requirements). We'll not include Requirements heading to avoid duplication. Now we need to format content: Use

for prose,

  • for any list of duties/requirements/benefits. We need to preserve all substantive information, not invent or summarize away detail. So we need to copy the text exactly? We can keep the meaning but not omit details. We'll need to break long paragraphs into

    as appropriate. For lists, we need to detect bullet points. The original text uses sentences separated by periods; not explicit bullet list. However we can treat each duty as a separate

  • if they are separated by line breaks? The original is a paragraph with many sentences. The instruction: Use
    • for any list of duties/requirements/benefits. So we need to identify lists. The posting includes many duties separated by sentences; we could convert each duty into a list item. But we need to decide what constitutes a list. The original doesn't have bullet points; but we can still create a list of duties. However we must not invent or summarize away detail; converting sentences to list items preserves detail. That's acceptable. Similarly for Knowledge & Skills list: we can break into items. Education/Experience: also list. Working Conditions: list of physical requirements. We'll need to ensure we don't lose any detail. Let's extract content. Job Purpose paragraph: "The Visual Inspection Program Leader is responsible for the technical leadership, governance, and continuous improvement of the Visual Inspection Program for injectable and ophthalmic pharmaceutical products manufactured in a sterile environment. This role serves as a technical Subject Matter Expert (SME) and program owner, providing strategic direction for manual and automated visual inspection systems, inspector qualification, defect standards and test sets, AQL strategy, Probability of Detection (PoD) studies, defect classification, particulate characterization, inspection validation, and ongoing program performance. This position provides technical leadership across the full lifecycle of Visual Inspection Program initiatives—from strategy and risk assessment through study design, execution, data analysis, implementation, effectiveness monitoring, and continuous improvement—while serving as a key technical representative during customer, regulatory, and quality audits." We'll put that in a

      under About the role. Responsibilities: The block "Essential Duties And Responsibilities" then a long paragraph with many duties separated by periods. We'll split into list items at each sentence that starts with a verb? Let's copy sentences: - Own and provide technical leadership for the Visual Inspection Program, including program strategy, governance, standards, procedures, protocols, technical reports, and continuous improvement initiatives. - Develop, review, approve, and maintain technical documentation supporting visual inspection activities, including: - Inspector training, qualification, and requalification programs - Defect classification standards and libraries - Defect test sets and test set lifecycle management - AQL sampling strategies and acceptance criteria - Manual Visual Inspection (MVI) strategies - Automated Visual Inspection (AVI) strategies - Visual inspection validation and qualification protocols - Probability of Detection (PoD) study protocols and reports - Establish scientifically sound and risk-based approaches for assessing inspection capability, defect detectability, inspection effectiveness, and product quality risk. - Lead defect classification, defect characterization, reject trending, and particulate identification initiatives to improve product and process understanding. - Develop, qualify, and maintain defect standards that represent actual manufacturing defect populations and appropriately challenge inspection systems. - Evaluate inspection program performance using statistical and data-driven approaches and translate findings into actionable technical improvements. - Partner cross-functionally to drive process improvements and implement upstream particulate control strategies. - Serve as Subject Matter Expert (SME) for Visual Inspection during client and regulatory audits, ensuring alignment with FDA, PDA, USP, and industry best practices. - Provide SME support for manufacturing operations, deviations, and investigations, ensuring thorough root cause analysis and effective resolutions. - Deliver technical guidance on inspection methods, including validation activities and Manual Visual Inspection (MVI) to Automated Visual Inspection (AVI) performance comparisons. - Drive project execution across the full lifecycle, including strategic planning, timeline development, and cross-functional resource management. - Lead and mentor team members, fostering talent development through coaching, knowledge sharing, and performance guidance. - Prioritize and delegate tasks effectively to optimize team productivity and meet organizational goals. - Demonstrate strong communication, presentation, and influencing skills to engage stakeholders, clients, and internal teams. - Assist with additional work duties or responsibilities as evident or required. We need to keep the sublist under "Develop, review, approve, and maintain technical documentation supporting visual inspection activities, including:" as a nested list? The instruction says use

      • for any list of duties/requirements/benefits. So we can have a
          for the main duties, and inside that, for the sublist we can also use
          • . That's fine. Now Skills (Knowledge & Skills): The paragraph: "Knowledge & Skills: Strong technical knowledge of pharmaceutical visual inspection principles, including Manual Visual Inspection (MVI), Automated Visual Inspection (AVI), defect detection, defect classification, particulate assessment, container/closure defects, and inspection system performance. Strong understanding of sterile injectable and/or ophthalmic pharmaceutical manufacturing processes and their relationship to visible particulate, cosmetic defects, container integrity, and other inspection attributes. In-depth knowledge of applicable cGMP, GDP, FDA regulations and guidance, USP requirements, PDA technical reports, and relevant industry standards related to visual inspection and sterile pharmaceutical manufacturing. Ability to develop scientifically sound protocols, technical reports, acceptance criteria, study designs, and technical justifications. Must be able to work individually and on a team." We can split into list items each sentence. Now Qualifications (Education/Experience): The paragraph: "Education/Experience Bachelor's degree in Pharmaceutical Sciences, Chemistry, Biology, Engineering, Life Sciences, or a related scientific or technical discipline required.Master's degree or advanced technical education preferred.7+ years of progressive experience in pharmaceutical manufacturing, quality, visual inspection, validation, technical operations, or a related discipline, with significant experience in sterile injectable and/or ophthalmic manufacturing.Experience leading cross-functional technical projects from strategy and planning through execution, implementation, and effectiveness monitoring.Experience supporting regulatory inspections, customer audits, deviations, investigations, CAPA, change controls, and other quality systems activities as a technical SME.Experience with statistical analysis, defect/reject trending, data interpretation, and risk-based decision-making preferred.Experience with automated inspection technologies, inspection equipment qualification, or MVI/AVI comparability assessments highly preferred.Experience working within aseptic processing and sterile manufacturing environments highly preferred.Equivalent combination of education, technical expertise, and relevant pharmaceutical experience may be considered where appropriate." We need to split into list items. Note there are no spaces after periods; we need to add spaces for readability but not change meaning. We'll just separate sentences. Now Working Conditions / Physical Requirements: The paragraph: "Working Conditions / Physical Requirements Position may require bending, typing climbing, lifting (up to 15lbs.), reaching, vision (20/20 corrected), standing, sitting, walking, and hearing." We need to split into list items? It's a single sentence; we can keep as

            or

            • . Since it's a list of requirements, we can make a
              • with the whole sentence, or break each item. Better to break each item: bending, typing climbing (maybe "typing, climbing"?), lifting (up to 15lbs.), reaching, vision (20/20 corrected), standing, sitting, walking, and hearing. We'll keep as list. Now we need to output only HTML fragment, no markdown. We'll structure:

                About the role

                ...

                Responsibilities

                • Own and provide technical leadership for the Visual Inspection Program, including program strategy, governance, standards, procedures, protocols, technical

Similar jobs

Program Manager

Shrive TechnologiesFremont, CA· 1 mo ago
Information Technology

Program Manager

Inherent TechnologiesSanta Clara, CA· 1 mo ago
Information Technology

Program Manager

MANTECHLinthicum Heights, MD· 1 mo ago
Information Technology

Program Manager

BorgWarnerAuburn Hills, MI· 1 mo ago
Information Technologyapply on borgwarner.wd5.myworkdayjobs.com

Program Manager

Terran Orbital CorporationIrvine, CA· 1 mo ago
Project Management$175k/yrapply on grnh.se

Program Manager

DevereuxPitman, NJ· 1 mo ago
Information Technology$58k–$68k/yrapply on careers-devereux.icims.com