Avionic Engineering Architect III
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove those paragraphs.
We need to decide sections: About the role (intro), Responsibilities (Your Challenges), Qualifications (Your Boarding Pass + Preferred Education/Skills), Skills (maybe list of specific skills like ARP 4761, DO-297 etc), Benefits (How we care for you), Pay (Financial Rewards). Could also include Travel Required, Citizenship, Clearance, Physical Requirements maybe under Qualifications or a separate section like Requirements. But we can incorporate into Qualifications/Requirements.
We must not create sections with filler. Ensure each heading has real content.
Let's extract content:
About the role: "Ready to shape the future of vertical flight? Airbus Helicopters is seeking a senior-level Engineering Architect Level 3 (Avionic Systems) to lead, design, and integrate core avionics architecture across our world-class helicopter fleet-including the H125, H130, H135, H145, and H160 platforms. In this high-visibility role, you will own critical architecture decisions, driving system integration and airworthiness standards from early design concepts through flight test and FAA certification. Meet the Team: Our Engineers have the privilege of working on complex, highly engineered machines and are involved at all stages of the aircraft life cycle, from product development to manufacturing and direct support to our airline customers. If you’re interested in designing, creating, and testing the present and future of Airbus products across the globe, join our mission to connect the world. Your working environment: A suburb just outside the Dallas-Fort Worth metropolitan area is home to Airbus Helicopters U.S. regional headquarters, where we have more than 1,000 employees. Check out one of the seven professional sports teams that also call Dallas home - you may even see a special, custom Airbus helicopter dedicated to the Dallas Cowboys flying during home games."
That's prose.
Responsibilities: "Your Challenges:" with three bullet-like paragraphs: Architecture and definition: 60% ... Integration activities: 30% ... Certification activities: 10%. Each contains sentences with details. We can turn each into
- items.
Qualifications: "Your Boarding Pass: (Required for consideration)" includes:
- Must possess a Bachelor of Science in Electrical Engineering (BSEE) or equivalent experience (4 years)
- Have a minimum of 10 (ten) years of proven experience (or verifiable demonstrated equivalent) of aircraft systems design, development, integration and certification
- Avionics architecture
- Avionics system integration
- System Engineering(e.g. ARP 4761 and ARP 4754)
- Airworthiness (identification of rules to be applied)
- Simulation
- Flight safety (safety objectives definition)
- Familiar with DO-297, DO-178 and DO-160
Then "Preferred Education/Skills:" includes:
- Masters in the above referenced degree
- Human Machine Interface (HMI) (parameter to be displayed and open mechanism to be implemented)
- Existing DER and/or ODA UM or existing capability to become DER and/or ODA UM
- Familiarity with MBSE Cameo Systems, and AutoCAD software.
Also Travel Required: 5% -10% Domestic and International
Citizenship: Must be a US Person under ITAR definition (U.S. Citizen, green card holder or person covered under our existing ITAR license)
Clearance: None required, but able to obtain one if becomes necessary
Physical Requirements: list.
We could put Travel, Citizenship, Clearance, Physical Requirements under Qualifications or a separate "Requirements" section. Since we already have Qualifications, maybe we rename to "Requirements". But rule says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use both Qualifications and Requirements? Probably better to have Requirements for mandatory, Qualifications for preferred? But we have both required and preferred. Could combine required into Requirements, preferred into Qualifications. Let's do:
- Requirements: mandatory (Boarding Pass items)
- Qualifications: preferred (Masters, HMI, DER/ODA, MBSE Cameo, AutoCAD) plus maybe Travel, Citizenship, Clearance, Physical Requirements? Those are also requirements. Could put them under Requirements as well.
Simplify: Use Requirements for all mandatory items (including travel, citizenship, clearance, physical). Use Qualifications for preferred items (Masters, HMI, DER/ODA, MBSE Cameo, AutoCAD). Use Skills for specific technical skills like ARP 4761, DO-297 etc? But those are already in Requirements. Might be redundant.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits, Pay. That's four sections. We can embed qualifications within Requirements.
Let's craft:
About the role
... (the intro paragraph)
Responsibilities
- Architecture and definition (60%): Define System/Integration architectures in accordance with engineering operation requirements as elaborated during offer phases to meet customer, airworthiness, general engineering standards and company requirements. Design, integrate and approve the defined solutions. Validate design solutions by implementing simulation, modeling, predictive tools. Define and approve verification methods (analysis, tests...), elaborate verification program including general engineering aspects such as Function Hazardous Analysis, EMI:EMC, general environment, vibrations, thermal analysis (list not limited) and deliver the verification results to Airworthiness team. Coordinate with test center to define the test intention and expected test results. Optimize design solution to enhance the reuse of existing solutions. Participate in quoting and feasibility studies.
- Integration activities (30%): Design, develop, and review technical documents and engineering drawings needed to integrate avionics and electrical equipment, and their associated interfaces. Create and/or review Installation Instructions and Instructions for Continued Airworthiness. Develop and verify Configuration Settings / Software Version Control documents. Develop and coordinate Technical Publications. Provide liaison support to various internal and external customers as required for support of aircraft integration and conformity efforts (suppliers, planning, industry, quality, etc.). Present and communicate modifications and aircraft configuration during design reviews and other required presentations to various customers.
- Certification activities (10%): Support the development of certification packages including certification plans, compliance checklists, and conformity inspection plans. Coordinate with FAA DERs and ODA Unit Members in support of certification requirements.
Requirements
- Bachelor of Science in Electrical Engineering (BSEE) or equivalent experience (4 years).
- Minimum of 10 years of proven experience (or verifiable demonstrated equivalent) in aircraft systems design, development, integration and certification.
- Experience in avionics architecture and avionics system integration.
- System Engineering knowledge (e.g., ARP 4761 and ARP 4754).
- Airworthiness expertise (identification of rules to be applied).
- Simulation and flight safety (safety objectives definition).
- Familiarity with DO‑297, DO‑178 and DO‑160.
- Travel required: 5%–10% domestic and international.
- Must be a US Person under ITAR definition (U.S. Citizen, green card holder, or person covered under existing ITAR license).
- Ability to obtain a security clearance if required (none required initially).
- Physical requirements: vision to see/read screens, documents, engineering drawings; hearing to participate in conversations and hear safety warnings; speaking ability; ability to operate office equipment; carry/lift up to 10 lbs/5 kg; push/pull small office furniture; ability to sit for long periods; squat/kneel to retrieve items; stand for discussions; travel independently at short notice; walk through office/production areas; PPE includes safety shoes, safety glasses, hearing protection, respirators/masks, protective gloves as required; steel‑toed shoes for shop floor visits.
Benefits
- Financial rewards: competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan, and ability to participate in an Employee Stock Ownership Plan (ESOP).
- Work/life balance: paid time off including personal time, holidays, and a generous paid parental leave program.
- Health & welfare: comprehensive insurance coverage including medical (traditional and high‑deductible health plans), prescription, dental, vision, life, disability, Employee Assistance Plan (EAP), and other supplemental benefit coverages.
- Relocation assistance for qualified positions.
Pay
Competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan, and the ability to participate in an Employee Stock Ownership Plan (ESOP).
But note that Pay duplicates Benefits financial rewards. Might be redundant. Could omit Pay section and just include in Benefits. However rule says include Pay section only if posting actually states them. It does state competitive base salary etc. But we already have that in Benefits. Could keep Pay separate but it's duplicate. Better to combine financial rewards into Benefits and not have separate Pay. Since we already have Benefits covering financial rewards, we can omit Pay. The rule: Prefer a few substantive sections over many thin ones. So we can drop Pay.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
Check that we haven't omitted any substantive info: We included the intro, responsibilities broken down, requirements (including education, experience, technical, travel, citizenship, clearance, physical), benefits (financial, work/life, health, relocation). We omitted Preferred Education/Skills (Masters, HMI, DER/ODA,
for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove those paragraphs. We need to decide sections: About the role (intro), Responsibilities (Your Challenges), Qualifications (Your Boarding Pass + Preferred Education/Skills), Skills (maybe list of specific skills like ARP 4761, DO-297 etc), Benefits (How we care for you), Pay (Financial Rewards). Could also include Travel Required, Citizenship, Clearance, Physical Requirements maybe under Qualifications or a separate section like Requirements. But we can incorporate into Qualifications/Requirements. We must not create sections with filler. Ensure each heading has real content. Let's extract content: About the role: "Ready to shape the future of vertical flight? Airbus Helicopters is seeking a senior-level Engineering Architect Level 3 (Avionic Systems) to lead, design, and integrate core avionics architecture across our world-class helicopter fleet-including the H125, H130, H135, H145, and H160 platforms. In this high-visibility role, you will own critical architecture decisions, driving system integration and airworthiness standards from early design concepts through flight test and FAA certification. Meet the Team: Our Engineers have the privilege of working on complex, highly engineered machines and are involved at all stages of the aircraft life cycle, from product development to manufacturing and direct support to our airline customers. If you’re interested in designing, creating, and testing the present and future of Airbus products across the globe, join our mission to connect the world. Your working environment: A suburb just outside the Dallas-Fort Worth metropolitan area is home to Airbus Helicopters U.S. regional headquarters, where we have more than 1,000 employees. Check out one of the seven professional sports teams that also call Dallas home - you may even see a special, custom Airbus helicopter dedicated to the Dallas Cowboys flying during home games." That's prose. Responsibilities: "Your Challenges:" with three bullet-like paragraphs: Architecture and definition: 60% ... Integration activities: 30% ... Certification activities: 10%. Each contains sentences with details. We can turn each into
- items.
Qualifications: "Your Boarding Pass: (Required for consideration)" includes:
- Must possess a Bachelor of Science in Electrical Engineering (BSEE) or equivalent experience (4 years)
- Have a minimum of 10 (ten) years of proven experience (or verifiable demonstrated equivalent) of aircraft systems design, development, integration and certification
- Avionics architecture
- Avionics system integration
- System Engineering(e.g. ARP 4761 and ARP 4754)
- Airworthiness (identification of rules to be applied)
- Simulation
- Flight safety (safety objectives definition)
- Familiar with DO-297, DO-178 and DO-160
Then "Preferred Education/Skills:" includes:
- Masters in the above referenced degree
- Human Machine Interface (HMI) (parameter to be displayed and open mechanism to be implemented)
- Existing DER and/or ODA UM or existing capability to become DER and/or ODA UM
- Familiarity with MBSE Cameo Systems, and AutoCAD software.
Also Travel Required: 5% -10% Domestic and International
Citizenship: Must be a US Person under ITAR definition (U.S. Citizen, green card holder or person covered under our existing ITAR license)
Clearance: None required, but able to obtain one if becomes necessary
Physical Requirements: list.
We could put Travel, Citizenship, Clearance, Physical Requirements under Qualifications or a separate "Requirements" section. Since we already have Qualifications, maybe we rename to "Requirements". But rule says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use both Qualifications and Requirements? Probably better to have Requirements for mandatory, Qualifications for preferred? But we have both required and preferred. Could combine required into Requirements, preferred into Qualifications. Let's do:
- Requirements: mandatory (Boarding Pass items)
- Qualifications: preferred (Masters, HMI, DER/ODA, MBSE Cameo, AutoCAD) plus maybe Travel, Citizenship, Clearance, Physical Requirements? Those are also requirements. Could put them under Requirements as well.
Simplify: Use Requirements for all mandatory items (including travel, citizenship, clearance, physical). Use Qualifications for preferred items (Masters, HMI, DER/ODA, MBSE Cameo, AutoCAD). Use Skills for specific technical skills like ARP 4761, DO-297 etc? But those are already in Requirements. Might be redundant.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits, Pay. That's four sections. We can embed qualifications within Requirements.
Let's craft:
About the role
... (the intro paragraph)
Responsibilities
- Architecture and definition (60%): Define System/Integration architectures in accordance with engineering operation requirements as elaborated during offer phases to meet customer, airworthiness, general engineering standards and company requirements. Design, integrate and approve the defined solutions. Validate design solutions by implementing simulation, modeling, predictive tools. Define and approve verification methods (analysis, tests...), elaborate verification program including general engineering aspects such as Function Hazardous Analysis, EMI:EMC, general environment, vibrations, thermal analysis (list not limited) and deliver the verification results to Airworthiness team. Coordinate with test center to define the test intention and expected test results. Optimize design solution to enhance the reuse of existing solutions. Participate in quoting and feasibility studies.
- Integration activities (30%): Design, develop, and review technical documents and engineering drawings needed to integrate avionics and electrical equipment, and their associated interfaces. Create and/or review Installation Instructions and Instructions for Continued Airworthiness. Develop and verify Configuration Settings / Software Version Control documents. Develop and coordinate Technical Publications. Provide liaison support to various internal and external customers as required for support of aircraft integration and conformity efforts (suppliers, planning, industry, quality, etc.). Present and communicate modifications and aircraft configuration during design reviews and other required presentations to various customers.
- Certification activities (10%): Support the development of certification packages including certification plans, compliance checklists, and conformity inspection plans. Coordinate with FAA DERs and ODA Unit Members in support of certification requirements.
Requirements
- Bachelor of Science in Electrical Engineering (BSEE) or equivalent experience (4 years).
- Minimum of 10 years of proven experience (or verifiable demonstrated equivalent) in aircraft systems design, development, integration and certification.
- Experience in avionics architecture and avionics system integration.
- System Engineering knowledge (e.g., ARP 4761 and ARP 4754).
- Airworthiness expertise (identification of rules to be applied).
- Simulation and flight safety (safety objectives definition).
- Familiarity with DO‑297, DO‑178 and DO‑160.
- Travel required: 5%–10% domestic and international.
- Must be a US Person under ITAR definition (U.S. Citizen, green card holder, or person covered under existing ITAR license).
- Ability to obtain a security clearance if required (none required initially).
- Physical requirements: vision to see/read screens, documents, engineering drawings; hearing to participate in conversations and hear safety warnings; speaking ability; ability to operate office equipment; carry/lift up to 10 lbs/5 kg; push/pull small office furniture; ability to sit for long periods; squat/kneel to retrieve items; stand for discussions; travel independently at short notice; walk through office/production areas; PPE includes safety shoes, safety glasses, hearing protection, respirators/masks, protective gloves as required; steel‑toed shoes for shop floor visits.
Benefits
- Financial rewards: competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan, and ability to participate in an Employee Stock Ownership Plan (ESOP).
- Work/life balance: paid time off including personal time, holidays, and a generous paid parental leave program.
- Health & welfare: comprehensive insurance coverage including medical (traditional and high‑deductible health plans), prescription, dental, vision, life, disability, Employee Assistance Plan (EAP), and other supplemental benefit coverages.
- Relocation assistance for qualified positions.
Pay
Competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan, and the ability to participate in an Employee Stock Ownership Plan (ESOP).
But note that Pay duplicates Benefits financial rewards. Might be redundant. Could omit Pay section and just include in Benefits. However rule says include Pay section only if posting actually states them. It does state competitive base salary etc. But we already have that in Benefits. Could keep Pay separate but it's duplicate. Better to combine financial rewards into Benefits and not have separate Pay. Since we already have Benefits covering financial rewards, we can omit Pay. The rule: Prefer a few substantive sections over many thin ones. So we can drop Pay. Thus sections: About the role, Responsibilities, Requirements, Benefits. Check that we haven't omitted any substantive info: We included the intro, responsibilities broken down, requirements (including education, experience, technical, travel, citizenship, clearance, physical), benefits (financial, work/life, health, relocation). We omitted Preferred Education/Skills (Masters, HMI, DER/ODA,