> Markdown version of [/jobs/ext/2282604-senior-principal-systems-architect](https://www.wearedevelopers.com/jobs/ext/2282604-senior-principal-systems-architect). 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). --- # Senior Principal Systems Architect - **Company:** Northrop Grumman - **Location:** Baltimore, MD, United States - **Experience:** Expert - **Salary:** $135,800.0 - $203,600.0 - **Contract:** Permanent contract - **Skills:** Adobe InDesign, Systems Engineering, Firmware, IBM Rational Software, SAP (Applications), Software Requirements Analysis, Systems Modeling Language, Systems Architecture, SC Clearance, Hardware Infrastructure - **Published:** August 28, 2026 - **Apply:** https://www.juju.com/job/00000000gpg5lx ## About the Role + Bachelor's Degree with 8 years of experience, a master's degree with 6 years of experience, or a PhD with 4 years of experience in Science, Technology, Engineering, Mathematics or related technical fields; an additional 4 years may be considered in lieu of a degree. + U.S Citizenship is required. + A current/active U.S Government Secret Clearance. + Ability to obtain Special Program Access (SAP). + Experience decomposing CONOPs to CONEMP and derived requirements + Experience creating, evolving and maintaining system architectures. + Demonstrated proficiency in analytical thinking and problem-solving skills. + Experience in creating and delivering technical presentations to internal and external leadership. + Experience working collaboratively on complex projects that encompass hardware, software, and firmware. Preferred Qualifications: + Advanced degrees in Science, Technology, Engineering or Mathematics or related technical fields. + Active U.S Government Top Secret Clearance or higher. + Understanding the RF impacts of different hardware components on the system level performance to include executing trades, analysis of alternatives, SWAP impacts + Experience in all aspects of the engineering process from proposal / requirements analysis through verification testing and fielding of systems. + Experience in Design, Architecture development, Analysis, Systems Engineering, Integration and/or Test in one or more of the following specialty areas: EOIR systems, optics, threat analysis. + Experience decomposing requirements for DoD-based platforms or systems + Experience defining Concept of Operations (ConOps), KPPs, and associated Technical Performance Measures (TPMs), Operational Concepts (OpsCon). + Experience collaborating across programs and product lines. + Demonstrated expertise in SysML modeling and MBSE tools (e.g., IBM Rational DOORS, Enterprise Architect, Cameo). Ability to develop and maintain system models, traceability matrices, and verification cross reference artifacts. + Experience in development and Earned Value Management (EVM) of cost accounts and schedules. ## Description The Senior Principal Systems Architect will support the maturation of the system architecture and design, be responsible for creating, evolving, and maintaining the system architecture to meet operational needs while accounting for cost, schedule, and risk. This role will also tailor system requirement margins based on risk and ensure compliance with Key Performance Parameters (KPPs). In addition, the Senior Principal Systems Architect is responsible for maintaining alignment between the selected solution and relevant internal roadmaps, product lines, and common components, as applicable. + Lead and serve as the primary authority for system architecture and design + Direct, manage, and oversee the creation, evolution, and maintenance of the overall system architecture to meet operational needs + Proactively manage architectural decisions to ensure alignment with cost, schedule, and risk constraints + Lead the tailoring of system requirements margins based on risk assessments and ensure compliance with Key Performance Parameters (KPPs) + Manage and maintain alignment between the selected solution and internal roadmaps, product lines, and/or common components, as applicable ## Related Videos - [Playing Pong on a shoulder press machine](https://www.wearedevelopers.com/videos/100140-playing-pong-on-a-shoulder-press-machine) - [We (don't) need a software architect!?!](https://www.wearedevelopers.com/videos/663-we-don-t-need-a-software-architect) - [Modern software architectures](https://www.wearedevelopers.com/videos/1684-modern-software-architectures) - [Agent Smith Gets Hardware: Autonomous IoT Hacking From Debug Port to Cloud API](https://www.wearedevelopers.com/videos/100258-agent-smith-gets-hardware-autonomous-iot-hacking-from-debug-port-to-cloud-api) - [Grappling With Clunky Old Software? Start by Understanding What’s Inside!](https://www.wearedevelopers.com/videos/1189-grappling-with-clunky-old-software-start-by-understanding-what-s-inside) - [When Agents Meet Legacy: Never Change a Running System](https://www.wearedevelopers.com/videos/100320-when-agents-meet-legacy-never-change-a-running-system) ## Related Articles - [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) - [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) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [Why Attend a Developer Event in 2026?](https://www.wearedevelopers.com/magazine/688-why-attend-a-developer-event-in-2026) - [7 Important Tips That Every Software Developer Should Know](https://www.wearedevelopers.com/magazine/101-7-important-tips-that-every-software-developer-should-know)