Principal Software Engineer

US Citizenship is required.
Candidate must have the ability to obtain and maintain a Secret Security Clearance.Job Responsibilities

Mentors less experienced software test engineers to help develop their software test capabilities and troubleshooting and problem‑solving skills. Collaborates across other engineering disciplines such as Mechanical, Electrical, Controls, and Systems. Ensures that the technical approach is consistent with established engineering principles and practices. Ensures that product outcomes meet customer needs and that customer and company technical, system, performance, process, and quality requirements are met.

Oversee the associated software engineering efforts, including estimating, planning, requirements analysis, architecture, design, implementation, unit testing, hardware/software integration, integration testing, simulated flyout testing, and testing at the range.

Monitor and control the execution of software engineering efforts with appropriate corrective actions as needed to keep the efforts on track with responsibility for technical, cost, and schedule performance. Support the software verification lead in areas to include software verification planning, software verification environment concepting/design, and the development, execution, debugging and review of software verification test scripts and procedures. Ensure that your team supports Software Quality Assurance and Software Configuration Management audits and activities.

Coordinate with Safety Engineering organization to ensure that software requirements development and software safety efforts are completed and recorded accurately and in a timely manner to correctly drive software‑level rigor requirements for software architecture, design, implementation, integration, and verification work products associated with safety‑related or safety‑critical software requirements.

Achieve on‑time delivery of contract deliverables with acceptable quality and 90%+ first pass customer acceptance. Ensure that your project team executes with appropriate process discipline and rigor in accordance with tailored Business Management System (BMS) Procedures, as tailored by your software IPT Lead and approved by functional management.

Oversee Control Account(s) or Work Package(s) as assigned, overseeing tasks, monitoring and reporting progress, and taking corrective action as needed to meet cost, quality, performance, and schedule constraints. Provide periodic estimates at complete (EAC) as required to support the EVMS reporting for each contract or work directive assigned to you. Plan the software project schedules and builds in support of product‑level development schedules.

Work with your software IPT lead and PEM(s) to plan formal software development milestone reviews with United States Government (USG) customer representatives, including System/Software Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR) and Test Readiness Review (TRR). Establish a work‑split with your software IPT Lead for developing and presenting the software engineering content for these milestone events.

Evaluate software requirements to ensure that they are consistent with higher‑level performance requirements, customer requirements, and the statement of work or other applicable contractual documents. Coordinate development work with the software Architect and evaluate designs to ensure technical outcomes are consistent with customer needs and established requirements. Software leads are responsible for ensuring the involvement of Software Functional Management and the Munitions Software Architect in reviewing and approving software architecture and significant design work.

Guide the project team in collaborative problem solving, involving relevant stakeholders, to include software architecture representation as appropriate.

Work collaboratively to resolve conflicts between subsystems or disciplines to the benefit of system performance, quality, reliability, and cost. Plan and ensure appropriate engagement of stakeholders in the activities of the software projects, referencing the project's stakeholder matrix and…