Model-Based Systems Engineer

Role overview Build and maintain the system model that explains how software services, deployments, hardware, networks, and partner systems fit together. You’ll work alongside software engineers to keep that model aligned with how systems are designed and delivered, and use it to support technical decisions and program work.

Responsibilities - Own the system model from initial design through ongoing development and maintenance. - Represent services, APIs, data flows, deployments, software processes, and their hardware and network interfaces. - Work with engineers to understand and model software design, testing, and release practices. - Map system architecture to partner and government reference frameworks. - Define requirements and trace them through verification. - Provide model content for design reviews, proposals, and other technical deliverables, while helping establish systems engineering practices.

Requirements - At least five years of systems engineering experience on software-intensive or networked systems, including three or more years of hands-on model-based systems engineering and end-to-end model ownership. - Expertise with SysML, preferably version 2, or a comparable modeling language, including system structure, behavior, and interfaces. - Strong understanding of software architecture, microservices, distributed systems, APIs, version control, CI/CD, and agile delivery. - Ability to model software development processes and explain technical architecture clearly to non-engineers. - Clear writing and the ability to translate user needs and desired system behavior for engineering teams.

Nice to have Experience shaping systems engineering practices in a growing organization and working with partner or government program frameworks.