Drimva

Saronic

Senior / Staff Robotics Security Software Engineer

Austin, TX · On-site · Staff · Full-time · Posted Oct 14, 2026

Experience
3+ years in security software engineering, preferably in autonomy, robotics, or embedded systems. Staff Engineers: 8+ years, including architecture, cross-functional leadership, or platform ownership in autonomy, robotics, or embedded systems.
Education
Bachelor’s or Master’s degree in Computer Science, Software Engineering, or a related field.
Visa sponsorship
If the role is based in the United States, it requires U.S. Person status to access export-controlled information or items.

About the job

Designs and hardens security controls across autonomous vessels, their communications networks, and the cloud systems that manage the fleet.

What you'll do

  • Implement vessel security features including secure boot, trusted execution, identity and authentication, cryptographic services, and secure updates.
  • Secure NixOS configurations, dependencies, and CI/CD pipelines; build reusable security tools and libraries.
  • Collaborate on security architecture, threat modeling, risk assessment, and incident response across engineering and field teams.

What they ask for

  • Bachelor’s or Master’s degree in Computer Science, Software Engineering, or a related field.
  • Proficiency in C/C++ or Rust and hands-on experience securing embedded Linux systems.
  • Understanding of cryptographic primitives and protocols, with experience integrating them into real systems.
  • Experience with hardware security modules, secure boot, and system-level software spanning kernel and bootloader.

Nice to have

  • Knowledge of DoD standards and regulations related to security software development.
  • Prior work on autonomous systems or experience with real-time systems.

Tools

Rust, C/C++, NixOS, Nix, TLS, mutual TLS

AI focus

Build reusable security tools, libraries, and instrumentation using automation and AI-assisted approaches.

Model-written summary · the original posting is authoritative

First seen Oct 15, 2026 · Last verified Nov 4, 2026 (UTC)