Quality Engineering Manager

for prose. We need to parse the posting. Key sections: - Position Summary (maybe heading "About the role"? The instruction says use h3 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 "Position Summary", "Essential Responsibilities" (with sub-sections: Quality Management, Quality Engineering, Field Performance & Warranty Management, Customer Quality, Supplier Quality, Continuous Improvement, Leadership & Development). Then "Qualifications" with sub-sections: Education, Experience, Technical Skills, Certifications (Preferred). Then "Why Work at Key Technology?" which includes benefits list. We need to decide which headings to use. Likely: - About the role: could contain Position Summary. - Responsibilities: essential responsibilities. - Qualifications: education, experience, technical skills, certifications. - Benefits: benefits list. - Possibly Skills: maybe technical skills could go under Skills, but we already have Qualifications includes technical skills. The instruction says prefer few substantive sections over many thin ones. So we could combine. We need to include sections only when posting has real specific content. So we need About the role (Position Summary). Responsibilities (Essential Responsibilities). Qualifications (Education, Experience, Technical Skills, Certifications). Benefits (Why Work at Key Technology?). Possibly Skills separate? But we can incorporate technical skills under Qualifications. We must not create Pay or Schedule sections because not mentioned. We must not include boilerplate like EEO etc. Remove those lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format as lists. We need to ensure we don't lose any content. Let's extract content. Position Summary paragraph: "The Quality Engineering Manager is responsible for leading the organization's quality assurance and quality/reliability engineering functions to ensure products, processes, and systems consistently meet customer requirements, regulatory standards, and company objectives. This role drives continuous improvement initiatives, oversees quality management systems, manages quality engineering resources, and collaborates cross-functionally to improve product quality, operational efficiency, and customer satisfaction." That's prose. Essential Responsibilities: multiple sub-sections each with bullet-like sentences. We need to turn each duty into

. Could group under Responsibilities heading. We have subheadings within responsibilities: Quality Management, Quality Engineering, Field Performance & Warranty Management, Customer Quality, Supplier Quality, Continuous Improvement, Leadership & Development. We could either keep them as headings inside the Responsibilities section (maybe as

but not allowed? Only h3 for section headings. We could keep them as or just as part of list items. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow. Probably we can keep subheadings as

or just bold. Safer to keep them as

maybe but not required. However to avoid extra headings, we could just list items with the subheading as part of the item text. But we need to preserve all substantive information; we can keep the subheadings as part of the list item text (e.g., "Quality Management: Develop, implement, and own the effectiveness..."). Thus we will create a

with each responsibility as
• . Ensure we include all details. Let's list each responsibility bullet: Quality Management: - Develop, implement, and own the effectiveness of the company's Quality Management System (QMS). - Ensure compliance with applicable industry standards, customer requirements, and regulatory requirements. - Establish quality objectives, metrics, and reporting processes to monitor performance. - Lead internal and external quality audits and support certification activities. Quality Engineering: - Lead the engineering team in product and process quality improvement initiatives. - Develop inspection, testing, validation, and acceptance criteria for products and processes. - Utilize quality tools and methodologies including: - Root Cause Analysis (RCA) - Corrective and Preventive Actions (CAPA) - Failure Mode and Effects Analysis (FMEA) - Control Plans and Process Control - Six Sigma and Lean methodologies - Review engineering changes and assess quality impacts. We need to keep the list of tools as sublist? Could embed as part of the same
• with a nested
  . That's allowed. Field Performance & Warranty Management: - Monitor product performance in the field. - Develop systems to collect and analyze warranty and service data. - Build maturity through establishing a closed loop process connecting field failures and warranty claims to RCA, CAPA and Process Controls/Improvement tools. - Identify systemic failures and lead corrective action initiatives. - Work with Service and Customer Support teams to improve product uptime and customer satisfaction. - Reduce warranty expenditures through proactive reliability improvements. Customer Quality: - Serve as the primary escalation point for major customer quality concerns. - Lead investigations into customer complaints and warranty issues. - Coordinate corrective action plans and ensure timely resolution. - Strengthen customer relationships through effective communication and continuous quality improvement. Supplier Quality: - Partner with Supply Chain and Procurement teams to improve supplier quality performance and to establish a PPAP process for suppliers. - Establish supplier quality requirements and performance metrics. - Lead supplier audits and corrective action activities. - Evaluate and approve supplier quality systems and processes. Continuous Improvement: - Drive a culture of continuous improvement throughout the organization. - Analyze quality data and identify opportunities to improve processes and reduce defects. - Lead cross-functional teams focused on improving quality, safety, productivity, and customer satisfaction. - Promote the use of quality tools and best practices across operations and engineering teams. Leadership & Development: - Recruit, develop, and mentor quality team personnel. - Set departmental goals aligned with corporate objectives. - Manage departmental budgets and resources. - Foster collaboration between engineering, operations, supply chain, sales, and customer service teams. - Drive a culture of problem solving and continuous improvement as part of Operations Staff. Now Qualifications: Education: - Bachelor's degree in Engineering, Quality Engineering, Reliability Engineering or a related technical field. - Master's degree preferred. Experience: - 7-10+ years of progressive experience in quality engineering, quality assurance, or manufacturing engineering. - 3-5+ years of leadership or management experience. - Experience within manufacturing, industrial equipment, food processing equipment, or related industries preferred. Technical Skills: - Strong knowledge of quality management systems and industry standards. - Experience with ISO 9001 and other applicable quality standards. - Proficiency in root cause analysis and problem-solving methodologies. - Experience with quality statistics and data analysis tools. - Knowledge of manufacturing processes, welding, fabrication, machining, assembly, and supplier quality management is preferred. Certifications (Preferred): - Certified Quality Engineer (CQE) - Certified Quality Manager (CQM) - Six Sigma Green Belt or Black Belt - ASQ certifications We need to decide how to format Qualifications. Could have a

  Qualifications and then sub-sections maybe as

  or just list items with headings. Since we want few sections, we could just list all qualification items under a single

  with headings inside each
  • . But we need to preserve the structure; maybe better to have subheadings inside

    or . However instruction says use

    • for any list of duties/requirements/benefits. So for qualifications we should use a list. We can embed the subheadings as part of the list item text, e.g., "Education: Bachelor's degree...". That would preserve info. Similarly for Benefits: list of benefits. Benefits list from "Why Work at Key Technology?": - Medical, Dental, and Vision coverage - Flexible Spending Accounts (FSA) or Health Savings Accounts (HSA), when allowed by tax law - Paid life insurance and disability insurance, with options to purchase additional coverage - Paid Maternity/Paternity Leave - Optional coverages: Long-term Care, Accident Insurance, and Critical Illness Insurance - 401(k) plan with company match - Educational Assistance reimbursement - Accrued Paid Time Off (PTO) - 10 paid holidays annually Also note: "Employment with Key Technology is contingent upon successfully completing a pre-employment drug screen, criminal history, social security, and reference check." This is not a benefit; it's a condition. Should we include? It's substantive info but not a benefit. The instruction says remove boilerplate, but this is a condition of employment. Might be considered substantive. However it's not a benefit, not a responsibility, not qualification. Could be placed under About the role? Probably better to include as a short paragraph under About the role or maybe a separate section like "Employment Conditions". But we only have allowed headings list; we could add a

      after the summary. The instruction says use

      for prose. So we can add a

      after the summary paragraph. Also EEO lines etc should be removed. Thus final HTML:

      About the role

      Position summary paragraph.

      Employment contingency sentence.

      Responsibilities

      • Quality Management: ...
      ...

      Qualifications

      • Education: Bachelor's degree ... Master's degree preferred.
      • Experience: 7-10+ years ... 3-5+ years leadership ... Experience within manufacturing ... preferred.
      • Technical Skills: Strong knowledge ... Experience with ISO 9001 ... Proficiency in root cause analysis ... Experience with quality statistics ... Knowledge of manufacturing processes ... preferred.
      • Certifications (Preferred): Certified Quality Engineer (CQE); Certified Quality Manager (CQM); Six Sigma Green Belt or Black Belt; ASQ certifications.

      Benefits

      • Medical, Dental, and Vision coverage
      • Flexible Spending Accounts (FSA) or Health Savings Accounts (HSA), when allowed by tax law
      • Paid life insurance and disability insurance, with options to purchase additional coverage
      • Paid Maternity/Paternity Leave
      • Optional coverages: Long-term Care, Accident Insurance, and Critical Illness Insurance
      • 401(k) plan with company match
      • Educational Assistance reimbursement
      • Accrued Paid Time Off (PTO)
      • 10 paid holidays annually
      We need to ensure we didn't miss any details: The initial paragraph about Key Technology: "Key Technology in Walla Walla, WA is a worldwide leader in food processing technology. As a global industrial manufacturing company, our ongoing innovations provide increased control, continuous processing, sorting, automated inspection, specialized conveying, and grading and sizing, in processed fruits and vegetables, nuts, dried fruit, fresh-cut produce and more." This is company description; should we include? It's substantive info about the company. Could be included in About the role section as a paragraph before the position summary. The instruction says preserve ALL substantive information. So we should include that description. It's not boilerplate. So add a

      with that description. Thus About the role will have two paragraphs: company description and position summary. Then maybe the contingency sentence. Let's craft. Now ensure we didn't include any boilerplate: EEO lines, "Key Technology is an equal employment opportunity (EEO) employer..." etc removed. Also remove "Employment with Key Technology is contingent upon successfully completing a pre-employment drug screen, criminal history, social security, and reference check." We kept