Senior Product Quality Engineer
Anduril Industries · Lexington, MA · 2 wk ago
Quality Assurance$146k–$194k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Team", "About The Job", "WHAT YOU'll DO", "Required Qualifications", "Preferred Qualifications", "US Salary Range", "Benefits". Also maybe "About The Team" and "About The Job" could be combined? 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 those headings. We should not repeat job title. We need to include sections only when posting has real specific content.
We have:
- About The Team: description of team. Could map to "About the role"? Actually "About the role" is generic. But we have "About The Team" and "About The Job". Could combine into "About the role" maybe? But we have separate sections: "About The Team" and "About The Job". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have responsibilities: "WHAT YOU'll DO" list. That's responsibilities.
We have requirements: "Required Qualifications". That's requirements.
We have preferred qualifications: could be under "Qualifications" or "Skills"? Probably "Qualifications" includes both required and preferred? But we have separate headings: Requirements, Qualifications, Skills. Could treat "Required Qualifications" as Requirements, "Preferred Qualifications" as Qualifications (or Skills). However we also have skills list within required qualifications (FMEA etc). Might be better to have:
- About the role: combine About The Team and About The Job? Or maybe we can have "About the role" as a short paragraph summarizing role. But we must preserve all substantive info; we cannot invent or summarize away detail. So we need to keep the content verbatim (or near). We can put the About The Team and About The Job under a heading "About the role"? That would be okay if we keep the content. But the heading must be exactly one of the allowed headings? 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. We should not repeat job title. We need to include sections only when posting has real specific content.
We have:
- About The Team: description of team. Could map to "About the role"? Actually "About the role" is generic. But we have "About The Team" and "About The Job". Could combine into "About the role" maybe? But we have separate sections: "About The Team" and "About The Job". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have responsibilities: "WHAT YOU'll DO" list. That's responsibilities.
We have requirements: "Required Qualifications". That's requirements.
We have preferred qualifications: could be under "Qualifications" or "Skills"? Probably "Qualifications" includes both required and preferred? But we have separate headings: Requirements, Qualifications, Skills. Could treat "Required Qualifications" as Requirements, "Preferred Qualifications" as Qualifications (or Skills). However we also have skills list within required qualifications (FMEA etc). Might be better to have:
- About the role: combine About The Team and About The Job? Or maybe we can have "About the role" as a short paragraph summarizing role. But we must preserve all substantive info; we cannot invent or summarize away detail. So we need to keep the content verbatim (or near). We can put the About The Team and About The Job under a heading "About the role"? That would be okay if we keep the content. But the heading must be exactly one of the allowed headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must only use those exact strings, but they are examples. Likely they expect those exact headings. Safer to use those exact headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role? We have About The Team and About The Job. We could put both under About the role.
Responsibilities: WHAT YOU'll DO.
Requirements: Required Qualifications.
Qualifications: Preferred Qualifications? Or maybe Skills: list of skills from required qualifications (FMEA etc). But we have many skill-like items. Could split: Qualifications = Preferred Qualifications, Skills = list of core tools etc. However the required qualifications also include "Bachelor’s degree..." etc which are qualifications. So maybe:
- About the role: About The Team + About The Job.
- Responsibilities: WHAT YOU'll DO.
- Requirements: Required Qualifications (including degree, years experience, etc).
- Qualifications: Preferred Qualifications.
- Skills: maybe the list of core tools (FMEA, RCCA/8D, etc) and hands-on experience with metrology tools, knowledge of electro-mechanical design, etc. But those are already in required qualifications. Could move them to Skills.
But we must not duplicate content. We need to preserve all substantive info; we can reorganize but not lose info. So we can split required qualifications into two parts: baseline qualifications (degree, years, experience, clearance) under Requirements; and technical skills under Skills. Preferred qualifications under Qualifications.
Pay: US Salary Range.
Benefits: Benefits section.
Schedule: not present, so omit.
We must not include boilerplate like EEO, scam warnings, data privacy, etc. Remove those.
Also remove duplicated lines, navigation, cookie, legal, application instructions.
We must not include headings with filler like "commensurate with experience". Not present.
Now produce HTML fragment.
Structure:
About the role
About the role
... combine About The Team and About The Job paragraphs.
We need to keep the content exactly as given but we can combine into paragraphs. About The Team text: "Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years. About The Team Our Quality Engineering team is a dedicated group of professionals committed to ensuring the highest standards of quality in our processes. We play a crucial role in maintaining the integrity and reliability of our products, working collaboratively to identify, analyze, and resolve quality issues. Our team thrives on a culture of continuous improvement and innovation, leveraging data-driven insights to enhance processes and outcomes." Wait the text includes "About The Team" heading then the paragraph. Actually the given text: after the mission description, there is "About The Team Our Quality Engineering team...". So we need to capture that. About The Job text: "About The Job We are seeking a Senior Product Quality Engineer to join our growing team, currently based out of Lexington, MA but relocating to Waltham, MA. You will ensure our manufacturing processes and products meet quality standards through inspections and data analysis while collaborating with cross-functional teams on quality assurance protocols. This role requires expertise in quality management systems and statistical process control within a regulated environment If you have strong analytical skills and attention to detail, this opportunity is for you! Your proactive problem-solving approach will be vital to our quality initiatives." We need to preserve that. We'll combine them into a singlemaybe two paragraphs. Now Responsibilities: list of duties from "WHAT YOU'll DO". It's a long paragraph with multiple sentences separated by line breaks? Actually it's a long sentence with many verbs. We need to turn into
- for any list of duties/requirements/benefits. The posting has a series of duties separated by line breaks? In the text they are separated by line breaks? Let's examine:
"WHAT YOU'll DO Drive improvement in product design, manufacturing, suppliers as well as service and field support in order to improve reliability across the product lifecycleDrive Quality Management System compliance & sustainability to the AS9100 certification.Develop & improve key performance indicators (KPIs) for Quality across product qualityDevelop and utilize a data driven approach to evaluating, prioritizing and tracking product quality & reliability (suppliers, manufacturing & field)Support and improve internal tracking tools for supplier incoming, manufacturing in-process, and field quality issuesLead investigations, initiatives, and projects to find root cause and implement corrective and preventative actions both internally and with suppliersSupport development and sustainability of raw material supplier inspection and incoming inspection programSupport the execution of MRB activitiesContribute to the evaluation, selection, qualification and performance of suppliersCarry out containment, audit, and disposition actions of any quality “escapes” or defective materialWork cross-functionally to define and execute the product roadmap, partnering with production to ensure incoming material inspection, process control plans and end of line tests capture the essential quality requirements for successful customer shipments."
It seems there is no punctuation between items; they are concatenated. We need to split into logical items. We can infer each duty starts with a verb: Drive improvement..., Drive Quality..., Develop & improve..., Develop and utilize..., Support and improve..., Lead investigations..., Support development..., Support the execution..., Contribute..., Carry out..., Work cross-functionally...
We'll create
- for each. Now Requirements: Required Qualifications list. It's a paragraph with multiple lines separated by line breaks? Let's see: "Required Qualifications Bachelor’s degree in Engineering or similar technical field5+ years of relevant experience working with OEM suppliers and manufacturing operations building complex hardware/software systems5+ years experience in engineering, manufacturing, or quality within the aerospace/defense, automotive, or medical device fieldsExperience working in a ISO 9001 and/or AS9100 regulated environmentWorking knowledge of Quality core tools such as Failure Modes and Effects Analysis (FMEA), Root Cause and Corrective Action (RCCA/8D), Change Management, Advanced Product Quality Planning (APQP), Production Part Approval Process (PPAP) and Geometric Dimensioning and Tolerancing (GD&T)Hands on experience using mechanical and electrical metrology tools/instrumentsWorking knowledge of electro-mechanical design and relevant manufacturing processes.A strong ownership mindset with demonstrated capability as a project manager to drive projects from start to finishEligible to obtain and maintain an active U.S. Secret security clearance" Again concatenated. We need to split into items. We'll separate each requirement. We'll separate: - Bachelor’s degree in Engineering or similar technical field - 5+ years of relevant experience working with OEM suppliers and manufacturing operations building complex hardware/software systems - 5+ years experience in engineering, manufacturing, or quality within the aerospace/defense, automotive, or medical device fields - Experience working in a ISO 9001 and/or AS9100 regulated environment - Working knowledge of Quality core tools such as Failure Modes and Effects Analysis (FMEA), Root Cause and Corrective Action (RCCA/8D), Change Management, Advanced Product Quality Planning (APQP), Production Part Approval Process (PPAP) and Geometric Dimensioning and Tolerancing (GD&T) - Hands on experience using mechanical and electrical metrology tools/instruments - Working knowledge of electro-mechanical design and relevant manufacturing processes. - A strong ownership mindset with demonstrated capability as a project manager to drive projects from start to finish - Eligible to obtain and maintain an active U.S. Secret security clearance Now Qualifications: Preferred Qualifications. Text: "Preferred Qualifications Master’s degree in a technical fieldExperience as a lead auditor for AS9100 or other ISO 9001-based QMS standard (e.g., ISO 13485, IATF 16949)Experience with supporting the manufacturing of Integrated Dewar Cooler Assemblies (IDCAs) and/or Infrared (IR) Cameras.Experience with high mix low volume manufacturing and suppliers" Split: - Master’s degree in a technical field - Experience as a lead auditor for AS9100 or other ISO 9001-based QMS standard (e.g., ISO 13485, IATF 16949) - Experience with supporting the manufacturing of Integrated Dewar Cooler Assemblies (IDCAs) and/or Infrared (IR) Cameras. - Experience with high mix low volume manufacturing and suppliers Now Skills: we could list the technical skills from required qualifications that are more skill-oriented: Working knowledge of Quality core tools (FMEA etc), Hands on experience using mechanical and electrical metrology tools/instruments, Working knowledge of electro-mechanical design and relevant manufacturing processes. Also maybe "strong ownership mindset" etc but that's more attribute. We'll put those three as skills. But we already used those in Requirements; we need to avoid duplication. If we move them to Skills, we should remove from Requirements. However the instruction says preserve ALL substantive information; we can reorganize but not lose. So we can move those skill items to Skills section and keep the rest in Requirements. Thus Requirements will contain: - Bachelor’s degree in Engineering or similar technical field - 5+ years of relevant experience working with OEM suppliers and manufacturing operations building complex hardware/software systems - 5+ years experience