Staff Engineer, Systems Safety (R4823)

Safety requirements development:

Derive and author safety requirements from system-level hazard analyses, functional hazard assessments (FHAs), and customer/regulatory safety objectives.

Translate safety requirements into clear, testable software requirements aligned with the appropriate Design Assurance Level (DAL) or software criticality classification.

Collaborate with requirements engineers, system architects, product managers, software developers, and test engineers to ensure safety requirements flow consistently and traceably through product and component requirements.

Requirements traceability and verification support

• Maintain bidirectional traceability from safety requirements through design, implementation, and verification.

• Collaborate with QA and test teams to define verification strategies, review test cases for safety coverage, and confirm that safety requirements are demonstrably satisfied prior to release.

• Documentation and modeling:

• Author clear, well-structured safety documentation and contribute to system models (SysML/MBSE) with a safety lens - capturing safety-relevant behavior, failure propagation paths, and mitigations.

• Produce artifacts that are defensible to airworthiness authorities and understandable to both technical and non-technical stakeholders.

• Hazard and safety analysis:

• Lead and support safety analysis activities including Functional Hazard Assessments (FHA), Failure Mode and Effects Analysis (FMEA), Fault Tree Analysis (FTA), and Failure Mode and Effects Summary (FMES) for Hivemind software components and autonomy pipelines.

• Identify safety-relevant failure conditions, assess severity, and drive mitigation strategies into the system architecture.

• Cross-stack safety integration:

• Work closely with engineers across the full product stack - including foundational software, autonomy and AI algorithms, simulation and test infrastructure, and GUI layers - to ensure safety requirements are correctly allocated to software components and that the system architecture supports safe operation under both nominal and off-nominal conditions.

• Certification Evidence Support:

• Collaborate with teams to ensure that process adherence, artifact completeness, and traceability are continuously demonstrated through development artifacts rather than assessed solely through manual reviews.

• Support the generation, organization, and validation of certification evidence, ensuring it is accurate, complete, and defensible for internal and external airworthiness assessments