- Location
- United States · Canada
- Workplace
- Remote
- Type
- Full-time
- Department
- Engineering
- Seniority
- C-Level
- Source
- Lever
Description
As the Software Leader/Chief Engineer, you are the senior technical authority for software across Kepler’s programs and the point of technical accountability for the integrity and coherence of our flight and ground software as an integrated capability. You will provide cross-program technical leadership to ensure software is architected, developed, verified, and operated to standard. You set software technical direction, vision, and roadmap, own the reference architecture and software standards baseline, resolve the hardest cross-cutting technical problems, conduct rigorous technical reviews, and communicate clearly with engineering teams, systems and program leadership, customers, and partners.
This is a horizontal technical-authority role. You do not own program delivery, schedule, or line management, those remain with the program managers and software leads. You are the technical conscience that keeps the software portfolio coherent, sound, and mission-ready, and a force multiplier for the architects and leads already embedded on programs.
Primary Accountability
The Software Leader/Chief Engineer is accountable for the technical integrity and coherence of Kepler's software across programs. You are responsible for the soundness of software architecture, cross-program reuse and interface consistency, verification rigor, security, and the maturity of the software technical baseline. You balance capability, reliability, maintainability, schedule realism, and technical risk to ensure Kepler's software is delivered to standard and fit for purpose across every program and product line.
Authorities
- Establish the software technical direction, vision, and roadmap across programs, reviewed and approved with the Director of Software & Digital Design
- Own and approve the software architecture and standards baseline (KEDS, ECSS-E-ST-40 / Q-ST-80, NASA NRP 7150.2 heritage).
- Chair software technical decision boards, architecture reviews, and cross-program trade studies.
- Resolve cross-program and cross-discipline software technical disagreements.
- Require additional analysis, review, refactoring, or verification when software risk warrants.
- Assess software technical readiness at major program milestones (PDR, CDR, TRR-equivalent gates) and provide recommendations to the program execution team.
- Recommend acceptance of software technical risks, waivers, and deviations.
- Escalate software technical issues that threaten program or platform success.
