Staff Robotics Engineer, Maritime

About the role

This role owns the full lifecycle of vehicle perception and planning capabilities for autonomous maritime systems. The position acts as a technical lead and senior contributor who drives architecture, delivery, and evolution of safety-critical autonomy. Success ensures and reliable autonomy through the entire product lifecycle.

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

Define and deliver a multi-year, multi-stakeholder software roadmap for vehicle perception and planning to ensure customer success across autonomous platforms.

Requirements from diverse systems and technologies are interfaced by external teams to enable cohesive maritime solutions.

The whole perception and planning stack is covered by implementation and architecture work to ensure and reliable autonomy.

Effective system integration and testing across maritime platforms are ensured through cross-functional collaboration with software, mechanical, and systems engineers.

Requirements

The posting states a pay range of $254000 to $336000.

A Bachelor's degree in Robotics, Mechatronics, Computer Science, Engineering, a relevant field, or equivalent experience.

Proficiency in C++ and/or Python software development for complex systems is required.

Familiarity with autonomous vehicle hardware and sensors such as radar, sonar, LIDAR, and cameras.

Knowledge of computer vision, sensor fusion, SLAM, motion planning, or machine learning is required.

Senior perception or planning experience for robotic systems in maritime, ground, air, or space domains is required.

The ability to act as the technical owner for a system includes stakeholder engagement, requirements definition, roadmap management, team coordination, design, implementation, sustainment, and evolution.

validation and verification strategies for perception and planning modules are defined and implemented in collaboration with stakeholders.

Team cohesion and capability are built through individual growth and mentoring of junior team members.

An active U.S. Secret security clearance must be obtainable and maintainable.

Practical notes

This role requires U.S. Secret security clearance.

Travel to customer sites may occur up to 20% of the time.

You will work within a multidisciplinary team across software, systems, and maritime operations.

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

Anduril builds defense technology that transforms military capabilities through advanced autonomy and AI.

The role uses computer vision, sensor fusion, machine learning, and simulation tools to enable maritime autonomy.

This is a staff-level position with significant ownership of end-to-end outcomes and mentorship responsibilities.

Work focuses on real-world mission-critical systems for national defense in maritime environments.

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.