Technical authority for the region. Serve as Chief Engineer for Air Defense's Middle East programs. Own system architecture, integration strategy, fielding readiness, and sustainment outcomes across every program in the portfolio. Set the technical baseline, chair design reviews, and make the technical decisions that keep schedules aligned with the engineering. Exercise this authority across engineers who don't report to you.
Integration across systems you do not own. Middle East programs integrate coalition hardware. Define interfaces to partner radars and effectors, customer-furnished equipment, legacy command and control being displaced, and third-party systems the customer has already bought. Much of the integration scope arrives underspecified. Negotiate it directly with partner vendors and government program offices, then give Anduril a clear account of what integrates cleanly, what requires an engineering sprint, and what isn't technically ready.
Foreign sales engineering. Direct commercial sales and foreign military sales create engineering requirements beyond those of domestic programs, including releasability and export posture, in-country localization and production content, sustainment concepts measured in years rather than task orders, and technical terms negotiated into the contract before design begins. Own the engineering position in those negotiations and write the basis of estimate that supports it.
Field operations and recovery. Deploy to the region, work alongside operators and field service teams, and own technical performance in the field. When a fielded site degrades, lead the recovery under time pressure and across a time zone gap, then feed what you learn back into the product to prevent the same failure at the next site.
Customer technical authority. Represent Anduril's engineering position to partner nation ministries, program offices, primes, and authorization authorities. Bring their requirements and constraints back to Anduril. Translate customer-stated operational requirements into executable technical plans, and explain engineering constraints in terms a customer can act on.
Growth. Shape the technical content of pursuits as the regional pipeline expands faster than the delivered baseline. Write credible estimates and flag any commitment that the engineering can't support.