QA/QMS Senior Specialist — Deviations & Investigations

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have About the Company (but not required heading). The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The posting includes "About the Company" (maybe we treat as About the role? Actually "About the role" is typical heading for role description. We have "Position Summary". Could map that to About the role. We'll include

About the role

with paragraph(s) from Position Summary and maybe About the Company? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include About the role (position summary). Also we have "Key Responsibilities" -> Responsibilities section. "Qualifications" -> Qualifications section. There's also "What We Offer" and "Benefits:" and "Pay range". So we can have Benefits and Pay sections. There's no explicit Skills section separate; but we could embed skills within Qualifications or maybe we can create Skills if there is content. The posting mentions skills: root cause analysis tools, technical writing, TrackWise, etc. Those could go under Skills. But we already have Qualifications covering education, experience, expertise. Might be okay to not create Skills if no distinct content. However we could create Skills section for technical skills: root cause analysis tools, TrackWise, technical writing, knowledge of regulations. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills? But they said use headings for those categories if content exists. We have content for Qualifications (education, experience). We also have content for Skills (tools, systems). Could split. Let's decide: We'll have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. No Schedule (not mentioned). We'll not include Requirements (maybe same as Qualifications). But we have Qualifications already. Requirements could be same as Qualifications; but we can omit Requirements if we already have Qualifications. The instruction: "include a section ONLY when the posting has real, specific content for it". So we need to decide which headings to use. We have content for About the role (position summary). Responsibilities (key responsibilities). Qualifications (education, experience). Skills (tools, systems, writing, regulations). Benefits (benefits list). Pay (pay range). We'll not include Requirements (maybe duplicate). We'll not include Schedule. Now we need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the Additional Information (EEO) and maybe the "If you're excited..." line? That's encouragement to apply, maybe considered application instruction? It's not exactly instruction but could be considered boilerplate. Safer to drop it. Also drop "Additional Information:" line. Also drop "Job Location:" maybe minor metadata; we can fold into a short

or drop it. The instruction: fold minor metadata into a short

or drop it. So we could include a

for location. But they said do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we could include a short

at top maybe. But we need to preserve ALL substantive information; location is substantive? It's location of job. Might be considered substantive. But they said fold minor metadata into a short

or drop it. So we can include a

for location. Let's include a

with location. Now we need to output only HTML fragment. Use

headings,

• for lists,

  for prose. We need to ensure we don't create empty sections. Let's extract content. About the Company paragraph: Could be considered About the role? Actually About the Company is separate. But we have Position Summary: "Nivagen Pharmaceuticals is looking for a QA/QMS Senior Specialist - Deviations & Investigations to lead the deviation management process across sterile GMP manufacturing operations. This individual will be responsible for the timely initiation, investigation, root cause analysis, and closure of deviations in compliance with FDA/cGMP requirements. The role serves as the central point of contact for deviation lifecycle management and requires strong investigative skills, technical writing ability, and cross-functional coordination." We could also include About the Company as part of About the role? Might be okay to include About the Company as a paragraph under About the role. But the heading "About the role" expects description of role, not company. However we can include both. The instruction didn't forbid adding extra paragraphs under heading. We'll put About the role: combine Position Summary and maybe a brief about company? But to be safe, we can put Position Summary under About the role, and maybe add a separate

  for About the Company? But there is no heading for About the Company. Could we treat it as part of About the role? Might be okay. Alternatively, we could create a heading "About the Company" but not in allowed list. 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 says use those for section headings. It might be safer to stick to those headings only. So we will not create About the Company heading. We'll incorporate its content maybe under About the role as a brief intro. Thus About the role

  About the role

  ... (position summary plus maybe company description). We'll include both. Now Responsibilities: list of key responsibilities. We'll convert each sentence into

• . Qualifications: list of qualifications (education, experience, expertise, etc). We'll bullet. Skills: list of skills: root cause analysis tools (Ishikawa, 5-Why, FMEA, fault tree analysis), hands-on experience investigating sterile-specific deviations (list), proficiency with TrackWise, Veeva QMS, or equivalent electronic quality management systems, strong technical writing skills, working knowledge of 21 CFR Parts 210, 211, 212; ICH Q7 and Q10; FDA guidance on investigating deviations, experience supporting FDA Pre-Approval Inspections (PAI) or routine GMP inspections is a plus, working familiarity with adjacent QMS processes (CAPA and Change Control) is strongly preferred; willingness to cross-train across these subsystems is required. We'll bullet. Benefits: The posting says: "What We Offer Competitive salary and comprehensive benefits package. Opportunity to build QMS infrastructure from the ground up at a growing pharmaceutical company. Direct impact on FDA inspection readiness and commercial manufacturing success. Collaborative work environment with a supportive quality leadership team. Professional development and career growth opportunities." Then "Benefits: Pay range $80,000-$90,000 per YearYearly bonus eligibilityBenefits: Nivagen offers a wide variety of benefits and programs to support health and well-beingMedical, dental and vision coveragePaid time off plan". There's duplication. We need to extract substantive benefits: competitive salary, comprehensive benefits package, opportunity to build QMS infrastructure, direct impact on FDA inspection readiness, commercial manufacturing success, collaborative work environment, supportive quality leadership team, professional development, career growth opportunities. Then specific benefits: medical, dental, vision coverage, paid time off plan, yearly bonus eligibility. Pay range $80,000-$90,000 per year. We need Benefits section (maybe list of benefits like medical, dental, vision, PTO, yearly bonus). Pay section separate for pay range. Thus Benefits

  Benefits

  • Medical, dental, and vision coverage
  • Paid time off plan
  • Yearly bonus eligibility
  Pay

  Pay

  Pay range $80,000-$90,000 per year

  We might also include the other offerings under Benefits? Could be considered benefits but they are more like "What We Offer". Could be included in Benefits as well. But to avoid thin sections, we could combine them into Benefits. However the instruction says prefer few substantive sections over many thin ones. So we could merge "What We Offer" into Benefits section as well. But we already have Benefits heading; we can include all offerings under Benefits. Pay separate. Thus Benefits
  includes: Competitive salary and comprehensive benefits package, Opportunity to build QMS infrastructure from the ground up at a growing pharmaceutical company, Direct impact on FDA inspection readiness and commercial manufacturing success, Collaborative work environment with a supportive quality leadership team, Professional development and career growth opportunities, Medical, dental, and vision coverage, Paid time off plan, Yearly bonus eligibility. That's many items but okay. Now we need to ensure we don't include any boilerplate like "Additional Information:" etc. Now produce HTML. Structure:

  Location: Nivagen Pharmaceuticals Inc., Sacramento, CA 3900 Duckhorn Dr, Sacramento, CA 95834

  maybe. Then

  About the role

  ...

  Then

  Responsibilities

  ...
  Then

  Qualifications

  ...
  Then

  Skills

  ...
  Then

  Benefits

  ...
  Then

  Pay

  ...

  Make sure no extra whitespace? It's fine. Now extract exact sentences. About the role: combine Position Summary and maybe About the Company? Let's include Position Summary only. But we could also add a brief about company as part of About the role? Might be okay but risk of adding non-role content. Safer to just use Position Summary. Thus:

  Nivagen Pharmaceuticals is looking for a QA/QMS Senior Specialist - Deviations & Investigations to lead the deviation management process across sterile GMP manufacturing operations. This individual will be responsible for the timely initiation, investigation, root cause analysis, and closure of deviations in compliance with FDA/cGMP requirements. The role serves as the central point of contact for deviation lifecycle management and requires strong investigative skills, technical writing ability, and cross-functional coordination.

  Now Responsibilities: list each bullet from "Key Responsibilities". Let's extract: - Own the deviation lifecycle from initiation through investigation, root cause analysis, corrective action identification, and closure within established timelines. - Serve as the primary point of contact for all deviation-related activities across Manufacturing, Quality Control, Engineering, and Validation departments. - Conduct thorough root cause analyses using structured methodologies including Ishikawa (6M), 5-Why, and fault tree analysis. - Author investigation narratives, initial quality assessments (IQAs), and final deviation reports in TrackWise. - Classify deviations by severity (Critical, Major, Minor) and assess impact on product quality, patient safety, validated state, and regulatory compliance. - Coordinate batch disposition activities in collaboration with QA batch release and QC laboratory teams. - Identify recurring deviation trends and escalate to the CAPA system when systematic issues are identified. - Track and report deviation KPIs including open aging, cycle time, recurrence rates, and root cause categories during management review. - Support internal audits and FDA/regulatory inspections by providing deviation records, trending data, and investigation summaries. - Ensure all deviations