Engineering Roles
Model-Based Systems Engineer
In this role, you’ll treat the system itself as the artifact. You’ll build and own the model-based representation of a mission system—requirements, architecture, interfaces, and behavior captured in a live digital model rather than scattered across documents. Practiced with the rigor of software engineering, that model is what keeps hardware, algorithms, and software converging on one coherent design.
The Work
You’ll formalize how a mission system behaves before anyone commits it to hardware or code. You’ll author SysML models in tools like Cameo or Rhapsody, decompose mission needs into requirements and interfaces, and run trade studies and model-based analyses that expose risk while it is still cheap to fix. Your toolkit spans systems modeling languages, requirements management, interface control, and enough scripting in Python or model APIs to keep the model connected to the engineering data around it. When a requirement shifts or a subsystem changes, you’ll trace the impact through the model and tell the team what it costs.
You’ll work across the whole lifecycle: capturing mission requirements with the customer, defining the architecture and the hardware that the software team builds against, and maintaining the digital thread from concept through verification. Some of your work is up-front design; some is keeping the model accurate when the as-built system diverges from the plan.
You’ll work across the whole lifecycle: capturing mission requirements with the customer, defining the architecture and the hardware that the software team builds against, and maintaining the digital thread from concept through verification. Some of your work is up-front design; some is keeping the model accurate when the as-built system diverges from the plan.
Who You Work With
You sit at the center of a mission system, working with the RF, hardware, algorithm, and software engineers whose subsystems your model integrates, and with program managers and customers who depend on your architecture to scope and verify the work. You’re the engineer who holds the whole system in view, so when two subsystems disagree at an interface, you’re where it gets resolved.
What We Look For
Systems engineering experience with model-based methods and fluency in SysML and a modeling tool (Cameo, Rhapsody, or equivalent), command of requirements decomposition, interface definition, and verification, and enough software skill to script against model data; experience on complex hardware/software mission systems is valued.
Open Positions
Ready to find your place?
Browse every open position for this role across all capability areas and all U.S. locations.
