Software Engineer, Product

Amca is building America’s new industrial base. Since the 1990s, our ability to build new aviation and military systems and maintain the ones we already have has eroded. Today, the gap between what the nation needs to produce and what it is capable of producing is the largest it has been in generations.

To help close that gap, Amca rapidly develops and manufactures new critical components and subsystems required to build and sustain the planes, military vehicles, and core infrastructure America needs. Today, we operate seven factories nationwide, including our advanced prototyping and testing headquarters in El Segundo, and deliver avionics, hydraulic, and electrical components for platforms such as the F-35, F-16, F/A-18, 737

MAX, 787, A320neo, A321, Mk-48, and M1 Abrams.

The Product Software Engineer role is an extreme ownership role and responsible for identifying where Amca moves more slowly than it should and building the software that resolves it. You will embed directly with teams at headquarters and across our factories nationwide, spending meaningful time on the floor to understand how the work actually gets done before deciding what to build.

This is a hybrid of product management, software engineering, and design. You will identify the problem, evaluate whether it is worth solving, design the solution, build it, put it in front of the people who will use it, and remain with it until it is working in practice. Some of what you build will be an exploratory prototype that answers a question within a few days and is then set aside, which is a successful outcome in its own right.

You will work directly with production, quality, planning, supply chain, and engineering teams across our sites, building tools that fit the way those teams already work and that measurably improve throughput, quality, or lead time.

• Embed with teams at headquarters and at our factory sites, spending sufficient time observing operations firsthand to identify where the actual constraints are.
• Identify the problems worth solving by interviewing operators, quality, planning, supply chain, and engineering, and quantify the cost of the current process before proposing to replace it.
• Evaluate whether software is the appropriate solution, recognizing that some constraints are better addressed through process or workflow changes, and make that recommendation clearly.
• Own the product decision, including scope, prioritization, sequencing, and the choice of what not to build, without a product manager writing requirements for you.
• Build the solution end to end using Type Script and React on the front end and Go services with their supporting data models on the back end, and take it through to production.
• Design the interfaces yourself, producing clear and efficient experiences suited to use in a production environment.
• Move quickly from concept to working software, putting a usable version in front of users early so that their feedback can validate or redirect the approach.
• Drive adoption after launch by working alongside users, gathering feedback, and iterating until the tool is delivering measurable value.
• Determine what happens to each project once it has proven itself, hardening successful prototypes into supported products with a clear owner and deliberately retiring those that have not earned continued investment.

Here’s the corrected text:

• 4+ years shipping production full-stack software
• Production experience with Type Script and React
• Backend service and API development in a typed language, with strong data modeling instincts
• Demonstrated ownership of a project from problem discovery through deployment, adoption, and iteration, rather than working from assigned tickets
• Genuine comfort working directly with non-technical users, including on a factory floor
• Willingness to travel to Amca factory sites across the United States as needed

• Some form of full-stack experience (Typescript, React, Go, Python, SQL)
• Experience in manufacturing, logistics, supply chain, field operations, or another operations-heavy domain
• Strong design sense, with the ability to produce a…