Senior Quality Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No metadata like location etc unless we fold into short p. We can include location in a short p maybe. The instructions: "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 location etc in a short p before sections. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections only when posting has real specific content. Let's parse the posting: - Job Title: Senior Quality Engineer - Location: WMFTS - USA - Supply - Devens, MA - Location Type: On-Site - Website: https://www.wmfts.com/en/ - Group: https://www.spiraxgroup.com/ - Intro paragraph: "When you join Watson-Marlow Fluid Technology Solutions, a part of the Spirax Group, you will be integrated into a cooperative and encouraging team, participate in challenging yet critical work, and experience ongoing growth opportunities to help you achieve your full potential. Visit our website to learn more." - "This Role Will Focus On The Senior Quality Engineer is responsible for leading, developing, and maintaining the site’s quality validation, product qualification, and risk management programs, ensuring alignment with ISO standards, internal Quality Management Systems, and regulatory expectations. This role supports NPI (New Product Introduction) and Design & Development Quality, providing technical oversight and quality governance on all activities including production to ensure product safety, regulatory compliance, and robust validation lifecycle control. Acting as the site’s subject matter expert (SME) in quality validation, risk management, and metrology, the Senior Quality Engineer collaborates with cross-functional stakeholders in Engineering, Manufacturing, R&D, Supply Chain, and Quality Assurance to drive consistent, compliant, and effective practices." - "Key Accountabilities Include" then a list of bullet points (starting with Supervise your designated team., etc.) - Then "Skills/Experience" list. - Then "This position offers a salary range of USD $85,000 - $107,000. Final salary offers are determined by multiple factors, including education, experience, internal equity, geographic location, and the candidate’s expertise, and therefore may vary from the range listed. For roles based outside Massachusetts, the applicable salary range may be lower." - Then benefits paragraph: "At Watson-Marlow, we believe in taking care of our colleagues. We offer a generous benefits package, including:" then list of benefits. - Then "We invite you to explore all the ways we strive to create a fulfilling and rewarding work environment." - Then "Everyone is Included at Spirax Group" paragraph about inclusion. - Then "Equal Opportunity Employer" boilerplate (should be removed). - Then "Company Overview" paragraph about Watson-Marlow (maybe we can keep as About the role? Actually "Company Overview" is generic but could be considered About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We need to decide which sections to include: - About the role: could include the introductory paragraph describing the role, maybe the "This Role Will Focus On" paragraph. That's substantive. - Responsibilities: the "Key Accountabilities Include" list. - Requirements: maybe the "Skills/Experience" list? Actually Skills/Experience includes both requirements and qualifications. We could split: Requirements (minimum education, years experience, ISO knowledge) and Qualifications (maybe certifications, etc). But we need to avoid thin sections. Could combine Requirements and Qualifications into one? But instruction says use headings as examples; we can include only those with real content. We could have Requirements (education, experience, ISO) and Qualifications (certifications, etc). However the posting lumps them together: Bachelor’s degree, Minimum 5 years experience, Proven working knowledge of ISO..., Strong ability to engage..., Demonstrated expertise..., In-depth understanding..., Proficient in conducting internal audits; lead auditor certification is highly desirable., Established track record..., Advanced problem-solving..., Excellent communication..., Resilient and delivery-focused... We could treat that as "Requirements" (or "Skills") but we also have a separate "Skills" heading. The posting already has a "Skills/Experience" heading. So we could map that to "Skills". Then we might not need separate Requirements/Qualifications. But we need to avoid thin sections; we could have only Skills section and maybe Benefits, Pay. Also About the role and Responsibilities. Schedule: not mentioned. So omit Schedule. Pay: we have salary range. So include Pay. Benefits: we have benefits list. So include Benefits. Thus sections: About the role, Responsibilities, Skills, Benefits, Pay. We should not include Requirements/Qualifications separately if they'd be thin; but we could incorporate them into Skills. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can choose which to include. So we can include Skills and maybe not Requirements/Qualifications. We need to preserve all substantive information. If we put all the Skills/Experience list under Skills heading, we preserve that info. The responsibilities list under Responsibilities. The intro paragraph under About the role. Benefits list under Benefits. Pay info under Pay. We also need to include location etc maybe as a short p before sections. Could do a

with location and website. We must not include boilerplate like Equal Opportunity Employer, Company Overview (maybe we could treat Company Overview as About the role? But we already have About the role from intro. The Company Overview is more about the company, not the role. Could be considered "About the role"? Not exactly. The instruction says we can include About the role heading for role description. The Company Overview is generic company info; could be considered boilerplate? It's not navigation/legal/EEO but it's still generic. Might be okay to include as About the role? But we already have role description. To be safe, we could include Company Overview as part of About the role? But that might duplicate. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep Company Overview info if it's substantive. It's about the company, not the role, but still substantive. However the sections we have are limited to role-focused headings. Could we add another heading like "About the company"? Not in the 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 implied to use those headings only. Safer to stick to those. Thus we may drop Company Overview as it's not directly about the role. But that would lose substantive info. However the instruction says "Prefer a few substantive sections over many thin ones." Company Overview might be considered thin? It's a paragraph about the company. Could be considered boilerplate? It's not legal/EEO but it's still generic marketing. Might be okay to drop? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company Overview is not listed there, but it's still kind of generic. However to be safe, we could include it under About the role? But that would mix role and company info. Might be acceptable. Better to include a short p for location and website, then sections. Let's craft HTML:

Location: WMFTS - USA - Supply - Devens, MA (On‑Site). Website: wmfts.com. Group: spiraxgroup.com.

Then

About the role

with paragraph(s) containing the intro and the "This Role Will Focus On" description. We need to preserve all substantive information: The intro: "When you join Watson-Marlow Fluid Technology Solutions, a part of the Spirax Group, you will be integrated into a cooperative and encouraging team, participate in challenging yet critical work, and experience ongoing growth opportunities to help you achieve your full potential. Visit our website to learn more." Then the role focus paragraph: "This Role Will Focus On The Senior Quality Engineer is responsible for leading, developing, and maintaining the site’s quality validation, product qualification, and risk management programs, ensuring alignment with ISO standards, internal Quality Management Systems, and regulatory expectations. This role supports NPI (New Product Introduction) and Design & Development Quality, providing technical oversight and quality governance on all activities including production to ensure product safety, regulatory compliance, and robust validation lifecycle control. Acting as the site’s subject matter expert (SME) in quality validation, risk management, and metrology, the Senior Quality Engineer collaborates with cross-functional stakeholders in Engineering, Manufacturing, R&D, Supply Chain, and Quality Assurance to drive consistent, compliant, and effective practices." We should keep that as is, maybe split into two

elements. Then Responsibilities:

Responsibilities

with each bullet from "Key Accountabilities Include". Need to preserve each bullet exactly as given. List: - Supervise your designated team. - Develop, implement, and sustain effective quality management system (QMS) processes, including the creation and control of procedures, templates, and quality records. - Provide quality engineering guidance and support to New Product Introduction (NPI) projects, and as part of change management ensuring all quality deliverables are completed on time and in compliance with regulatory and internal requirements. - Work closely with the validation technical SME to ensure effective verification and validation (V&V) of new products and processes within the NPI lifecycle. - Champion thorough investigation of nonconformities using our eQMS Quality Event process, including product non-conformances, process deviations, and customer complaints. - Drive effective Corrective and Preventive Actions (CAPA) through structured data driven root cause analysis (e.g., 5 Whys, Fishbone, FMEA). - Drive improvements in design, product, and process changes by ensuring changes are impact and risk assessed, documented and implemented in line with quality standards. - Collaborate with cross-functional teams (Engineering, Manufacturing, Supply Chain, Quality) to implement quality improvements, in line with the WMFTS Quality Strategy. - Support validation activities by ensuring the development and maintenance of validation protocols, procedures, and documentation in line with policy and process. - Be part of the internal audit team, conducting and generating audit reports to drive process improvements. - Provide training, coaching and guidance on quality tools, systems, and best practices to colleagues and stakeholders. - Promote a culture of quality, continuous improvement, and risk-based thinking throughout the product lifecycle and across all functions. - Other duties as assigned. We need to keep the exact phrasing. Then Skills:

Skills

with the Skills/Experience list. List: - Bachelor’s degree in engineering, or a scientific discipline. - Minimum of 5 years’ experience in Quality Assurance within a regulated industry. - Proven working knowledge of ISO 13485 and ISO 9001 standards. - Strong ability to engage and communicate effectively with cross-functional stakeholders. - Demonstrated expertise in product and process validation methodologies. - In-depth understanding of the design and development lifecycle. - Proficient in conducting internal audits; lead auditor certification is highly desirable. - Established track record in driving continuous improvement initiatives and applying lean methodologies. - Advanced problem-solving capabilities, including root cause analysis and effective CAPA (Correct