Principal Engineer, Software Architect (r4562)

Shield AI Shield AI · Defense · Dallas, TX · X-BAT Engineering - Software

Principal Engineer, Software Architect for Shield AI's XBAT program, focusing on defining and evolving the system-wide software architecture for airborne vehicles, ground stations, and autonomy layers. The role emphasizes translating safety and security goals into technical requirements, ensuring architecture supports safety-critical and cyber-relevant workflows, and driving cross-team alignment. It involves setting technical direction for long-term scalability, mentoring engineers, producing architecture artifacts, leading technical reviews, defining architecture governance, and collaborating with various teams to manage boundaries and drive technology evaluation. The position requires deep expertise in software architecture for complex, multi-domain systems, particularly in safety-critical fields like aerospace or defense, with a proven track record of delivering production software that meets stringent requirements.

What you'd actually do

  1. Define and evolve the system‑wide software architecture for XBAT, spanning airborne vehicle, ground station, and autonomy layers.
  2. Translate safety and security goals into technical requirements, standards, and design patterns that guide engineers across multiple software teams.
  3. Ensure architecture supports safety‑critical and cyber‑relevant workflows. This includes formalizing architecture decisions, traceability, and compliance pathways appropriate for advanced airborne systems.
  4. Drive cross‑team alignment on APIs, data flows, fault handling, verification strategy, and risk management so mission, vehicle, and autonomy components integrate cleanly.
  5. Partner with engineering leadership, system architects, and validation teams to balance innovation speed with rigorous assurance practices.

Skills

Required

  • software architecture for complex, multi‑domain systems
  • aerospace
  • defense
  • autonomous systems
  • safety-critical fields
  • designing and delivering production software
  • stringent safety, security, or mission assurance requirements
  • systems thinking
  • tradeoffs across performance, latency, reliability, testability, and certification or compliance considerations
  • written and verbal communication
  • driving architecture adoption and discipline across multiple teams

Nice to have

  • aerospace software assurance frameworks or standards
  • autonomy
  • mission planning
  • AI‑enabled software
  • cyber hardening
  • secure design practices
  • distributed or networked vehicle systems
  • ground infrastructure
  • leadership or mentor role
  • building and scaling architecture practices
  • design culture
  • constrained platforms
  • real‑time requirements
  • limited compute
  • avionics‑style integration challenges
  • VTOL or other advanced aircraft programs
  • austere operations
  • long‑range operations
  • resilient autonomy
  • end‑to‑end product lifecycle
  • flight test or operational deployment
  • modern software tooling
  • traceability
  • CI/CD
  • automated verification
  • static analysis
  • high‑assurance pipelines
  • highly collaborative, fast‑paced environment
  • requirements can evolve quickly
  • architecture must adapt without losing rigor

What the JD emphasized

  • safety-critical
  • cyber-relevant
  • safety
  • security
  • mission assurance
  • assurance