Systems Engineer, Air Defense

About the role

This role operates within the Air Defense team, which designs and builds robots that detect and defeat unmanned aerial systems. The position supports critical warfighter capabilities across detection, tracking, identification, deterrence, and defeat. The scope covers integration, verification, and deployment of multi-domain sensor and effector solutions in varied operational configurations.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Integration of emerging capabilities is led to bring new hardware and software products into the Anduril Air Defense Family of Systems. Requirements decomposition is led across cross-functional teams to define success despite ambiguous constraints. System laydown is scoped rigorously, while performance is scrutinized and deployment outcomes are ensured to meet customer requirements. Systems are managed end to end, with problems identified and solved between components to achieve final mission success.

Requirements

Two to four years of hardware and software systems engineering experience is required. A degree in Engineering, Physics, Robotics, Mathematics, or a related field must be held. Model based systems engineering must be demonstrated throughout the program lifecycle. Proficiency with tools such as JAMA, Cameo, Matlab, Simulink, and AFSIM must be shown. Programming experience in Python, C/C++, or Rust for analysis and simulation is required. Skills in Statistics, AI/ML, MBSE, and Requirements must be applied. Engineering standards must be consistently applied to processes and requirements. Collaboration across cross-functional teams must be handled effectively. Ambiguity, evolving priorities, and challenging problems must be navigated comfortably. Clear communication and presentation to diverse stakeholders must be maintained.

Practical notes

Authorization to work in the United States is mandatory. Travel to customer sites may reach 25% of time. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Model based systems engineering is widely used for safety and mission critical functions. Robotics, computer vision, and sensor fusion are central to modern air defense workflows. Cross-functional collaboration aligns product, engineering, and operational stakeholders. Standards based engineering processes support reliability in defense environments. Command, control, and effectors are integrated through data driven decision layers.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.