Quality Engineer I

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract content. The posting includes: - Intro: "DRT is seeking a Quality Engineer I to join our growing aerospace manufacturing team. This is an outstanding opportunity..." etc. That's about the role. - "Why Join DRT?" bullet list: Work on components..., Gain hands-on..., Learn..., Build skills..., Enjoy opportunities..., Competitive pay and comprehensive benefits package. That's benefits? Actually "Competitive pay and comprehensive benefits package" is a benefit statement. Could be Benefits section. - "What You'll Do" with subheadings: Drive Manufacturing Quality, Solve Real Production Challenges, Support Aerospace Quality Systems, Improve Processes. Those are responsibilities. - "What We're Looking For" includes Required Qualifications and Preferred Qualifications. That's qualifications/skills. - "Apply Today" is application instruction, to be removed. - Also mention relocation: "Relocation: No relocation package..." that's minor metadata, can be folded into short p or dropped. We must not include boilerplate like EEO etc. Not present. We need sections: About the role (intro), Responsibilities (What You'll Do), Requirements (maybe Required Qualifications), Qualifications (maybe Preferred?), Skills (maybe specific skills like GD&T, SPC etc), Benefits (Competitive pay and comprehensive benefits package). Pay and Schedule only if stated; we have "Competitive pay" mentioned but not specific amount; but rule says: never create Pay/Schedule/Benefits sections unless posting actually states them. It states "Competitive pay and comprehensive benefits package". That's a statement about pay and benefits. So we can include Benefits section with that sentence. Pay section? It mentions competitive pay but not specifics; but rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive pay". That's a statement, albeit vague but still states pay. Should we include Pay section? The instruction: Prefer a few substantive sections over many thin ones. Could combine pay and benefits into Benefits section. But we have separate headings for Benefits and Pay. Might be better to have Benefits section that includes both pay and benefits. Since they said "Competitive pay and comprehensive benefits package". So we can put that in Benefits section. No separate Pay section. Schedule: not mentioned, so omit. Now we need to preserve all substantive information. Let's extract. About the role: first paragraph(s) up to "Why Join DRT?" maybe include that as About the role. Could also include the relocation note as short p. Responsibilities: "What You'll Do" sections with bullet points under each subheading. We need to convert to

• . The subheadings (Drive Manufacturing Quality, Solve Real Production Challenges, Support Aerospace Quality Systems, Improve Processes) could be either headings within responsibilities or just part of list. Since we only have h3 for section headings, we could keep responsibilities as a section with subheadings maybe as or just include in list items. But we must not create extra headings beyond allowed? The instruction only says use

  for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just make a list under Responsibilities without internal headings. However we need to preserve the structure; we could embed the subheadings as part of list items (e.g.,

  Drive Manufacturing Quality: ...

  ). That preserves info. Similarly for Requirements: we have Required Qualifications and Preferred Qualifications. Could combine into Requirements section with subheadings. Skills: maybe extract specific skills like GD&T, SPC, root cause analysis, etc. Could be a separate Skills section. But we must not create thin sections. Perhaps combine Requirements and Skills into one Qualifications section? But we have both headings allowed. Let's think. We have Required Qualifications (education, experience, etc.) and Preferred Qualifications (certifications, software). That's qualifications. Skills could be things like "Strong analytical, organizational, and problem-solving skills. Proficiency with Microsoft Office, including Excel." Those are also qualifications. Might be okay to have a single Qualifications section that includes both required and preferred. But we have headings for Requirements and Qualifications separate. Could use Requirements for required qualifications, Qualifications for preferred qualifications and skills. Or combine. Better: Use Requirements for required qualifications (education, years experience, specific experiences). Use Qualifications for preferred qualifications and skills (certifications, software, etc.). Skills maybe not needed separately. But we also have Skills like GD&T, SPC, root cause analysis, etc. Those appear in responsibilities and qualifications. Could list them under Skills section. Given the instruction to prefer few substantive sections, maybe we have About the role, Responsibilities, Requirements, Benefits. That's four sections. Could embed qualifications within Requirements. But we have both required and preferred; we could still put all under Requirements. Let's decide: Sections: - About the role (intro + Why Join DRT? maybe) - Responsibilities (What You'll Do) - Requirements (Required Qualifications + Preferred Qualifications + Skills) - Benefits (Competitive pay and comprehensive benefits package) We'll omit Pay and Schedule. Now we need to extract content precisely. About the role: The first paragraph: "DRT is seeking a Quality Engineer I to join our growing aerospace manufacturing team. This is an outstanding opportunity for an early-career engineer or quality professional who wants to develop expertise in aerospace manufacturing, quality systems, process validation, and continuous improvement. Relocation: No relocation package or relocation assistance is offered for this position. Candidates must be able to work from the local area and commute to the designated work location as required. You'll work alongside experienced Manufacturing Engineers, Quality Engineers, Operations leaders, and suppliers while gaining hands-on exposure to advanced aerospace manufacturing processes, AS9100 quality systems, First Article Inspection (FAIR), PPAP, supplier quality, and process improvement initiatives. If you enjoy solving technical challenges, analyzing processes, and driving quality improvements, we'd love to hear from you!" Then "Why Join DRT?" bullet list: Work on components that support critical aerospace applications; Gain hands-on experience in manufacturing quality, supplier quality, and process validation; Learn from experienced aerospace professionals and industry experts; Build skills in FAIR, PPAP, AS9100, root cause analysis, SPC, and continuous improvement; Enjoy opportunities for long-term career growth and advancement; Competitive pay and comprehensive benefits package. We could include the "Why Join DRT?" as part of About the role or separate section? Since we have only About the role, we can incorporate that list as part of About the role. Now Responsibilities: "What You'll Do" with subheadings. Let's extract each bullet: Under Drive Manufacturing Quality: - Support qualification and validation of aerospace manufacturing processes. - Lead and coordinate AS9102 First Article Inspection Reports (FAIR), PPAP, and process validation activities. - Develop and improve quality plans that align customer, engineering, and manufacturing requirements. - Create and maintain in-process and final inspection documentation. - Conduct Gage R&R, MSA, and correlation studies to ensure measurement accuracy. - Review engineering drawings, specifications, GD&T requirements, and customer quality requirements. Under Solve Real Production Challenges: - Participate in Material Review Board (MRB) activities and help resolve nonconforming material issues. - Support Root Cause Corrective Action (RCCA) investigations and corrective action implementation. - Analyze quality and process performance metrics to identify improvement opportunities. - Partner with Manufacturing, Engineering, and Inspection teams to resolve quality concerns and improve process capability. Under Support Aerospace Quality Systems: - Help maintain compliance with AS9100 and customer-specific requirements. - Participate in internal and external audits. - Maintain quality documentation, traceability records, inspection reports, and KPI metrics. Under Improve Processes: - Support Lean Manufacturing, Kaizen, and Six Sigma initiatives. - Utilize SPC and data analysis tools to improve process performance. - Drive improvements that reduce scrap, rework, and variation while increasing efficiency. Now Requirements: Required Qualifications: - Bachelor's degree in Engineering, Manufacturing, Aerospace, Quality, Mechanical Engineering, Engineering Technology, or a related technical field. - 3+ years of manufacturing, quality, engineering, or related technical experience. - Experience supporting AS9102 FAIR, PPAP, and process validation activities. - Experience with First Piece, In-Process, and Final Inspection activities. - Experience participating in RCCA investigations and corrective action implementation. - Strong understanding of GD&T. - Ability to interpret engineering drawings, specifications, and inspection requirements. - Knowledge of AS9100 and/or ISO 9001 quality systems. - Strong analytical, organizational, and problem-solving skills. - Proficiency with Microsoft Office, including Excel. Preferred Qualifications: - Aerospace or other regulated manufacturing experience. - Six Sigma Green Belt certification. - DQR and/or LCS (CLCSR) certification. - Internal Quality Management System auditing experience. - Experience with VBA or Python. - Familiarity with Hexagon PC-DMIS, Mitutoyo systems, and GOM software. - Exposure to supplier quality and supplier audits. - CQE, Lean Manufacturing, or additional quality certifications. - Experience supporting OEM, Tier 1 aerospace suppliers, or FAA-regulated environments. Now Benefits: "Competitive pay and comprehensive benefits package." We should also maybe include the relocation note as a short p inside About the role or separate? The instruction: fold minor metadata into a short

  or drop it. We can include a short p about relocation within About the role. Now produce HTML:

  About the role

  DRT is seeking a Quality Engineer I to join our growing aerospace manufacturing team. This is an outstanding opportunity for an early-career engineer or quality professional who wants to develop expertise in aerospace manufacturing, quality systems, process validation, and continuous improvement. Relocation: No relocation package or relocation assistance is offered for this position. Candidates must be able to work from the local area and commute to the designated work location as required. You'll work alongside experienced Manufacturing Engineers, Quality Engineers, Operations leaders, and suppliers while gaining hands-on exposure to advanced aerospace manufacturing processes, AS9100 quality systems, First Article Inspection (FAIR), PPAP, supplier quality, and process improvement initiatives. If you enjoy solving technical challenges, analyzing processes, and driving quality improvements, we'd love to hear from you!

  Why Join DRT?

  • Work on components that support critical aerospace applications
  • Gain hands-on experience in manufacturing quality, supplier quality, and process validation
  • Learn from experienced aerospace professionals and industry experts
  • Build skills in FAIR, PPAP, AS9100, root cause analysis, SPC, and continuous improvement
  • Enjoy opportunities for long-term career growth and advancement
  • Competitive pay and comprehensive benefits package
  But note: "Why Join DRT?" is a heading; we could make it

  Why Join DRT?

  but we only allowed certain headings. However we could treat it as a

  with strong? 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 suggests to use those for sections. Safer to not add extra headings; we can incorporate "Why Join DRT?" as a

  with or just as a sentence. But we need to preserve the content; we can keep it as a <