> Markdown version of [/jobs/ext/2142062-sr-principal-systems-engineer](https://www.wearedevelopers.com/jobs/ext/2142062-sr-principal-systems-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Sr. Principal Systems Engineer - **Company:** Northrop Grumman - **Location:** Melbourne, FL, United States - **Experience:** Expert - **Salary:** $122,800.0 - $184,200.0 - **Contract:** Permanent contract - **Skills:** Systems Engineering, Configuration Management, Computer Engineering, Software Design Documents, Requirements Traceability, Systems Modeling Language, Systems Architecture, Infrastructure Automation Frameworks, Information Technology - **Published:** August 20, 2026 - **Apply:** https://www.juju.com/job/00000000go1682 ## About the Role * Bachelor's degree in Systems Engineering, Electrical Engineering, Computer Engineering, Computer Science, or related STEM discipline with 9 years of experience OR at least 7 years with Master's Degree OR at least 4 years with PhD * Significant professional experience in systems engineering across the development lifecycle (requirements analysis, architecture/design, integration, verification & validation) * Hands-on experience with Model-Based Systems Engineering (MBSE) practices, such as developing and maintaining SysML-based models, and using Cameo for system architecture, behavior, and interface modeling * Demonstrated experience preparing for and executing Systems Engineering Technical Review (SETR) events such as SFR, PDR, and/or CDR, including development of technical artifacts and presenting to internal and customer stakeholders * Strong technical writing and verbal communication skills, with the ability to convey complex model-based and architectural concepts to diverse audiences * Ability to work onsite as required to support lab activities, reviews, and team collaboration * Experience managing suppliers' adherence to requirements and developing RTGs if/when supplier performance requires it * Must possess an active DoD Secret clearance that is in scope and have the ability to obtain and maintain a DoD Top Secret clearance Preferred Qualifications * Master's degree in Systems Engineering or related STEM field * Direct experience applying MBSE to training systems, simulators, or mission rehearsal/training environments (e.g., VR/AR trainers, cockpit trainers, maintenance trainers) * Prior lead or principal role in major SETR events (PDR, CDR, TRR), with responsibility for the model-based technical baseline and closure of review action items * Advanced proficiency with Cameo, including profile customization, automated checks, report/document generation, and integration with requirements or configuration management tools * Demonstrated track record of driving technical risk identification and mitigation, and maintaining configuration control of system models, requirements, and design artifacts * Experience working with NAVAIR requirements, processes, and standards, including interpreting, tailoring, and implementing NAVAIR requirements within system architectures and training system designs. ## Description Northrop Grumman is seeking a Sr. Principal Systems Engineer (Level 4) to support our training systems engineering development team with a strong emphasis on Model-Based Systems Engineering (MBSE). The selected candidate will own key elements of the training system architecture and requirements, leverage SysML and Cameo to develop and maintain system models, and help lead the team through major Systems Engineering Technical Review (SETR) events, including Training PDR TIMs, PDR, and CDR. This position is located in Melbourne, FL. This role will be responsible for developing and maturing training system specifications, requirements traceability, and design documentation, as well as coordinating with internal and supplier teams to deliver a robust technical baseline that meets customer needs. Responsibilities * Support Training PDR Technical Interchange Meetings (TIMs), including agenda preparation, government coordination/approval, and documentation of minutes, risks, issues, and actions * Plan, prepare, and execute Training SETR and associated review events, ensuring clear entry/exit criteria and closure of action items * Develop and mature the training system architecture and requirements to PDR-level maturity, including post-SFR gap assessment, functional decomposition, and allocated baseline definition * Integrate supplier subsystem specifications and models into the overall training system/weapon system architecture; validate logical decomposition, interfaces, and requirements traceability * Update and mature system/software design documents (SSDDs) and other element-level design artifacts to support Trainer SETR event and subsequent reviews * Support Trainer SETR events across VR, panel, hardware, and operational trainer devices, ensuring consistency with the technical baseline and customer expectations * Incorporate SETR event outcomes (RFAs and review comments) into updated requirements, architecture, and Cameo models; manage burn-down plans and coordinate submittal of updated baselines * Coordinate with supplier engineering teams to review and refine trainer subsystem specifications and models, provide clear technical feedback, adjudicate comments, and ensure supplier deliverables align with the system architecture, requirements, and program review milestones. ## Related Videos - [Model Based Systems Engineering in an Agile Product Development Process](https://www.wearedevelopers.com/videos/68-model-based-systems-engineering-in-an-agile-product-development-process) - [Swapping a Data Warehouse at Runtime: Zero-Downtime Migration Without Changing a Single Client](https://www.wearedevelopers.com/videos/100311-swapping-a-data-warehouse-at-runtime-zero-downtime-migration-without-changing-a-single-client) - [The QUEST for Better Software](https://www.wearedevelopers.com/videos/721-the-quest-for-better-software) - [Why Your Best Mediors Never Become Seniors (And How to Fix It)](https://www.wearedevelopers.com/videos/2108-why-your-best-mediors-never-become-seniors-and-how-to-fix-it) - [Automated Driving - Why is it so hard to introduce](https://www.wearedevelopers.com/videos/628-automated-driving-why-is-it-so-hard-to-introduce) - [Agentic AI: building autonomous systems for developers](https://www.wearedevelopers.com/videos/100034-agentic-ai-building-autonomous-systems-for-developers) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Résumé-Driven Development: How IT trends affect the job market for software developers](https://www.wearedevelopers.com/magazine/59-resume-driven-development-how-it-trends-affect-the-job-market-for-software-developers) - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering) - [What’s the Difference between a Junior, Mid, and Senior Developer?](https://www.wearedevelopers.com/magazine/238-what-s-the-difference-between-a-junior-mid-and-senior-developer) - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated)