Quality Management System Engineer
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes sections: Summary, Key Responsibilities (with sub-sections), Qualifications, Competencies, Physical Demands, Work Environment. Also includes #MalibuBoats maybe ignore.
We need to decide which sections to include: About the role (summary), Responsibilities, Qualifications, Skills? There's Competencies list. Benefits, Pay, Schedule only if present. There's mention of typical work hours, overtime, schedule. That's schedule info. So we can include a Schedule section with that info. Benefits not mentioned. Pay not mentioned. So we omit those.
We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive info. So we need to capture summary paragraph, responsibilities broken into subcategories maybe as lists. Use
- for any list of duties/requirements/benefits. For prose use
. For subheadings within responsibilities maybe we can still use
for each sub-section? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those top-level headings. Within responsibilities we can use - for list items. Could also have paragraphs describing each subcategory. Probably better to have a
Responsibilities
then maybe subheadings not required but we could still use for each category description then
- for bullet points. However the instruction says use
- for any list of duties/requirements/benefits. So we can turn each duty into list items. But we have many duties grouped under categories. Could flatten all duties into a single list? Might lose grouping but still preserve info. Better to keep categories as
then list.
We need to ensure we don't create empty sections.
Let's extract content:
Summary paragraph: "The QMS Engineer is responsible for implementing, maintaining, and continuously improving the Quality Management System (QMS) at the Malibu Boats manufacturing facility. This position serves as the local subject matter expert for quality system requirements, document control, audits, corrective actions, training, and compliance activities. The QMS Engineer works closely with Operations, Engineering, Supply Chain, Human Resources, and Quality teams to ensure established quality standards, procedures, and documentation are consistently applied and sustained throughout the facility. This role supports enterprise quality initiatives, site-level quality improvement efforts, and continuous improvement activities while ensuring compliance with company policies, customer requirements, and applicable quality standards."
Key Responsibilities sections:
Quality Management System Administration:
- Maintain and coordinate all site QMS processes, procedures, work instructions, forms, and records in alignment with enterprise-wide QMS roadmap implementation roadmap.
- Ensure quality documentation remains current, properly controlled, and accessible to applicable personnel.
- Support implementation of enterprise quality standards, policies, and procedures at the facility.
- Monitor compliance with document control and records retention requirements.
- Partner with department leaders to update and improve quality-related documentation.
Deployment & Implementation:
- Lead the strategic deployment of QMS processes and systems across all facilities and business units.
- Develop and execute implementation roadmaps, timelines, and milestone tracking for QMS rollouts.
- Partner with site-level quality leaders to ensure successful adoption and sustainability of QMS standards.
- Identify and resolve barriers to effective QMS deployment, driving continuous alignment and improvement.
Training & Capability Building:
- Coordinate QMS training programs for new and existing employees.
- Maintain training records and verify completion of required quality training.
- Develop training materials and support department-specific quality education needs.
- Coach supervisors and employees on quality system requirements and best practices.
- Support quality awareness initiatives that strengthen a culture of quality ownership.
Corrective Action & Continuous Improvement:
- Facilitate root cause analysis activities using structured problem-solving methodologies.
- Manage CAPA (Corrective and Preventive Action) processes and closure tracking.
- Support improvement projects aimed at reducing defects, process variation, and quality risks.
- Track quality system performance metrics and communicate trends to facility leadership.
- Promote proactive quality practices that prevent issues before they occur.
Audit & Compliance:
- Plan, coordinate, and conduct internal quality system audits.
- Assist with external audits, customer audits, and certification activities.
- Track audit findings and ensure corrective actions are completed in a timely manner.
- Verify effectiveness of corrective and preventive actions.
- Monitor compliance to established procedures and quality requirements throughout the facility.
Collaboration & Communication:
- Partner with Operations, Engineering, Customer Service, Supply Chain, and Human Resources to ensure quality requirements are integrated into facility processes.
- Participate in management reviews and quality performance discussions.
- Support implementation of enterprise quality initiatives and system improvements.
- Serve as the primary site contact for QMS-related questions and activities.
Qualifications:
- Bachelor’s degree in Engineering, Quality, Business, or related field.
- 3-5 years of experience in Quality Systems, Quality Assurance, Quality Engineering, Manufacturing, or related disciplines.
- Experience supporting or maintaining a Quality Management System in a manufacturing environment.
- Experience conducting audits and managing corrective action processes.
- Working knowledge of ISO 9001 and/or IATF 16949 standards; Lead Auditor certification preferred.
- Professional certifications such as CQE (Certified Quality Engineer) or CQA (Certified Quality Auditor) preferred.
- Strong project management, organizational, and analytical skills.
- Excellent communication, training, and facilitation abilities.
- Proficiency with QMS software, document control systems, and data analytics tools.
Competencies list: (these are like skills)
- Quality Management Systems
- Document Control
- Internal Auditing
- Corrective and Preventive Action (CAPA)
- Root Cause Analysis
- Regulatory and Standards Compliance
- Process Improvement
- Project Coordination
- Training and Facilitation
- Data Analysis
- Cross-Functional Collaboration
- Attention to Detail
- Organizational Skills
- Communication and Influence
Physical Demands: includes description and specifics. We need to preserve all substantive info. This is not a list but prose with details. We'll put under a section maybe "Physical Demands". However the instruction only lists certain headings; but we can still include Physical Demands as a section? It 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 "include a section ONLY when the posting has real, specific content for it". It gives examples but not exclusive. So we can add Physical Demands and Work Environment sections as . Use
for prose.
Physical Demands content: "The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Continuous/C = 67-100%, Frequent/F = 33-66%, Occasional/O = 33%, None/N Sits hours Stands hours Walks hours Drives hours Employee Lifts and/or Carries: type amount of weight in each area Maximum: 50 (lbs) Frequently: 20 (lbs) Occasionally: 35 (lbs) Employee Uses Hands For Repetitive Activities Simple Grasping: Right, Left, Pushing/Pulling: Right, Left, Fine Manipulation: Right, Left, Employee Uses Feet For Repetitive Activities Right: Left: Bending At Waist Employee is required to perform these activities: Squatting Climbing Ladders, Stairs: Kneeling On Ground Reaching Above Shoulder:"
That's messy but we keep as is.
Work Environment: "The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job (i.e., heat/cold, dust/dampness, height; chemical; noise) PPE requirements are included. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Typical 10-hour workdays based upon facility.Typical 4- or 5-day work week schedule based upon facility and schedule loading.Overtime is occasional to frequent based on a number of factors.Required to work indoors and outdoors, year-round and in all weather conditions.May be required to work during production shutdowns or other “off-schedule” periods to conduct special activities.Safety glasses required while in production areasOther PPE may be required based on specific projects."
We also have schedule info inside Work Environment; but we could also create a Schedule section pulling out schedule details: "Typical 10-hour workdays based upon facility. Typical 4- or 5-day work week schedule based upon facility and schedule loading. Overtime is occasional to frequent based on a number of factors." Might be better to put schedule details in Schedule section. However the instruction says include Schedule section only if posting actually states them. It does state typical workdays, week schedule, overtime. So we can create Schedule section with that info. Then Work Environment can focus on environment conditions.
Let's extract schedule details: "Typical 10-hour workdays based upon facility.Typical 4- or 5-day work week schedule based upon facility and schedule loading.Overtime is occasional to frequent based on a number of factors."
We'll put those in Schedule section as
or maybe
- . Since it's prose, use
.
Now Work Environment: remaining: "The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job (i.e., heat/cold, dust/dampness, height; chemical; noise) PPE requirements are included. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Required to work indoors and outdoors, year-round and in all weather conditions.May be required to work during production shutdowns or other “off-schedule” periods to conduct special activities.Safety glasses required while in production areasOther PPE may be required based on specific projects."
We'll keep as
.
Now we need to ensure we don't repeat job title as heading. We'll not.
We need to output only HTML fragment, no /, no markdown.
Let's structure:
About the role
...
Responsibilities
Maybe we can have subheadings but not required. We'll just use - for each duty, but we lose categorization. Could do
Quality Management System Administration
then etc. The instruction didn't forbid other headings; it only said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot use other heading levels. Safer to stick to for main sections and use
and
- inside. For categorization we can use
to introduce each category then
- . That's fine.
Thus:
Responsibilities
Quality Management System Administration
- ...
...
Deployment & Implementation
...
... etc.
Similarly for Qualifications: we can just - .
Competencies: also list.
Physical Demands:
Physical Demands
...
Schedule: Schedule
...
Work Environment: Work Environment
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes sections: Summary, Key Responsibilities (with sub-sections), Qualifications, Competencies, Physical Demands, Work Environment. Also includes #MalibuBoats maybe ignore. We need to decide which sections to include: About the role (summary), Responsibilities, Qualifications, Skills? There's Competencies list. Benefits, Pay, Schedule only if present. There's mention of typical work hours, overtime, schedule. That's schedule info. So we can include a Schedule section with that info. Benefits not mentioned. Pay not mentioned. So we omit those. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. So we need to capture summary paragraph, responsibilities broken into subcategories maybe as lists. Use
- for any list of duties/requirements/benefits. For prose use
. For subheadings within responsibilities maybe we can still use
for each sub-section? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those top-level headings. Within responsibilities we can use
- for list items. Could also have paragraphs describing each subcategory. Probably better to have a
Responsibilities
then maybe subheadings not required but we could still usefor each category description then
- for bullet points. However the instruction says use
- for any list of duties/requirements/benefits. So we can turn each duty into list items. But we have many duties grouped under categories. Could flatten all duties into a single list? Might lose grouping but still preserve info. Better to keep categories as
then list. We need to ensure we don't create empty sections. Let's extract content: Summary paragraph: "The QMS Engineer is responsible for implementing, maintaining, and continuously improving the Quality Management System (QMS) at the Malibu Boats manufacturing facility. This position serves as the local subject matter expert for quality system requirements, document control, audits, corrective actions, training, and compliance activities. The QMS Engineer works closely with Operations, Engineering, Supply Chain, Human Resources, and Quality teams to ensure established quality standards, procedures, and documentation are consistently applied and sustained throughout the facility. This role supports enterprise quality initiatives, site-level quality improvement efforts, and continuous improvement activities while ensuring compliance with company policies, customer requirements, and applicable quality standards." Key Responsibilities sections: Quality Management System Administration: - Maintain and coordinate all site QMS processes, procedures, work instructions, forms, and records in alignment with enterprise-wide QMS roadmap implementation roadmap. - Ensure quality documentation remains current, properly controlled, and accessible to applicable personnel. - Support implementation of enterprise quality standards, policies, and procedures at the facility. - Monitor compliance with document control and records retention requirements. - Partner with department leaders to update and improve quality-related documentation. Deployment & Implementation: - Lead the strategic deployment of QMS processes and systems across all facilities and business units. - Develop and execute implementation roadmaps, timelines, and milestone tracking for QMS rollouts. - Partner with site-level quality leaders to ensure successful adoption and sustainability of QMS standards. - Identify and resolve barriers to effective QMS deployment, driving continuous alignment and improvement. Training & Capability Building: - Coordinate QMS training programs for new and existing employees. - Maintain training records and verify completion of required quality training. - Develop training materials and support department-specific quality education needs. - Coach supervisors and employees on quality system requirements and best practices. - Support quality awareness initiatives that strengthen a culture of quality ownership. Corrective Action & Continuous Improvement: - Facilitate root cause analysis activities using structured problem-solving methodologies. - Manage CAPA (Corrective and Preventive Action) processes and closure tracking. - Support improvement projects aimed at reducing defects, process variation, and quality risks. - Track quality system performance metrics and communicate trends to facility leadership. - Promote proactive quality practices that prevent issues before they occur. Audit & Compliance: - Plan, coordinate, and conduct internal quality system audits. - Assist with external audits, customer audits, and certification activities. - Track audit findings and ensure corrective actions are completed in a timely manner. - Verify effectiveness of corrective and preventive actions. - Monitor compliance to established procedures and quality requirements throughout the facility. Collaboration & Communication: - Partner with Operations, Engineering, Customer Service, Supply Chain, and Human Resources to ensure quality requirements are integrated into facility processes. - Participate in management reviews and quality performance discussions. - Support implementation of enterprise quality initiatives and system improvements. - Serve as the primary site contact for QMS-related questions and activities. Qualifications: - Bachelor’s degree in Engineering, Quality, Business, or related field. - 3-5 years of experience in Quality Systems, Quality Assurance, Quality Engineering, Manufacturing, or related disciplines. - Experience supporting or maintaining a Quality Management System in a manufacturing environment. - Experience conducting audits and managing corrective action processes. - Working knowledge of ISO 9001 and/or IATF 16949 standards; Lead Auditor certification preferred. - Professional certifications such as CQE (Certified Quality Engineer) or CQA (Certified Quality Auditor) preferred. - Strong project management, organizational, and analytical skills. - Excellent communication, training, and facilitation abilities. - Proficiency with QMS software, document control systems, and data analytics tools. Competencies list: (these are like skills) - Quality Management Systems - Document Control - Internal Auditing - Corrective and Preventive Action (CAPA) - Root Cause Analysis - Regulatory and Standards Compliance - Process Improvement - Project Coordination - Training and Facilitation - Data Analysis - Cross-Functional Collaboration - Attention to Detail - Organizational Skills - Communication and Influence Physical Demands: includes description and specifics. We need to preserve all substantive info. This is not a list but prose with details. We'll put under a section maybe "Physical Demands". However the instruction only lists certain headings; but we can still include Physical Demands as a section? It 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 "include a section ONLY when the posting has real, specific content for it". It gives examples but not exclusive. So we can add Physical Demands and Work Environment sections as
. Use
for prose. Physical Demands content: "The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Continuous/C = 67-100%, Frequent/F = 33-66%, Occasional/O = 33%, None/N Sits hours Stands hours Walks hours Drives hours Employee Lifts and/or Carries: type amount of weight in each area Maximum: 50 (lbs) Frequently: 20 (lbs) Occasionally: 35 (lbs) Employee Uses Hands For Repetitive Activities Simple Grasping: Right, Left, Pushing/Pulling: Right, Left, Fine Manipulation: Right, Left, Employee Uses Feet For Repetitive Activities Right: Left: Bending At Waist Employee is required to perform these activities: Squatting Climbing Ladders, Stairs: Kneeling On Ground Reaching Above Shoulder:" That's messy but we keep as is. Work Environment: "The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job (i.e., heat/cold, dust/dampness, height; chemical; noise) PPE requirements are included. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Typical 10-hour workdays based upon facility.Typical 4- or 5-day work week schedule based upon facility and schedule loading.Overtime is occasional to frequent based on a number of factors.Required to work indoors and outdoors, year-round and in all weather conditions.May be required to work during production shutdowns or other “off-schedule” periods to conduct special activities.Safety glasses required while in production areasOther PPE may be required based on specific projects." We also have schedule info inside Work Environment; but we could also create a Schedule section pulling out schedule details: "Typical 10-hour workdays based upon facility. Typical 4- or 5-day work week schedule based upon facility and schedule loading. Overtime is occasional to frequent based on a number of factors." Might be better to put schedule details in Schedule section. However the instruction says include Schedule section only if posting actually states them. It does state typical workdays, week schedule, overtime. So we can create Schedule section with that info. Then Work Environment can focus on environment conditions. Let's extract schedule details: "Typical 10-hour workdays based upon facility.Typical 4- or 5-day work week schedule based upon facility and schedule loading.Overtime is occasional to frequent based on a number of factors." We'll put those in Schedule section as
or maybe
- . Since it's prose, use
. Now Work Environment: remaining: "The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job (i.e., heat/cold, dust/dampness, height; chemical; noise) PPE requirements are included. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Required to work indoors and outdoors, year-round and in all weather conditions.May be required to work during production shutdowns or other “off-schedule” periods to conduct special activities.Safety glasses required while in production areasOther PPE may be required based on specific projects." We'll keep as
. Now we need to ensure we don't repeat job title as heading. We'll not. We need to output only HTML fragment, no /, no markdown. Let's structure:
About the role
...
Responsibilities
Maybe we can have subheadingsbut not required. We'll just use
- for each duty, but we lose categorization. Could do
Quality Management System Administration
then- etc. The instruction didn't forbid other headings; it only said use
- inside. For categorization we can use
to introduce each category then
- . That's fine.
Thus:
Responsibilities
Quality Management System Administration
- ... ...
Deployment & Implementation
- ...
- .
Competencies: also list.
Physical Demands:
Physical Demands
...
Schedule:Schedule
...
Work Environment:Work Environment
- . That's fine.
Thus:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot use other heading levels. Safer to stick to
for main sections and use
and
- inside. For categorization we can use
- for each duty, but we lose categorization. Could do
- . Since it's prose, use
- for any list of duties/requirements/benefits. So we can turn each duty into list items. But we have many duties grouped under categories. Could flatten all duties into a single list? Might lose grouping but still preserve info. Better to keep categories as
- for bullet points. However the instruction says use
- for list items. Could also have paragraphs describing each subcategory. Probably better to have a