About The Team

The Sentry Tower Software team develops robotic systems that provide force protection capabilities, monitoring the perimeter of secure areas, land or sea, for approaching people, vehicles, and vessels. We live in a world where security officers are increasingly overwhelmed by sensor data feeds. Our products leverage advanced sensor fusion and autonomy to seamlessly render activity in the environment to Lattice’s common operating picture.

About the Job

Every Sentry Tower we ship, across Counter-Intrusion and Air Defense, boots from a common software platform: a NixOS-based overlay that defines the base images, the system services, the compute configuration for each hardware generation, and the network topology that ties the tower’s payloads together. That platform is the foundation the entire product line stands on, and we are looking for a Senior Software Engineer to own it.

This is a systems and infrastructure role with unusually direct product consequences. The tower’s network is not a datacenter network: it is a set of VLANs and bridges carrying camera, radar, GPS, and sensor-board traffic over a mix of mesh radio, cellular, and satellite backhaul, on hardware that sits at the far end of a very long support loop. When a business line adds a new payload with its own switch, or when a routing priority is wrong, the failure shows up in the field. You will own the topology as a contract: define it, document it, review changes against it, and make the correct integration the easy one.

You will also be a primary steward of our build and configuration system. Our images are fully declarative and reproducible, spanning several compute generations and a dozen product variants, and we are actively consolidating legacy per-product configurations into a common, composable base.

Our Product: https://www.anduril.com/sentry

WHAT YOU’LL DO

• Own the shared base of our NixOS overlay: system modules, compute platform definitions, common tower services, and the image definitions that every product variant composes from.
• Own the tower network topology end to end: VLAN and subnet allocation, bridging, link ranking and failover across heterogeneous backhaul, NAT and firewall policy, and the physical-port-to-payload mapping for each carrier board.
• Define and enforce the integration contract that business line teams use to add network-attached payloads, so their additions extend the platform instead of diverging from it.
• Drive the consolidation of legacy, per-product configurations into the common overlay, with build-time checks that keep them from drifting back apart.
• Support and extend our real-time messaging layer as services migrate from the legacy pub-sub bus to its next-generation replacement, including the topic and schema contracts that define who owns which data.
• Debug problems that cross every layer at once: kernel and device tree, systemd unit ordering, Nix evaluation, link-layer configuration, and the sensor daemons on top.

REQUIRED QUALIFICATIONS

• 4+ years of professional software engineering with substantial time in Linux systems, embedded platforms, or infrastructure work.
• Deep, practical networking knowledge: VLANs, bridging, routing and policy routing, DHCP, multicast, NAT, and firewalling, plus fluency with ip, tcpdump, and Wireshark for diagnosing real traffic.
• Strong experience with declarative configuration management and reproducible builds. Nix or NixOS is what we use and what we most want to see; adjacent depth in Bazel, Buildroot, Yocto, or infrastructure-as-code tooling (Terraform, Ansible, Pulumi) is a solid substitute.
• Proficiency in Rust or C++, enough to read and modify the services that sit on top of the platform, not just the configuration that deploys them.
• Comfort operating and troubleshooting real hardware: serial consoles, provisioning and reflashing, boot problems, and remote debugging of systems you cannot physically reach.
• Demonstrated ability to define a technical interface that other teams build against, and to hold that line through code review and documentation rather than authority.
• US person status required, with eligibility to obtain and maintain a US security clearance.

NICE TO HAVE

• Hands-on NixOS experience, including writing modules and maintaining flakes.
• Python for tooling and automation.
• Experience with NVIDIA Jetson platforms (Xavier, Orin, Thor) including BSP integration, device trees, and JetPack upgrades.
• Fleet-scale operational experience: over-the-air update systems, observability pipelines, or long-lived embedded deployments.
• Familiarity with CAN, SNMP, or managed-switch configuration in an embedded context.
• Experience setting up and maintaining CI/CD for large build graphs and hardware-in-the-loop pipelines.