Principal Systems Engineer / Systems Architect – Modular Weapons GRA

KBR•Eglin Air Force Base, FL

10d•Onsite

About The Position

KBR is seeking a highly experienced Principal Systems Engineer and Modular Systems Architect to support a U.S. Government organization advancing the Weapons Government Reference Architecture (GRA) and Weapons Open Systems Architecture (WOSA) for conventional weapon systems. The role will help turn the existing architecture into an actionable, Government-owned framework that expands the industrial base and supplier competition, enables nontraditional and component-level suppliers to participate, accelerates technology insertion, reduces reliance on closed or vertically integrated solutions, lowers redesign and integration costs, and supports scalable production across weapon systems. The position leads systems architecture and Model-Based Systems Engineering (MBSE) efforts to define physical parameters, interfaces, constraints, attributes, and model-based severable data packages. It will refine and extend architecture domains and products for application across current and future Air Force conventional weapon programs, supporting reuse and repeatable integration of qualified subsystem solutions while maintaining system-level integrity and Government control of critical interfaces and data. The architect will develop and assess models, interface definitions, reusable libraries, reference patterns, and data-package approaches; connect technical decisions to acquisition and industrial-base outcomes; and coordinate with Government program offices, technical authorities, digital engineering teams, test organizations, acquisition stakeholders, and industry. The role is on-site at Eglin AFB, Florida, with low travel and a standard work schedule with core hours from 0900 to 1500. The position requires an active Secret clearance. KBR states that its Mission Technology Solutions business is expected to spin off as Trinzic in January 2027. Employees who join that business before the spin-off will transition to Trinzic when the separation is complete and will not need to reapply.

Requirements

Bachelor’s degree in Systems Engineering, Aerospace Engineering, Mechanical Engineering, Electrical Engineering, Computer Engineering, or a related technical field.
15 or more years of progressively responsible experience in systems engineering, system architecture, digital engineering, MBSE, open systems architecture, weapon-system development, or closely related defense or aerospace domains.
Extensive hands-on experience applying MBSE principles and methodologies to complex DoW/DoD aerospace, missile, munition, or weapon systems.
Experience developing model-based severable data packages, modular technical data packages, interface-control models, reusable architecture libraries, or reference implementations.
Expert practical proficiency using SysML to develop, manage, analyze, and communicate system architectures, requirements relationships, interfaces, and model-based technical baselines.
Experience with both SysML v1 and SysML v2.
Experience translating physical constraints, mechanical and electrical interfaces, environmental conditions, form and fit considerations, modularity parameters, and verification needs into rigorous system models that support competitive acquisition and subsystem integration.
Strong understanding of requirements development, functional decomposition, logical and physical architecture, interface management, configuration management, verification planning, and technical baseline control.
Ability to independently lead complex architecture and MBSE efforts, connect technical architecture choices to acquisition and industrial-base outcomes, and develop executable recommendations for Government decision-makers.
Exceptional ability to communicate complex engineering concepts to senior leaders and conduct detailed technical discussions with Government and industry engineers.
Active Secret clearance.

Nice To Haves

20 or more years of systems engineering, weapon-system architecture, MBSE, modular open systems, digital engineering, or advanced aerospace and defense engineering experience.
Advanced degree in a relevant engineering discipline.
Direct experience with Weapons GRA, WOSA, or other DoW/DoD weapon-system reference architectures.
Demonstrated experience developing or applying Government Reference Architectures, open systems architectures, modular open systems approaches, or comparable frameworks to improve competition, supplier access, technology insertion, affordability, or production flexibility.
Experience connecting architecture decisions to industrial-base expansion, supplier interchangeability, second-source qualification, technology insertion, reduced non-recurring engineering, lower integration cost, production scalability, upgradeability, and rapid capability integration.
Prior support to a Government program office, System Program Office, chief engineer, digital engineering organization, defense prime, or weapon-system integrator.
INCOSE CSEP or ESEP certification.
OMG OCSMP certification at the Model Builder level or higher.
DAWIA Engineering certification at the Practitioner or Advanced level, or comparable Program Management certification.
Active Top Secret clearance or TS/SCI eligibility.

Responsibilities

Serve as the principal systems engineer and architect for evolving the Weapons GRA and WOSA into an implementable framework supporting industrial-base expansion, supplier competition, technology insertion, affordability, production scalability, and Government control of critical technical interfaces and data.
Communicate architecture, interface, SysML, and MBSE concepts to Government and industry engineers, and explain technical approaches, tradeoffs, risks, and value to senior leaders and non-specialist stakeholders.
Architect and lead MBSE efforts defining physical parameters, interfaces, constraints, attributes, and model-based severable data packages.
Augment and refine the Weapons GRA framework for application across current and future Air Force conventional weapon programs, reducing program-unique design, increasing reuse, and enabling repeatable integration of qualified subsystem solutions.
Extend established WOSA domains to address parameters, constraints, interface characteristics, form-factor considerations, environmental conditions, and other attributes needed to govern physical modularity.
Define the structure, content, technical requirements, configuration controls, intellectual-property boundaries, and acceptance criteria for model-based severable data packages.
Develop architecture viewpoints, system models, interface definitions, requirements relationships, reusable model libraries, and reference patterns that provide supplier entry points while protecting system-level integration integrity.
Use SysML and MBSE methods to maintain traceability among mission needs, requirements, logical and physical architecture, interfaces, verification methods, and production considerations.
Evaluate how modular physical interfaces and severable data packages can support rapid insertion and competition of weapon subsystem solutions from traditional and nontraditional suppliers.
Identify architecture decisions and interface standards that reduce redesign, non-recurring engineering, integration time, qualification burden, supplier lock-in, production disruption, and total weapon-system cost.
Define architecture and data-package approaches that allow independent competition of domain solutions where appropriate without compromising weapon-level safety, performance, cybersecurity, airworthiness, or integration responsibility.
Identify common interfaces and reusable architecture products that could attract suppliers, justify private investment, and improve the business case for innovative technologies and expanded manufacturing capacity.
Evaluate tradeoffs between standardization and mission-specific optimization to improve competition, affordability, and production flexibility without imposing unnecessary performance penalties or constraining future innovation.
Define proof-of-concept efforts to test whether model-based severable data packages and physically modular domain solutions can reduce integration time and cost, enable supplier substitution, and support production scaling without unacceptable performance or qualification risk.
Assess architectures and models for completeness, consistency, interoperability, configuration integrity, usability, extensibility, affordability implications, supplier accessibility, and alignment with Government open-systems and industrial-base objectives.
Coordinate with Government program offices, technical authorities, digital engineering teams, test organizations, acquisition stakeholders, and industry partners.
Lead or support architecture reviews, model reviews, interface working groups, design reviews, and technical interchange meetings.
Deliver incremental architecture releases and demonstrate improvements in technical clarity, supplier accessibility, modularity, competition, integration speed, affordability, or production scalability.
Deliver a final release package at the end of the period of performance, including documentation, examples, and a reference implementation to support future Government modeling efforts.