Lead Avionics Engineer - Flight Termination System
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include sections only when posting has real specific content.
We have:
- About Castelion: description of company. That could be "About the role"? Actually "About Castelion" is company overview, not role. But we can map to "About the role"? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists. For company overview maybe "About the role" could include description of role and company? The posting includes "About Castelion" which is about company. Could treat as "About the role" content: combine company description and role summary? The role summary is given after title: "As the Lead Avionics Engineer specializing in Flight Termination Systems (FTS), you will be responsible for the design, development, testing, and qualification of systems that ensure the safe termination of a flight if it deviates from its planned trajectory. You will work with both hardware and software components, as well as coordinating with various key stakeholders." That's a role summary. So we can put that under About the role.
Responsibilities: we have a big list.
Requirements: The posting has "Basic Qualifications" and "Preferred Skills And Experience". Also "Leadership Qualities". Also "ITAR Requirements". Also "All employees are granted long-term stock incentives..." etc. Those are benefits.
We need to map to sections: Requirements (maybe basic qualifications), Qualifications (maybe preferred skills?), Skills (maybe leadership qualities?), Benefits (stock incentives, medical, PTO). Pay and Schedule: not mentioned, so omit.
We must not include filler like "commensurate with experience". Not present.
We must preserve all substantive info, not invent.
We need to remove boilerplate: ITAR Requirements is substantive (citizenship requirement). Should we include under Requirements? Probably yes. Also EEO statement is boilerplate, remove.
Also "All employees are granted long-term stock incentives as part of their employment at Castelion. All employees receive access to comprehensive medical, vision, and dental insurance, and the company offers four weeks of paid time off per year." That's benefits.
We need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
About the role
... company description + role summary ...
Responsibilities
- ... each responsibility ...
Requirements
- ... basic qualifications + ITAR requirement ...
Qualifications
- ... preferred skills and experience ...
Skills
- ... leadership qualities ...
Benefits
- ... long-term stock incentives, medical/vision/dental insurance, four weeks PTO per year ...
About the role
Castelion is bringing a new approach to defense development and production: one that focuses on short, iterative design cycles, rapid testing in development, and modern commercial manufacturing strategies for production at scale. We're designing, building, and testing next generation long range strike weapons systems to give America and its Allies a definitive edge and deter future conflicts. As the Lead Avionics Engineer specializing in Flight Termination Systems (FTS), you will be responsible for the design, development, testing, and qualification of systems that ensure the safe termination of a flight if it deviates from its planned trajectory. You will work with both hardware and software components, as well as coordinating with various key stakeholders.
Responsibilities
- Own system and electrical architecture development and integration of Flight Termination System components (RF command interfaces, control boxes, electronic safe and arm devices, initiators, and destruct charges) for the Blackbeard vehicle.
- Define detailed system design, including component selection, system interconnect schematics, RF interfaces, consumable budgets, harness and channel capabilities, fault tolerance, and reliability.
- Execute system validation, including compatibility testing with range assets, system electrical testing in HITL, and flight test qualification.
- Collaborate closely with regulatory partners and Range Safety to develop and maintain a tailored set of requirements specific to the Blackbeard program that defines FTS certification.
- Design and analysis of safety-critical circuits for ordnance initiation and command destruct receivers.
- Define test plans, processes, fixturing, test sequences, and generate technical reports to show compliance to strict regulatory standards.
- Lead qualification and acceptance testing of components under rigorous test environments (shock, vibration, thermal cycle, etc.) that validate component reliability and functionality.
- Conduct analyses to support reliability data and reduced scope of testing
- Generate and maintain detailed system & component documentation and specifications
- Act as the technical expert for the overall system and piece-part components, leading component & system anomaly root cause investigations and with data-driven rationale to determine hardware disposition & corrective
- Challenge applicability of baseline requirements through understanding the intent of the regulatory requirement versus solely the face value as-written requirement.
- Act as the responsible engineer