CHAOS Industries · posted · checked
Principal Systems Engineer, System Architecture
$233k – $320kOn-site · United StatesStaff+
Who can apply
On-site · United States
Location: El Segundo, California, United States
CHAOS Industries is redefining modern defense with a multi-product portfolio that gives the ultimate advantage: domain dominance. The company's products are powered by Coherent Distributed Networks (CDN™), empowering warfighters, commercial air operators, and border protection teams to act faster, adapt rapidly, and stay ahead of evolving threats.
CHAOS Industries was founded in 2022 and has raised a total of $1 billion in funding from leading investors, including 8VC, Accel, and Valor Equity Partners. The company is headquartered in Los Angeles, with offices in Washington, D.C., San Francisco, San Diego, Seattle, and London. For more information, please visit www.chaosinc.com.
Role Overview:
CHAOS Aeronautics is designing a long-range, modular, uncrewed aircraft under a government prototype agreement. We are seeking a Principal Systems Engineer to lead the system architecture for that aircraft: the system definition and decomposition, the functional decomposition and the allocation of functions to hardware, software and firmware, and the interface architecture that lets a mission module be replaced without requalifying the aircraft around it.
You will set the technical direction for the systems engineering and modeling work performed by specialist subcontractors, hold it to a standard you define, and remain accountable for the deliverables that reach the customer. You will make binding architecture decisions, and you will be the engineer who presents and defends them in technical reviews and customer forums.
Within the CHAOS Aeronautics Division, a small team carries the systems engineering for an aircraft program that a traditional prime would staff with fifty people. If “this is not my area” is part of your vocabulary, this role would not be the right fit for you. The candidate we are looking for takes full ownership of their own area, and works effectively with others to bridge the gaps between areas.
During the interview, you should be able to walk us through a system decomposition and functional allocation you owned end to end, including the boundary calls you got wrong and their impact on the downstream design. You should also be able to describe where Large Language Models (LLMs) have increased your productivity, the types of mistakes you have seen in their output, and the workflows you have organized to get the best work products from them.
Responsibilities:
Own the system of systems decomposition and definition from stakeholder needs through systems, subsystems and items in close collaboration with Subject Matter Experts (SMEs), including the rule set that requires every system boundary to be justified by the function it performs rather than by supplier, location or technology.
Lead the functional decomposition and decide the allocation of functions across flight sciences, propulsion, structures, avionics, mission systems, autonomy, software, cybersecurity and product support.