Airworthiness & Safety Engineer, Lead

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, navigation, cookie, application instructions, duplicated lines. Also remove "Other duties as assigned"? Might be considered boilerplate? It's part of responsibilities maybe keep? It's generic but maybe keep as part of responsibilities. However we should not include filler like "commensurate with experience". We have salary range given, so Pay section. Benefits given. Schedule? Not mentioned explicitly; there is "9/80 work schedule" mentioned in benefits. That is schedule info. So we can include Schedule section referencing 9/80 work schedule. Also maybe mention "Willing to travel both domestically and internationally as required" could be part of Responsibilities or Qualifications? It's a requirement maybe. We'll include under Responsibilities or maybe under Qualifications? It's more like a requirement. We'll put under Responsibilities? Actually it's a physical demand/travel requirement. Could be under Responsibilities? Might be better under Qualifications as "Willing to travel...". We'll decide. We need to parse the posting. Key sections: - Summary: "Job Description The Lead Airworthiness (AW) & Safety Engineer Leads airworthiness and product safety activities for complex Unmanned Aircraft Systems (UAS) throughout the product lifecycle. Develops certification strategies, plans, requirements, and compliance approaches supporting military and civil authorities. Coordinates cross-functional engineering teams to resolve safety and certification requirements and support flight releases and continued airworthiness. Engages with customers, regulatory agencies, and senior leadership on certification, audits, RFIs, and RFPs." That's about the role. So we can put under

About the role

a

with that summary. - Responsibilities: list bullet points under "Position Responsibilities". Many sentences. We'll extract each as

. Need to preserve all substantive info. Let's list them: 1. Develops and performs technical airworthiness and product safety planning, internally driven, customer contract and regulatory driven 2. Product requirements development support based on expected market, customer, and regulatory requirements 3. Verification support including development of airworthiness and product safety approach, plans, basis of certifications, means of compliance, and certification activities for complex total systems 4. Ensures the logical and systematic realization of customer airworthiness and product safety compliance into UAS solutions to meet program and business objectives (e.g. flight releases, military certification, type certification and supplemental type certifications, continued airworthiness, and operational or airspace Integration) 5. Reviews and coordinates with engineering disciplines at all levels of total system including concept development, requirements, design, test, manufacturing, operation, maintenance and disposal 6. Works with both military and civil airworthiness authorities for certification of Unmanned Aircraft Systems (UAS) 7. Facilitates changes to product designs, testing, analyses, maintenance, operations and documentation in order to satisfy certification and product safety requirements 8. Supports Field Service Bulletin and Problem Report support related to Airworthiness and product safety 9. Tracks and reports product improvements that provide airworthiness certification value, resolve airworthiness or product safety deficiencies or improve airworthiness or safety of products 10. Participates with other senior managers to establish strategic plans and objectives 11. Leads Airworthiness efforts with the support of broad cross-functional teams 12. Facilitates customer Safety and AW Accreditation audits supporting company processes 13. Supports Requests for Information (RFI) and Request for Proposals (RFP) in the Airworthiness and Product Safety capacity 14. Communicates AV’s AW and Product Safety position to Customer and Regulatory bodies 15. Other duties as assigned (maybe keep) We'll include these as

• . - Basic Qualifications (Required Skills & Experience): list: - BS degree in Engineering required is required or equivalent combination of education, training, and experience - Minimum of 8+ years of directly related experience - A minimum of 4 years of relevant experience in Airworthiness related work - Experienced in and has demonstrated strong systems engineering background - Experienced working in a highly technical, fast-paced environment with both Domestic and International customers - Has a detailed understanding of Military, FAA, EU, NATO, and EASA airworthiness and certification processes and standards - Understanding of US Government and international safety requirements (UL, CE, REACH, RoHS, etc) - Has a proven track record of performance on successful programs - Experience communicating with executive level management, Customers, and Customer AW authorities - Takes initiative to own tasks and can perform with little/no daily management or oversight We'll put under

  Requirements

  maybe? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Requirements and Qualifications. Basic Qualifications likely map to Requirements. Other Qualifications & Desired Competencies map to Qualifications (desired). Skills maybe separate? Could combine desired competencies under Qualifications. We'll treat Basic Qualifications as Requirements, Other Qualifications & Desired Competencies as Qualifications. Skills maybe we can extract from desired competencies: strong computer skills, MS Office proficiency, leadership skills, communication skills, ability to excel in fast-paced, initiative, ownership, learning from mistakes, vision, inspire/motivate/empower. Those are skills/competencies. We could put them under Skills section. But we already have Qualifications covering many. To avoid duplication, we could put desired competencies under Qualifications and maybe not have separate Skills unless there is explicit skills list. The posting includes "Demonstrates strong computer skills and proficiency in MS Office (Excel, Word, PowerPoint, Outlook)" etc. That's skills. We'll put under Skills. Thus: - Requirements: Basic Qualifications list. - Qualifications: Other Qualifications & Desired Competencies list (desired). - Skills: maybe we can pull out the computer skills, leadership, communication, initiative, etc. But many overlap. To avoid duplication, we could treat Qualifications as desired competencies and Skills as specific technical skills (MS Office). Let's decide: We'll create Skills section for "Demonstrates strong computer skills and proficiency in MS Office (Excel, Word, PowerPoint, Outlook)" and maybe "Outstanding Leadership skills and experience in a highly technical environment is desire" (leadership). Also "Demonstrates strong verbal and written communication skills". Also "Able to excel in a fast-paced, deadline-driven environment, where small teams share a broad variety of duties". Also "Displays strong initiative and drive to accomplish goals and meet company objectives". Also "Takes ownership and responsibility for current and past work products". Also "Is committed to learning from mistakes and driven to improve and enhance performance of oneself, others, and the company". Also "Uses vision to think beyond the immediate situation, explore multiple potential paths and adapt decision-making style based on the situational circumstances". Also "Inspires, motivates and empowers people to deliver organizational goals, while also delivering value back to employees". That's many; maybe better to put all under Qualifications. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section? But headings are prescribed; we can omit sections if no real content. We could have Requirements and Qualifications only, and maybe Benefits, Pay, Schedule. That's enough. We'll omit Skills if content overlaps with Qualifications. However the instruction says use headings for those categories if we have content. We can decide to not include Skills if we think it's covered. But we might lose some specifics like MS Office proficiency. Could include under Qualifications as bullet. That's fine. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now Benefits: "AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." Also link to benefits page (we should drop link? It's not boilerplate? It's a link for more info; maybe we can keep as part of benefits but it's a URL; we could keep as plain text but it's not substantive? Might be considered navigation? Probably we can keep the description but drop the URL. We'll keep the description. Pay: Salary range $122,500 - $187,000. Schedule: The 9/80 work schedule mentioned under benefits; we could also put schedule section referencing that. But we already have schedule in benefits. However we can still have Schedule section: "9/80 work schedule". We'll include. Now we need to remove boilerplate: EEO, legal, ITAR requirement? ITAR requirement is substantive (citizenship requirement). Should we keep? It's a requirement for the role. It's not boilerplate; it's a specific requirement. So we should include under Requirements maybe as a bullet: "Must qualify as a U.S. person under ITAR/EAR; U.S. citizen, lawful permanent resident, refugee/asylee, or eligible for export license." Also note about Some positions will require current U.S. Citizenship due to contract requirements. We'll include. Also "Principals only need apply. NO agencies please." That's application instruction; remove. Also "About AV" section is company description; could be considered boilerplate? It's not required but maybe we can keep as part of About the role? It's about company, not role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About AV" is not explicitly listed but could be considered company overview, maybe not required. However it's substantive about the company; but the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it? It's not about the role but about the company. The instruction didn't say to remove company description. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep About AV as a section? But we only have prescribed headings; we could put it under About the role? Might be weird. Better to include as a separate section? Not in list. Could we add a heading like "About the company"? Not 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? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not add other headings. Therefore we should incorporate company description maybe into About the role? But that would mix role and company. Could we omit About AV? It's not about the role but it's substantive. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit it, we lose substantive info. But maybe they consider it boilerplate? Not sure. The examples of boilerplate include cookie/navigation/legal/EEO/equal-opportunity/scam-warning. About AV is not those. It's more like company marketing. Might be considered not required for job posting but still substantive. However typical tasks often remove company description. I'd lean to keep it as a paragraph under About the role? Could be okay. But we need to decide. I think we should keep it as a separate paragraph under About the role, maybe after role description. That preserves info. Now we need to ensure we don't repeat job title. Not include "Lead Airworthiness (AW) & Safety Engineer" as heading. Now produce HTML fragment. Let's craft:

  About the role

  The Lead Airworth