Sr Quality & Failure Analysis Engineering Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to decide which sections to include. The posting includes:
- About The Role (intro paragraph)
- What You Will Do (list of duties)
- What You Bring (qualifications)
- About ZT Systems (company description)
- What We Offer (benefits)
We could combine About The Role and About ZT Systems into an "About the role" or "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have sections: About the role (intro paragraph), Responsibilities (What You Will Do), Requirements (What You Bring), Benefits (What We Offer). Possibly also a short paragraph about company could be part of About the role? But they said "About the role" heading for section headings. The "About ZT Systems" is company overview, not role. Could we include it under About the role? Might be okay to include as part of About the role? But better to keep it separate? The instruction list didn't include "About the company". However we could include it as part of About the role? Might be considered filler if we create a heading with no real content? But we have content: company description. Could we create a heading "About the company"? Not in list but maybe allowed? 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. Probably we should stick to those headings. So we can incorporate company description into About the role section? Might be okay.
We need to avoid boilerplate: EEO, equal-opportunity, scam-warning, etc. Remove those lines.
We need to preserve all substantive information. So we need to keep the duties list, qualifications list, benefits list, and the intro paragraphs.
We need to format as HTML fragment: use for each section heading, then content: either
for prose,
- for lists.
We need to ensure we don't repeat job title as heading.
Let's extract content.
About The Role paragraph:
"The Senior Quality & Failure Analysis (FA/SVT/MAT) Engineering Manager is responsible for leading quality engineering and failure analysis organizations that support the development, validation, manufacturing, and deployment of complex hardware platforms. This role drives end-to-end product quality strategy, root cause investigations, corrective action execution, and systemic improvements to ensure the highest levels of product reliability, manufacturability, and customer satisfaction. The ideal candidate combines deep technical expertise in failure analysis, system validation testing (SVT), manufacturing analysis, and quality engineering with proven leadership capabilities. Working across design, hardware, firmware, validation, manufacturing, supplier quality, and operations teams, this leader ensures quality issues are rapidly identified, thoroughly investigated, and effectively resolved throughout the product lifecycle."
That's prose.
What You Will Do list:
- Lead quality engineering, failure analysis, and manufacturing assessment teams supporting multiple hardware development programs.
- Drive root cause investigations for product failures identified during development, validation, manufacturing, and field deployment.
- Establish and oversee processes for failure analysis, defect tracking, corrective actions, and preventive action implementation.
- Partner with hardware, firmware, software, validation, and manufacturing teams to identify and resolve complex technical issues.
- Define quality objectives, metrics, and reporting mechanisms to monitor product reliability and manufacturing performance.
- Lead system-level and component-level failure investigations using data-driven methodologies and structured problem-solving techniques.
- Drive continuous improvement initiatives that reduce defects, improve yield, and enhance product reliability.
- Collaborate with supplier quality and manufacturing partners to address quality concerns and implement corrective actions.
- Ensure timely execution of quality reviews, failure analysis reports, and risk assessments.
- Develop strategies for reliability growth, quality monitoring, and manufacturing process improvement.
- Establish escalation paths and governance processes for high-priority quality and reliability issues.
- Present quality trends, failure analysis findings, risks, and mitigation plans to executive leadership and key stakeholders.
That's a list.
What You Bring list (qualifications):
- Bachelor's degree in Electrical Engineering, Mechanical Engineering, Computer Engineering, Materials Science, or a related technical discipline; advanced degree preferred.
- 10+ years of experience in quality engineering, failure analysis, reliability engineering, manufacturing quality, or related technical leadership roles.
- Proven experience leading root cause investigations and corrective action programs for complex hardware products.
- Strong understanding of failure analysis methodologies, system validation testing (SVT), manufacturing assessment techniques, and reliability engineering principles.
- Experience with hardware platform development, manufacturing processes, product qualification, and production ramp activities.
- Deep knowledge of quality management systems, defect tracking processes, and continuous improvement methodologies.
- Experience applying structured problem-solving tools such as 8D, FMEA, RCA, Six Sigma, or similar quality frameworks.
- Demonstrated success working across cross-functional teams including engineering, validation, manufacturing, operations, and supplier management organizations.
- Strong analytical skills with the ability to interpret failure data, identify trends, and drive actionable improvements.
- Excellent communication, stakeholder management, and executive presentation skills.
- Ability to influence technical and business decisions in highly complex, fast-paced environments.
- Proven track record of improving product reliability, manufacturing quality, operational performance, and customer outcomes through disciplined quality and failure analysis practices.
That's list.
About ZT Systems paragraph:
"At ZT Systems, a Sanmina Company, you’ll get to do work you are proud of alongside smart, passionate people. Every day, there are opportunities to collaborate with the best in the industry to design, build, and deliver impactful solutions to world-class customers. Along the way, you will gain hands-on experience in a fast-paced environment that’s challenging, rewarding, and career-defining. A culture built around our values we work hard and think fast. We view challenges as opportunities—to do better, push harder, and be faster than we were the day before. When we fail, we learn from it and move on together. And when we succeed, we use the momentum to go even further. We create value with everything we do, building the foundation of today—and transforming the future of tomorrow. Join ZT Systems and help us build technology infrastructure that connects the world."
That's prose.
What We Offer (benefits) includes several sub-sections: Compensation & Financial Security, Health & Wellness, Time Away & Work-Life Balance, Growth & Purpose. Each has bullet points.
We need to decide whether to create a Benefits section with subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Benefits heading and then list benefits. Could also have subheadings inside? Not required. We could just list all benefits under Benefits as a - . But we need to preserve all substantive information; we can keep the subheadings as plain text inside
- maybe? Or we could keep them as inside
- . The instruction didn't forbid using other tags inside
- . It said use
- for any list of duties/requirements/benefits, and
for prose. So we can have
- where each
- contains the benefit description, possibly with for subheadings.
We need to avoid boilerplate: "These benefits are available to eligible employees and are designed to grow with you as your career evolves. Full benefits and eligibility varies by work location. Learn more about our benefits here." That's boilerplate? It's somewhat generic but still substantive? Might be considered boilerplate but it's still info. However we might drop it as it's generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits description about eligibility and learn more might be considered boilerplate but it's still part of benefits. However it's not duplicated. Might keep? Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The eligibility line is substantive (though generic). I'd keep it.
Also "ZT Group Int’l. is an Equal Opportunity Employer..." is EEO boilerplate; remove.
Also the export control license paragraph is legal; remove.
Thus final HTML:
About the role
... (intro paragraph + maybe company description? We'll decide.)
But we have company description separate; maybe we can add another About the company
but not in list. Could we treat it as part of About the role? Might be okay to include it as a separate paragraph under About the role heading. The instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). It doesn't forbid adding other headings, but they gave examples. Safer to stick to those headings. So we can merge company description into About the role paragraph after the role description. That would be substantive.
Thus About the role section will have two paragraphs: first the role description, second the company description. Or we can combine into one paragraph with a space.
We'll output:
About the role
The Senior Quality & Failure Analysis (FA/SVT/MAT) Engineering Manager is responsible for leading quality engineering and failure analysis organizations that support the development, validation, manufacturing, and deployment of complex hardware platforms. This role drives end-to-end product quality strategy, root cause investigations, corrective action execution, and systemic improvements to ensure the highest levels of product reliability, manufacturability, and customer satisfaction. The ideal candidate combines deep technical expertise in failure analysis, system validation testing (SVT), manufacturing analysis, and quality engineering with proven leadership capabilities. Working across design, hardware, firmware, validation, manufacturing, supplier quality, and operations teams, this leader ensures quality issues are rapidly identified, thoroughly investigated, and effectively resolved throughout the product lifecycle.
At ZT Systems, a Sanmina Company, you’ll get to do work you are proud of alongside smart, passionate people. Every day, there are opportunities to collaborate with the best in the industry to design, build, and deliver impactful solutions to world-class customers. Along the way, you will gain hands-on experience in a fast-paced environment that’s challenging, rewarding, and career-defining. A culture built around our values we work hard and think fast. We view challenges as opportunities—to do better, push harder, and be faster than we were the day before. When we fail, we learn from it and move on together. And when we succeed, we use the momentum to go even further. We create value with everything we do, building the foundation of today—and transforming the future of tomorrow. Join ZT Systems and help us build technology infrastructure that connects the world.
Then Responsibilities:
Responsibilities
- Lead quality engineering, failure analysis, and manufacturing assessment teams supporting multiple hardware development programs.
- Drive root cause investigations for product failures identified during development, validation, manufacturing, and field deployment.
- Establish and oversee processes for failure analysis, defect tracking, corrective actions, and preventive action implementation.
- Partner with hardware, firmware, software, validation, and manufacturing teams to identify and resolve complex technical issues.
- Define quality objectives, metrics, and reporting mechanisms to monitor product reliability and manufacturing
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - About The Role (intro paragraph) - What You Will Do (list of duties) - What You Bring (qualifications) - About ZT Systems (company description) - What We Offer (benefits) We could combine About The Role and About ZT Systems into an "About the role" or "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have sections: About the role (intro paragraph), Responsibilities (What You Will Do), Requirements (What You Bring), Benefits (What We Offer). Possibly also a short paragraph about company could be part of About the role? But they said "About the role" heading for section headings. The "About ZT Systems" is company overview, not role. Could we include it under About the role? Might be okay to include as part of About the role? But better to keep it separate? The instruction list didn't include "About the company". However we could include it as part of About the role? Might be considered filler if we create a heading with no real content? But we have content: company description. Could we create a heading "About the company"? Not in list but maybe allowed? 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. Probably we should stick to those headings. So we can incorporate company description into About the role section? Might be okay.
We need to avoid boilerplate: EEO, equal-opportunity, scam-warning, etc. Remove those lines.
We need to preserve all substantive information. So we need to keep the duties list, qualifications list, benefits list, and the intro paragraphs.
We need to format as HTML fragment: use for each section heading, then content: either
for prose,
- for lists.
We need to ensure we don't repeat job title as heading.
Let's extract content.
About The Role paragraph:
"The Senior Quality & Failure Analysis (FA/SVT/MAT) Engineering Manager is responsible for leading quality engineering and failure analysis organizations that support the development, validation, manufacturing, and deployment of complex hardware platforms. This role drives end-to-end product quality strategy, root cause investigations, corrective action execution, and systemic improvements to ensure the highest levels of product reliability, manufacturability, and customer satisfaction. The ideal candidate combines deep technical expertise in failure analysis, system validation testing (SVT), manufacturing analysis, and quality engineering with proven leadership capabilities. Working across design, hardware, firmware, validation, manufacturing, supplier quality, and operations teams, this leader ensures quality issues are rapidly identified, thoroughly investigated, and effectively resolved throughout the product lifecycle."
That's prose.
What You Will Do list:
- Lead quality engineering, failure analysis, and manufacturing assessment teams supporting multiple hardware development programs.
- Drive root cause investigations for product failures identified during development, validation, manufacturing, and field deployment.
- Establish and oversee processes for failure analysis, defect tracking, corrective actions, and preventive action implementation.
- Partner with hardware, firmware, software, validation, and manufacturing teams to identify and resolve complex technical issues.
- Define quality objectives, metrics, and reporting mechanisms to monitor product reliability and manufacturing performance.
- Lead system-level and component-level failure investigations using data-driven methodologies and structured problem-solving techniques.
- Drive continuous improvement initiatives that reduce defects, improve yield, and enhance product reliability.
- Collaborate with supplier quality and manufacturing partners to address quality concerns and implement corrective actions.
- Ensure timely execution of quality reviews, failure analysis reports, and risk assessments.
- Develop strategies for reliability growth, quality monitoring, and manufacturing process improvement.
- Establish escalation paths and governance processes for high-priority quality and reliability issues.
- Present quality trends, failure analysis findings, risks, and mitigation plans to executive leadership and key stakeholders.
That's a list.
What You Bring list (qualifications):
- Bachelor's degree in Electrical Engineering, Mechanical Engineering, Computer Engineering, Materials Science, or a related technical discipline; advanced degree preferred.
- 10+ years of experience in quality engineering, failure analysis, reliability engineering, manufacturing quality, or related technical leadership roles.
- Proven experience leading root cause investigations and corrective action programs for complex hardware products.
- Strong understanding of failure analysis methodologies, system validation testing (SVT), manufacturing assessment techniques, and reliability engineering principles.
- Experience with hardware platform development, manufacturing processes, product qualification, and production ramp activities.
- Deep knowledge of quality management systems, defect tracking processes, and continuous improvement methodologies.
- Experience applying structured problem-solving tools such as 8D, FMEA, RCA, Six Sigma, or similar quality frameworks.
- Demonstrated success working across cross-functional teams including engineering, validation, manufacturing, operations, and supplier management organizations.
- Strong analytical skills with the ability to interpret failure data, identify trends, and drive actionable improvements.
- Excellent communication, stakeholder management, and executive presentation skills.
- Ability to influence technical and business decisions in highly complex, fast-paced environments.
- Proven track record of improving product reliability, manufacturing quality, operational performance, and customer outcomes through disciplined quality and failure analysis practices.
That's list.
About ZT Systems paragraph:
"At ZT Systems, a Sanmina Company, you’ll get to do work you are proud of alongside smart, passionate people. Every day, there are opportunities to collaborate with the best in the industry to design, build, and deliver impactful solutions to world-class customers. Along the way, you will gain hands-on experience in a fast-paced environment that’s challenging, rewarding, and career-defining. A culture built around our values we work hard and think fast. We view challenges as opportunities—to do better, push harder, and be faster than we were the day before. When we fail, we learn from it and move on together. And when we succeed, we use the momentum to go even further. We create value with everything we do, building the foundation of today—and transforming the future of tomorrow. Join ZT Systems and help us build technology infrastructure that connects the world."
That's prose.
What We Offer (benefits) includes several sub-sections: Compensation & Financial Security, Health & Wellness, Time Away & Work-Life Balance, Growth & Purpose. Each has bullet points.
We need to decide whether to create a Benefits section with subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Benefits heading and then list benefits. Could also have subheadings inside? Not required. We could just list all benefits under Benefits as a
- . But we need to preserve all substantive information; we can keep the subheadings as plain text inside
- maybe? Or we could keep them as inside
- . The instruction didn't forbid using other tags inside
- . It said use
- for any list of duties/requirements/benefits, and
for prose. So we can have
- where each
- contains the benefit description, possibly with for subheadings.
We need to avoid boilerplate: "These benefits are available to eligible employees and are designed to grow with you as your career evolves. Full benefits and eligibility varies by work location. Learn more about our benefits here." That's boilerplate? It's somewhat generic but still substantive? Might be considered boilerplate but it's still info. However we might drop it as it's generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits description about eligibility and learn more might be considered boilerplate but it's still part of benefits. However it's not duplicated. Might keep? Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The eligibility line is substantive (though generic). I'd keep it.
Also "ZT Group Int’l. is an Equal Opportunity Employer..." is EEO boilerplate; remove.
Also the export control license paragraph is legal; remove.
Thus final HTML:
About the role
... (intro paragraph + maybe company description? We'll decide.)
But we have company description separate; maybe we can add anotherAbout the company
but not in list. Could we treat it as part of About the role? Might be okay to include it as a separate paragraph under About the role heading. The instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). It doesn't forbid adding other headings, but they gave examples. Safer to stick to those headings. So we can merge company description into About the role paragraph after the role description. That would be substantive. Thus About the role section will have two paragraphs: first the role description, second the company description. Or we can combine into one paragraph with a space. We'll output:About the role
The Senior Quality & Failure Analysis (FA/SVT/MAT) Engineering Manager is responsible for leading quality engineering and failure analysis organizations that support the development, validation, manufacturing, and deployment of complex hardware platforms. This role drives end-to-end product quality strategy, root cause investigations, corrective action execution, and systemic improvements to ensure the highest levels of product reliability, manufacturability, and customer satisfaction. The ideal candidate combines deep technical expertise in failure analysis, system validation testing (SVT), manufacturing analysis, and quality engineering with proven leadership capabilities. Working across design, hardware, firmware, validation, manufacturing, supplier quality, and operations teams, this leader ensures quality issues are rapidly identified, thoroughly investigated, and effectively resolved throughout the product lifecycle.
At ZT Systems, a Sanmina Company, you’ll get to do work you are proud of alongside smart, passionate people. Every day, there are opportunities to collaborate with the best in the industry to design, build, and deliver impactful solutions to world-class customers. Along the way, you will gain hands-on experience in a fast-paced environment that’s challenging, rewarding, and career-defining. A culture built around our values we work hard and think fast. We view challenges as opportunities—to do better, push harder, and be faster than we were the day before. When we fail, we learn from it and move on together. And when we succeed, we use the momentum to go even further. We create value with everything we do, building the foundation of today—and transforming the future of tomorrow. Join ZT Systems and help us build technology infrastructure that connects the world.
Then Responsibilities:Responsibilities
- Lead quality engineering, failure analysis, and manufacturing assessment teams supporting multiple hardware development programs.
- Drive root cause investigations for product failures identified during development, validation, manufacturing, and field deployment.
- Establish and oversee processes for failure analysis, defect tracking, corrective actions, and preventive action implementation.
- Partner with hardware, firmware, software, validation, and manufacturing teams to identify and resolve complex technical issues.
- Define quality objectives, metrics, and reporting mechanisms to monitor product reliability and manufacturing