Staff Engineer, Systems Safety; R4823

Founded in 2015, Shield AI is a venture‑backed deep‑tech company with the mission of protecting service members and civilians with intelligent systems. Its products include the V‑BAT and X‑BAT aircraft, Hivemind Enterprise, and the Hivemind Vision product lines. With offices and facilities across the U.S., Europe, the Middle East, and the Asia‑Pacific, Shield AI’s technology actively supports operations worldwide. For more information, visit (Use the "Apply for this Job" box below).

Follow Shield AI on Linked In, X, Instagram, and You Tube.

This role is hands‑on and highly collaborative, requiring experience with safety‑critical software systems and familiarity with airborne software safety processes (DO‑178C, ARP
4761, ARP
4754A, and/or MIL‑HDBK‑516C). It requires strong software system intuition, and a software engineering background. You will serve as a safety authority across the Hivemind platform team, ensuring that safety considerations are built into architecture decisions, requirements, code, and verification strategies from the outset – not bolted on at the end.

What you’ll do:

• 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.

Required qualifications:

• Bachelor’s degree with approximately 7+ years of relevant experience, or Master’s degree with approximately 5+ years of relevant experience, in Systems Engineering, Software Engineering, or a closely related technical field with demonstrated experience on safety‑critical airborne software.
• Experience working within or applying safety‑critical standards (e.g., DO‑178C, MIL‑HDBK‑516C, ARP
  4754A, ARP
  4761).
• Experience deriving safety requirements and allocating them to software components at defined criticality levels.
• Experience in software…