ABOUT THE JOB

Anduril runs two kinds of air defense programs for the U.S. Marine Corps. The first is a counter-UAS program of record that defends Marine Corps installations in the U.S. and overseas. The second is organic counter-UAS for the Marine maneuver force across dismounted, mounted, and expeditionary formations, where the Marine Corps is selecting systems now through competitive white papers, government demonstrations, and fly-offs.

As Chief Engineer, you're the single technical authority across both. You own the architecture and technical performance of everything Anduril delivers or proposes to the Marine Corps: our own sensors and effectors, the third-party and government-furnished systems we integrate, and the networks and command and control that connect them.

The Marine Corps acquires these two kinds of capability in different ways. An installation is a sustained service, where uptime, configuration control, safety, and accreditation carry as much weight as the sensors. A Marine maneuver unit buys a system, takes it out of the box, and expects it to work without a software update in the field. That changes what counts as ready, how Anduril prices and sustains the system, and what we can responsibly promise. You keep the two models separate where they have to differ, and you build commonality across them where it holds up.

You also decide what Anduril presents to the customer as ready. Each product team owns its own product, and you own the integrated answer: what we have, which fielded systems we could integrate, what a winning solution looks like for how Marines will use it, and what isn't mature enough to show a customer yet.

WHAT YOU'LL DO

Portfolio technical authority. Serve as Chief Engineer for Air Defense's U.S. Marine Corps programs. Own system architecture, integration strategy, fielding readiness, and sustainment outcomes across the fielded installation program and the maneuver programs and pursuits. Set the technical baseline, chair design reviews, and make the technical decisions that keep schedule and engineering aligned. Exercise this authority across program engineers, product teams, and field teams who don't report to you.

Fielded baseline. Maintain the engineering baseline for a fleet deployed across many sites as it transitions to a next-generation sensor and compute configuration. Run engineering change and configuration management so hardware, software, and documentation agree at every site. Change the baseline when field evidence shows it's incomplete or wrong, and make the case for the investments the next delivery needs.

Maneuver architecture. Turn Marine Corps operational concepts for dismounted, mounted, and expeditionary counter-UAS into systems a Marine can carry, mount, or set up and trust. Design within size, weight, power, and transportability limits, and own integration onto vehicles and other platforms. Define interfaces to the command and control and effectors the Marine Corps already fields. Own the technical case through government demonstrations and fly-offs.

Technical maturity. Review what product teams and business development plan to show the customer before they show it. Give Anduril a clear account of what works today, what needs an engineering sprint, and what isn't ready, and hold customer commitments to what the engineering supports.

Field performance and recovery. Define the verification and qualification approach, and make the call on whether a configuration is ready to ship or demonstrate. When a fielded site degrades, lead the recovery under time pressure, including at overseas sites that depend on host-nation approvals and sit several time zones away. Feed what you learn back into the product so the next site doesn't repeat the failure.

Customer technical authority. Represent Anduril's engineering position to the Marine Corps program office, its test and evaluation community, and the authorities who approve safety, cybersecurity, and fielding. Bring their requirements and constraints back to Anduril, and explain engineering constraints in terms the customer can act on.

Growth. Partner with business development and program management on the technical content of pursuits, including white papers, requests for information, rough order of magnitude estimates, and proposals. Write the basis of estimate behind each one.

REQUIRED QUALIFICATIONS

• Engineering, science, or other technical degree, or equivalent practical experience
• 10+ years of systems or engineering experience, with a track record of technical ownership on fielded systems
• End-to-end technical accountability for whether a delivered system worked in an operational environment, not only for producing its design artifacts
• Ownership of the architecture, interface set, and verification approach for a program or portfolio delivered to a U.S. defense customer
• Ability to carry technical authority across teams that don't report to you, and to brief senior technical leadership and customer program leadership directly
• Ability to negotiate requirements, deviations, and acceptance with a customer's technical representatives, and to write a credible basis of estimate
• Willingness to travel up to 25% of the time, including overseas
• Eligibility to obtain and maintain an active U.S. Secret security clearance

PREFERRED QUALIFICATIONS

• Experience delivering counter-UAS, ground-based air defense, or force protection capability to the U.S. Marine Corps
• Experience running recovery at a fielded site under time pressure, working from real hardware and real data
• Experience integrating third-party and government-furnished hardware and software into a system you were accountable for
• Prior Marine Corps service, or experience in a Marine Corps program office or test and evaluation organization
• Experience fielding dismounted or vehicle-mounted systems, including platform integration and design under tight size, weight, and power limits
• Experience sustaining a system at multiple permanent installations under an availability commitment
• Configuration management and engineering change experience on a program of record, including system safety and item identification requirements
• Experience owning a system's technical case through a competitive government demonstration or fly-off
• Depth in one or more of: radar, passive RF detection and electronic warfare, electro-optical and infrared sensors, effector integration, tactical networking, or air defense command and control
• Experience fielding at overseas installations, including host-nation spectrum and site approvals