Own the product definition. Set the missions and users Tempest serves, the configurations we offer, and what each must deliver. Own the requirements. Write and maintain capability and system level requirements with threshold and objective values and measurable acceptance criteria, traced to operator needs and concepts of operations (CONOPS). Make the product call. Decide when capability, unit cost, schedule, and producibility pull against each other, with program management and engineering at the table.
Keep one source of truth. Maintain the Tempest capability baseline and product documentation, so business development (BD), capture, and customers work from the same facts.
Roadmap and business case
Own the roadmap. Decide which configurations, payloads, and capabilities come next, and why. Tie each choice to customer demand, funding signals, acquisition timelines, and technology readiness. Build the business case. Justify new configurations and major investments, and provide product input to pricing. Know the competition. Track competing systems and turn what you learn into positioning and roadmap decisions.
Validation, test, and delivery
Define done. Set the acceptance criteria and operational validation for each release that prove Tempest meets operator expectations, not only the specification. Shape the test plan. Work with engineering and flight test so ground test, flight test, and demonstrations validate the requirements that matter most. Be at the tests and read the data. Make the readiness call. Decide when each release is ready for a customer from a product standpoint.
Program management owns the delivery schedule and execution. Weigh the operator experience. Factor setup time, training burden, maintainability, and field repair with xCell into every decision.
Customers and field feedback
Be the voice of the operator. Spend regular time with military operators, program offices, and allied and partner users to understand their missions, constraints, and buying paths. Own the feedback loop. Gather field feedback with our Mission Success Team, define the metrics that show how Tempest performs in the field, and turn what you learn into requirement and roadmap changes. Support the win. Give BD and capture the technical content, demonstrations, customer briefings, and white papers they need. Communicate clearly. Share product decisions, risks, and status with leadership, engineering, and customers.
Required Qualifications
Experience. 7+ years in product management, systems engineering, program management, or engineering roles on hardware or electromechanical systems, including at least 3 years owning a product's definition, requirements, or roadmap. Hardware delivered. You have taken a hardware product from development through test and customer acceptance into production or fielding. Requirements and test. You have written requirements with measurable acceptance criteria and used test results to decide whether a product was ready.
Industry. Experience in defense, aerospace, or another regulated hardware industry. Technical fluency. You can read a system architecture, follow a performance trade across weight, power, range, endurance, and payload, and understand why a change is hard. User focus. A record of gathering needs directly from end users and turning them into product decisions. Communication. Clear, concise writing and briefing. You can explain a trade to an operator, a program office, and an engineer.
Education. Bachelor's degree, or equivalent practical experience. Eligibility. U.S. citizenship and the ability to obtain and maintain a Department of Defense (DoD) security clearance.